Hierarchy

⤷

⤷

Basic Data
Data Element | GBIWPIDELTA_VIA_AIED |
Short Description | Determination of Delta Using AIED Process |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | BOOLE | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | AIED |
Medium | 19 | AIED (After Image) |
Long | 34 | AIED (After Image from Totals Tab) |
Heading | 50 | AIED (After Image from Totals Table) |
Documentation
Definition
Use
If you opt for this delta procedure, the Time Stamp field is used in an initial step to select all of the records changed since the last delta load in the totals table. In a second step, all logically dependent records for the records selected in the initial step (such as the equivalent credit record for a debit record) are selected subsequently and transferred to BW.
Advantages:
- Postings can be made during delta initialization
- Data is available in BW in a timely fashion
- Relatively good performance when relatively few totals records have been added or changed between two delta transfers
- No start routine required to calculate the Balance key figure
Disadvantages:
- Severe performance problems when very many totals records have been added or changed between two delta transfers
- Relatively high volume of data is transferred to BW
- DSO or ODS is required due to overwrite mode (with restriction to a maximum of 16 key fields!)
- Additional secondary index on totals table is necessary for the Time Stamp field
Notes on System Performance
Due to the above-mentioned two-step procedure, this delta procedure can only transfer approximately 1000 totals records (which correspond to between 50 000 and 70 000 records in BW due to the period and currency block size in the totals record) per minute to BW. Consequently, we only recommend using this procedure if only relatively few totals records are added or changed between two delta transfers. If a relatively large number of totals records are added or changed between two delta transfers, this procedure invariably leads to severe performance problems. Almost 2 hours are required for 100 000 extracted totals records, for example.
If this procedure leads to performance problems that persist after SAP Note 1056245 has been applied, you need to use a different delta procedure.
Further Important Notes on this Procedure
If you opt for this procedure, you need to make sure that the update type Overwrite is selected for all key figures in the transformation to DSO or in the update rule for the ODS.
Furthermore, it is essential that you ensure that all relevant characteristics of the transfer structure are defined as key fields in the DSO or ODS because data could otherwise be lost. For more information, see SAP Note 1002272.
Dependencies
Example
History
Last changed by/on | SAP | 20100310 |
SAP Release Created in |