A PLM - Cross-References for the Process Integration for Product Management

This appendix describes the cross references used in the process integration for product lifecycle management (PLM) and provides information about the product synchronization flow and the discount synchronization flow.

This appendix contains the following sections:

• Section A.1, "Integration Solution Cross-References"

• Section A.2, "Product Synchronization Flow"

• Section A.3, "Discount Synchronization Flow"

A.1 Integration Solution Cross-References

Table A-1 lists the integration solution cross-references.

Table A-1 Integration Solution Cross-References

Operation	Entity	Siebel CRM ID	Oracle BRM ID
Inserts/Refers	ITEM_ITEMID	Product ID	Product ID
Inserts/Refers	PRICELINE_ID (main products only)	Price Line ID to Common ITEM_ITEMID of main product	Product ID
Inserts/Refers	PRICELINETYPE_ID (for event/special type products)	Price Line ID to Common ITEM_ITEMID	Generated Product ID for Event products (ProductIDEvent Name)
Inserts/Refers	SIEBELPRODUCTEVENTXREF	Common ITEM_ITEMID for the parent product to Common PRICELINETYPE_ID for event product	$

A.1.1 Cross-Reference Values

The following values denote the entries made to the cross-reference table and what they mean.

ITEM_ITEMID: cross references the Oracle BRM (Portal) ProductID and the Siebel CRM ProductID.

COMMON: auto generated GUID

BRM_01: POID of BRM Product ABM.

SEBL_01: ProductID of Siebel Product ABM.

PRICELINE _ID: cross references the Oracle BRM (Portal) Product ID to Siebel CRM PriceLineID. Also links to the COMMON of ITEM_ITEMID.

COMMON: auto generated GUID.

BRM_01: POID of BRM Product ABM.

SEBL_01: Siebel PriceListItemID for the main product.

ITEM_ID_COMMON: From ITEM_ID.COMMON.

PRICELINETYPE _ID: cross references Oracle BRM (Portal) Product's Event to Siebel CRM PriceLineID. Also links to the COMMON of ITEM_ITEMID.

COMMON: Auto generated GUID.

BRM_01: POID of BRM Product ABM + Event Name.

SEBL_01: Siebel PriceListItemID for the event product.

ITEM_ID_COMMON: From ITEM_ID.COMMON.

SIEBELPRODUCTEVENTXREF: cross references Oracle BRM (Portal) Product's Event that is associated with the main product in Siebel CRM.

ITEM_ID_COMMON: From ITEM_ID.COMMON

LINEPRICETYPECODE: PRICELINETYPE _ID.COMMON

A.2 Product Synchronization Flow

Figure A-1 illustrates the events that occur for product synchronization. Tables Table A-2, Table A-3, Table A-4, Table A-5, Table A-6, Table A-7, and Table A-8 describe the entries that are made in the XREF_DATA table for each event.

Figure A-1 Product Synchronization Flow

1. Before the call 3, which SyncProductBRMCommslReqABCSImpl makes to SyncItemCompositionListSiebelCommsProvABCSImpl, the entries listed in Table A-2 are made in the XREF_DATA table.

   Table A-2 XREF_DATA

   XREF_TABLE_NAME	VALUE
   ITEM_ITEMID	<POID of BRM product>
   ITEM_ITEMID	COMMON GUID1

   
   

2. During the response back from Siebel CRM to SyncItemCompositionListSiebelCommsProvABCSImpl, the entry listed in Table A-3 is made in the XREF_DATA table.

   Table A-3 XREF_DATA

   XREF_TABLE_NAME	VALUE
   ITEM_ITEMID	<ProductID in Siebel >

   
   

3. Before the call 5 from SyncProductBRMCommslReqABCSImpl to ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl is made, the entries listed in Table A-4 are made in XREF_DATA table.

   Table A-4 XREF_DATA

   XREF_TABLE_NAME	VALUE
   PRICELINE_ID	POID of BRM product
   PRICELINE_ID	COMMON GUID2
   PRICELINETYPE_ID	POID of BRM Event product
   PRICELINETYPE_ID	COMMON GUID2

   
   

4. Before the call 6 from ProductOptimizedSyncPriceListListSiebelProvABCSImpl to SyncItemCompositionListSiebelCommsProvABCSImpl is made, the entries listed in Table A-5 are made in the XREF_DATA table.

   Table A-5 XREF_DATA

   XREF_TABLE_NAME	VALUE
   SIEBELPRODUCTEVENTXREF	LINEPRICETYPECODE GUID2
   SIEBELPRODUCTEVENTXREF	ITEM_ID_COMMON GUID1

   
   

5. During the response from SyncItemCompositionListSiebelCommsProvABCSImpl for the call 7, the entries listed in Table A-6 are made in the XREF_DATA table.

   Table A-6 XREF_DATA

   XREF_TABLE_NAME	XREF_COLUMN_NAME
   ITEM_ITEMID	COMMON GUID2
   ITEM_ITEMID	< ProductID in Siebel of Event Product >

   
   

   Note:

   For the simple product synchronization, the previous call is not made because the main product is synchronized as an Item.

6. Before the call 8 from ProductOptimizedSyncPriceListListSiebelProvABCSImpl to Siebel System is made, the entries listed in Table A-7 are made in the XREF_DATA table.

   Table A-7 XREF_DATA

   XREF_TABLE_NAME	VALUE
   PRICELINE_ID	ITEM_ID_COMMON
   PRICELINETYPE_ID (in case of multi-event product)	ITEM_ID_COMMON

   
   

7. During the response from the Siebel system, ProductOptimizedSyncPriceListListSiebelProvABCSImpl, the entries listed in Table A-8 are made in the XREF_DATA table.

   Table A-8 XREF_DATA

   XREF_TABLE_NAME	VALUE
   PRICELINE_ID	< ProductID in Siebel for Event Product >
   PRICELINETYPE_ID (in case of multi-event product)	< ProductID in Siebel for Event Product >

   
   

A.2.1 Simple Product Synchronization Example

Consider an actual scenario in which a simple product is being synchronized from Oracle Communications Billing and Revenue Management (Oracle BRM) to Siebel Customer Relationship Management (Siebel CRM).

Simple product synchronization example:

1. Create products in Oracle BRM to be synchronized with Siebel CRM, as shown in Figure A-2.

   Figure A-2 Create Products in Oracle BRM

   
   

2. Verify the synced records in Siebel CRM, as shown in Figure A-3.

   Figure A-3 Synced Records in Siebel CRM

   
   

3. Verify the data entered into the XREF_DATA table is correct as shown in tables Table A-9, Table A-10, Table A-11, Table A-12, Table A-13, and Table A-14.

   These tables show how data entered into the cross-reference table correspond to the points 1 through 7 explained previously.

Table A-9 Table corresponding to point 1

$	XREF_TABLE_NAME	XREF_COLUMN_NAME	ROW_NUMBER	VALUE
1	ITEM_ITEMID	BRM_01	<ROWNUM_1>	<BRM_PROD_01>
2	ITEM_ITEMID	COMMON	<ROWNUM_1>	<COMMON_PROD_01>

Table A-10 Table corresponding to point 2

$	XREF_TABLE_NAME	XREF_COLUMN_NAME	ROW_NUMBER	VALUE
1	ITEM_ITEMID	SEBL_01	<ROWNUM_1>	<CRM_PROD_01>

Table A-11 Table corresponding to point 3

$	XREF_TABLE_NAME	XREF_COLUMN_NAME	ROW_NUMBER	VALUE
1	PRICELINE_ID	BRM_01	<ROWNUM_2>	<BRM_PROD_01>
2	PRICELINE_ID	COMMON	<ROWNUM_2>	<COMMON_PRICE_ID1>
3	PRICELINETYPE_ID	BRM_01	<ROWNUM_3>	<BRM_PROD_01_EVENT1>
4	PRICELINETYPE_ID	COMMON	<ROWNUM_3>	<COMMON_PRICETYPE_ID1>

Table A-12 Table corresponding to point 5

$	XREF_TABLE_NAME	XREF_COLUMN_NAME	ROW_NUMBER	VALUE
1	SIEBELPRODUCTEVENTXREF	LINEPRICETYPECODE	<ROWNUM_4>	<COMMON_PRICETYPE_ID1>
2	SIEBELPRODUCTEVENTXREF _ID	ITEM_ID_COMMON	<ROWNUM_4>	<COMMON_PROD_01>

Table A-13 Table corresponding to point 7

$	XREF_TABLE_NAME	XREF_COLUMN_NAME	ROW_NUMBER	VALUE
1	PRICELINE_ID	ITEM_ID_COMMON	<ROWNUM_2>	<COMMON_PROD_01>
2	PRICELINE_ID	SEBL_01	<ROWNUM_2>	<CRM_PRICE_01>

Table A-14 Complete entry for product sync

$	XREF_TABLE_NAME	XREF_COLUMN_NAME	ROW_NUMBER	VALUE
1	ITEM_ID	BRM_01	<ROWNUM_1>	<BRM_PROD_01>
2	ITEM_ID	COMMON	<ROWNUM_1>	<COMMON_PROD_01>
3	ITEM_ID	SEBL_01	<ROWNUM_1>	<CRM_PROD_01>
4	PRICELINE_ID	BRM_01	<ROWNUM_2>	<BRM_PROD_01>
5	PRICELINE_ID	COMMON	<ROWNUM_2>	<COMMON_PRICE_ID1>
6	PRICELINETYPE_ID	BRM_01	<ROWNUM_3>	<BRM_PROD_01_EVENT1>
7	PRICELINETYPE_ID	COMMON	<ROWNUM_3>	<COMMON_PRICETYPE_ID1>
8	SIEBELPRODUCTEVENTXREF	LINEPRICETYPECODE	<ROWNUM_4>	<COMMON_PRICETYPE_ID1>
9	SIEBELPRODUCTEVENTXREF _ID	ITEM_ID_COMMON	<ROWNUM_4>	<COMMON_PROD_01>
10	PRICELINE_ID	ITEM_ID_COMMON	<ROWNUM_2>	<COMMON_PROD_01>
11	PRICELINE_ID	SEBL_01	<ROWNUM_2>	<CRM_PRICE_01>

A.2.2 Complex Product Synchronization Example

Consider the scenario in which a complex product is being synchronized from Oracle BRM to Siebel CRM.

Complex product synchronization example:

1. Create products in Oracle BRM to be synchronized with Siebel CRM, as shown in Figure A-4.

   Figure A-4 Create Products in Oracle BRM

   
   

2. Verify the synced records in Siebel CRM, as shown in Figure A-5.

   Figure A-5 Synced Records in Siebel CRM

   
   

3. Verify the data entered into the XREF_DATA table is correct as shown in tables Table A-15, Table A-16, Table A-17, Table A-18, Table A-19, Table A-20, and Table A-21.

   These tables show how data entered into the cross-reference table correspond to the points 1 through 7 explained previously.

Table A-15 Table corresponding to point 1

$	XREF_TABLE_NAME	XREF_COLUMN_NAME	ROW_NUMBER	VALUE
1	ITEM_ITEMID	BRM_01	<ROWNUM_1>	<BRM_PROD_01>
2	ITEM_ITEMID	COMMON	<ROWNUM_1>	<COMMON_PROD_01>

Table A-16 Table corresponding to point 2

$	XREF_TABLE_NAME	XREF_COLUMN_NAME	ROW_NUMBER	VALUE
1	ITEM_ITEMID	SEBL_01	<ROWNUM_1>	<CRM_PROD_01>

Table A-17 Table corresponding to point 3

$	XREF_TABLE_NAME	XREF_COLUMN_NAME	ROW_NUMBER	VALUE
1	PRICELINE_ID	COMMON	<ROWNUM_2>	<BRM_PROD_01>
2	PRICELINE_ID	BRM_01	<ROWNUM_2>	<COMMON_PRICE_01>
3	PRICELINETYPE_ID	COMMON	<ROWNUM_3>	<COMMON_PRICETYPE_01>
4	PRICELINETYPE_ID	BRM_01	<ROWNUM_3>	<BRM_PROD_01_EVENT1>
5	PRICELINETYPE_ID	BRM_01	<ROWNUM_4>	<BRM_PROD_01_EVENT2>
6	PRICELINETYPE_ID	COMMON	<ROWNUM_4>	<COMMON_PRICETYPE_02>

Table A-18 Table corresponding to point 4

	XREF_TABLE_NAME	XREF_COLUMN_NAME	ROW_NUMBER	VALUE
1	SIEBELPRODUCTEVENTXREF	LINEPRICETYPECODE	<ROWNUM_4>	<COMMON_PRICETYPE_01>
2	SIEBELPRODUCTEVENTXREF _ID	ITEM_ID_COMMON	<ROWNUM_4>	<COMMON_PROD_01>

Table A-19 Table corresponding to point 5

$	XREF_TABLE_NAME	XREF_COLUMN_NAME	ROW_NUMBER	VALUE
1	ITEM_ID	COMMON	<ROWNUM_5>	<COMMON_PROD_02>
2	ITEM_ID	SEBL_01	<ROWNUM_5>	<CRM_PROD_02>

Table A-20 Table corresponding to points 6 and 7

$	XREF_TABLE_NAME	XREF_COLUMN_NAME	ROW_NUMBER	VALUE
1	PRICELINE_ID	ITEM_ID _COMMON	<ROWNUM_3>	<COMMON_PRICETYPE_01>
1	PRICELINE_ID	SEBL_01	<ROWNUM_3>	<CRM_ITEM_PRICE_01>
2	PRICELINETYPE_ID	ITEM_ID _COMMON	<ROWNUM_4>	<COMMON_PRICETYPE_02>
2	PRICELINETYPE_ID	SEBL_01	<ROWNUM_4>	<CRM_ITEM_PRICE_02>

Table A-21 Complete entry for product sync

$	XREF_TABLE_NAME	XREF_COLUMN_NAME	ROW_NUMBER	VALUE
1	ITEM_ID	BRM_01	<ROWNUM_1>	<BRM_PROD_01>
2	ITEM_ID	COMMON	<ROWNUM_1>	<COMMON_PROD_01>
3	ITEM_ID	SEBL_01	<ROWNUM_1>	<CRM_PROD_01>
4	PRICELINE_ID	COMMON	<ROWNUM_2>	<BRM_PROD_01>
5	PRICELINE_ID	BRM_01	<ROWNUM_2>	<COMMON_PRICE_01>
6	PRICELINETYPE_ID	COMMON	<ROWNUM_3>	<COMMON_PRICETYPE_01>
7	PRICELINETYPE_ID	BRM_01	<ROWNUM_3>	<BRM_PROD_01_EVENT1>
8	PRICELINETYPE_ID	BRM_01	<ROWNUM_4>	<BRM_PROD_01_EVENT2>
9	PRICELINETYPE_ID	COMMON	<ROWNUM_4>	<COMMON_PRICETYPE_02>
10	SIEBELPRODUCTEVENTXREF	LINEPRICETYPECODE	<ROWNUM_4>	<COMMON_PRICETYPE_01>
11	SIEBELPRODUCTEVENTXREF _ID	ITEM_ID_COMMON	<ROWNUM_4>	<COMMON_PROD_01>
12	ITEM_ID	COMMON	<ROWNUM_5>	<COMMON_PRICETYPE_02>
13	ITEM_ID	SEBL_01	<ROWNUM_5>	<CRM_PROD_02>
14	PRICELINE_ID	ITEM_ID _COMMON	<ROWNUM_3>	<COMMON_PRICETYPE_01>
16	PRICELINE_ID	SEBL_01	<ROWNUM_3>	<CRM_ITEM_PRICE_01>
15	PRICELINETYPE_ID	ITEM_ID _COMMON	<ROWNUM_4>	<COMMON_PRICETYPE_02>
17	PRICELINETYPE_ID	SEBL_01	<ROWNUM_4>	<CRM_ITEM_PRICE_02>

Figure A-6 shows a high-level overview of how the mappings are maintained in the cross-reference table.

Figure A-6 Cross-Reference Table

A.3 Discount Synchronization Flow

Figure A-7 illustrates the events that occur for the discount synchronization flow.

Figure A-7 Discount Synchronization Flow

1. Before the call 3, which SyncDiscountBRMCommsReqABCSImpl makes to SyncItemCompositionListSiebelCommsprovABCSImpl, the entries listed in Table A-22 are made in the XREF_DATA table: ITEM_ITEMID, COMMON, POID of BRM product.

   Table A-22 XREF_DATA

   XREF_TABLE_NAME	VALUE
   ITEM_ITEMID	COMMON GUID
   ITEM_ITEMID	<POID OF BRM PRODUCT>

   
   

2. During the response from the Siebel system, a SyncItemCompositionListSiebelCommsProvABCSImpl the entry listed in Table A-23 is made in the XREF_DATA table with the value: ProductID of Siebel Product.

   Table A-23 XREF_DATA

   XREF_TABLE_NAME	VALUE
   ITEM_ITEMID	<PRODUCTID OF SIEBEL PRODUCT>

   
   

A.3.1 Discount Synchronization Example

Consider an actual scenario in which a discount is being synchronized from Oracle BRM to Siebel CRM.

Discount synchronization example:

1. Create discounts in Oracle BRM to be synchronized with Siebel CRM, as shown in Figure A-8.

   Figure A-8 Create Discounts in Oracle BRM

   
   

2. Verify the synced records in Siebel CRM, as shown in Figure A-9.

   Figure A-9 Synced Records in Siebel CRM

   
   

3. Verify the data entered into the XREF_DATA table is correct as shown in Figure A-10 and Figure A-11.

   These tables show how data entered into the cross-reference table correspond to points 1 and 2 explained previously.

   Figure A-10 Figure Corresponding to Point 1

   
   

   Figure A-11 Figure Corresponding to Point 2