List of files
File | Edition | Content |
|---|---|---|
Standard Edition | Details of objects (like description or other attributes/properties) | |
Standard Edition | Relations between Reporting Elements, InfoProvider, DataSources, and Transformations | |
Premium Edition/Extended Edition | Buildup of the objects with their contained fields or rules (in case of Transformations) | |
Premium Edition | Mappings between InfoObjects and Fields across InfoProvider, DataSource, and Transformations | |
Premium Edition | Descriptions on Field/InfoObject Level |
Standard cases
In all the files we use IDs for entities and Field/InfoObjects.
The ID include the object type in every case. A list with all object types can be found here.
Entities
For entities the IDs are a combination of the SAP internal identifier, a separator “|”, and the entity type.
The normal case is <object ID>|<object type>, but there are exceptions (see chapter exceptions).
Examples:
BW Query: 00O2TFIS8KH7TIIRUUIONW8BZ|REP (00O2TFIS8KH7TIIRUUIONW8BZ is the UID and SAP internal identifier)
CompositeProvider: /IMO/V_FIGL03|HCPR
Calculated Key Figure: 18GYMPC6EXPPMBD8WHA5HY6TD|CKF (18GYMPC6EXPPMBD8WHA5HY6TD is the UID and SAP internal identifier)
Fields
For Fields/InfoObjects and Elements (locale Formulas, local Selection, Restricted and Calculated Key Figures) the IDs are a combination of the SAP internal identifier of the Field/InfoObject, a separator “|”, and the parent entity ID.
The normal case is <field/InfoObject ID>|<object ID>|<object type>, but there are exceptions (see chapter exceptions).
Examples:
Calculated Key Figure in BW Query: 055QGZV4AT4XGFL1YQUULKE0G|055QGZV4AT4XFZSRLRULRR4OO|REP
Field/InfoObject in CompositeProvider: 0AC_LEDGER|/IMO/V_FIGL03|HCPR
Field/InfoObject in CKF: ZKEY11|18GYMPC6EXPPMBD8WHA5HY6TD|CKF
Transformation Rules
Transformation rules are part of the Mappings file and the Buildup file. The IDs are a combination of the SAP internal identifier of the Rule (Number as ID), a separator “|”, and the parent entity ID.
The normal case is <rule ID>|<Transformation ID>|TRFN
Examples:
13|0T4W0HM2PKJ5TE4UCESXS6SVP5X9ITQN|TRFN
6|0T4W0HM2PKJ5TE4UCESXS6SVP5X9ITQN|TRFN
Exceptions
DataSources
For DataSources we have another identifier, the logical system. This identifier is written on the second place. The same is done for fields of DataSources, where the logical system is on the third place.
In general rules we have
DataSources: <DataSource ID>|<logical System>|<object type>
Fields of DataSources: <field ID>|<DataSource ID>|<logical System>|<object type>
Examples
DataSource: Z_2LIS_02_HDR|BW4CDS|RSDS
Field of DataSource: EBELN|Z_2LIS_02_HDR|BW4CDS|RSDS
Fields of Open ODS Views
Open ODS Views can contain one or two so called semantics. The semantics can contain the same fields. So we have to distinguish between the semantics (there are 3 different types - F, M, and T). For that reason we inserted a semantics identifier on the second place:
General rule
<field ID>|<Semantics ID>|<Open ODS View ID>|FBPA
Example
CONT_ITEM|F|ZPUROV01|FBPA
Navigation Attributes
In some places you will fine navigation attributes which are written in an exceptional way. The navigation attribute can be found on the second place.
That logic is needed, because their description can be overwritten on multiple places in SAP.
Open ODS Views
In Open ODS Views you can find Navigation Attributes in form of
<field ID>|<Navigation Attribute ID>|<Semantics ID>|<Open ODS View ID>|FBPA
example:
COMP_CODE|0COMPANY|F|ZDL_ODS04|FBPA
CompositeProvider
In CompositeProvider you can find Navigation Attributes in form of
<field/InfoObject ID>|<Navigation Attribute ID>|<CompositeProvider ID>|HCPR
example:
0NOTIFICATN|0NOTIFICATN__0BATCH|/IMO/V_QM02|HCPR