Deleting Scheduled Downtime Oracle Fusion Middleware Online Documentation Library

13-2 Oracle Fusion Middleware Users Guide for Oracle B2B Figure 13–1 A Purchase Order Example: Using Callouts for Differently Formatted XML Messages The image shows a box on the far right labeled Remote Trading Partner buyer RosettaNet XML. There are two arrows on the left side of this box. The top arrow labeled Purchase Order Request RosettaNet XML format points out to the left to a box labeled Host Trading Partner seller. The bottom arrow labeled Purchase Order Acceptance RosettaNet XML format points from the box labeled Host Trading Partner seller into the box labeled Remote Trading Partner buyer RosettaNet XML. The box labeled Host Trading Partner seller has a smaller box inside in the upper left that is labeled A and a smaller box inside in the lower left that is labeled B. An arrow labeled Callout Usage Transforms RosettaNet XML to Oracle E-Business Suite XML points down to the box labeled A. An arrow labeled Responding Callout Usage Transforms Oracle E-Business Suite XML to RosettaNet XML points up to the box labeled B. There are two arrows on the left side of box labeled Host Trading Partner seller. The top arrow labeled Purchase Order Request Oracle E-Business Suite XML format points out to the left to a box labeled Host Application Oracle E-Business Suite XML. This top arrow is also labeled Internal Delivery Channel. The bottom arrow labeled Purchase Order Acceptance Oracle E-Business Suite XML format points from the box labeled Host Application Oracle E-Business Suite XML into the box labeled Host Trading Partner seller. This bottom arrow is also labeled Responding Internal Delivery Channel. The Host Application Oracle E-Business Suite XML box and the Host Trading Partner seller box are inside a larger dashed box. Remote Trading Partner Host Trading Partner Host Application Purchase Order Request Oracle E-Business Suite XML format Purchase Order Acceptance Oracle E-Business Suite XML format Responding Callout Usage Transforms Oracle E-Business Suite XML to RosettaNet XML Callout Usage Transforms RosettaNet XML to Oracle E-Business Suite XML Oracle E-Business Suite XML seller buyer RosettaNet XML A B A B Internal Delivery Channel Responding Internal Delivery Channel Purchase Order Request RosettaNet XML format Purchase Order Acceptance RosettaNet XML format Source Document Definition: PurchaseOrderRequest Target Document Definition: PurchaseOrderAcceptance Source Document Definition: PurchaseOrderAcceptance Target Document Definition: PurchaseOrderRequest Managing Callouts 13-3 Below the illustration is a key with two letters: A and B. The key letter A which denotes the smaller upper left box inside the Host Trading Partner seller box says Source Document Definition: PurchaseOrderRequest and Target Document Definition: PurchaseOrderAcceptance. The key letter B which denotes the smaller lower left box inside the Host Trading Partner seller box says Source Document Definition: PurchaseOrderAcceptance and Target Document Definition: PurchaseOrderRequest. In this example, the host application of the host trading partner is an Oracle E-Business Suite application that does not use RosettaNet XML-formatted messages. To enable communication between these two different formats, you create two callouts, as follows: ■ One callout, callout_inbound, for example, transforms the RosettaNet XML-formatted purchase order request into an Oracle E-Business Suite XML format understood by the Oracle E-Business Suite application. The Oracle E-Business Suite application, in turn, responds to the request message with a purchase order acceptance message in Oracle E-Business Suite XML format. ■ The other callout, callout_outbound, for example, transforms the Oracle E-Business Suite XML format back into a RosettaNet XML-formatted message for the remote trading partner. These two callouts are then associated with the two agreements created for this exchange, as follows: ■ Include callout_outbound in the agreement for the outbound message, that is, the agreement for the initiating purchase order request. ■ Include callout_inbound in the agreement for the inbound message, that is, the agreement for the responding purchase order acceptance. Because a document definition is a component of an agreement, a callout is associated with a specific document definition. This purchase order example depicts a simple association of one callout to one agreement. In reality, however, the same callout can be included in many different agreements by changing the value of one or more callout parameters. See Figure 13–3 for where you add parameters and see Table 13–2 for a list of parameter attributes.

13.1.1 Transport Callouts

Another type of callout is the transport callout, which is associated with a channel. For the inbound message, B2B invokes the transport callout immediately after it receives a message from the transport. For the outbound message, B2B invokes the transport callout immediately before it sends a message to the transport. Transport callouts can be selected in the channel configuration, as shown in Figure 13–2 , and can be used with any protocol.