How Order Management Integrates with eBusiness Suite

Oracle Order Management and Oracle eBusiness Suite use connectors and web services that you set up to communicate details about each of your sales orders.

Sales Order Flow

Here's how the detail flows between Order Management and eBusiness Suite when you create a sales order.

Note

1. You create a sales order in the Order Management work area.

2. Order Management uses routing rules that you set up to determine how to route the sales order to eBusiness Suite, including the connector it will use to do routing.

3. Order Management uses a connector that you set up on the Manage Connector Details page to identify the location of the connector on the SOA server (Service Oriented Architecture). For this example, assume you named the server My_SOA_Server.

4. Order Management uses fulfillment tasks to transform the sales order to a message, and then send it to DooFulfillOrderEBSConnector on My_SOA_Server.

5. The SOA server transforms the message, uses the set up you make in Integrated SOA Gateway on eBusiness Suite to call a web service on the gateway, and then send the message to eBusiness Suite.

6. eBusiness Suite processes the message as a sales order.

   eBusiness Suite uses a business event during processing.

   For example, if eBusiness Suite schedules the sales order for shipping, or if eBusiness Suite changes scheduled ship date or scheduled arrival date because some other attribute that influences scheduling changes, then eBusiness Suite uses a business event, and then uses the event to send these dates to Order Management. It also sends the warehouse and ship method.

   eBusiness Suite uses the set up you do on business events in eBusiness Suite to communicate status changes. You enable the business event, subscribe to it so eBusiness Suite knows when to use it, and specify the web service to use when communicating with My_SOA_Server.

7. eBusiness Suite uses your set up for the web service and business event in Integrated SOA Gateway to send the update to the connector on My_SOA_Server.

8. The connector on My_SOA_Server server sends status updates to Order Management.

9. Order Management updates sales order attributes in the Order Management work area.

Order Management also uses this flow for a status update or order line split. Other flows use a similar sequence.

Flow Through SOA Server

Note

1. The fulfillment task in Order Management uses DooEBSConnectorService to call the fulfillOrderEBSRequest operation of DooFulfillOrderEBSConnector on My_SOA_Server.

   Connector Attribute	Value
   Partner Link	DooEBSConnectorService This value is the name of the connector.
   Port Type	FulfillOrderEBSProcess
   Operation	fulfillOrderEBSRequest

   The fulfillment task in Order Management manages the create flow, update flow, and hold flow.

2. The fulfillment task uses the security that you set up in Oracle Enterprise Manager and the WebLogic Console on My_SOA_Server. The user and password that you use in Enterprise Manager must match the user and password you use on the Manage Connector Details page.

   For details, see Oracle Enterprise Manager.

3. My_SOA_Server uses the set up you do in Enterprise Manager and WebLogic Console to call the Sales Order Service in Integrated SOA Gateway on eBusiness Suite. The user and password you use in Enterprise Manager must match the user and password you use in eBusiness Suite.

4. An event happens in eBusiness Suite that requires communication with Order Management, such as an update to the sales order status.

5. Sales Order Service in eBusiness Suite calls the fulfillOrderEBSInboundRequest operation on DooFulfillOrderEBSConnector.

   Connector Attribute	Value
   Partner Link	DooEBSConnectorInboundService_ep
   Port Type	FulfillOrderEBSProcess
   Operation	fulfillOrderEBSInboundRequest

   eBusiness Suite uses the security you set up in Enterprise Manager on My_SOA_Server for the eBusiness Suite user that calls DooFulfillOrderEBSConnector.