How to Support Trading Partner-Specific Variants How to Enable Error Handling

Developing and Implementing Inbound B2B Integration Flows 18-17 Figure 18–15 Reference to the AIA EBS Invoked by the B2BCS Annotated in the composite.xml For your reference, the AIA_ HOMEInfrastructureB2BsrcB2BConnectorsEDIX12B2BCSAppX12Process SalesOrder ReqB2BCSImplcomposite.xml file contains sample Requester B2BCS Impl annotations.

18.4.7 How to Support Trading Partner-Specific Variants

Support for Trading Partner-specific processing can be built into the requester B2BCS in a manner similar to the way they are built into the provider B2BCS. For more information about how to build trading partner-specific support in B2BCSs, see Section 17.3.8, How to Support Trading Partner-Specific Variants.

18.4.8 How to Enable Error Handling

For more information about how to enable AIA services for error handling and recovery, see Setting Up Error Handling in Oracle Fusion Middleware Infrastructure Components and Utilities Users Guide for Oracle Application Integration Architecture Foundation Pack. In short, the following steps must be taken: ■ Associate a fault-policy.xml with the B2BCS composite. ■ Invoke the AIAAsyncErrorHandlingBPELProcess for business faults, as shown in Figure 18–16 and Figure 18–17 . 18-18 Developers Guide for Oracle Application Integration Architecture Foundation Pack Figure 18–16 B2BCS Composite Defined to Invoke AIAAsyncErrorHandlingBPELProcess Figure 18–17 Invocation of the AIAAsyncEHService While invoking the AIAAsyncErrorHandlingBPELProcess, the B2B-specific elements in the fault schema can be populated as shown in Table 18–4 . Table 18–4 B2B-Specific Elements in the Fault Schema That Can Be Populated by AIAAsyncErrorHandlingBPELProcess Fault Element Schema Description Example FaultB2BMReferenceB2BMI D Unique identifier of the B2B document 13232325 FaultB2BMReferenceB2BDo cumentTypeTypeCode Document type of the B2B document being processed by the requester B2BCS 855 FaultB2BMReferenceB2BDo cumentTypeVersion Document version of the B2B document being processed by the Requester B2BCS 4010 FaultB2BMReferenceB2BDo cumentTypeTypeCodelist AgencyID Standard of the B2B document being processed by the Requester B2BCS X12 FaultB2BMReferenceGatew ayID Name of the B2B software being used. Oracle B2B FaultB2BMReferenceSender TradingPartnerTradingPartn erID Sender trading partner, mapped from the B2BM MyCompany Developing and Implementing Inbound B2B Integration Flows 18-19 Figure 18–18 provides the B2B-specific elements in the corecom:Fault. Figure 18–18 B2B-Specific Elements in corecom:Fault The B2B details of the failed AIA service now available in the fault instance will be logged and available for debugging the failed flow.

18.5 Step 4: Developing or Extending an Existing Enterprise Business Service

The next step, as shown in Figure 18–19 , is to develop a new EBS or use an existing EBS that is invoked by the requester B2BCS. FaultB2BMReferenceReceiv erTradingPartnerTradingPart nerID Receiver trading partner, mapped from the B2BM Global Table 18–4 Cont. B2B-Specific Elements in the Fault Schema That Can Be Populated by AIAAsyncErrorHandlingBPELProcess Fault Element Schema Description Example