|Bookshelf Home | Contents | Index | PDF|
The Siebel General Ledger Analytics application uses the Group ID when data is posted at a detail level. The Group ID identifies one set of offsetting debits and credits. Each time the debits and credits are offset, the Group ID is reset.
In relation to Siebel General Ledger Analytics, the Group ID changes each time the debits and credits offset each other. Although the sales order number is the same, the Group ID changes. In this way, the Group ID relates a single record on the sales order side to multiple records in Siebel General Ledger Analytics. From the sales order perspective, the Group ID changes when the line item changes.
Similar to loading header-level data, the Siebel General Ledger Analytics application also loads detail-level data from the SAP R/3 tables BKPF and BSEG into six staging tables, then into their IA tables. However, the Siebel General Ledger Analytics application uses staging tables for detail-level data to determine three data streams—invoice, sales order, and others.
When loading data at the detail level, Siebel General Ledger Analytics first extracts and loads transactional data from the SAP R/3 tables BKPF and BSEG into the same three staging tables that it does for loading header level information—
In this next phase of loading detail-level information, the Siebel General Ledger Analytics application selects all invoice lines from
For invoice lines data, sales invoice lines data is extracted from
When creating header tables, the tables
Similar to the Invoice Lines data, when creating header tables, the subitems of the sales order lines are created. The tables (
|Siebel Customer-Centric Enterprise Warehouse Installation and Configuration Guide|