Diagnosis
Characteristic &V2& appears in several base planning areas and hasdifferent technical attributes there This problem can then occur if

• The basic planning areas refer to different RFC destinations, and the
characteristic in the different systems has different settings on thetype, length, attributes, compound or hierarchies.

• The characteristic is compounded to another characteristic and a
constant is set up for the higher-level characteristic in one of theInfoCubes concerned, but in another one is not.
Example: The characteristic 0FISCPER is compounded to characteristic0FISCVARNT (fiscal year variant). The constant K4 is set up for0FISCVARNT in an InfoCube, however, in another InfoCube there are noconstants.
However, characteristics with the same name from different planningareas can then be included in the same planning area, if they have thesame technical properties.

Procedure
Create characteristic &V2& (and with compound characteristics also itshigher-level characteristics) in all affected systems and (withInfoCube-dependent attributes such as constants) all InfoCubes involvedwith the same technical attributes.