Quick Summary: Netstock can export purchase and transfer orders in a format compatible with Sage 300. Importing requires a configuration change in your Sage Inventory Advisor environment and access to the from_netstock folder on the integration server. This article explains how to import purchase orders and transfers into Sage 300 and details the file format structure.
Prerequisites
Before importing:
Ask the Netstock implementation team to configure your Sage Inventory Advisor environment for Sage 300 uploads.
Ensure you have access to the
from_netstockfolder on the server where the connector is installed.For convenience, request IT to create a mapped drive pointing to the
from_netstockfolder.
Importing Purchase Orders
In Sage 300, go to Purchase Orders > P/O Transactions > Purchase Order Entry > File > Import.
In the import dialog, set the file type to Single CSV File.
Browse to the
from_netstockfolder via the mapped drive.Select the order file to import:
Choose the file with the largest order number or the latest create date/time.
Verify the status changes from “Import not ready” to “Import Ready.”
Click OK to import the file.
Confirm the purchase order was created by viewing it in the Purchase Orders module.
Importing Transfers
In Sage 300, go to Inventory Control > I/C Transactions > Transfers > File > Import.
In the import dialog, set the file type to Single CSV File.
Browse to the
from_netstockfolder via the mapped drive.Select the transfer file to import:
Choose the file with the largest transfer number or the latest create date/time.
Verify the status changes from “Import not ready” to “Import Ready.”
Click OK to import the file.
Confirm the transfer was created by viewing it in the Transfers module.
Order File Format
Sage 300 order files include Header, Line Detail, and optional Line Comment records.
Header Detail (Indicated by RECTYPE = 1)
Position | Field Name | Description |
1 | RECTYPE | Character indicating the Purchase order Header Line. Default to an 1. |
2 | PORHSEQ | Sage 300 generated a unique order reference number. Default to 0. Not double quoted. |
3 | DATE | Date the purchase order was created as shown in the PO summary YYYYMMDD FORMAT. Not double quoted. |
4 | VDCODE | Vendor code (not description) of the supplier as displayed in the PO summary. |
5 | EXPARRIVAL | Expected Arrival Date of the purchase order on SIA recommended order. Use the average of the dates as they appear in line detail YYYYMMDD FORMAT. Not double quoted. |
6 | COMMENT | Comment for Purchase order header. Default to null for now. |
7 | REFERENCE | Contains the name of the user creating the order as it appears in the summary on the Order schedule. |
Line Detail (Indicated by RECTYPE = 2)
Position | Field Name | Description |
1 | RECTYPE | Character indicating the Purchase order Header Line. Default to an 1. |
2 | PORHSEQ | Sage 300 generated a unique order reference number. Default to 0. Not double quoted. |
3 | DATE | Date the purchase order was created as shown in the PO summary YYYYMMDD FORMAT. Not double quoted. |
4 | VDCODE | Vendor code (not description) of the supplier as displayed in the PO summary. |
5 | EXPARRIVAL | Expected Arrival Date of the purchase order on SIA recommended order. Use the average of the dates as they appear in line detail YYYYMMDD FORMAT. Not double quoted. |
6 | COMMENT | Comment for Purchase order header. Default to null for now. |
7 | REFERENCE | Contains the name of the user creating the order as it appears in the summary on the Order schedule. |
8 | UNITCOST | Amended unit cost (adjusted for Purchase Factor if greater than 0). |
9 | EXPARRIVAL | Expected arrival date (YYYYMMDD). |
Line Comment (Indicated by RECTYPE = 3)
Position | Field Name | Description |
1 | RECTYPE | Character indicating the Purchase order comment Line. Default to a 3. |
2 | PORHSEQ | Sage 300 generated a unique order reference number. Default to 0. Not double quoted. |
3 | PORCREV | Place holder. Default to 0. Not double quoted. |
4 | PORCSEC | Default to a 0. Not double quoted. |
5 | COMMENTTYP | Default to a 1. Not double quoted. |
6 | COMMENT | Comments entered against the recommended order in the SIA Order schedule. |
File Layout Example
"RECTYPE","PORHSEQ","DATE","VDCODE","EXPARRIVAL","COMMENT","REFERENCE" "RECTYPE","PORHSEQ","PORLREV","ITEMNO","LOCATION","ORDERUNIT","OQORDERED","UNITCOST","EXPARRIVAL" "RECTYPE","PORHSEQ","PORCREV","PORCSEQ","COMMENTTYP","COMMENT" 1,0,20121123,"1400",20121225,"comment for PO...","Purchase Name: Francis Lau" 2,0,1000,"A1-105/0","1","Ea.",75,3.855201,20120315 3,0,0,0,1,"Comment is 80 char long for line above" 2,0,2000,"A1-106/0","4","Ea.",150,3.847887,20120315 3,0,0,0,1,"Comment is 80 char long for line above" 1,0,20121123,"1400",20121225,"comment for PO...","Purchase Name: Buyer2" 2,0,1000,"A1-104/0","1","Ea.",75,3.855201,20121225 3,0,0,0,1,"Comment is 80 char long for line above" 2,0,2000,"A1-103/0","4","Ea.",150,3.847887,20130112 3,0,0,0,1,"Comment is 80 char long for line above"
Forget about these 👇 😞 😐 😃 Have your say here!