Working with BOR Objects and BW-InfoObjects 

If you want to create a correlation between BW InfoObjects and BOR objects (Business Object Repository), you have to define it manually with the Relationship Editor.

You can see the D&R-compatible links between BOR objects and BW InfoObjects in the list of Characteristics Compatible with Drag&Relate.

With all other InfoObjects and BOR objects the following has to be taken into account:

Correlations are only useful if a 1:1 key relationship exists between the BW characteristic and the BOR object. Furthermore the length and order of the key fields have to agree. In addition Drag&Relate can work with transitive relations.

For example you are able to drag the characteristic Plant (0PLANT) to an SAP transaction that contains information on the factory. This navigation is possible because of the 1:1 key relationship between 0PLANT and the corresponding Business Object Repository (BOR) object BUS0008.

For example, you can drag the characteristic Business Partner (0BPARTNER) to a SAP transaction that contains information on the characteristic if 0PLANT is a navigation attribute of 0BPARTNER.

If the characteristic does not have a 1:1 relationship to the BOR object and no characteristic attribute with a 1:1 key relationship to the BOR object is available, additional data modeling in the BW is necessary to make D&R possible. If the characteristic that you want to use for D&R does not have the necessary key it is, in straightforward cases, possible to attain the desired result by modeling and adding an attribute with the corresponding key.

If a 1:1 key relationship is maintained between 0MATERIAL and BOR object BUS1001, you can automatically execute D&R between a compound characteristic such as 0MAT_PLANT and BUS1001 (the keys of which do not correspond 1:1), as long as 0MATERIAL has been maintained as an attribute of 0MAT_PLANT.

These “generic“ D&R mappings function for attributes, compounding, and navigation attributes.

InfoObjects and BOR objects are also often semantically different. In such cases it is possible that you have to generate a new D&R characteristic in BW that corresponds to the BOR object.

Check whether it is possible to model your scenario using the report-report interface instead of Drag&Relate first.