order management technical toi ready

Copyright © 2007, Oracle. All rights reserved.1 - 1

Objectives

After completing this course, you should be able to:• Describe the architecture and sequence for the Process

Integration for Order Management• Define the integration artifacts• Describe design assumptions• Describe the software installation process• Define the configuration steps • Configure Siebel CRM• Configure Oracle BRM • Configure the Order Management integration


Architecture for Order Management

SiebelBRM GL

Report in XMLBRMSiebelABCS

BRMABCSEBS

Oracle SOA Suite

BRMJCA Adapter

Oracle Application

Server


Order Management Solution

SiebelCRM

Integration Oracle BRM

Synchronous

Asynchronous

* Order Orchestration flow is not shipped in this release

Portal Sync Order ABCS

BRM Apps

8

Interface Customer to Billing

EBFSiebelApps

OrderOrchFlow

Update SORDLine

Siebel ABCS Prov 14

.Update Line

Status

SalesOrderEBS

SOOEBS

.Process

SOOEBS

.Interface Order to Billing

Interface Order to

Customer EBF

Process SalesOrder

JMSConsumer

JMS/ AQ

ProcessSalesOrder

JMSProducer

2

Process Sales Order

Siebel ABCS Req

4


Sequence Flow for the Order Management Process Integration

Synchronous

Asynchronous

Portal Sync Order ABCS

OracleBRMS

6

8

Interface Customer to Billing

EBFSiebelApps

OrderORCHFlow

Update SORDLine

Siebel ABCS Prov 14 13 12

.Update Line

Status

SalesOrderEBS

SOOEBS

.Process

SOOEBS

.Interface Order to Billing

Interface Order to

Customer EBF

11

9 10

87Process

SalesOrder JMSConsumer

JMS/ AQ

ProcessSalesOrder

JMSProducer

1 2

Process Sales Order Siebel Req

ABCS

4

3

5

* Order Orchestration flow is not shipped in this release


Integration ArtifactsIndustry Components

EBO• SalesOrderEBO

EBM• ProcessSalesOrderEBM• UpdateSalesOrderLineStatusEBM

EBS• SalesOrderEBS

– Create, Update

• SalesOrderOrchestrationEBS– Process, InterfaceOrdertoCustomer,InterfaceOrdertoBilling


Integration ArtifactsApplication Interfaces

ABCS Components– ProcessSalesOrderSiebelReqABCSImpl (BPEL

Implementation)– ProcessBillingPortalProvABCSImpl (BPEL Implementation)– UpdateSORDLineSiebelProvABCSImpl (BPEL

Implementation)

Transport Services (AQ)– ProcessSalesOrderSiebelJMSProducer (BPEL

Implementation)– ProcessSalesOrderSiebelJMSConsumer (BPEL

Implementation)

Enterprise Business Flows (EBF)– InterfaceOrderToCustomer

Leslie Hayne

See verify notes in slide notes. need to add this info to slides that display BPEL and ESB


Describing the Software Installation Process

Environment:• Fusion Middleware: 10.1.3.3 SOA Suite• Oracle Siebel Communications : 7.8.2.6• Oracle BRMS – Release 7.3.1• Oracle BRM Adapter – Release 7.3.1

Location: • edelivery.oracle.com

Installation• Refer to the readme instructions available with the install

to perform the software installation


Describing the Design Assumptions

• The Process Integration for Product Management is available to synchronize the product data between the CRM and BRM. This product information is used in the Order flow.

• The Process Integration for Customer Management is available to synchronize the customer data between CRM and BRM. This service is invoked during the Order flow to create the customer in BRM.

• The product definition methodology (defined by Process Integration for Product Management) is followed. Customer data set-up complies with data requirements of the Process Integration for Customer Management.


Configuration Steps Siebel CRM

Configure Siebel CRM• Apply Siebel QF (Quick Fix) 2603 on Siebel 7.8.2.6.• Configure the web services required for AIA for Communications.

– Refer to Siebel QF2603 release notes.Schemas • Siebel QF includes the integration object that defines the Siebel

schema. This is also referred to as the Application Business Message (ABM).

• ListOfOrders is the ABM that Siebel sends out.Services • Siebel QF includes the following services that are used in the

integration:– CMUOrderSubmit– CMUOrderLineItemUpdate


Configuration Steps Oracle BRM

Configure Oracle BRM • Apply requisite patches to get BRM to version 7.3.1.• Perform the set-ups required for AIA for Communications.

(See the Oracle BRM documentation.)


Configuration Steps Oracle BRM, continued

BRM Services used in this integration:PCM_OP_CUST_MODIFY_CUSTOMERUsed for creation of new services, update of existing services

PCM_OP_SUBCRIPTION_PURCHASE_DEALUsed when new product/discount needs to be added to a service

PCM_OP_CUSTOMER_UPDATE_SERVICEUsed for updating the Service ID – Login.

PCM_OP_CUST_SET_STATUSUsed for updating the status of the service – Active/Inactive/Closed

PCM_OP_READ_FLDSUsed for reading Portal Object Information


Configuration Steps Oracle BRM, continued

BRM Services used in this integration:PCM_OP_SUBCRIPTION_CANCEL_PRODUCTUsed for Deleting a Product

PCM_OP_SUBCRIPTION_CANCEL_DISCOUNTUsed for Deleting a Discount

PCM_OP_SUBSCRIPTION_TRANSFER_SUBCRIPTIONUsed for transferring a service from one account to another

PCM_OP_SUBSCRIPTION_SET_PRODINFOUsed for communicating price overrides

PCM_OP_SEARCHUsed for fetching Portal data


Configuration StepsAIA

• Choose the server where SOA Suite is to be installed.• Install SOA Suite.• Identify the database where XREF database is to be

installed. (Preferably on the same database where the SOA dehydration exists).

• Set up JMS queue for storing inbound Sales Orders from Siebel.

• Please refer to AIA installation guide for further details.


Configuration StepsAIA, continued

• Install the BRM Adapter.• Login to Application Server Console

– Navigate to Oracle Home->Applications->Standalone Resource Adapters ->BRM Adapter

– Create Connection Factory — JNDI Location (eis/BRM)— Interface:

oracle.tip.adapter.api.OracleConnectionFactory— Connection Pool : Private

– Set the properties for the connection, based on the BRM environment.


Configuration Steps AIA, continued

AIAConfigurationProperties.xml settings:• CAVS Routing for ProcessSalesOrderSiebelReqABCSImpl,

ProcessBillingPortalProvABCSImpl and UpdateSORDLineStatusSiebelProvABCSImpl

• Use Default Balance Group for ProcessBillingPortalProvABCSImpl

• Siebel Web Service Path for UpdateSORDLineStatusSiebelProvABCSImpl


Describing the Integration SolutionIntegration Points

BRM Integration points:Inbound Opcodes (web services) used:•PCM_OP_CUST_MODIFY_CUSTOMER•PCM_OP_SUBCRIPTION_PURCHASE_DEAL•PCM_OP_CUSTOMER_UPDATE_SERVICE•PCM_OP_CUST_SET_STATUS•PCM_OP_READ_FLDS•PCM_OP_SUBCRIPTION_CANCEL_PRODUCT•PCM_OP_SUBCRIPTION_CANCEL_DISCOUNT•PCM_OP_SUBSCRIPTION_TRANSFER_SUBCRIPTION•PCM_OP_SUBSCRIPTION_SET_PRODINFO•PCM_OP_SEARCH


Describing the Integration SolutionIntegration Points, continued

Siebel CRM Integration Points

Inbound Web Services:• Update Order Item Status

Outbound Workflows:• Submit Order


Describing the Integration SolutionOut-of-the-Box Routing Rules

• Default routing rules are provided for connecting the out-of-the-box AIA processes. Any addition of new ABC services requires that the default routing is changed. • A test order orchestration process has also been shipped which first sets the target billing system in the order EBM and then orchestrates interfacing the customers from the order to billing, before interfacing the order itself. It also orchestrates the process for updating the appropriate order line status back to Siebel. • The test order orchestration gets called by default routing rule of the SalesOrderOrchestrationEBS.process operation. Implementers need to add their own orchestration and change the routing rule of SalesOrderOrchestrationEBS.process to route to it. This orchestration needs to set the target billing system before calling any of the AIA processes.

Leslie Hayne

leslie delete note in lecture notes if this slide is ok


Describing the Integration SolutionTransaction Management

• Supports “All-Or-None” Transactions. Either all lines in the Order Message are interfaced, or none of them are interfaced to billing.

• “Customer Creation” is treated as an individual transaction separate from the order. So “Customer Creation” in BRM could be successful even though an order fails.

• Uses BRM APIs: TRANS_OPEN, TRANS_COMMIT & TRANS_ABORT for providing transaction support. Code added in the BRM ABC service to support this.

• Set these properties: cacheConnections set to False and useJCAConnectionPool set to True in bpel.xml for the BRM ABC service.

Leslie Hayne

This slide or the next or a combination?


Describing the Integration SolutionTransaction Management [Order]

• Each call to a BRM ABC service is an atomic operation. In cases where multiple order lines passed, either all or none are processed.

• Uses the BRM APIs, TRANS_OPEN, TRANS_COMMIT and TRANS_ABORT for providing transaction support.


Describing the Integration Solution Domain Value Maps

DVMS (set up as part of the install)

• SALESORDER_STATUS• SALESORDER_ACTIONCODE• SALESORDER_LINESTATUS• PRICE_TYPE• CURRENCY_CODE


Describing the Integration SolutionCross References

XREF Configuration

Operation Entity Siebel CRM Id Oracle BRM Id Inserts/Refers InstalledProduct Asset Integration Id Service Instance Id,

Purchased Product Id, Purchased Discount Id

Inserts OrderLine Order Line Id NA Refers CustomerPartyAccount Account Id Account Id Refers Item Product Id Product Id Refers Customer Party Bill

Profile Bill Profile Id Bill Info

Refers CUSTOMERPARTY_PAYPROFILEID

Bill Profile Id Pay Info Id

Refers Customer Party Default BG

Default Balance Group ID for a Common Account Id


Describing the Integration SolutionError Handling

These are the standard Error Handling Framework services, there are no AIA specific errors thrown by Order Management services:

• AIAASyncErrorHandlingBPELProcess (BPEL Implementation)

• AIAReadJMSNotificationProcess (BPEL Implementation)

• AIAErrorTaskAdministrationProcess (BPEL Implementation)

Leslie Hayne

decide on which error handling slide we want


Describing the Integration SolutionError Handling

Services Used: • AIAAsyncErrorHandlingBPELProcess• AIAErrorTaskAdministrationProcess• AIAReadJMSNotificationProcess

Settings:• Fault Policy Update (at the service level)

– Retry Count.– Invoke Error Handling Code.

• Update E-Mail Address for Notification– Out of the box, all OM errors go to the default role:

AIAIntegration Admin role.• Update Error Codes.


Summary

In this course you have learned how to:• Describe the architecture and sequence for the Process

Integration for Order Management• Identify the integration artifacts• Describe design assumptions• Configure the Process Integration for Order Management

order management technical toi ready

Documents