If, for your organization, you are handling writing of StockIQ order suggestions into your ERP from data published by StockIQ, the following provides some guidelines and information on how to do this.
The most common scenario is that StockIQ will publish pipe-delimited text files to a standard location each time the users place an order. A database output is also available that uses identical columns and fields to the text files.
- The format and values used by the StockIQ order files is in the StockIQ Interface spec document.
- dato.SupplyOrder - represents the order header, e.g. the PO header, Transfer header, etc.
- dato.SupplyOrderLine - contains data for the individual lines, e.g. the PO line detail, such as the item ordered, quantity ordered, etc.
- For each order, there will be a pair of files produced
- <OrderNumber>_Header.txt - contains the header information, in the dato.SupplyOrder format. (this file is always 1 line)
- <OrderNumber>_Lines.txt - contains the line details, the dato.SupplyOrderLine format. This file will have 1 to N lines in it.
- In an on-premise installation where you are hosting your StockIQ instance, the files will be written directly to your StockIQ application server, located at a path similar to: C:\StockIQ\Instances\<CompanyName>-Prod\Orders\1\
- In a cloud installation where StockIQ is remote to your network, the files will most often be published to your FTP site in the /orders/1/ directory.
- We recommend that you delete the files from disk or the FTP site after you have processed them into your ERP, or at least rename or move them into an archive folder. StockIQ maintains all data to reproduce these files internally if you need to re-sync them later for some reason.
- The same file formats are used for PO, Transfer and Work Order supply orders. The type of order is defined in the dato.SupplyOrder.SupplyType field.
- We recommend placing a test PO, Transfer, and/or workorder through StockIQ to get a sense of what the files look like, and to test your integration logic as part of the implementation project. Your StockIQ implementer can help you create this test order.
- Additionally, your StockIQ implementer should set a "TST" prefix on all order number sets so the PO is easily identifiable as a test, and can be deleted later from your system.