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 (receipts or invoices)
- “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. – “ P1234567.ODB” for a purchase order receipt import file.)
The following table illustrates the ASCII import file format for Sage MAS 90 and MAS 200 Purchase Order Module Receipt of Goods and/or Receipt of Invoice transactions. Note Records should be terminated with LF or LF/CR combination. Note – a valid purchase order needs to already exist within Sage MAS 90 or MAS 200 in order for the receipt of goods data to be properly imported.
|P/O Receipt of Goods||Start||Length|
|Receipt Type (hard code – “G”)||1||1|
|Receipt Date (YYMMDD format)||2||6|
|Purchase Order Number||8||7|
|Invoice Number (optional)||15||10|
|Invoice Date (YYMMDD format or blank if no invoice)||25||6|
|Item Number (or Miscellaneous Item Code)||31||15|
|Receipt Quantity (#####.0000)||46||10|
|Lot/Serial Number (if applicable)||56||15|
|PO Line #||71||5|
*NOTE – For Version 4.40 (The length of the item number changed from 15 to 30 for expanded item codes), the import does not support the expanded item codes.