Sage MAS 90 Bar Code Invoice/Shipment Import

The Sage MAS 90 and MAS 200 Bar Code Module helps import transactions usually gathered with a scanner (although it’s not required).  While specific scanners are certainly recommended for use with the module, any scanner will do as long as it produces a text file in the appropriate format.

The file must meet the following requirements:

  • ASCII Text format
  • The file name must begin with a specific letter of the alphabet corresponding to the type of transaction records to be imported:
    • “B” for Bill of Materials Transactions
    • “I” for Inventory Transactions
    • “P” for Purchase Order Transactions
    • “S” for Sales Order Transactions  (invoices or shipments)
  • The file name should be in an “8.3” file name format, ending with a *.ODB extension
    (e.g. – ” S1234567.ODB” for a sales order import file.)

The following table illustrates the ASCII import file format for Sage MAS 90 and MAS 200 Sales Order Module transactions.   Note Records should be terminated with LF or LF/CR combination.   Note – a valid sales order needs to already exist within Sage MAS 90 or MAS 200 in order for the invoice or shipment data to be properly imported.

For Invoice Data Entry

   
Field Description Start Length
Transaction Type (hardcode “S”) 1 1
Ship Date (YYMMDD) 2 6
Sales Order Number (Alpha-Numeric Entry) pad with  0’s 8 7
Item Code 15 30
Line Index Number ##### Fix$(Lineidx,0,-5) fill with spaces 45 6
Ship Quantity (######.###) Fix $(Qty,3,-10) 51 10
Lot/Serial Number – fill with spaces 61 15
Weight fix (0,.5) Numeric, NO fractions 76 5
Freight Charge (######.##) Fix (Freight .2, -9) 81 9

For Shipping Data Entry

   
Field Description Start Length
Transaction Type – “P” 1 1
Ship Date (YYMMDD) 2 6
Sales Order Number 8 7
Item Code 15 30
Line Index Number 45 6
Ship Quantity 51 10
Lot/Serial Number 61 15
Shipper ID 76 3
Package Number 79 4