SAP ABAP Message Class CC Message Number 160 (Not all objects were allocated)
Hierarchy
☛
SAP_ABA (Software Component) Cross-Application Component
⤷
CA-GTF-ECM (Application Component) Engineering Change Management
⤷
CC (Package) Engineering Change Management

⤷

⤷

Attribute
Message class | ![]() |
CC | |
Short Description | ![]() |
ECM: Messages | |
Message Number | ![]() |
160 | |
Documentation status | ![]() |
||
Authorization check Error Message | |||
Changed On | ![]() |
Message Text
Not all objects were allocated
Help Document
Diagnosis
You want to allocate an object (for example, a BOM) to an alternative date.
This allocation changes the sequence of the effectivity periods.
System Response
The system
- locks the object (for example, BOM)
- checks whether the object is still consistent
The consistency of the object is violated if, for example the object (such as BOM) has already been changed with a change number whose valid-from date is the same as the alternative date to which you want to allocate the object.
Procedure
Check whether another user is processing the object.
You cannot allocate the object to the alternative date if this would violate the consistency of the object.
History
Last changed on/by | ![]() |
20131127 | SAP |
SAP Release Created in |