Is anything written to Netsis?

No. The connector reads from views and procedures installed in a vidistock schema in the Netsis database, and its SQL user has permission only on that schema. Netsis tables are not accessed directly and no record is changed.

Are sales read from invoices or delivery notes?

You decide during setup. Sales are read from the sales object (a view or a procedure); the sample script reads sales invoices, and to read delivery notes you change the document type in the object.

We have several branches. Can we read only one?

Yes. A branch filter is added to the sales object, so only that branch's transactions are read. Warehouses are also mapped one by one; data of an unmapped warehouse is not read.

How do foreign-currency purchase orders appear?

The currency type and foreign price on the order line are read; the order appears in VidiStock in the same currency.

How mature is the connection?

It is in beta. It was tested against a Netsis test database; validation in real customer installations is ongoing. In the first installation we compare the figures with your Netsis reports together.

Demand forecasting and order suggestions for Netsis

VidiStock reads products, sales, stock and purchase orders from the Netsis database read-only and produces a demand forecast, safety stock and order suggestion for every product and warehouse.

Netsis keeps your stock and account records; but answering “what should I order, for which warehouse, when and how much?” requires turning past sales into a forecast and accounting for lead time and uncertainty. VidiStock does this calculation with your Netsis data for every product and warehouse.

Which data is read from Netsis?

Data is read from views or procedures installed in a vidistock schema in the Netsis database; the connector has no permission on the Netsis tables. The sample scripts read the tables below and are adapted during setup to how the company uses Netsis.

Data	Netsis table in the sample script
Product cards, group, preferred supplier, cost	`TBLSTSABIT`, `TBLSTGRUP`, `TBLCASABIT`
Sales and return transactions (day, warehouse, customer)	`TBLSTHAR`
Purchase orders and goods receipts (with warehouse and currency type)	`TBLSIPATRA`, `TBLSIPAMAS`, `TBLSTHAR`
Inter-warehouse transfers (outgoing and incoming on the same slip; beta)	`TBLSTHAR`
Warehouse balances	`TBLSTOKPH`
Warehouses	`TBLSTOKDP`

Product attributes (such as brand or sales channel) are extra columns of the products object; the sample script includes KOD_1 and KOD_2 from TBLSTSABIT. A multi-valued field is read as comma-separated tags.

Setup

In VidiStock, on Administration → Integrations, choose Netsis and generate a connector key.
Install the VidiStock Connector on a Windows computer that can reach the Netsis database and enter the key.
Download the sample scripts from the Integrations page and run them in the Netsis database: they create the vidistock schema, a SQL user with permission only on that schema, and the reading objects. Adapt the sales source (invoice or delivery note), branch filter and campaign mark in the objects to the company.
Enter the SQL Server address, the database name and this user; choose a view or a procedure for each data type, then choose Save and test connection. The test checks the objects, columns and permissions.
Set the history start (at least two years recommended) and the warehouse mapping.
Choose the schedule and enable it. The first synchronisation reads the history; later ones refresh only the last days.

What is calculated from Netsis data?

For every product and warehouse:

Demand forecast: from past sales, with a method suited to the product’s demand pattern (a steadily selling product and a rarely selling spare part are forecast differently).
Safety stock: from the forecast error and lead time variability, for the service level you choose.
Reorder point and order suggestion: after deducting stock on hand and open orders; rounded to the minimum order quantity and case size.

Example: for a product that sells 10 units a day on average with a 14-day lead time, the forecast error and lead time variability give a safety stock of 83 units and a reorder point of 223 units; since the 150 units on hand are below this point, an order of 700 units is suggested. Every step is in the How to calculate safety stock guide.

Good to know

The connection is in beta. After the first synchronisation, compare last month’s sales and warehouse balance of a few products with your Netsis report.
If the stock card has no currency columns, the currency columns are removed from the products object and prices are read in Turkish lira.
VidiStock does not transfer orders to Netsis; you export the suggestion list to Excel and create the order in Netsis.

Detailed setup: ERP integration.