| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
TODO Alexander Dürrstein
...
File | Edition | Content |
|---|---|---|
Standard Edition | ||
Standard Edition | Relations between Reporting Elements, InfoProvider, DataSources, and Transformations | |
Premium Edition | ||
Premium Edition | Mappings between InfoObjects and Fields across InfoProvider, DataSource, and Transformations | |
Premium Edition | Descriptions on Field/InfoObject Level | |
… coming soon … | Extended Edition |
Standard cases
...
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:
...
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:
...
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
...
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>|<logical System>|<object type>
Example
CONT_ITEM|F|ZPUROV01|FBPA