Siebel Customer-Centric Enterprise Warehouse Installation and Configuration Guide > Configuring Siebel Enterprise Sales Analytics > Process of Configuring Siebel Enterprise Sales Analytics for SAP R/3 >

About Tracking Attribute Changes in Bookings

Changes in booked orders are tracked in the Booking Lines table (IA_SALES_BKGLNS), not in the Sales Order Lines table (IA_SALES_ORDLNS). By default, the only changes tracked in the IA_SALES_BKGLNS table are changes in the ordered amount, ordered quantity, or Booking ID. By default, the Booking ID is defined as:

EXT_SALES_ORDER_NUM ||'~'|| TO_CHAR(EXT_SALES_ORDER_ITEM)||'~'|| EXT_MATERIAL_NU||'~'||EXT_CLIENT_CODE

Any changes in these fields results in another row in the IA_SALES_BKGLNS table. However, changes in any other fields does not result in a new row; instead, the existing information are overwritten with the changed information. No history is kept for changes to these other field values. If you want to track other changes you can do so. For example, you may want to track changes to the sales representative who is handling the order. The ETL processes are prepackaged to overwrite sales representative changes; however, if you want to retain them, you must add the attribute to the Booking ID definition in the Booking ID expression in the Source Adapter mapplet (MPLT_SAI_SALES_ORDLNS). The following section describes what happens if you modify the Booking ID to include the sales representative.

About Viewing the Data Warehouse Changes by Salesperson ID

Assume you want to track changes to the sales representative for bookings and debookings. You decide to do this to better evaluate each representative's sales performance. To track changes by Salesperson ID, you have to modify the VAR_BOOKING_ID to use the value:

EXT_SALES_REP_NUM_VAR

The following paragraphs and tables describe what happens in the source system and the IA_SALES_BKGLNS table when you change sales representatives under this scenario.

Day 1: One order is placed with Salesperson 1001. The source system displays the information as shown in Table 32.

The row in Table 36 is entered into the IA Bookings table (IA_SALES_BKGLNS) as shown in Table 33.

Day 2: Salesperson 1002 takes over this order, replacing Salesperson 1001. Thus, the salesperson associated with the order is changed from 1001 to 1002 in the source system. The row in the source system looks like the row shown in Table 34.

The Sales Order Lines ADI, which also writes to the booking table, now does a debooking for the old line and inserts a new row into the IA_SALES_BKGLNS booking table. On day two, the row in the IA_SALES_BKGLNS table looks like the row shown in the Table 35.