1. Using B2B for Oracle Integration 3
  2. Use B2B for Oracle Integration in Standalone Mode
  3. Use the B2B Action in Standalone Mode

Use the B2B Action in Standalone Mode

You can translate a message to or from the Electronic Data Interchange (EDI) format in an integration with the B2B action.

The B2B action translates an incoming EDI document into an Oracle Integration XML message and an outgoing Oracle Integration XML message into an EDI X12 document.

Note:

This section provides an overview of how to add a B2B action to an integration. Complete integration design details are provided. See Create Application Integrations in Using Integrations in Oracle Integration 3.
  1. In the navigation pane, click Design, then Integrations.
  2. Click Create, then select Application or Schedule.
  3. Design your integration. For example, add a trigger connection if you selected Application.
  4. Add a B2B action to the integration in either of the following ways:
    • On the right side of the canvas, click Actions Integration actions icon and drag the B2B action to the appropriate location.
    • Click Zoom in icon at the location where you want to add the for-each action, then select B2B.
    The Configure B2B Action Wizard is displayed.
  5. Enter a name and optional description.
  6. Select how you want to use the B2B action, then click Continue.
    • B2B Trading Partner mode: Select to include B2B trading partner profiles and message persistence in your integration.
    • Standalone mode: Select to use the B2B action independently in your integration without a B2B trading partner profile or message persistence.
  7. If you select B2B Trading Partner mode, follow these wizard steps:
    1. Select the B2B message direction for this B2B action:
      • Inbound: The B2B message is sent from the trading partner to the host trading partner (partner where Oracle Integration is installed).
      • Outbound: The B2B message is sent from the host trading partner (partner where Oracle Integration is installed) to the trading partner.
    2. Select the operation for the B2B action to perform based on the direction.
      If You Selected... Then Select an Operation...
      Inbound
      • Fetch Message: Fetches a B2B business message from the persistence store, given a message identifier.
      • Translate: Translates an inbound EDI message to an Oracle Integration message.
      • Mark As Error: Marks a B2B business message with a failed processing status.
      Outbound
      • Translate: Translates an Oracle Integration message to an outbound EDI message.
      • Mark As Error: Marks a B2B business message with a failed processing status.
      • Fetch raw messages: Fetches a B2B business message payload from persistence stored for processing.
    3. If you select either of the following, the Select Data Format page is displayed.
      • Inbound message direction and Fetch Message operation
      • Outbound message direction and Translate operation
      1. Select the document definition for the B2B action to handle, and click Search to refresh the page.
      2. Select the document standard, version, and type.
      3. Click >.
    4. Review your selections on the Summary page, then click Done.
  8. If you select Standalone mode, follow these wizard steps:
    1. Specify the message translation and document format details.
      Element Description
      Select the direction in which to translate the message
      • Inbound EDI message to Oracle Integration message: When an integration receives an EDI document from a business partner, it is considered an inbound document (an EDI document is translated to XML).
      • Oracle Integration message to outbound EDI message: When an integration sends an EDI document to a business partner, it is considered an outbound document (an EDI document is generated from XML).
      Document Standard Select the document standard to follow when exchanging business documents between partners.
      • Custom
      • Delimited
      • EDIFACT
      • FixedLength
      • OAG
      • X12
      • X12HIPAA
      Document Version Select the version of the document standard to use.
      Document Type Select the document type (for example, purchase order, invoice, shipping notice, or others). The document types available for selection are based on the document version you selected.
      Document Definition Select the document definition that you created on the Documents page. For EDIFACT, X12, or X12HIPAA, you can also select Standard.

      See Create a Custom B2B Document Definition.

      EDI Character Encoding Select the character encoding that the inbound EDI document is expected to use.
      Perform validations on input data
      • Yes: Validates the structure and data of an inbound EDI message. Enabling message validation has an impact on performance. If errors are found, translation does not succeed.
      • No: Errors are ignored during translation and the message is passed through in its current format.

        You can override this setting at runtime with the Validate request element in the mapper.

    2. Click Continue.
    3. Specify to optionally upload sample data to test that translation is successful.
      Element Description
      Run a test translation with sample data (optional) Select or drag and drop a sample file. To test inbound EDI message translation, upload an EDI document. To test outbound EDI message generation, upload an XML document.
      Translate Click to translate your sample data. Output is displayed in the Output of translation field. Any errors are displayed in the Error in translation field.
    4. Click Continue.
    5. Review your selections on the Summary page, then click Finish.