Defining Outbound EDI Routes

Defining this object establishes the route that ERP data follows for integration to your trading partners.

1. Specify a Trading Partner for the Route.
2. (Optional) Specify the Priority Level.

   For each Business Document (Invoice, Purchase Order, etc.) within the data, you may specify one or more Outbound EDI Routes. Specifying more than one Route for a document directs the Studio to perform multiple Business Processes for a single document. The Priority Level indicator directs the order in which the Business Processes are performed.  

3. (Optional) Specify the Parent.

   Inbound EDI Routes can be organized into a logical hierarchy; this provides a way to share information between common Routes. For example, most organizations trade more than one kind of business document with a single trading partner. They may trade purchase orders, ship notices, invoices, etc. The envelope information between the business documents is nearly identical. You can define an Outbound EDI Route that simply identifies your trading partner's Customer Number (who the document is from). If you send invoices and ship notices to your trading partner, you will also create an Outbound EDI Route for both documents. When you define the invoice and ship notice Outbound EDI Routes, you select the Route with the Customer Number info, as the "Parent Outbound EDI Route". This will cause the Application Matching information to be inherited from the Parent Route to the ship notice and invoice Routes. This way, you don't have to re-enter the Customer Number information on the document-level Routes.

4. Enter a value for Name.

   Name is a user-defined tag that describes the routing fields in your source data. For example, if you route on customer number and ship-to location, you can create a "Customer Number" name and a "Ship-to" name in the Application Interface object. The Studio will search Outbound EDI Routes containing those values for the customer number and ship-to information.

5. Enter the envelope routing criteria in the value column.

   You should enter a value for each name. Any name that doesn't have a value will be ignored by the routing process. The values you enter will be matched against any outbound application document. When a match is found, the Studio executes the associated Outbound EDI Business Process.

6. Use the Process Binding to specify the Business Process to be performed for the outbound EDI document. Use the green Add button to add a row, and then select the Business Process. The list of Business Processes will be filtered; only those who have Outbound EDI Business Process as their template will appear in the list.
7. Use the Properties | Fields tab to set any runtime parameter values that will be passed into the Business Process. 

   Note: For more information on how these work, see Fields.

8. Use the Properties | Target tab to select an EDI Enveloper.

   An EDI Enveloper is used to produce X12, EDIFACT/TRADACOMS EDI envelope data. The information specified on the EDI Enveloper will be used to create the standard- specific envelope segments (ISA/GS/ST, UNA/UNB/UNH, STX and MHD).