Orders upload - Sage 100
For Sage 100, the import mechanism requires the installation of Visual Integrator to function. Please ensure this is working before trying the instructions below.
To import an SIA order file into Sage 100, either:
the Import Job has to be created
or a template file can be imported using Visual Integrator
Steps to import a template file
The name of the import job template file is called SIA_PO_IMPORT_V45.EXP – this file can be found in the ..\scripts folder on the server where Sage Inventory Advisor is installed.
Open the Visual Integrator module within Sage 100 and select Job Import
Locate the SIA_PO_IMPORT_V45.EXP file:
Click OK to “Imported Jobs must be compiled before use”
The job has now been installed and can be edited or maintained by selecting Visual Integrator – Main menu – Import Job Maintenance
Search for the “SIA PUR ORDERS” job and click on “Accept” – the Import Job Maintenance screen will appear for the company currently active
On the “1. Configuration” tab, ensure that the Import File path is correctly setup by browsing for the repco.csv in the from_netstock folder on the server
Select the “2. Data” tab to verify the fields to be imported, if necessary
The “4. Record” tab is to edit the Header and Line row identifier records, if necessary
After reviewing each of the tabs, select “Accept” to finalize the setup of the purchase order import
Select “Yes” to execute the job
To test that the import has been configured correctly, click on “Test”. If no errors are seen then all is well
To import the purchase orders and create them in Sage 100, click on “Accept”
NOTE: please contact your Sage Inventory Advisor implementor to complete the activation of this upload format in Sage Inventory Advisor.
Order file format
|1||H.HeaderLine||Character indicating the HeaderLine. Default to an H. Can be anything although suggest against using special characters.|
|2||H.PurchaseOrderNo||SIA generated unique order reference number. Either this number can be used as the PO number, or the Purchase Order module 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||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. Default value to a zero for now.|
|8||H.Comment||The user who created the order as displayed in the SIA PO summary.|
|1||L.LineHeader||Character indicating the Line Detail Lines. Default to an L. Use same character “L” for each line detail row. 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 for just in case we need an extra line field one day. Default value to a zero for now.|
|9||L.CommentText||Comments entered against the recommended order in SIA.|
File layout example
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 ..."
L,6656,000,EACH,123.45,101,2012/12/15,0,"this is comment1 ..."