Siebel Customer-Centric Enterprise Warehouse Installation and Configuration Guide > Configuring Siebel Strategic Sourcing Analytics >

Configuring Expenses for Post-Load Processing

Post-load processing procedures for Expenses allow expense cycle time analysis and update aggregate tables when data captures are performed at different frequencies. Each of these features require some configuration to best suit your organization's needs.

About the S_M_PLP_EXPENSES_INVOICE_UPD_ALT Session

The Siebel Business Analytics prepackage M_PLP_EXPENSES_INVOICE_UPD to run at the same frequency as the NU_AP_XACTS table load, which is its source. NU_AP_XACTS is truncated before each load of the IA_AP_XACTS table. This truncation can lead to data loss if you decide to run the sessions that update NU_AP_XACTS at different times other than when you execute your post-load update processes.

CAUTION:  To prevent data loss resulting from truncation of the NU_AP_XACTS table, you must run an alternate PLP mapping that uses IA_AP_XACTS as a source, as described in this topic. This is because this table always contains a set of invoice data.

Depending on how frequently you want to update data that is already loaded in the Siebel Customer-Centric Enterprise Warehouse, you must use one of the following tasks:

• If you change the update mapping frequency on a regular basis, disable the S_M_PLP_EXPENSES_INVOICE_UPD session and schedule S_M_PLP_EXPENSES_INVOICE_UPD_ALT session to run in its place.
• If you miss a single run of the S_M_PLP_EXPENSES_INVOICE_UPD session, run the S_M_PLP_EXPENSES_INVOICE_UPD session, but do not disable the S_M_PLP_EXPENSES_INVOICE_UPD_ALT session.

The S_M_PLP_EXPENSES_INVOICE_UPD_ALT session is found in the Sessions directory.

About Implementing Temporary Storage When Aggregate Load Frequencies Are Modified

The Siebel Business Analytics designed IA_EXPENSES and IA_EXPENSES_A1 loads to be synchronized in order to populate NU_EXPENSES at the same time. An incremental snapshot table, NU_EXPENSES is truncated before every load, which can cause data loss for the time period if IA_EXPENSES and IA_EXPENSES_A1 are loaded asynchronously.

CAUTION:  To prevent data loss resulting from truncation of the NU_EXPENSES table, the incremental data from NU_EXPENSES must be stored temporarily until it is loaded into the aggregate table. Therefore, you must build an intermediate table and modify M_PLP_EXPENSES_A1_DERIVE to source from it. Your new intermediate table must have the same structure as the NU_EXPENSES table and be set to truncate before loading the IA_EXPENSES_A1.