You use the Repost by Characteristicv Relationship function to repost transaction data so that it is consistent with the characteristic relationships. The original records are deleted and reposted to the correct characteristic combinations.
In characteristic usage, you can specify which characteristics are to be corrected. This only makes sense for characteristics that can be derived in accordance with the characteristic relationships.
The following condition applies: A planning function of this type can only be created on an aggregation level that has been directly created on a planning-relevant InfoProvider (a simple aggregation level, see Aggregation Level). The aggregation level must contain all the InfoObjects of the InfoProvider that are valid in aggregation levels.
Since normal use of an InfoCube does not allow you to completely delete combinations of characteristics (records) the planning function just resets all key figures to zero. To fully remove combinations of characteristics from the InfoCube, you have to compress the InfoCube in InfoCube Administration (transaction RSA1). The With Zero Elimination flag has to be selected when doing this.
Planning functions of this type on aggregation levels that reference a DataStore object for direct updates in planning mode, work in exactly same the way as planning functions of this type on aggregation levels that reference a real-time InfoCube. A specific example: the planning function only sets key figure values to 0. Data records are not physically deleted.