Quick Summary: For Sage 100, order imports require the Visual Integrator (VI) module. Netstock generates purchase order files that can be imported via VI using a pre-configured job or template. This article explains how to set up the import job, update file locations, and understand the Sage 100 order file format.
Preparing for Import
Before proceeding:
Confirm that the Visual Integrator module is installed and working in Sage 100.
Ensure the Netstock/SIA integration is correctly configured on your Windows server.
Order files appear in the from_netstock folder and must be mapped into Sage using VI.
Setting Up the Import Job
Log in to Sage 100 with valid credentials.
Navigate to Visual Integrator > Job Import.
Select the job import file from your server.
Example:
C:\sage_inventory_advisor\swstrings\scripts\SIAPurchaseOrders.exp
In the wizard, select the job for SIA PO Imports.
Click Accept and OK to add the job into Visual Integrator.
Create a blank file called
recpo.csvin the from_netstock folder.
Updating the Job
In Sage, go to Visual Integrator > Import Job Maintenance.
Locate the job SIA_PUR_ORDERS.
Change the file path for
recpo.csvto point to the correct location:Example:
C:\sage_inventory_advisor\swstrings\from_netstock\recpo.csv
Click Accept.
When prompted, select Yes to execute the job.
Confirm the import file’s location, then click Accept again.
The job will complete — if there are no records, it will report “0 processed.”
You do not need to view the job log unless errors are indicated.
Information to Provide Netstock
When setting up Sage 100 integration, you may need to supply the following to Netstock Support:
Sage Company Code
Sage User ID
Sage User Password
VI Job Number (can be seen on the top-right of the VI Job "Completed File Name)
VXXXXX (The font makes it difficult to distinguish between "1" and "I")
You should be able to copy the name
Order File Format
Orders imported into Sage 100 have a Header and Line Detail structure.
Header Fields
Position | Field Name | Description |
1 | H.HeaderLine | Character indicating the HeaderLine. Default to an H. It can be anything, although suggest against using special characters. |
2 | H.PurchaseOrderNo | SIA generated a unique order reference number. Either this number can be used as the PO number, or the Purchase Order feature within Sage can generate a PO number. |
3 | H.WarehouseCode | Warehouse/branch code (not description) as displayed in the PO summary. Duplicated in Line for flexibility. |
4 | H.VendorNo | Vendor code (not description) of the supplier as displayed in the PO summary. |
5 | H.PurchaseOrderDate | The date the purchase order was created as shown in the PO summary. Use earliest, latest, or average of due dates from line detail YYYY/MM/DD format. |
6 | H.RequiredExpireDate | Expected Arrival Date of the purchase order on SIA recommended order. Duplicated in Line for flexibility YYYY/MM/DD format. |
7 | H.Filler | A filler for just in case we need an extra header field one day. The default value set to zero for now. |
8 | H.Comment | The user who created the order as displayed in the SIA PO summary. |
Line Detail Fields
Position | Field Name | Description |
1 | L.LineHeader | Character indicating the Line Detail Lines. Default to an L. Use the same character “L” for each line detail row. It can be anything, although suggest against using special characters. |
2 | L.ItemCode | Product / SKU code |
3 | L.WarehouseCode | Warehouse/branch code (not description) as displayed in the PO summary. Duplicated in header for flexibility. |
4 | L.UnitOfMeasure | The purchasing unit of measure. Default to SIA unit of measure if not available. |
5 | L.UnitCost | Amended unit cost on SIA recommended order multiplied by the Purchase Factor if greater than 0, else multiply by 1. |
6 | L.QuantityOrdered | Amended quantity ordered on SIA recommended order multiplied by the Purchase Factor if greater than 0, else multiply by 1. Express in terms of the “PURCHASE Unit of Measure”. |
7 | L.RequiredDate | Expected Arrival Date of the item on SIA recommended order YYYY/MM/DD format. |
8 | L.Filler | A filler just in case we need an extra line field one day. The default value set to zero for now. |
9 | L.CommentText | lComments entered against the recommended order in SIA. |
File Layout Example
H,000345,000,01-CONT,2012/11/15,2012/12/15,0,ADMIN L,6655,000,EACH,123.45,101,2012/12/15,0,"this is comment1 ..." L,6652-28-24-15,000,EACH,234.45,102,2012/12/16,0,"this is comment2 ..." L,6657-24-20-12,000,EACH,345.45,103,2012/12/17,0,"this is comment3 ..." H,000346,000,01-CONT,2012/11/15,2012/12/15,0,ADMIN L,6656,000,EACH,123.45,101,2012/12/15,0,"this is comment1 ..."
Forget about these 👇 😞 😐 😃 Have your say here!