| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
List of files
File |
|---|
Level | Content |
|---|---|
Object level | Details of objects (like description or other attributes/properties) |
Object level | Relations between Reporting Elements, InfoProvider, DataSources, and Transformations | |
InfoAreas.<SID>.xml | Object level | Tree structure of BW InfoAreas with their descriptions. |
Premium Edition
Extended Edition
Field and code level | Buildup of the objects with their contained InfoObject, Fields, and Rules + some additional information |
Field level | Mappings between InfoObjects, Fields, and Rules across BW Queries, InfoProvider, DataSource, and Transformations |
Field level | Descriptions of Fields, InfoObjects, and Rules |
Object and field level | all content of |
object and field level in one uml like file |
Standard cases
In all the files we use IDs for entities and Field/InfoObjects.
...
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:
...
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
...
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 in the second place:
General rule
<field ID>|<Semantics ID>|<Open ODS View ID>|FBPA
Example
CONT_ITEM|F|ZPUROV01|FBPA
...
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
example:
COMP_CODE|0COMPANY|F|ZDL_ODS04|FBPA
...
In CompositeProvider you can find Navigation Attributes in the form of
<field/InfoObject ID>|<Navigation Attribute ID>|<CompositeProvider ID>|HCPR
example:
0NOTIFICATN|0NOTIFICATN__0BATCH|/IMO/V_QM02|HCPR