The XML Map Connector requires a sample Source File and Destination File, which represent the starting XML structure and ending XML structure respectively. Once both the source and destination formats have been represented as XML, the powerful XML Map Connector is used to transform one XML structure into the other. This sample document will be used to create the XML model for the mapping step. a sample 810) prior to creating the mapping flow. It is important to have a sample output document (e.g. This guide focuses on mapping an X12 document, so the X12 Connector will be used to generate an XML representation of the target 810 document. Arc includes many different connectors to convert between EDI and XML formats (X12, EDIFACT, etc). In order to map the XML data pulled from a database into an EDI document, the EDI document must also be represented as XML. The section in this guide dedicated to configuring a Database Connector will include the steps necessary to pull from both a ‘PurchaseOrders’ table and a ‘LineItems’ table (with the appropriate foreign key relationship) at the same time. The ‘LineItems’ table has a foreign key to the ‘PurchaseOrders’ table in order to know which Line Items are associated with which Purchase Order, but data must be pulled from both tables in order to retrieve all of the necessary information to populate an 810 Invoice. Purchase Orders can contain multiple Line Items, and a typical database setup will store Line Item data in a ‘LineItems’ table that is separate from the ‘PurchaseOrders’ table. When configuring a Database Connector for this mapping flow, the Database Connector will target the tables where the Purchase Order data is held. This guide assumes that incoming Purchase Order data is automatically inserted into a database, so the Purchase Order database tables hold the data relevant to the 810 Invoice. When a manufacturing company receives a Purchase Order that requests a set of manufactured goods, the manufacturing company responds with an Invoice to pay for the requested goods.Īs a result, the data used to generate an Invoice typically comes from a Purchase Order received earlier. Invoices are typically sent to trading partners in response to a Purchase Order.
EDI 810 INVOICE EXAMPLE DRIVER
This guide will use the Database Connector configured with a MySQL driver to interface with a MySQL database.
Thus, data that is pulled from a database is immediately ready to be mapped or transformed. All EDI mapping flows involve converting the source data (in this case database data) and destination data (in this case an EDI file) into XML.Īll Arc connectors that pull data from databases (or database-like applications) automatically format the output data as XML files. EDI Mapping in CData Arc Pulling Database Data as XMLĪrc uses XML as a common format for data transformation and manipulation. The sample data used in this article (database structure and output files and the resulting 810 document) are included at the bottom of the page.
EDI 810 INVOICE EXAMPLE HOW TO
This guide will begin with an overview of how to accomplish the mapping in Arc, then walk through each step of the mapping flow.
The approach and principles described in this article are also applicable to generating other EDI documents, however there may be differences in the specific data pulled from the database and the relationships between mapped values. The sample Invoice used mirrors the syntax required by Amazon, and is provided at the bottom of the page. This guide will walk through the process of creating a database-to-EDI workflow, focusing on generating an X12 810 document (Invoice). Map Database Output to an EDI 810 InvoiceĬData Arc contains powerful tools to retrieve targeted data from back-end databases and map this data into an outbound EDI document (X12, EDIFACT, etc).
0 kommentar(er)
