Hierarchy
⤷ FIN-SEM-BCS (Application Component) Business Consolidation
⤷ UCF1 (Package) SEM-BCS: Allocation
Attribute
Message class | UCF1 | ||
Short Description | Messages for Allocations | ||
Message Number | 005 | ||
Documentation status | Space: object requires documentation | ||
Authorization check Error Message | |||
Changed On | 20041006 |
Message Text
Help Document
Diagnosis
At this time, the Customizing settings for method step "" are set so that all receivers serve as senders again. Executing an allocation may produce worthless results because the senders cannot be depleted (the iteration is not convergent).
System Response
This is only a warning. You can still save the method for the allocation.
Procedure
- In the Customizing of the method, set the indicator Deactivate Iteration, or
- Try to limit the sender definition as much as possible to avoid this situation (see following examples).
Example 1:
Customizing
Sender Receiver Trigger
Cost
Center [ ] 100-200
Cost
Element = 300000 = 300000 [ ] 100000-200000
Effect
The definition of the sender is not further delimited: Nothing is specified for the sender cost centers, meaning that all cost centers are sender cost centers. Therefore, all existing receiver cost centers can serve as senders again. The allocation would not lead to a meaningful result (regardless of how the distribution key is defined).
Example 2:
Customizing
Sender Receiver Trigger
Cost
Center [ ] 0-100 [ ] 100-200
Cost
Element = 300000 = 300000 [ ] 100000-200000
Effect
Only a portion of the receiver cost centers (cost center 100) serves also as senders. This allocation produces meaningful results, assuming that the distribution is defined so that less than 50% is allocated to receiver cost center 100.
Procedure for System Administration
History
Last changed on/by | 20041006 | SAP | |
SAP Release Created in | 3.0A |