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 General Ledger Analytics Balance Extract

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

The Balance and Key IDs set the grain at which you want to maintain the balances. There are three different IDs—General Ledger Balance ID, Accounts Payable Key ID, and Accounts Receivable Key ID. The default configurations are set to the most representative grains for maintaining the three different balances.

By default, the General Ledger Balance ID (BALANCE_ID) is configured as follows:

Account_number||'~'||Company_code||'~'||Business_area||'~'||Client

Therefore, the General Ledger Account, Company Code, Business Area, and Client Code maintain the General Ledger Balances. You use the Client Code 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 for your Japan business, you may have the same General Ledger Account numbers in each system referring to different accounts. To distinguish the same General Ledger Account numbers in different instances, the grain of the balance includes the Client Code.

To change the grain at which you accumulate the General Ledger balance, modify the Balance ID or Key ID definition in the Expression transformation in the applicable mapping. Note that there are two sets of mappings—the balance extract mapping and the initial fact load mapping. The extract moves the balance from the source to staging tables, and the initial fact load mappings move the data from staging tables to the data warehouse. The following procedure provides instructions on how to configure the balance extract.

To configure the balance extract for the General Ledger 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 GL_BALANCE_ID.
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_GL_XACTS_HDR_SALES_IVCLNS_DERIVE
   • M_S_GL_XACTS_HDR_SALES_ORDLNS_DERIVE
   • MS_GL_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_GL_XACTS_DET_SALES_IVCLNS_KEYS_DERIVE
   • M_S_GL_XACTS_DET_SALES_ORDLNS_KEYS_DERIVE
   • M_S_GL_XACTS_OTHERS_DERIVE