Consistency Check for Compounding 

With regard to compounding, characteristics and navigation attributes have to be identified consistently within a MultiProvider. Otherwise the query results may be inconsistent. Data records may appear in the MultiProvider that do not physically exist in any of the InfoProviders in the MultiProvider.

The system checks for consistency. If a MultiProvider is not consistently modeled, it cannot be activated. The system produces an error message. However, you can change this to a warning. This allows you to activate the MultiProvider anyway. Only do this if you are certain that it will not result in inconsistent values.

If you have upgraded from SAP BW 3.x to SAP NetWeaver 7.0, MultiProviders defined in SAP BW 3.x may be seen as being incorrect and can no longer be activated. In this case, check the definition and modify it as required. For more information about how to execute a check using a report, see MultiProvider.

Example: Inconsistent Compounding

Characteristic cost center 1 (COSTCENTER1) is compounded to characteristic controlling area (CO_AREA1). Characteristic cost center 2 (COSTCENTER2) references characteristic COSTCENTER1. Characteristic controlling area 2 (CO_AREA2) references characteristic controlling area 1 (CO_AREA1). As a result, COSTCENTER2 is compounded to CO_AREA2.

These four characteristics are contained in an InfoProvider and the MultiProvider.

The following graphic shows how the characteristics are identified:

COSTCENTER2 is mapped to COSTCENTER1. This means that the higher-level characteristic CO_AREA2 in the InfoProvider also has to be mapped to CO_AREA1 (because this is the higher-level characteristic for COSTCENTER1 in the MultiProvider). This is not the case, which means that the compounding is not consistent.

Correct the assignment:

CO_AREA1  ¬ CO_AREA2

The following example illustrates the problem with inconsistent assignments. You have the following master data:

CO_AREA	COSTCENTER
1000	A
2000	B
2000	C

Because of the incorrect assignment shown above, the following data record could be created in the MultiProvider.

CO_AREA	COSTCENTER
1000	C

This master data does not exist.