The following are the few design considerations when reporting for New General Ledger Accounting module is implemented in SAP BW. This is applicable for the following data sources.

0FI_GL_10           General Ledger: Balances, Leading Ledger

3FI_GL_xx_TT      General Ledger (New): Balances from Any Ledgers (Generated)

0FI_GL_14           General Ledger Accounting (New): Line Items of the Leading Ledger

3FI_GL_XX_SI      General Ledger Accounting (New): Line Items of Any Ledger (Generated)

Factors / Delta Methods

AIED

ADD

ADDD

DSO

Mandatory

Not required

Not required

Update type for key figures

Over write

Addition (if DSO is used)

Addition (if DSO is used)

Data load performance

Considerable performance problems if a large number of totals records are added or changed between two delta transfers. In particular, performance can drop dramatically when the balance carry forward or mass postings are executed during the year-end closing activities.

Good performance if there are large data volumes

Very good performance if there are large data volumes

Data volume

Relatively high data volumes are transferred to BW.

Relatively low data volume is transferred to BI

Since the data is aggregated only in a logical unit of work (LUW) for totals records, the data volume transferred to BI is usually greater than the volume transferred during the method ADD

ECC downtime during delta initialization

Not required

A posting-free period must be ensured in ECC

A posting-free period must be ensured in ECC

Planning data in delta mode

Planning data can be extracted in delta mode

No planning data can be extracted in delta mode

No planning data can be extracted in delta mode. (However , this can be enabled using a modification with SAP note)

Key figure 0BALANCE

Data is available by default

It has to be calculated in start routine in BW.  The prerequisite for using this method is that line items are written in period 0.

It has to be calculated in start routine in BW

Data availability in BW

Data in BW is current

1 hour latency. Upper safety interval of an hour, that is, only line items that are MORE THAN ONE HOUR OLD are transferred to BI. This safety interval is NOT allowed to be reduced because this would risk posting records being lost during the extraction.

Data in BW is current

Additional Index in ECC

An additional secondary index is required for the totals table for the field TIMESTAMP

Additional index for the TIMESTAMP field in the line item table required

No additional index is required in the totals table or the line item table

Recommendation

This delta method can transfer only about 1,000 totals records each minute to BW. Therefore, this delta method is recommended only if a relatively low number of totals records are added or changed between two delta transfers.

For example, almost two hours are required for 100,000 extracted totals records.

If there are large data volumes, this method is faster than the method AIED described previously. It is particularly efficient if a large number of the SAME characteristic combinations are posted between two delta transfers (for example, numerous postings to the value-added tax account with the same profit center) because, in this case, the selected line items are transferred to BW in aggregated form

This method is the best alternative in most cases if there are large data volumes because of its performance advantages compared with the two other methods(AIED & ADD). The data is aggregated only in a LUW, this method is most efficient if relatively few DIFFERENT characteristic combinations are posted between two delta transfers (for example, all postings are made to different profit centers)

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply