Quick Summary: Sage ERP X3 includes Import/Export templates that allow supplier orders created in Netstock (SIA) to be imported directly. This article explains how to configure the standard import template for purchase orders and the required file format structure.
Configuring the Import Template
In Sage X3, go to Setup → Usage → Import/Export Templates.
Create a new template for supplier purchase orders.
Configure the layout parameters exactly as required for external imports.
On the Fields tab, define the fields to be imported (see File Format section).
Save the template — this will be reused for future imports.
💡 Note: To configure inter-site orders or manufacturing orders, additional fields may need to be included.
Using the Import
Once the template is in place and Netstock (SIA) is configured to export in Sage X3 format:
Export orders from Netstock.
In Sage X3, go to Usage → Import and select your template.
Import the order file from the
from_netstockfolder.The system will create the orders in Sage X3.
From here, your normal workflows and supplier communication processes continue as usual.
Order File Format
Sage X3 order files include Header and Line Detail records.
Header Detail
Position | Field Name | Description |
1 | H.HeaderLine | Character indicating the HeaderLine. Default to an H. It can be anything, although it is 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 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 | The date the purchase order was created, as shown in the PO summary. Use earliest, latest or average of due dates from line detail YYYYMMDD format. |
6 | H.RequiredExpireDate | Expected Arrival Date of the purchase order on SIA recommended order. Duplicated in Line for flexibility YYYYMMDD 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
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 it is 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 YYYYMMDD format. |
8 | L.Filler | A filler just in case we need an extra line field one day. The default value set to a zero for now. |
9 | L.CommentText | Comments entered against the recommended order in SIA. |
File Layout Example
H,000345,000,01-CONT,20121115,20121215,0,ADMIN L,6655,000,EACH,123.45,101,20121215,0,"this is comment1 ..." L,6652-28-24-15,000,EACH,234.45,102,20121216,0,"this is comment2 ..." L,6657-24-20-12,000,EACH,345.45,103,20121217,0,"this is comment3 ..." H,000346,000,01-CONT,20121115,20121215,0,ADMIN L,6656,000,EACH,123.45,101,20121215,0,"this is comment1 ..."
Forget about these 👇 😞 😐 😃 Have your say here!