EDI Outbound B2B Send Extraction Business Process

The EDI Outbound B2B Send Extraction business process is used to extract outbound B2B translation data to send messages to trading partners. This business process sends documents to the trading partner identified as the consumption profile (receiving partner) in a contract.

When to Use

The EDI Outbound B2B Send Extraction business process is used for B2B data.

What You Must Configure Prior to Using

Prior to using the EDI Outbound Bootstrap business process, you must configure the following:
  • Create a map to translate the outbound EDI data.
    Note: If you are sending XML data, you do not need a map because extraction occurs using the parameter values you configure in the EDI XML Outbound File System adapter.
  • Create an envelope for the type of data you will send (for example, ASC X12 data). See Creating Envelopes to Use with EDI Translation Business Processes for more information.
  • On the document (transaction-level) envelope, provide the name of the map (unless you are sending XML data). See Creating Envelopes to Use with EDI Translation Business Processes for more information.
  • On the envelope, configure the Extraction Options parameter to Determined by Business Process and specify the B2B business process. See Creating Envelopes to Use with EDI Translation Business Processes for more information.
  • On the envelope, configure the Data Extraction Directory and Data Extraction Filename parameters. See Creating Envelopes to Use with EDI Translation Business Processes for more information.
  • You may need to modify the predefined file system adapter configurations if you want to use a non-default option such as setting up a schedule to perform automatic file extraction. See Predefined EDI Translation File System Adapters for more information.

Outbound Process Flow

The EDI Outbound B2B Send Extraction business process is initiated as part of the following outbound process flow:
  1. A file is dropped into the default directory (install_dir/edioutbound/collect) or a file is collected from the default mailbox (EDIOutboundCollectionMailbox).
  2. If the file is collected from the default mailbox, the EDIOutboundCollectionMailbox default routing rule collects the mailbox message and places the message ID into ProcessData.
  3. The EDI Outbound File System adapter is kicked off to collect the file (by default the Outbound File System adapter is not kicked off automatically).
  4. Determines that the data is B2B and calls the EDI Outbound B2B Send Extraction business process.
  5. Calls the B2B Send service.
  6. The B2B Send service retrieves and uses information from trading profiles and the associated trading profile contract to identify how and where to send the documents.

If exceptions occur when running the EDI Outbound B2B Send Extraction business process, Sterling B2B Integrator generates an EDI Compliance Report.