Create an Outbound Backend Integration | Outbound Message Processing | B2B for Oracle Integration

HighLevel steps for Outbound EDI Message Processing:

Create an Outbound Backend Integration:

Step1: Create an appdriven Integration and configure rest trigger connection.

In our example, a simple REST adapter is used. You can use any type of adpater like Oracle ERP adapter or any one.

Step2: Place a B2B action with an outbound translate operation.

Step3: Configure the mapper to convert the application message to B2B canonical format.

Part1:

1. Map an element to either B2B Trading Partner Id or Application Partner Id. These elements are used to specify the trading partner to which to send. Here, B2B Trading partner has been mapped.
2. Optionally mapped Application Message ID. This is the message id assigned by the backend application. If this is mapped, the value will be displayed in Monitoring>>B2B Tracking >> Business Messages 

Part2: 

Map the Backend application data to B2B canonical EDI data using edi-xml-document element.

Step3: Add a Check for Successful EDI Translation

Place a switch action after the B2B translate action. This action is to check the translation status if it is Succeeded or failed.

For success case condition used: translation-status="Success"

Step4: If translation is successful, deliver the document to the Send Outbound default Integration to Trading partner.

Add a local integration invoke action in the Translation succeeded route.

Step5: configure the mapper before the local Integration invoke 

1. TranslateOutput>> B2B Message Reference >> b2b-message-reference
2. TranslateOutput>>Trading Partner Name >> trading-partner
3. TranslateOutput>>Connectivity-properties-code >> connectivityProperties >> LocalIntegration>>code
4. TranslateOutput>>Connectivity-properties-version >> connectivityProperties >> LocalIntegration>>version

Step6: Add a rerurn acrion for success and a fault for an error.

Step7: Add B2B business identifiers for integration tracking.