Entering content frame

Dummy text General Ledger (New): Transaction Figures Locate the document in its SAP Library structure

Technical name: 0FIGL_O10

Use

This ODS object is required for the delta process of the DataSource General Ledger: Balances, Leading Ledger (0FI_GL_10). It contains all the totals records (transaction figures) from new General Ledger Accounting that were uploaded from the connected source system(s) using the InfoSource General Ledger (New): Transaction Figures . The DataSource works in the after image process. This means that it always delivers the totals records with the latest status from the OLTP system. In the ODS object, the difference (or delta) from the previously extracted total is calculated.

All fields from the InfoSource must be transferred to the ODS object.

Key Fields

Key Field

Description

Structure link0VERSION

Version

Structure link0COMP_CODE

Company code

Structure link0FISCPER

Fiscal year/period

Structure link0GL_ACCOUNT

G/L account

Structure link0FUNC_AREA

Functional area

Structure link0COSTCENTER

Cost center

Structure link0VTYPE

Reporting value type

Structure link0PROFIT_CTR

Profit center

0SEGMENT

Segment for segment reporting

Structure link0FISCVARNT

Fiscal year variant

Structure link0CURTYPE

Currency type

Structure link0VALUATION

Valuation view

0CURKEY_TC

Currency key: Transaction currency

Structure link0UNIT

Unit of measure

0VTYPE

The characteristic Record Type in FI-SL is displayed on the InfoObject Value Type:

Record types 0 and 2 are converted into value type 10: record type 0 = actual; record type 2 = actual assessment.

Record types 1 and 3 are converted into value type 20: record type 1 = plan; record type 3 = plan assessment.

0CURKEY_TC

This is always the currency key of the transaction currency; it is also filled for records with a different currency type. Without this key field, postings with different transaction currencies would be overwritten after summarization and thereby be lost.

The InfoObject 0CURKEY_TC is filled with data from field RTCUR in the transfer structure and should not be confused with the InfoObject 0CURRENCY (which is filled with data from CURRUNIT). The InfoObject 0CURRENCY contains the currency key for the current currency type and does not have to be the key field of the ODS object because the field Currency Type (0CURTYPE) is already used as the key.

Caution

All fields from the transfer structure must be updated to the ODS object. Otherwise, data may be lost, as in the following examples:

1. The new field ZZCUST is in the transfer structure, but not in the ODS object. The extractor delivers the following data in a request:

COMP_CODE

FISCPER

ZZCUST

DEBIT

1000

001.2004

1000

100

1000

001.2004

2000

50

Apart from the field ZZCUST, the data in all data records is the same for all key fields (underlined).

If the data is then updated using MOVE logic, both data records in the ODS object would overwrite each other. In this example, the data record with DEBIT = 100 would be missing from the data updated to the InfoCube:

COMP_CODE

FISCPER

DEBIT

1000

001.2004

50

For this reason, each key field of the transfer structure in the ODS object must be used to create the key (at least logically); Summarization is not possible here. The data can be summarized in the extractor (you need to remove a characteristic from the transfer structure) or in the update rules in the InfoCube.

The ODS object may only contain a maximum of 16 key fields. The remaining fields have to be updated as ordinary data fields. Note that no data records are lost as a result of undesired summarization due to missing or incorrect key fields.

2. The data is updated into the ODS object when ZZCUST is in the data part and does not depend on a key of the ODS object:

COMP_CODE

FISCPER

ZZCUST

DEBIT

1000

001.2004

2000

50

If these characteristics do not already depend on other key fields of the ODS object (such as the controlling area depends on the key field Company Code), you can include a technical key in the ODS object that is unique for all "logical key fields in the data part". Take, for example, a field that originates as a result of the concatenation of all "logical key fields" in the data part. This field must then be filled correspondingly in the update rules in the ODS object.

Navigational Attributes

The navigational attributes are derived automatically from the InfoObjects.

Delta Update

This ODS object is intended for the delta update MOVE with the DataSource General Ledger: Balances, Leading Ledger (0FI_GL_10). The DataSource delivers an after image, that is, changed totals records are always transferred from the OLTP system as the new data set, which has to overwrite existing data when updated to the ODS object.

 

 

 

Leaving content frame