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

Configuring the Siebel Receivables Analytics Balance Extract

This task is a step in the Process of Configuring Siebel Financial Analytics for SAP R/3.

By default, the Accounts Receivable (AR) Key ID (KEY_ID) is configured as follows:

Customer_number||'~'||Company_code||'~'||Client

Therefore, the Accounts Receivable balance is maintained by customer number, company code, and client code. The client code is used to distinguish between different instances of SAP R/3. For example, if you are running one instance of SAP R/3 for your U.S. business, and another instance of SAP R/3 in your Japan business, you may have the same AR account numbers that refer to different accounts in each system. To distinguish the same GL account numbers in different instances the grain of the balance is set to include the client code.

To change the grain at which you accumulate the balances, modify the Key ID definition in the Expression transformation in the applicable mapping. Note that there are two sets of mappings—the balance extract mappings and the initial fact load mappings. The extract provides the balance from the source to staging tables. The initial fact load mappings move the data from staging tables to the data warehouse.

To configure the balance extract for the AR Balance

1. In PowerCenter Designer, open the Configuration for SAP R/3 folder.
2. In Mapplet Designer, open the M_S_GL_XACTS_EXTRACT_SPLIT mapping.
3. Double-click the Expression transformation to open the Edit Transformations window.
4. Edit Key_ID.

   Make sure the AR Key ID in the extract mapping is the same precision as the AR Balance ID in the fact load mapping.

5. Validate and save your changes to the repository.
6. Repeat Step 2 to Step 5 for the following mappings, if you are configuring Siebel Enterprise Sales Analytics with Siebel Financial Analytics, and the sales and purchase subledger post to the General Ledger at the header level:
   • M_S_AR_XACTS_HDR_SALES_IVCLNS_DERIVE
   • M_S_AR_XACTS_HDR_SALES_ORDLNS_DERIVE
   • MS_AR_XACTS_OTHERS_DERIVE

     Repeat Step 2 to Step 5 for the following mappings, if you are configuring Siebel Enterprise Sales Analytics with Siebel Financial Analytics, and the sales and purchase subledger post to the General Ledger at the detail level:

   • M_S_AR_XACTS_DET_SALES_IVCLNS_KEYS_DERIVE
   • M_S_AR_XACTS_DET_SALES_ORDLNS_KEYS_DERIVE
   • M_S_AR_XACTS_OTHERS_DERIVE