Message Number list used by SAP ABAP Function Module /AIN/PUB_POBJ_HIER_CREATE (Create Object Hierarchy)
SAP ABAP Function Module
/AIN/PUB_POBJ_HIER_CREATE (Create Object Hierarchy) is using
# | Object Type | Object Name | Object Description | Note |
---|---|---|---|---|
![]() |
![]() |
|||
1 | ![]() |
/AIN/PUB_POBJ - 001 | Physical object internal ID must be provided | |
2 | ![]() |
/AIN/PUB_POBJ - 004 | Physical object does not exist | |
3 | ![]() |
/AIN/PUB_POBJ - 012 | Parent-child relation of physical object must be provided | |
4 | ![]() |
/AIN/PUB_POBJ - 013 | Physical objects must belong to same location | |
5 | ![]() |
/AIN/PUB_POBJ - 014 | Only objects in stock can be added to physical object hierarchy | |
6 | ![]() |
/AIN/PUB_POBJ - 015 | Physical object '&1&2' currently belongs to another object hierarchy | |
7 | ![]() |
/AIN/PUB_POBJ - 016 | Update time must be provided | |
8 | ![]() |
/AIN/PUB_POBJ - 017 | Update user must be provided | |
9 | ![]() |
/AIN/PUB_POBJ - 022 | Parent physical object must not be an untagged object | |
10 | ![]() |
/AIN/PUB_POBJ - 049 | Physical object with ID '&1&2' is decommissioned | |
11 | ![]() |
/AIN/PUB_POBJ - 050 | Physical object '&1&2' cannot be added to own sub hierarchy (pack cycle) |