...
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 | Buildup of the objects with their contained InfoObject, Fields, and Rules + some additional information | |
Premium Edition | Mappings between InfoObjects, Fields, and Rules across BW Queries, InfoProvider, DataSource, and Transformations | |
Premium Edition | Descriptions of Fields, InfoObjects, and Rules | |
Premium Edition | all content of Premium edition in one uml like file |
Standard cases
In all the files we use IDs for entities and Field/InfoObjects.
The ID include includes the object type in every case. A list with all object types can be found here.
...
For DataSources we have another identifier, the logical system. This identifier is written on in the second place. The same is done for fields of DataSources, where the logical system is on in the third place.
In general rules we have
...
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 in the second place:
General rule
...
Navigation Attributes
In some places, you will fine find navigation attributes which that are written in an exceptional a special way. The navigation attribute can be found on in the second place.
That logic is needed , because their description can be overwritten on in multiple places in SAP.
Open ODS Views
In Open ODS Views you can find Navigation Attributes in the form of
<field ID>|<Navigation Attribute ID>|<Semantics ID>|<Open ODS View ID>|FBPA
...
In CompositeProvider you can find Navigation Attributes in the form of
<field/InfoObject ID>|<Navigation Attribute ID>|<CompositeProvider ID>|HCPR
...