Sample
Files
(Last Update
8/16/2007)
This is used to accept changes and additions to a customer's retails and authorization.
A mixture of General Item, Warehouse-Specific Item, and Customer-Specific Item
This file represents a series of item-related transactions. Each product has information delivered in three different (but related) transactions. In order to have a complete representation of an item, a retailer will need information from all three transactions.
Comprehensive Customer-Item Aggregate CI v2.00
This sample contains item information in the "I1" format version 2.00. This format provides customer-specific information about a product, including nearly all item information that may be useful to a retailer, in a single, comprehensive message.
Comprehensive Customer-Item Aggregate CI v2.01
This sample contains item information in the "I1" format version 2.01. This format provides customer-specific information about a product, including nearly all item information that may be useful to a retailer, in a single, comprehensive message.
Here is a sample of a file which can be sent by a retailer to create an order in DAC. Note that the Emulated Sales Order can do the same thing-- however, it's not intended for general purpose use. The Requested Sales Order transaction set, on the other hand, is much more simplified and goes through a much more rigid set of checks and balances upon importing.
This is an example of a sales order which DAC generates. It can be used by a retailer as a detailed invoice and receiving document.
This is another example of a sales order which DAC generates. It can be used by a retailer as a detailed invoice and receiving document. This sample uses version 1 CETE. Sales Orders can be specified as CETE version 1 for special purposes although this is not recommended.
This is another example of a sales order which DAC generates. It can be used by a retailer as a detailed invoice and receiving document. This sample uses the V2.01 Sales Order Transaction Set.
This file is a sample of an Emulated Sales Order transaction set. The file can be imported into DAC to create a sales order in the billing system. Exercise caution when using this transaction set. This is not intended for use by a retailer for general-purpose order importing. The use of this transaction set is very specialized.
This file is a sample of a Sales Order formatted for CMI. CMI is a natively supported POS system. See the documentation on native interfaces here.
This file is a sample of a Price Book formatted for CMI. CMI is a natively supported POS system. See the documentation on native interfaces here.
This file is a
sample of a single customer's A/R.
This is a sample of a Purchase Order transaction set.
This is a sample of the template used to import prebook orders.
RCV Inbound Sales Order format
This is a sample of a sales order using the RCV format. This format represents a simplified alternative for formatting a "Requested Sales Order" (Purchase Order). This is the original format used by the legacy remote order receiving (Telxon) systems.