Diagnosis
The consistency of the compounding cannot be guaranteed.
In one of the affected InfoProviders, InfoObject &V1& is compounded withInfoObject &V2&. &V1& is mapped to InfoObject &V3& in the identificationlist. As a result, &V2& is also mapped to &V4& (because InfoObject &V3&is compounded with &V4& in the MultiProvider),

System Response
In InfoProviders, compounded InfoObjects form interrelated "blocks" thatcannot be separated in a MultiProvider when assignments are made.
Particularly when using InfoSets in MultiProviders, problems may arisewhen you make assignments to InfoObjects in the MultiProvider due to themultiple occurrence of InfoObjects in the InfoSet.
Example:
InfoObjects X and Y are both compounded with Z: X->Z, Y->Z
An InfoSet contains InfoObjects F1, F2, F3, and F4 with theirequivalents (field aliases):
F1 ~ X, F2 ~ Z, F3 ~ Y, F4 ~ Z.
The compounding F1->F2 and F3->F4 result from the original compoundingfor X and Y.
If InfoObjects X, Y, and Z are included in a MultiProvider, it is NOTpossible for F1 to be mapped to X and F3 to be mapped to Y. This isbecause F2 and F4 would both have to be mapped to Z to ensureconsistency. This is not possible because an InfoObject in aMultiProvider can only be filled from one InfoObject from eachMultiProvider involved.
In other words, if F3 and F4 are to be "visible" in the MultiProvider,they have to be added to the MultiProvider with these InfoObject namesas a "second block". The assignment is then based on the identity F3 toF3 and F4 to F4.

Procedure
Define the assignments in the MultiProvider so that the compoundingconsistency described above can be guaranteed.

Procedure for System Administration
If you want to explicitly use the MultiProvider in this form, you canset the parameter 'NO_A135_A152' to 'X' with program'SAP_RSADMIN_MAINTAIN'. This turns this message and the terminationmessage BRAIN A152 into warnings.
Keep in mind that this is valid for all MultiProviders and that as ofRelease 7.1 the system checks the consistency of the compoundingindividually for each MultiProvider.
Also note that a MultiProvider with inconsistent compounding can only bescheduled with restrictions. You cannot create an aggregation level onthe MultiProvider containing the InfoObject if the inconsistency of thecompounding of <(>&<)>V3& was caused by an InfoProvider that is waitingfor input (see also long text for BRAIN A326).