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 Payables 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 a balance. There are three different IDs—General Ledger Balance ID, Accounts Payable Key ID, and Accounts Receivable Key ID. You set the default configurations to the most-representative grains for maintaining the three different balances.

By default, the Accounts Payable AP Key ID (KEY_ID) is configured as follows:

Vendor__creditor__account_number||'~'||Company_code||'~'||Client

Therefore, you use the vendor or creditor account number, company code, and client code to maintain the Accounts Payable Balance. 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 in your Japan business, you may have the same AP account numbers in each system, which refer to different accounts. To distinguish the same GL account numbers in different instances, you set the grain of the balance to include the client code.

To configure the balance extract for the AP 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 AP_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_AP_XACTS_HDR_SALES_IVCLNS_DERIVE
   • M_S_AP_XACTS_HDR_SALES_ORDLNS_DERIVE
   • MS_AP_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_AP_XACTS_DET_SALES_IVCLNS_KEYS_DERIVE
   • M_S_AP_XACTS_DET_SALES_ORDLNS_KEYS_DERIVE
   • M_S_AP_XACTS_OTHERS_DERIVE