DAC Retailer Implementation Guide
Version 2.02 1/1/2008
Copyright 2008 Creative Data Research, All rights reserved.
Printed in the United States of America
No part of this publication may be electronically or mechanically reproduced, stored in a retrieval system, or transmitted, in any form or by any means, except as permitted by CDR. Translation of this material to another language without express written permission of CDR is prohibited. The information in this publication is for informational use only and is subject to change without notice. The reader of this document should not construe the contents of this document to be a commitment by CDR, and CDR assumes no responsibility or liability for inaccuracies that may appear in this publication. The CDR logo and DAC are trademarks of CDR.
CDR is located at 1150 N. Causeway
Blvd. Mandeville, LA 70471.
CDR's telephone number is (985) 626-8408
The DAC software system used by your distributor supports the exchange of a number of transactions which may be of interest to a retailer. For example, DAC can supply the Retailer with electronic versions of invoices, price-books, promotions, and more. DAC can also accept from the Retailer purchase orders, retail price changes, and more. Using DAC, these transactions are generally exchanged between the Distributor and the Retailer through ASCII "Flat Files". The DAC software component which produces this data is known as the CV1 Integration Module (hereafter referred to as CIM).
CIM uses proprietary transactional formats for data going to and coming from the Retailer. This document describes these formats. Often, a Retailer will already have an established protocol for the electronic exchange and formatting of transactions. This may consist of an available standard (such as ANSI X.12 EDI with VAN support) or, it could be that the Retailerís software system, like DAC, supports a proprietary transactional format. While CIM itself does not provide a custom mapping solution, it does provide a very robust transaction set which programmers, third-party integrators, and EDI mapping software can easily take advantage of.
In order to understand the structure of CIM transactions, you'll need to have a basic understanding of the following key concepts:
|CIM Message||Describes the two major components of a CIM Message, and how they relate to one another.|
|CETE||Documents the first of the two major components of a CIM Message.|
|CIM Transaction||Documents the second of the two major components of a CIM Message.|
|CIM Transaction Set||Describes how transactions can be grouped together to form a set.|
|Spec Determination Guide||A procedure for determining what transaction specification is in use by visually examining raw transaction data.|
|Sample Files||A list of various samples of actual raw transaction and transaction set data.|
The following is a list of the transactions most commonly exchanged between a Retailer and a Distributor using CIM. A detailed description of the formatting for these transactions is given in the next section. For a complete list all supported transactions, please visit CIM Programmers Guide and Reference.
Transactions provided to the Retailer:
|General Item Transaction (Topic IT)||This transaction provides general information about a single product- such as the name of the product, the UPC codes, and how the product is classified and packaged. Upon request, the Distributor is capable of providing the retailer with a bulk "dump" of all items. As the Distributor adds new products or changes existing products, the Retailer will receive a single transaction representing the change or addition. See latest on-line documentation|
Warehouse-Specific Item Transaction (Topic IB)
This transaction further defines a product. It is intended to augment the General Item transaction. It contains information relevant to a product being sold from a specific warehouse location. Information such as minimum purchase requirements and standard pricing is given. Upon request, the Distributor is capable of providing the retailer with a bulk "dump" of all items from a given warehouse. As the Distributor adds new products to a warehouse or changes existing products in a warehouse, the Retailer will receive a single transaction representing the change or addition. See latest on-line documentation
|Customer-Specific Item Transaction (Topic CI)||This transaction further defines a product. It is intended to augment the General Item transaction. It contains information relevant to a product being sold to a specific Retailer. Information such as the price the Retailer pays the Distributor for the product, and the price the Retailer charges the consumer for the product is given. Upon request, the Distributor is capable of providing the retailer with a bulk "dump" of all items from a given warehouse. As the Distributor adds new products to a warehouse or changes existing products in a warehouse, the Retailer will receive a single transaction representing the change or addition. See latest on-line documentation|
|Sales Order Transaction Set (Topic X4)||This transaction set contains a series of individual transactions representing a single order in the Distributorís order-fulfillment system. These orders are typically created as the result of the Retailer sending in a purchase order. This transaction set contains a header for the order, shipping details, parcel details, and each individual line-item. Itís useful to the Retailer once the Distributor has filled and invoiced the order. It can be used by the Retailer as an electronic invoice and/or receiving document. See latest on-line documentation|
Transactions accepted from the Retailer:
|Requested Sales Order Transaction Set (Topic X5)||This transaction set is used by the Retailer to supply a purchase order to the Distributor. It consists of a header and multiple detail lines which represent the products being ordered. See latest on-line documentation Use CETE version 1 when generating these transactions.|
|Retail Request Transaction (Topic RR)||This transaction allows a Retailer to set the retail prices they charge a consumer. It also allows a Retailer to authorize or de-authorize themselves from a specific product. See latest on-line documentation. See a sample file. Use CETE version 1 when generating these transactions.|