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

1-1

Copyright 2007, Oracle. All rights reserved.

Architecture for Order Management

Siebel

Siebel
ABCS

BRM
EBS

ABCS

BRM

BRM GL
BRM
Report in XML
JCA Adapter

Oracle SOA
Suite
Oracle
Application
Server

1-2

Copyright 2007, Oracle. All rights reserved.

Order Management Solution

Siebel
CRM

Integration

ProcessSales
Order
JMSProducer
Process
SalesOrder
JMSConsumer

Siebel

2
.Process
JMS/
AQ

SOO
EBS

Apps

Process
Sales Order
Siebel
ABCS Req

14

Update
SORDLine
Siebel ABCS
Prov

Oracle
BRM

Interface
Customer
to Billing
EBF

Interface
Order to
Customer
EBF

BRM
Apps

Order
Orch

Sales
Order
EBS

.Update

Flow

Portal
Sync
Order
ABCS

SOO
EBS

.Interface
Order to
Billing

Line
Status

Synchronous
Asynchronous

1-3

* Order Orchestration flow is not shipped in this release

Copyright 2007, Oracle. All rights reserved.

Sequence Flow for the Order Management

Process Integration
1

ProcessSales
Order
JMSProducer
Process
SalesOrder
JMSConsumer

Siebel

2
.Process
JMS/
AQ

SOO
EBS

Process
Sales Order
Siebel Req
ABCS

14

Update
SORDLine
Siebel ABCS
Prov

Interface
Order to 8
Customer
EBF

Oracle

ORCH
5

Sales
Order
EBS
Line
Status

SOO
EBS

Flow

.Interface
11

.Update

13

Interface
Customer
to Billing
EBF

Order

Apps

Order to
Billing

12

Portal
Sync
Order
ABCS

10

BRMS

Synchronous
Asynchronous

1-4

* Order Orchestration flow is not shipped in this release

Copyright 2007, Oracle. All rights reserved.

Integration Artifacts
Industry Components

EBO
SalesOrderEBO

EBM
ProcessSalesOrderEBM
UpdateSalesOrderLineStatusEBM
EBS
SalesOrderEBS
Create, Update

SalesOrderOrchestrationEBS
Process, InterfaceOrdertoCustomer,InterfaceOrdertoBilling
1-5

Copyright 2007, Oracle. All rights reserved.

Integration Artifacts
Application 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
1-6

Copyright 2007, Oracle. All rights reserved.

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

1-7

Copyright 2007, Oracle. All rights reserved.

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.

1-8

Copyright 2007, Oracle. All rights reserved.

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
1-9

Copyright 2007, Oracle. All rights reserved.

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

1 - 10

Copyright 2007, Oracle. All rights reserved.

Configuration Steps
Oracle BRM, continued
BRM Services used in this integration:
PCM_OP_CUST_MODIFY_CUSTOMER
Used for creation of new services, update of existing services
PCM_OP_SUBCRIPTION_PURCHASE_DEAL
Used when new product/discount needs to be added to a service
PCM_OP_CUSTOMER_UPDATE_SERVICE
Used for updating the Service ID Login.
PCM_OP_CUST_SET_STATUS
Used for updating the status of the service Active/Inactive/Closed
PCM_OP_READ_FLDS
Used for reading Portal Object Information
1 - 11

Copyright 2007, Oracle. All rights reserved.

Configuration Steps
Oracle BRM, continued
BRM Services used in this integration:
PCM_OP_SUBCRIPTION_CANCEL_PRODUCT
Used for Deleting a Product
PCM_OP_SUBCRIPTION_CANCEL_DISCOUNT
Used for Deleting a Discount
PCM_OP_SUBSCRIPTION_TRANSFER_SUBCRIPTION
Used for transferring a service from one account to another
PCM_OP_SUBSCRIPTION_SET_PRODINFO
Used for communicating price overrides
PCM_OP_SEARCH
Used for fetching Portal data
1 - 12

Copyright 2007, Oracle. All rights reserved.

Configuration Steps
AIA
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.

1 - 13

Copyright 2007, Oracle. All rights reserved.

Configuration Steps
AIA, 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.

1 - 14

Copyright 2007, Oracle. All rights reserved.

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

1 - 15

Copyright 2007, Oracle. All rights reserved.

Describing the Integration Solution

Integration 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

1 - 16

Copyright 2007, Oracle. All rights reserved.

Describing the Integration Solution

Integration Points, continued
Siebel CRM Integration Points
Inbound Web Services:
Update Order Item Status
Outbound Workflows:
Submit Order

1 - 17

Copyright 2007, Oracle. All rights reserved.

Describing the Integration Solution

Out-of-the-Box Routing Rules
Default routing rules are provided for connecting the out-ofthe-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.
1 - 18

Copyright 2007, Oracle. All rights reserved.

Describing the Integration Solution

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

1 - 19

Copyright 2007, Oracle. All rights reserved.

Describing the Integration Solution

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

1 - 20

Copyright 2007, Oracle. All rights reserved.

Describing the Integration Solution

Domain Value Maps
DVMS (set up as part of the install)

1 - 21

SALESORDER_STATUS
SALESORDER_ACTIONCODE
SALESORDER_LINESTATUS
PRICE_TYPE
CURRENCY_CODE

Copyright 2007, Oracle. All rights reserved.

Describing the Integration Solution

Cross References
XREF Configuration

Operation

Entity

Siebel CRM Id

Inserts/Refers

InstalledProduct

Inserts
Refers
Refers
Refers

OrderLine
Order Line Id
CustomerPartyAccount Account Id
Item
Product Id
Customer Party Bill
Bill Profile Id
Profile
CUSTOMERPARTY_PA Bill Profile Id
YPROFILEID
Customer Party Default
BG

Refers
Refers

Asset Integration Id

Oracle BRM Id
Service Instance Id,
Purchased Product Id,
Purchased Discount Id
NA
Account Id
Product Id
Bill Info
Pay Info Id
Default Balance Group
ID for a Common
Account Id

1 - 22

Copyright 2007, Oracle. All rights reserved.

Describing the Integration Solution

Error 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)

1 - 23

Copyright 2007, Oracle. All rights reserved.

Describing the Integration Solution

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

1 - 24

Copyright 2007, Oracle. All rights reserved.

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

1 - 25

Copyright 2007, Oracle. All rights reserved.