Skip Headers
Oracle® Application Integration Architecture Order Management Integration Pack for Oracle Transportation Management, Oracle E-Business Suite and Siebel CRM Implementation Guide
Release 3.1.1

Part Number E20504-05
Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Feedback page
Contact Us

Go to previous page
Go to next page
PDF · Mobi · ePub

6 Process Integration for Order

This chapter provides an overview of the process integration for transportation orders and includes the following sections:

6.1 Overview

In the transportation order management solution, transportation orders are created in Siebel CRM application and executed in Oracle Transportation Management (OTM) application. New or revised orders are synchronized in one direction from Siebel to OTM. Whenever a new transportation order is submitted in Siebel, a real time synchronization flow is initiated to publish it to AIA. AIA creates a corresponding order release, and sell shipment in OTM.

6.2 Business Process Flows

The process integration for order supports these integration flows:

Each Siebel transportation order includes these components:

The prices of the transportation, accessorial, and special service lines are retrieved from Oracle Transportation Management (OTM) through the order itinerary/rating integration as described in Chapter 5, "Process Integration for Query Transportation Order Itinerary".

Corresponding to a transportation order in Siebel, the AIA synchronization process creates an order release and a sell shipment in OTM.

The major components of order release synchronized to OTM are:

The major components of sell shipment synchronization to OTM are:

Figure 6-1 shows the order process integration:

Figure 6-1 Order Process Integration Flow

Description of Figure 6-1 follows
Description of "Figure 6-1 Order Process Integration Flow"

This diagram shows that the Siebel application sends all its order messages in a queue. An AIA service reads that queue, gets the messages, and further sends the message to requester. Inside the requester service, Siebel application business message (ABM) message is transformed to the SyncTransportationSalesOrderListEBM, and then this service sends that EBM to transportation sales order EBS.

The TransportationSalesOrderEBS routes that SyncTransportationSalesOrderListEBM to Oracle Transportation Management (OTM) provider. Inside the provider, the EBM message is transformed to OTM ABM and that OTM ABM is send to OTM webservice to create or modify the order.

6.2.1 Synchronizing Order Information

Figure 6-2 shows the incremental changes in the account:

Figure 6-2 Synchronizing Order Information Sequence Diagram

Description of Figure 6-2 follows
Description of "Figure 6-2 Synchronizing Order Information Sequence Diagram"

6.3 Assumptions and Constraints

These are the assumptions and constraints:

6.4 Siebel CRM Interfaces

Use the Order schema for this integration. The interface required for updating the order in Siebel is Siebel order web services definition language (WSDL).

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.

6.5 Oracle Transportation Management Interfaces

The Oracle Transportation Management (OTM) application provides an interface through a webservice to connect to its application. This connectivity is established as a partner link in the provider service. The logistics webservice immediately returns an acknowledgment with a transmission number when called and sends a transmission report back indicating the success or the failure when the process completes.

For more information about the Logistics Service, see Oracle Transportation Management Integration Guide.

6.6 Core Application Integration Architecture Components

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".

6.7 Integration Services

This integration delivers these services:

6.7.1 AIA Transportation Sales Order Queue

This transportation sales order queue is used to queue Siebel order messages. This is an AQ. This queue can reside any oracle database. For this integration, AIA database is used as the place for this queue. The queue name is AIA_SiebelTransportationSalesOrderJMSQueue.

6.7.2 TransportationSalesOrderListSiebelConsumer

TransportationSalesOrderListSiebelConsumer is the consumer to the queue that is invoked when OTM places a message into the AIA_SiebelTransportationSalesOrderJMSQueue queue. This service routes and invokes SyncTransportationSalesOrderListSiebelReqABCSImpl service.

6.7.3 SyncTransportationSalesOrderListSiebelReqABCSImpl

SyncTransportationSalesOrderListSiebelReqABCSImpl is a BPEL process. This process receives Siebel application business message (ABM) as an input from Siebel system and transforms the message to SyncTransportationSalesOrderListEBM. During this transformation, Siebel ABM is transformed to SyncTransportationSalesOrderListEBM and enterprise business message (EBM) Header and cross-reference tables are populated. This process invokes TransportationSalesOrderEBS with SyncTransportationSalesOrderListEBM as an input. This process then waits for the response back from the TransportationSalesOrderResponseEBS. Based on the response received this service updates the Siebel application indicating whether the order synchronized or failed.

6.7.4 TransportationSalesOrderEBS

TransportationSalesOrderEBS is an Enterprise Business Service. This service is used to route all transportation sales order related actions like CreateTransportationSalesOrder, QueryTransportationSalesOrder, SyncTransportationSalesOrderList, and UpdateTransportationSalesOrder, and so on.

6.7.5 TransportationSalesOrderResponseEBS

TransportationSalesOrderResponseEBS is the Enterprise Business Service. This service is used to route all transportation sales order response actions like CreateTransportationSalesOrderResponse, QueryTransportationSalesOrderResponse, SyncTransportationSalesOrderListResponse, UpdateTransportationSalesOrderResponse, and so on.

6.7.6 SyncTransportationSalesOrderListLogisticsProvABCSImpl

SyncTransportationSalesOrderListLogisticsProvABCSImpl is a BPEL process. This process receives SyncTransportationSalesOrderListEBM as a request from TransportationSalesOrderEBS and returns a response to TransportationSalesOrderResponseEBS. This service transforms the EBM to Oracle Transportation Management (OTM) ABM and invokes the logistics webservice using the OTM ABM. At the end the cross-reference table is updated with OTM data. Then a response message is prepared and sent back to TransportationSalesOrderResponseEBS.