SAP ABAP Data Element GBIWPIDELTA_VIA_ADDD (Determination of Delta Using ADDD Process)
Hierarchy
☛ SAP_FIN (Software Component) SAP_FIN
   ⤷ FI-SL-IS (Application Component) Information System
     ⤷ GBIW_PI (Package) FI-SL: Interface to Business Information Warehouse
Basic Data
Data Element GBIWPIDELTA_VIA_ADDD
Short Description Determination of Delta Using ADDD 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 ADDD 
Medium 19 ADDD (Queue) 
Long 34 ADDD (Delta Queue) 
Heading 50 ADDD (Additive Extraction Using Delta Queue) 
Documentation

Definition

Use

When you opt for this procedure, the delta upload is performed using a delta queue.

The delta queue is updated with every posting made to the relevant totals table in the ERP system (in the update task). With a delta upload, the data is read from this delta queue and transferred to BI. Once the data of the delta queue has been transferred successfully to BI, it is deleted from the delta queue after the next successful delta upload.

Advantages of using this procedure:

  • Good performance with large volumes of data
  • Data in BI is up to date
  • No DSO or ODS required
  • Additional index to totals table or line item table is not required

Disadvantages:

  • Since each posting is transferred to BI in a nonsummarized form, the expected data volume in BW is very large
  • Postings cannot be made during delta initialization (this has to be set up from an organizational point of view)

It is advisable to use this procedure with large volumes of data due to the advantages for performance. Since the data is not aggregated with this procedure, the procedure operates most efficiently when postings are made to many different characteristic combinations (such as all postings to different profit centers) between two delta transfers.

If you opt for this procedure, you need to make sure that the update type Addition is selected for all key figures when a DSO or ODS is used in the transformation to DSO or in the update rule for the ODS.

Caution

If you are interested in the noncumulative key figure Balance, you have to create a start routine in the transformation or update rule in BI (using the correction instructions for the program UPDATE_ROUTINE detailed in SAP Note 1153944).

With this start routine, Balance is calculated very quickly in BI.

Since an ODS is no longer required during this additive procedure, we recommend using the start routine in the transformation or the update rule for the InfoCube because this reduces the data volume, which consequently improves performance in BI.

For more information, see section 4 Additional Steps for the ADDD Procedure in SAP Note 1153944.

Dependencies

Example

History
Last changed by/on SAP  20100310 
SAP Release Created in 605