Setting Up Siebel Financial Services Customer Order Management for Banking

This chapter covers tasks for setting up Siebel Financial Services Customer Order Management for Banking. It includes the following topics:

Roadmap for Setting Up Siebel Financial Services Customer Order Management for Banking

All users must perform some required tasks to set up Siebel Financial Services Customer Order Management for Banking. You might have to perform some additional tasks depending on your business model. For more information about the required and optional tasks, see the following:

Required Tasks

To set up and work with Siebel Financial Services Customer Order Management for Banking, all users perform the following tasks:

Activating Workflow Processes for Siebel Financial Services Customer Order Management for Banking. Some order management for financial services functionality is based on workflow processes for Siebel CRM. You must activate these workflow processes.
Setting Up Products and Catalogs. You must define products and create product catalogs, and make the catalogs available to users. Optionally, you can define price lists that assign prices to products.
Modeling the Financial Product. You must define the product type, ownership, UI template, and attributes.

Optional Tasks

In addition, depending on your business model, you might have to perform some of the following tasks to complete the setup of order management:

Setting up pricing. Optionally, you can set up price lists and assign prices to products. For example, you can create multiple price lists if you sell the same products to different customers at different prices. If you want to use pricing, you must perform additional setup tasks. For information about setting up price lists, see Siebel Pricing Administration Guide.
Setting up asset-based ordering. Asset-based ordering is available with the Siebel Financial Services Customer Order Management for Banking module. If you want to use asset-based ordering, you must perform additional setup tasks. For more information, see Siebel Order Management Guide.
Defining Configurator eligibility rules. You must define eligibility rules to specify which customers are eligible to buy products. For more information, see Siebel Product Administration Guide.
Setting up needs-analysis. You must create needs analysis scripts and set up product scores to determine what financial products and services can be offered to customers. For more information, see Siebel Finance Guide.
Setting up recommendations. You can display additional product recommendations to customers when they select products. For more information, see Siebel Order Management Guide.

Activating Workflow Processes for Siebel Financial Services Customer Order Management for Banking

Siebel Financial Services Customer Order Management for Banking is based on workflow processes and business services for Siebel CRM that you can configure. You can customize ordering to meet the order management requirements of your company.

You must activate all workflows under following workflow categories before using the product:

Eligibility and Compatibility
Pricer
Product Promotions
Product Recommendation
Asset Based Ordering
Configurator
Marketing
FINS AcctOrig
C/OM UI Processes

For information about activating workflow processes, see Siebel Business Process Framework: Workflow Guide.

Modeling the Financial Product

Siebel Financial Services Customer Order Management for Banking uses a customizable product model that allows customers to use the entire order management framework. In Siebel Financial Services Customer Order Management for Banking, contacts can be added as applicants and assigned ownership roles for financial product components. Every financial product can have multiple applicants and owners.

Siebel Financial Services Customer Order Management for Banking is customizable. However, to use Asset Based Ordering (ABO) logic, a financial product must be created as a Customizable Product, and its type must be Fin Account. In addition, an Applicant must be created as a Customizable Product and the product type must be Owner. The applicant must always maintain a child relationship with the financial product, and this cannot be changed. To understand these concepts, refer to the Gold Package Offering product, which is provided as an example. For help on how to obtain this sample product file, create a service request (SR) on My Oracle Support, For more information about products, see Siebel Product Administration Guide on Oracle Technology Network (http://www.oracle.com/technetwork/indexes/documentation/index.html).

Using the Existing Contact and Financial Account Relationships with Siebel Financial Services Customer Order Management for Banking

In Siebel Finance, the relationship between a contact and a financial account is stored in the S_ASSET_CON intersection table. Siebel Financial Services Customer Order Management for Banking stores the contact and financial account relationship in the S_ASSET table. If you have existing data in the S_ASSET_CON table, then it must be migrated to the S_ASSET table in order for it to be usable in Siebel Financial Services Customer Order Management. At this time, Oracle does not provide a migration script.

It is strongly recommended that you use only the S_ASSET table. There are a number of vertical applications and customers that have added functionality that leverage the S_ASSET_CON table to represent contact relationships to an asset as well as drive business component logic that leverages this association to display the results to the user in a number of views throughout the application.

Because of this use of the S_ASSET_CON table in legacy configurations, Oracle provides a business service that you can use with runtime events, which can update the S_ASSET_CON table whenever assets in the S_ASSET table are modified. The following image shows the S_ASSET_CON business service.

For more information about owner records, see Modeling the Financial Product.

S_ASSET_CON Business Service. In this image, Asset Business Component R/T Event is connected to New/Update/Delete Record Event? At this decision point, If No, End. If Yes, PROD_ID is Contact Pseudo Product ID? At this decision point, If No, End. If Yes, Extract: PAR_ASSET_ID, OWNER_CON_ID REL_TYPE_ID Field Values. This is connected to: Do UpSert on S_ASSET_CON where S_ASSET.PAR_ASSET_ID arrow S_ASSET_CON.ASSET_ID S_ASSET.OWNER_CON_ID arrow S_ASSET_CON.CONTACT_ID S_ASSET.REL_TYPE_ID arrow S_ASSET_CON.RELATION_TYPE_CD.

Setting Up Products and Catalogs

Before you can create orders, you must do the following:

Set up products. Define the products that are being sold. If the products have attributes, you can set up a class system to manage the attributes before defining the products. If you have customizable products that have other products as their components, you must specify the components and design the selection pages that users will see. For information about setting up products, see Siebel Product Administration Guide on Oracle Technology Network (http://www.oracle.com/technetwork/indexes/documentation/index.html).
Set up product catalogs. Users can select products for customers from product catalogs and add them to an order. When you create a catalog, you specify what products are included in it, and arrange them in a hierarchy of categories. When catalogs are set up, users can browse through categories to find products, and they can search for products using full-text search or parametric search. For more information about setting up product catalogs, see Siebel Order Management Guide on Oracle Technology Network (http://www.oracle.com/technetwork/indexes/documentation/index.html).