/SCMTMS/MC_PB - Message Class for Package Builder
The following messages are stored in message class /SCMTMS/MC_PB: Message Class for Package Builder.
It is part of development package /SCMTMS/PLN_PB in software component TM-PLN. This development package consists of objects that can be grouped under "Package Bulder".
It is part of development package /SCMTMS/PLN_PB in software component TM-PLN. This development package consists of objects that can be grouped under "Package Bulder".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Unified package building failed: Header data not available |
| 002 | Unified package building failed for some doc.: Header data not available |
| 003 | Unified package building failed: Item data not available |
| 004 | Unified package building failed for some doc.: Item data not available |
| 005 | Unified package building finished |
| 006 | Unified package building not available for document category of &1 |
| 007 | No unified package building profile assigned to &1: UPB not possible |
| 008 | No UPB profile assigned to &1: Default settings are applied |
| 009 | Capacity planning already finalized for &1: UPB not possible |
| 010 | UPB not possible for &1: No unique consolidation location |
| 011 | Unified package building not available for document type of &1 |
| 012 | Unified package building not possible for already packaged item |
| 013 | Document &1 is fixed: Unified package building not possible |
| 014 | &1 top level packages created |
| 015 | &1 product items couldn't be packaged |
| 016 | UPB failed; no package unit type defined in planning profile |
| 017 | UPB not possible for document &1: Document already planned |
| 018 | UPB failed for some documents: Items could not be packaged |
| 019 | Some items excluded from UPB because of whse proc. status |
| 020 | UPB canceled because of the whse processing status of item |
| 021 | No package unit created for location &1: too many main packages required |
| 022 | No package unit created for partner &1: too many main packages required |
| 023 | Package unit created for location &1 |
| 024 | Package unit created for business partner &1 |
| 025 | Item &1 is not relevant because the requirement assignment is fixed |
| 026 | &1 items are not relevant because the requirement assignment is fixed |
| 027 | |
| 028 | Item &1 is not relevant because the load plan item status is finalized |
| 029 | &1 items are not relevant because the load plan item status is finalized |
| 030 | |
| 031 | Item &1 is not relevant because the load plan item status is not relevant |
| 032 | &1 items are not relevant because load plan item status is not relevant |
| 033 | |
| 034 | Package item &1 is not relevant because load plan status is finalized |
| 035 | &1 package items are not relevant because load plan status is finalized |
| 036 | |
| 100 | ***SPREADING MESSAGES*** |
| 101 | &1 documents processed by spreading |
| 102 | Spreading not supported for &1 documents |
| 103 | Spreading not supported for document &1 |
| 104 | Spreading failed for &1 documents |
| 105 | Spreading failed for document &1 |
| 106 | Spreading applied for document &1 (&2) |
| 107 | Spreading not applied for document &1 (top item &2 &3): no free capacity |
| 108 | Document &1 (&2): &3 packages excluded from spreading |
| 109 | Document &1 (&2): &3 full-quantity packages excluded |
| 110 | Document &1 (&2): &3 single-product packages excluded |
| 111 | Document &1 (&2): &3 exclusive packages excluded |
| 112 | Document &1 (&2): &3 referenced packages excluded |
| 113 | Document &1 (&2): &3 packages excluded by custom logic |
| 114 | Document &1 (&2): no relevant packages for spreading |
| 115 | Document &1 (&2): &3 packages considered for spreading |
| 116 | Document &1 (&2): &3 packages used as source |
| 117 | Document &1 (&2): for &3 source packages item check failed |
| 118 | Document &1 (&2): &3 target packages filled successfully |
| 119 | Document &1 (&2): &3 reassigned to target package |
| 120 | Spreading (package unit balancing) applied for document &1 |
| 121 | Top item &2 &3 |