Outbound Process in Detail
The Outbound process is the reverse of the Inbound process.
The Gateway reads data from the QAD Enterprise Applications database, Transformation writes the Exchange File Repository, and the Unload process writes the outbound data into a transmission group.
Summary
In summary, EDI eCommerce has a simple architecture, which uses 3 modular processes to accomplish any data interchange from simple to very complex:
1 Load/Unload
2 Transformation
3 Gateway Processing
Execution
Import or Export of a set of documents is a one-step task.
• Importing is done in Document Import (35.1)
• Exporting is done by type of document:
• Shipment ASN Export (35.4.1)
• Consignment Usage Export (35.4.2)
• Invoice Export (35.4.3)
• Purchase Order Acknowledgment (35.4.5)
• Supplier Shipping Schedule (35.4.8)
• Purchase Order Export (35.4.9)
• Supplier Self Billing Export (35.4.11)
• Inventory Cycle Count Export (35.4.13)
• Packing List Export (35.4.15)
• Distribution Order Packing List Export (35.4.16)
• Price Catalog Export (35.4.17)
• Warehouse Shipment Advise (35.4.18)
• Generic Gateway Export (35.4.20)
• Status and Error Reporting
• Exchange Doc Status Report (35.9.2)
• Application Doc Status Report (35.9.9)
• Exchange-Application Xref Report (35.9.14)
Setup
The 3 modular processes that combine to Import or Export EDI documents are independent of each other. Each process is set up separately:
Exchange File Processing
1 EC Subsystem Definition Maintenance (35.3.1)
2 EC Subsystem/Exchange Maintenance (35.13.3)
3 Trading Partner Maintenance (35.13.7)
4 Trading Partner Parameter Maintenance (35.13.10)
5 Transmission Group Maintenance (35.13.13)
6 Exchange Definition Maintenance (35.15.6)
Transformation
1 Transformation Definition Maintenance (35.15.17)
2 eCommerce Function Maintenance (35.15.21)
Gateway Processing
1 Implementation Definition Maintenance (35.15.13)
2 Application Definition Maintenance (35.15.10)
Modular Character of Processes
The modular character of the processes enables any “setup” to be reused. A new trading partner relationship is typically implemented by using “copy” functions to create the basic implementation from existing processes. The unique requirements of the relationship are implemented by making minor modifications to the “copied” setups.
• The copy functions are:
• Exchange Definition Copy (35.15.1)
• Application Definition Copy (35.15.2)
• Implementation Definition Copy (35.15.3)
• Transformation Definition Copy (35.17.1)
• eCommerce Function Copy (35.17.2)
Note: You can also create document definitions using Create eCommerce Doc Definitions (35.15.4) from a different type of document definition; a temp-table definition in Progress syntax from either Progress source code (.p or .i file) or a .txt file; an XML document (.xml file); or an XSD document (.xsd file).