/SCMTMS/TOR_OH - Overview Hierarchy Messages
The following messages are stored in message class /SCMTMS/TOR_OH: Overview Hierarchy Messages.
It is part of development package /SCMTMS/PLN_REASSIGN in software component TM-PLN. This development package consists of objects that can be grouped under "Planning: Re-Assignment".
It is part of development package /SCMTMS/PLN_REASSIGN in software component TM-PLN. This development package consists of objects that can be grouped under "Planning: Re-Assignment".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Object must not be initial |
| 002 | Level must not be initial |
| 003 | If this level is expandable, the preceding level must also be expandable |
| 004 | There must not be a gap between the levels |
| 005 | Object &1 must not be below object &2 |
| 006 | Class &1 does not exist |
| 007 | Class &1 does not implement interface &2 |
| 008 | Field &1 does not belong to the overview item |
| 009 | Data access definition does not exist |
| 010 | Field level must not be initial |
| 011 | Enter attribute name (overview) for attribute-based grouping (overview) |
| 012 | Data access definition field must not be initial for DAD-based grouping |
| 013 | Field class name must not be initial for class-based groupings |
| 014 | Enter the attribute name (item) for attribute-based grouping (item) |
| 015 | Only one grouping level is allowed |
| 016 | Enter the transportation mode |
| 017 | &1 must not be the first level |
| 018 | There must be a corresponding object below the grouping |
| 019 | Cannot save data; consecutive hierarchy levels have same object type |
| 020 | Enter a grouping category |
| 021 | Hierarchy type must not be self-referential |
| 022 | Hierarchy type can only be specified once |
| 023 | Hierarchy type &1 not found |
| 024 | You cannot filter entries based on activities for level &1 |
| 025 | You cannot use the location and stage level together |
| 026 | You cannot group a level multiple times |
| 027 | Object &1 must not be used |
| 028 | Specify which function is allowed to use the hierarchy &1 |
| 029 | Hierarchy &1 used in transportation cockpit must display all items |
| 030 | UIBB configuration is ignored for transp.-cockpit-relevant hierarchy &1 |
| 031 | Locations are ignored for cargo-relevant hierarchies |
| 032 | Hierarchy &1 does not have the same consumer as hierarchy &2 |
| 033 | Hierarchy &1 does not have same transp. mode cat. as hierarchy &2 |
| 034 | Hierarchy type &1 is reserved for an immutable standard hierarchy |
| 035 | Hierarchy type &1 can only be defined for consumer freight doc. overview |