5 Process Integration for Price Lists

This chapter provides an overview of the process integration for price lists and discusses loading initial and incremental price lists, and solution assumptions and constraints.

This chapter includes the following section:

• Section 5.1, "Process Integration for Price Lists"

5.1 Process Integration for Price Lists

The process integration for price lists is different from the other integrations in the Order to Cash pre-built integration. The price list integration provides an initial bulk load process and an incremental load process that both use Oracle Data Integrator (ODI) to update price list data from Oracle E-Business Suite (Oracle EBS) to Siebel Customer Relationship Management (Siebel CRM).

The price list integration between Oracle EBS and Siebel CRM supports the following integration flows:

• Initial or bulk load: This flow enables the extract, transformation, and load (ETL) of initial price list data from Oracle EBS to Siebel CRM.

  This feature uses ODI to extract relevant data from Oracle EBS and map it to Siebel CRM interface tables. This process also enables cross-referencing between Oracle EBS and Siebel CRM.

• Incremental load: This flow moves new price lists and lines or updates to existing price lists from Oracle EBS into Siebel CRM for use in the order capture process.

For more information about initial data loads, see Chapter 2, "Loading Initial Data."

For more information about incremental loads, see Chapter 14, "Loading Initial Price List Data"

The price list integration point is different from that of other data types, such as customer and product. Use the bulk load feature to synchronize changes to active price list data in the Oracle EBS database to the Siebel CRM database. Changes after the initial bulk load can be either the creation of new price lists or updates to the header and line information of existing price lists.

The incremental bulk loads create or update price lists or the header and line information in the Siebel CRM database, depending on whether the price lists or the header and line information exist in that database.

If you change the name of a price list in Oracle EBS, a new price list with that name is created in Siebel CRM. Siebel CRM does not delete or rename the original price list. You can do that manually if required.

If Pricing Security is turned on and if a price list is not global, you must initialize the context in Oracle EBS before synchronizing price list lines.

To initialize, use the QP_CRMINTEG_PRICELIST_V view and the following statement:

fnd_global.apps_initialize(<User ID>, <Responsibility ID>,<Application id>);
For example: fnd_global.apps_initialize(1318, 24021, 661);
 

To make a price list nonglobal, clear the Global check box on the Oracle EBS price list screen. You can use a nonglobal price list only in the operating unit set in the Oracle EBS profile MO: Operating Unit.

If you change the start date of a price list in Oracle EBS, the system creates a new price list with the same name in the Siebel database. However, if you change only the end date of a price list in Oracle EBS, the system updates the existing price list in the Siebel database.

5.1.1 Prerequisites

Find prerequisites in Section 13.4, "Price Lists: Prerequisites."

5.1.2 Solution Assumptions and Constraints

The integration design assumes that the following statements are true:

1. Only a bulk load process is supported.

   • ODI pulls all of the order-related active price lists from Oracle EBS into Siebel CRM.

   • To synchronize incremental loads, run the same process but specify the price list names that pull those price lists and lines from Oracle EBS into Siebel CRM, including any changes to those price lists. The process updates or creates price lists and lines, depending on whether the price list and lines exist in Siebel CRM.

2. Order-capture related active price lists from Oracle EBS to Siebel CRM are synchronized as part of the initial load.

3. Price lists such as those used by purchasing, interoffice, contracts, and so on are not synchronized.

4. Price list header information (such as name, currency, start date, and end date), and price list line information (such as product, list price, start date, and end date) are synchronized.

   Advanced pricing features, such as volume discount, attribute pricing, qualifier, and so on, are not synchronized.

For more information about initial data loads, see Chapter 2, "Loading Initial Data."

For more information about incremental loads, see Chapter 14, "Loading Initial Price List Data"