|Oracle® Application Integration Architecture Order Management Integration Pack for Oracle Transportation Management, Oracle E-Business Suite and Siebel CRM Implementation Guide
Part Number E20504-05
|PDF · Mobi · ePub|
This chapter provides an overview of the process integration for query transportation order itinerary and includes the following sections:
This integration flow enables Siebel users to query OTM for various itineraries, schedules, and their rates.
In the Siebel transportation order, you can query the ratings based on origin and destination location details, pickup and delivery time, and commodity (to be shipped) details. The corresponding OTM itineraries with details are pulled into Siebel solution view using AIA. You can select a solution and update the rate upon negotiation with the customer.
This integration flow supports these services:
Query transportation sales order process is a synchronous BPEL process. This process gets the itinerary information and rates from OTM and sends the data to Siebel for order confirmation.
The overall flow is described here:
Siebel Application invokes the QueryTransportationSalesOrderItineraryListSiebelReqABCSImpl with the SWIOrderIO application business message (ABM) as an input.
If the preprocess ABM property is true in the AIA configuration file, then the QueryTransportationSalesOrderItineraryListSiebelReqABCSImpl service invokes the QueryTransportationSalesOrderSiebelReqABCSImplExt through the PreProcessABM operation as a synchronous process, which accepts and replies with the TransportationSalesOrderSiebelABM message.
The TransportationSalesOrderSiebelABM message is transformed to the QueryTransportationSalesOrderItineraryListEBM and the EBMHeader is populated.
If the PreProcessEBM property is set to true in the AIA configuration file, the QueryTransportationSalesOrderSiebelReqABCSImplExt is invoked through the PreProcessEBM operation, which is a synchronous process that accepts and replies with the QueryTransportationSalesOrderItineraryListEBM.
The QueryTransportationSalesOrderSiebelReqABCSImpl then invokes TransportationSalesOrderEBS.
TransportationSalesOrderEBS then in-turn invokes the QueryTransportationSalesOrderItineraryListLogisticsProvABCSImpl.
The QueryTransportationSalesOrderItineraryListLogisticsProvABCSImpl then invokes the logistics web service that returns the itineraries and rates.
This response is sent to TransportationSalesOrderEBS.
The TransportationSalesOrderEBS returns the response to QueryTransportationSalesOrderItineraryListSiebelReqABCSImpl.
The QueryTransportationSalesOrderItineraryListSiebelReqABCSImpl returns the response to Siebel after transformation.
Figure 5-2 shows query transportation sales order itinerary list:
Itineraries and rates have been defined within Oracle Transportation Management (OTM).
These are the assumptions and constraints:
Exchange rates required as part of the rate negotiation are manually set up in Siebel; they are not synchronized as part of this integration.
This query requests only sell rates, not buy rates, from OTM.
This outbound web service is configured in Siebel for this flow: QueryTransportationSalesOrderItineraryListSiebelReqABCSImpl.
This service takes the SWIOrder as input and returns the SWIOrderEntrySalesIORes or a Fault.
For more information about Siebel CRM web services, navigate to the documentation library for Siebel applications on Oracle Technology Network and see Siebel CRM Web Services Reference.
Oracle Transportation Management (OTM) provides an interface through a web service to connect to its application. This connectivity is established as a partner link in the provider service. The logistics web service on being called immediately returns a response.
The RIQQuery element in OTM is used to request rate information for the order to be shipped.
For more information about the Logistics Service, see Oracle Transportation Management Integration Guide.
The integration flow uses these components:
The core enterprise business object (EBO) and enterprise business message (EBM) XSD files can be located by EBO within the $AIA_HOME/AIAMetaData/AIAComponents/EnterpriseObjectLibrary/Core/EBO/ parent folder.
The core enterprise business services (EBS) web services definition language (WSDL) files can be located by EBO within the $AIA_HOME/AIAMetaData/AIAComponents/EnterpriseBusinessServiceLibrary/Core/EBO/ parent folder.
For detailed documentation of individual EBOs and EBMs, click AIA Reference Doc link on EBO and EBM detail pages in the Oracle Enterprise Repository.
For more information about using the Oracle Enterprise Repository and configuring it to provide the AIA Reference Doc link, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack, "Configuring and Using Oracle Enterprise Repository as the Oracle AIA SOA Repository."
EBOs can be extended, for instance, to add new data elements. These extensions are protected, and remain intact after a patch or an upgrade.
For more information, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack, "Extensibility for AIA Artifacts".
This integration delivers these services:
This BPEL process receives the TransportationSalesOrderABM as input from the Siebel application, transforms the message to the QueryTransportationSalesOrderEBM, and invokes the TransportationSalesOrderEBS service. After transformation, based on the response, the message is again transformed into Siebel application business message (ABM) and sent to Siebel application.
TransportationSalesOrderEBS is an Enterprise Business Service that exposes all the enterprise operations related to the TransportationSalesOrder like create TransportationSalesOrder, update TransportationSalesOrder, delete TransportationSalesOrder, and so on. For this flow, the QueryTransportationSalesOrderItineraryList operation is implemented. It routes the request to the appropriate provider like QueryTransportationSalesOrderItineraryListLogisticsProvABCSImpl or composite application validation system (CAVS) based on the filter condition and operation.
This is a synchronous BPEL process. This process accepts a QueryTransportationSalesOrderItineraryListEBM as input from TransportationSalesOrderEBS, transforms this message into TransportationSalesOrderItineraryListOTMABM, and invokes the logistics webservice. This service transforms the LogisticsResponseEBM message to QueryTransportationSalesOrderItineraryListResponseEBM, and sends the message back to TransportationSalesOrderEBS.