Skip to main content
Order Formats - Orders upload - Sage 100
Ruvisha Pillay avatar
Written by Ruvisha Pillay
Updated over 2 months ago

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

PO import job setup

  • Login to Sage 100 with valid credentials.

  • Navigate to Visual Integrator -> Job Import.

  • Select the Job import file from the file location (Which should be copied to your server).

    • Location example: C:\sage_inventory_advisor\swstrings\scripts\SIAPurchaseOrders.exp

  • The job import wizard shows all the Available jobs. Select the job for SIA PO Imports.

  • Click Accept and OK to add the job in your visual integrator of Sage 100.

  • Create a blank recpo.csv file in the from_netstock folder

  • Update the Job

    • In Sage; go to visual integrator -> Import Job Maintenance

  • Locate the newly imported Job "SIA_PUR_ORDERS"

  • Change the location of the repo.csv file to the correct one

    • Example: C:\sage_inventory_advisor\swstrings\from_netstock\recpo.csv

  • Click Accept

  • Say "Yes" to Execute the job

  • Confirm the import file's location

  • Click "Accept"

  • The Job run and complete, but with 0 records

  • There's no need to view the job log.

  • Information customer needs to pass on to Netstock

    • 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

Header detail

Position. Field Name

Description

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.

Line detail

Field Name

Description

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

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 ..."

Did this answer your question?