How to Route Based on Trading Partner B2B Preferences

Developing and Implementing Outbound B2B Integration Flows 17-27 Figure 17–29 Step 3: Developing or Extending an Existing Enterprise Business Service For more information about creating a new EBS, see Chapter 10, Designing and Developing Enterprise Business Services.

17.4.1 How to Route Based on Trading Partner B2B Preferences

A B2B implementation may possibly exist in which different trading partners may require that the same EBM information be sent using different B2B document protocols. For example, suppliers XLS Inc., New Networks, and Office Systems may require that new purchase orders be sent using the OAG Process Purchase Order document format, while suppliers ABC Inc. and Global may require that new purchase orders be sent using the X12 850 document format. To support the needs of this implementation, two B2BCSs must be developed, as shown in Figure 17–30 : ■ OAGCreatePurchaseOrderB2BCSImpl, which transforms the CreatePurchaseOrderEBM into an OAG Process Purchase Order B2B document. ■ X12CreatePurchaseOrderB2BCSImpl, which transforms the CreatePurchaseOrderEBM into an X12 850 B2B document. The CreatePurchaseOrderEBM implementation must include routing rules to invoke both of these B2BCSs. Figure 17–30 B2B Implementation in which Trading Partners Need the Same EBM Data Sent Using Different B2B Document Protocols 17-28 Developers Guide for Oracle Application Integration Architecture Foundation Pack If a small number of trading partners are involved, the filter expression in the EBS routing rules to each of the B2BCSs can be used to route the EBM based on the trading partner involved, as shown in Figure 17–31 . Figure 17–31 Filter Expression in the EBS Routing Rule to Each B2BCS Used to Route the EBM Based on the Trading Partner However, if a large number of trading partners are involved, the trading partners B2B preferences can be stored in an external configuration file, for example, in a DVM file, as shown in Figure 17–32 . Figure 17–32 DVM Used to Store Trading Partner B2B Preferences This configuration can be looked up during run time by the EBS implementation to determine the target provider B2BCS to be invoked, as shown in Figure 17–33 . Developing and Implementing Outbound B2B Integration Flows 17-29 Figure 17–33 EBS Implementation Lookup to Determine the Target Provider B2BCS to be Invoked Note that though this approach works, a need exists to keep the trading partner information between the application and these DVM files synchronized. Each time a new trading partner is defined in the application, a corresponding record should be created in this DVM to store the B2B document preference of the trading partner. A well-established administrative process to manage these changes should exist.

17.5 Step 4: Developing or Extending an Existing Requester ABCS