QAD 2017 Enterprise Edition > User Guides > EDI eCommerce > EDI eCommerce Overview > Elements of EDI eCommerce
  
Elements of EDI eCommerce
EDI eCommerce consists of several elements.
A document repository
A tool set containing table definitions and transformation procedures required to integrate transactions and support table maintenance, import, and export
Document import and export process control functions
Document Repository
EDI eCommerce includes a document repository, a set of tables that store data in transition during various phases of processing. Types of data included in the repository include:
Exchange file documents
Application documents
Turnaround data
See EDI eCommerce Processing.
Maintenance programs let you change all three types of repository data. However, change data with care since modifying data values in the eCommerce tables can cause data synchronization problems within the database.
See Maintaining the Document Repository.
Exchange File Repository
This portion of the repository holds data at two stages of processing.
Inbound data from a standards neutral format (SNF) file before it undergoes transformation processing and is moved into the application document repository
Outbound data that has already undergone transformation processing before it is written to an SNF file and transferred to the EC subsystem
The system moves documents into and out of the repository as needed. A maintenance program lets you modify data in the exchange file data repository, if necessary.
See Exchange Data Repository.
Application Data Repository
The application data repository includes data in business-document formats:
Outbound data that is awaiting transformation processing before it is moved to the exchange file repository
Inbound data that has already undergone transformation processing and is waiting to be transferred into the database
The system moves documents into and out of the repository as needed. A maintenance program lets you modify data in the application document repository, if necessary.
See Application Document Repository.
Direct Import to Application Repository
To provide flexibility in using the document mapping functions of EDI eCommerce, you can import source files directly into the application document repository and export them without having to create business documents.
For example, you can use this feature to:
Receive an EDI file containing a sales order from an external system.
Load it into the repository based on an implementation definition.
Transform it into XML format.
Post it using an HTTP adapter on a Web server where it is available to a second external system.
During this process, you are never required to create a sales order in the database.
See Importing Documents.
Turnaround Data
Turnaround data includes some data items being stored from transactions imported from an EC subsystem. Such data items cannot be mapped into the database as elements of a business document, but are required for related outbound documents.
Example: An inbound supplier schedule includes additional customer data your company does not ordinarily track in shipping documents. However, the customer requires the same data on all advance ship notices (ASNs) your company exports for items included on the schedule.
You can define inbound documents from this customer to map turnaround data during gateway processing. The system marks this data as turnaround data and stores it, but does not attempt to map it to the database. The corresponding outbound implementation for this trading partner calls for the outbound gateway program to pick up these data items. The system places them in the appropriate fields on the ASN exchange file document sent to the EC subsystem.
EDI eCommerce provides a tool for modifying stored turnaround data.
See Turnaround Data.
EDI eCommerce Tool Set
The EDI eCommerce tool set includes a set of tables containing trading partner data, exchange file document definitions, and implementation-specific application document definitions used in the transformation process. Additionally, a set of menu programs lets you maintain these tables. Other menu programs are used to set up the system and to run the import and export functions.
Most of the programs are not intended for day-to-day use. Typically, you only require import and export programs, reprocessing programs, and a few reports and browses.
System implementers use the other programs to perform initial setup and to add trading partners and document types during system maintenance.
EDI eCommerce programs are on the 35 menu.
Document Types
EDI eCommerce allows several types of documents to be exchanged with EC subsystems. Sample EDI eCommerce Document Types lists examples of the international standards typically associated with some of the document types that eCommerce supports. The following organizations define associated standards:
American National Standards Institute (ANSI) Accredited Standards Committee (ASC) X12
Electronic Data Interchange for Administration, Commerce, and Transportation (EDIFACT)
Organization for Data Exchange by Teletransmission in Europe (ODETTE)
Verband der Automobilindustrie e.V. (VDA)
Note: These standards are provided as examples. Because of the flexible, database-centered design of eCommerce, the SNF-based maps can be tailored to any standard or nonstandard business document.

Sample EDI eCommerce Document Types
 
Document Type
Examples of International Standards
Planning and shipping schedules
ANSI X12 830 and 862
EDIFACT DELFOR and DELJIT
ODETTE DELINS
VDA 4905
Purchase orders (including changes and acknowledgments)
ANSI X12 850, 860, and 865
EDIFACT ORDERS and ORDCHG
ODETTE ORDERR
Invoices
ANSI X12 810
EDIFACT INVOIC
ODETTE INVOIC
VDA 4906
Remittance advices
ANSI X12 820
EDIFACT REMADV
Advance ship notices (ASNs)
ANSI 856
EDIFACT DESADV
ODETTE AVIEXP
VDA 4913
Inventory advice
ANSI X12 846
EDIFACT INVRPT
ODETTE STOACT
Distribution order receipts
ANSI X12 944
ODETTE STOACT
Sales order shipments
ANSI X12 945
ODETTE STOACT