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

1. To create an integration in a project.
   1. In the navigation pane, click Projects.
   2. Open the project in which to create the integration.
   3. In the Integrations section, click Add.
2. To create an integration in a standalone environment.
   In the navigation pane, click Design, then Integrations.
3. Click Create, then select Application or Schedule.
4. Design your integration. For example, add a trigger connection if you selected Application.
5. Add a B2B action to the integration in either of the following ways:
   • On the right side of the canvas, click Actions and drag the B2B action to the appropriate location.
   • Click at the location where you want to add the for-each action, then select B2B.
   The Configure B2B Action Wizard is displayed.
6. Enter a name and optional description.
7. Select Standalone mode, then click Continue.
8. 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.
   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.

9. Click Continue.
10. 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.

11. Click Continue.
12. Review your selections on the Summary page, then click Finish.