EDI Inbound Bootstrap Business Process

The EDI Inbound Bootstrap business process is used by the EDI Inbound File System adapter to collect a file and then call the proper deenveloping services based on the data found.

When to Use

The EDI Inbound Bootstrap business process is invoked by the EDI Inbound File System adapter to collect data, which you can use to automate your inbound EDI deenveloping.

When You Must Configure Prior to Using

Prior to using the EDI Inbound Bootstrap business process, you must configure the following:
  • Create a map to translate the incoming data.
  • Create an envelope for the type of data you will receive (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. See Creating Envelopes to Use with EDI Translation Business Processes for more information.
  • On the envelope, configure the Extraction Options parameter to Extract to a file system directory. 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 collection. See EDI Inbound File System Adapter Configuration for more information.
  • Divert your inbound files to the install_dir/ediinbound/collect directory.

Inbound Process Flow Using File System Directory

The EDI Inbound Bootstrap business process is initiated as part of the following inbound process flow when you a file is placed in the default collection directory:
  1. A file is dropped into the install_dir/ediinbound/collect directory.
  2. The EDI Inbound File System adapter collects the file and calls the EDI Inbound Bootstrap business process.
  3. Starts the EDI Deenvelope service which determines which standard the file is using (for example, an ACH file) and locates the proper envelope (for example, ACH Inbound envelope).
    Note: You must create this envelope.
  4. Calls the business process for the specified standard (for example, ACH Deenvelope business process).
  5. Starts the deenvelope service for the specified standard (for example, ACH Deenvelope service).
  6. Uses the data extraction setting that you configured in the envelope you created to write out the results of the deenveloping to the default directory (install_dir/ediinbound/extract).

Inbound Process Flow Using Mailbox

The EDI Inbound Bootstrap business process is initiated as part of the following inbound process flow when you a file is passed to the default mailbox:
  1. A file is collected from the default mailbox (EDIInboundCollectionMailbox).
  2. The EDIInboundCollectionMailbox default routing rule collects the mailbox message and places the message ID into ProcessData.
  3. Calls the EDI Inbound Bootstrap business process which obtains the primary document for each message ID.
  4. Starts the EDI Deenvelope service which determines which standard the file is using (for example, an ACH file) and locates the proper envelope (for example, ACH Inbound envelope).
    Note: You must create this envelope.
  5. Calls the business process for the specified standard (for example, ACH Deenvelope business process).
  6. Starts the deenvelope service for the specified standard (for example, ACH Deenvelope service).
  7. Uses the data extraction setting that you configured in the envelope you created to write out the results of the deenveloping to the default mailbox (EDIInboundExtr actionMailbox).

If exceptions occur when running the EDI Inbound Bootstrap business process, Sterling B2B Integrator generates an EDI Compliance Report.