/SCWM/WHO - Warehouse Order
The following messages are stored in message class /SCWM/WHO: Warehouse Order.
It is part of development package /SCWM/WHO in software component SCM-EWM-WOP. This development package consists of objects that can be grouped under "Warehouse Order Processing".
It is part of development package /SCWM/WHO in software component SCM-EWM-WOP. This development package consists of objects that can be grouped under "Warehouse Order Processing".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Warehouse order creation started |
| 001 | &1 WTs with directly assigned creation rule |
| 002 | &1 WTs with search sequence for determining creation rules |
| 003 | New process started for warehouse order creation |
| 004 | Warehouse order creation called up within a process |
| 005 | Activity area &1 used to determine the creation rule |
| 006 | Creation rule &1 used for &2 warehouse tasks |
| 007 | Inbound warehouse task sorting rule &1 used |
| 008 | &1 WTs passed, &2 WTs didn't pass item filter &3 |
| 009 | &1 WTs passed, &2 didn't pass subtotal filter &3 |
| 010 | &1 consolidation groups passed the subtotal filter |
| 011 | Limit value &1 used for &2 warehouse tasks |
| 012 | Warehouse order &1 created on the basis of creation rule &2 with &3 WTs |
| 013 | Minimum limit values were not reached due to &1 WTs |
| 014 | Maximum limit values were exceeded due &1 WT |
| 015 | Limits for items: minimum &1, maximum &2, current &3 |
| 016 | Limits for volume: minimum &1 &4, maximum &2 &4, current &3 &4 |
| 017 | Limits for weight: minimum &1 &4, maximum &2 &4, current &3 &4 |
| 018 | Limits for consolidation group per whse order: maximum &1, current &2 |
| 019 | Limits for consolidation group per HU: maximum &1, current &2 |
| 020 | Limits for number of HUs: maximum &1, current &2 |
| 021 | Outbound WT sorting rule &1 used |
| 022 | Limit values: current values for these &1 warehouse tasks |
| 023 | Maximum limit value for &1 warehouse tasks was adhered to |
| 024 | No further rules defined; remainder rule will be used |
| 025 | Standard rule will be used for the remaining warehouse tasks |
| 026 | Consolidation group changed from &1 to &2 |
| 027 | Consolidation group &1 with &2 WTs passed subtotal filter |
| 028 | Consolidation group &1 with &2 WTs did not pass subtotal filter |
| 029 | Consolidation group &1 passed subtotal filter |
| 030 | The search sequence for activity area &1 is used for &2 WTs |
| 031 | No WTs were transferred. Warehouse order creation cancelled |
| 032 | WT &1 passed the filter |
| 033 | Creation rule &1 is of the type "Consolidation Group" |
| 034 | Creation rule &1 is of the type "Pick Path" |
| 035 | Creation rule &1 is of the type "Pick and Pack" |
| 036 | Creation rule &1 is of the type "Pick, Pack, and Pass: System-Driven" |
| 037 | Creation rule &1 is of the type "Pick, Pack, and Pass: User-Driven" |
| 038 | Creation rule &1 is of the type "load/unload" |
| 039 | Creation rule &1 is of the type "Distributive Putaway" |
| 040 | Item filter &1 checked |
| 041 | Subtotal &1 checked |
| 042 | Limits for processing time: min. &1 &4, max. &2 &4, current &3 &4 |
| 043 | Number range object &1 is in critical area |
| 044 | Last number assigned in number range object &1 |
| 045 | Warehouse order &1 is divided up according to activity areas |
| 046 | Warehouse order &1 created with rule &2 with &3 WTs for activity area &4 |
| 047 | Minimum limit values were not reached |
| 048 | Warehouse order cannot be created without a number range object |
| 049 | Handling unit &1 contains warehouse tasks with the status 'waiting' |
| 050 | Warehouse order &1 &2 does not exist |
| 051 | You can only process open warehouse orders |
| 052 | Warehouse order &1 &2 is already assigned user &3 |
| 053 | Warehouse order should be executed using resource &1 |
| 054 | The number range interval for warehouse orders is missing in whse no. &1 |
| 055 | Assigned HU &1 was not read |
| 056 | Assigned HU &1 was not deleted |
| 057 | Assigned HU &1 was deleted |
| 058 | Warehouse task &1 passed limit value |
| 059 | Delivery changed from &1 &2 to &3 &4 |
| 060 | Dest. data of WT for warehouse order changed according to current rule |
| 061 | Stor. process of WT for whse order changed to &1 acc. to current rule |
| 062 | Dest. data of WT for WO changed according to pack. station determination |
| 063 | No division of WO possible, as activity area is defined incorrectly |
| 064 | Rule &1 cannot be used, since activity area &2 cannot be divided |
| 065 | Destination data of WT for WO changed according to ext. process step &1 |
| 066 | Warehouse order creation is processing: |
| 067 | Warehouse order creation started for WTs being activated |
| 068 | Rule is not consistent; max. no. of consolidation groups per HU <> 1 |
| 069 | Destination data for &1 WTs must be changed |
| 070 | Destin. data for &1 WTs not changed due to incorrect bin determination |
| 071 | Start date must not be more current than confirmation date |
| 072 | Start date lies in the future; specify a valid start date |
| 073 | Warehouse order &1 created |
| 074 | &1 warehouse orders created |
| 075 | &1 warehouse tasks should be assigned to a new warehouse order |
| 076 | Activity area &1 |
| 077 | Warehouse tasks are part of queue &1 |
| 078 | Transaction type on WO level was changed in BAdI from &1 to &2 |
| 079 | Destination data of &1 WTs was not changed due to reference to VAS |
| 080 | Activity area &1 activity &2 used for determining creation rule |
| 081 | Size of WO in putaway restricted to one HU WT (in rule DEF) |
| 082 | WO creation carried out in BAdI |
| 083 | WTs of a WO must contain only one queue. |
| 084 | WTs of a WO must contain only one activity area |
| 085 | All WTs must contain a reference to a WO. |
| 086 | WT &1 is unknown: check your BAdI implementation |
| 087 | WO &1 is unknown: check your BAdI implementation |
| 088 | BAdI for WT creation did not return any warehouse orders |
| 089 | BAdI for WT creation did not return any warehouse orders |
| 090 | Confirmation date cannot be in the future; enter a valid date |
| 091 | Creating WOs for inactive warehouse tasks |
| 092 | MFS rule used for WTs with relevance to material flow system |
| 093 | Limit of one WT per WO set for WOs with relevance to material flow system |
| 094 | Limit was reached due to a change of the determined destination data |
| 095 | BADI shows no result |
| 096 | missing BADI implementation |
| 097 | BAdI added or removed WTs |
| 098 | BAdI called for HU determination |
| 099 | ***************** PACKING -------------------------------- |
| 100 | HU determination started for &1 WTs |
| 101 | Packaging material was not determined. No pick-HU determination |
| 102 | Maximum number of consolidation groups per HU reached |
| 103 | Maximum number of HUs &1 reached for each warehouse order |
| 104 | Max. number of items for each warehouse order reached. No split in order |
| 105 | Partial quantity assigned, WT &1 will be split |
| 106 | WT &1 does not fit into packaging material &2 |
| 107 | WT &1 no longer fits in HU. Maximum number of HUs already reached |
| 108 | Warehouse order &1 canceled |
| 109 | WT &1 does not fit completely into HU. Quantity reduced to &2 |
| 110 | WT &1 packed |
| 111 | WT &1 split. Maximum number of HUs reached. No split in this order |
| 112 | Check WT &1 |
| 113 | WT &1 is OK |
| 114 | Rule &1 inconsistent. Max. no. WTs per HU * max. no. HUs < max. no. WTs |
| 115 | Rule &1 invalid. Max.no. consol. grps per HU * max.no. HUs < max.no. WTs |
| 116 | Rule &1 inconsistent. Max. weight per HU * max. no. HUs < max. WO weight |
| 117 | Rule &1 inconsistent. Max. vol. per HU * max. no. HUs < max. WO volume |
| 118 | Pick HU determination for creation rule &1 is therefore not possible |
| 119 | Limit for maximum weight of rule &1 is too large |
| 120 | Limit for maximum volume of rule &1 is too large |
| 121 | &1 pick-HUs with packaging material &2 due to limit max. items/HU |
| 122 | &1 pick-HUs with packaging material &2 due to maximum consol.groups/HU |
| 123 | &1 pick-HUs with packaging material &2 due maximum weight of a HU |
| 124 | &1 pick-HUs with packaging material &2 due to maximum volume of a HU |
| 125 | Smallest pack. material too small for min. number of HUs in profile &1 |
| 126 | Maximum number of items per HU reached |
| 127 | Maximum number of consolidation groups per HU with WT &1 reached |
| 128 | No packaging material is maintained for packing profile &1 |
| 129 | Limits require &1 HUs. Minimum volume of &2 not reached |
| 130 | Limits require &1 HUs. Minimum weight of &2 not reached |
| 131 | Maximum number of WTs per order reached |
| 132 | Maximum number of HUs per warehouse order reached |
| 133 | Packing profile &1 is not assigned to an algorithm |
| 134 | WT &1 with quantity &2 &3 is too large for the largest HU |
| 135 | WT &1 with quantity &2 &3 was split |
| 136 | New HU opened with packaging material &1 |
| 137 | WT &1 is too large for the HU. Next largest packaging material &2 |
| 138 | WT &1 is too large for the HU and will be skipped |
| 139 | WT &1 is too large for the HU. Packable quantity will be split |
| 140 | WT &1 is too large, packing in this HU terminated |
| 141 | WT &1 has different destination data; try to close the handling unit |
| 142 | WTs do not meet the minimum limits for the HU. Next rule will be used |
| 143 | Minimum number of WTs per HU not reached => WTs in next rule |
| 144 | Maximum number of WTs per HU exceeded. WTs in next rule |
| 145 | Max. number of consolidation groups per HU exceeded. WTs in next rule |
| 146 | WT &1 has a different destination storage bin and will be skipped |
| 147 | WT &1 has a different destination storage bin. Current HU ended |
| 148 | &1. Packing proposal created with packaging material &2 |
| 149 | Shipping HU determination started for &1 WTs |
| 150 | Packing-WT sorting rule &1 used |
| 151 | Cannot create handling unit. Manual creation necessary |
| 152 | Dimensions of product &1 do not fit HU of type &2 |
| 153 | Dimension of HU &1 does not fit into HU of type &2 |
| 154 | WT &1 can be packed |
| 155 | WT &1 has different destination data and will be skipped |
| 156 | Packing complete; checking minimum limit values |
| 157 | Minimum limits of &1 will not be reached |
| 158 | &1 was OK and will be used for suitable WTs |
| 159 | Acty area &2 (activity &1) has no starting bin; HU creation not possible |
| 160 | Error reading packaging material &1 |
| 161 | Whse no. &1 missing a determination procedure for HU creation for WOs |
| 162 | Unable to determine a packaging specification |
| 163 | Rule & 1 invalid; more dest. storage bins than allowed handling units |
| 164 | Maximum number of consolidation groups per HU reached; WT &1 skipped |
| 165 | WT was filtered out via BAdI; finish packing check for HU |
| 166 | WT filtered out via BAdI; WT skipped |
| 167 | WT &1 does not fit into packing profile &2; will be checked in next rule |
| 168 | Simulation mode |
| 169 | Route &1 passed to packspec determination |
| 170 | Warehouse order is created in status 'Locked' due to external demand |
| 171 | BAdI determined handling unit position in handling unit |
| 172 | Creation rule &1 is type "Pick for Distribution Equipment" |
| 173 | Planned Completion time could not be determined |
| 174 | You can't enter a standard HU as a pick-HU for distribution equipment |
| 175 | Warehouse order created with status "Open" due to external demand |
| 176 | Creation rule &1 is type "Process for Distribution Equipment" |
| 177 | Warehouse order created with status "Locked" due to warehouse order rule |
| 199 | ************** Customizing -------------------------- |
| 200 | Item filter is not defined as an item filter |
| 201 | Subtotal filter is not defined as a subtotal filter |
| 202 | Filter &1 is not defined in warehouse number &2 |
| 203 | Limit value &1 is not defined in warehouse number &2 |
| 204 | Packing profile &1 is not defined in warehouse number &2 |
| 205 | WT sorting &1 is not defined in warehouse number &2 |
| 206 | Search sequence for activity area &1 is not defined in warehouse no. &2 |
| 207 | Creation rule &1 is not defined in warehouse number &2 |
| 208 | Creation rule &1 in warehouse number &2 is inconsistent |
| 209 | Filter &1 is not defined as an item filter |
| 210 | Filter &1 is not defined as a subtotal filter |
| 211 | For pack. prof. &1 no stor. bin defined in whse no. &2 activ. area &3 |
| 213 | Specify the storage process or select work center determination |
| 299 | **************** Read WHO Tables ------------------ |
| 300 | Packaging material or HU entry not found for warehouse order |
| 301 | One of the warehouse orders is already being processed by user &1 |
| 302 | Warehouse order &2 is already being processed by user &1 |
| 303 | Handling unit &1 is not assigned to a warehouse order |
| 304 | Selection criteria are not sufficient |
| 305 | Warehouse number was not transferred |
| 400 | ****** Delete, Change, Create, Etc. -------------- |
| 401 | Warehouse order already contains confirmed WTs. No deletion possible |
| 402 | None of the WTs are part of warehouse order &1 |
| 403 | The warehouse orders do not contain any WTs |
| 404 | Error accessing warehouse order &1 |
| 405 | Input parameters inconsistent; check the input parameters |
| 406 | Error changing WTs for warehouse order &1 |
| 407 | Error accessing WTs |
| 408 | Warehouse order &1 is already confirmed; no changes possible |
| 409 | Queue &1 for WO &2 and queue &3 for WT &4 are different |
| 410 | Warehouse order was archived |
| 411 | Errors during additional checks prevent archiving |
| 412 | Warehouse order &1 is already confirmed; no changes possible |
| 413 | Warehouse order &1 already canceled; no change possible |
| 414 | Warehouse order &1 already has the status "Waiting" |
| 415 | Warehouse order &1 already has the status "Open" |
| 416 | Status of warehouse order &1 changed to "Waiting" |
| 417 | Status of warehouse order &1 changed to "Open" |
| 418 | You do not have authorization for warehouse number &1 |
| 419 | You can only create higher-level WOs of type "Load/Unload" |
| 420 | Queue for WT &1 was changed from &2 to &3 for warehouse order &4 |
| 421 | A warehouse order should be added to higher-level WO &1 |
| 422 | WO &1 was added to the higher-level "Load/Unload" warehouse order &2 |
| 423 | WO &1 is of category 'Pick, Pack, and Pass'; split not possible |
| 424 | WO &1 is of category 'Pick, Pack, and Pass'; merge not possible |
| 425 | Queue &1 for warehouse task &2 was redetermined |
| 426 | Warehouse order &1 in status "waiting"; no change possible |
| 427 | Warehouse order &1 was changed |
| 428 | WT split with WOCR &1 not possible => rollback split WT |
| 429 | WT is subsystem relevant, action is not possible |
| 430 | WO &1 with Shipping Packing Profil of Higher Level WO; split not possible |
| 431 | WO &1 with Shipping Packing Profil of Higher Level WO; merge not possible |
| 432 | WO &1: Adjustment of latest start date triggered by WT confirmation &2 |
| 433 | Warehouse order &1: Cannot adjust latest start date |
| 434 | WO &1: Latest start date adjusted; new latest start date is &2 |
| 435 | Warehouse order &1 used as a template for new warehouse order |
| 436 | Pick-HUs of former warehouse orders shall be taken over |
| 437 | Pick-HUs cannot be taken over if different activity areas/queues are used |
| 438 | Warehouse orders cannot be read |
| 439 | Pick-HUs cannot be taken over for warehouse orders with rule type &1 |
| 440 | Pick-HUs cannot be taken over for warehouse orders with confirmed WTs |
| 441 | Pick-HUs can only be taken over if all WTs of original WOs are unassigned |
| 442 | Pick-HUs of former warehouse orders are taken over |
| 501 | &1 WTs were split from warehouse order &2. Reason: &3 |
| 502 | &1 WTs were assigned to warehouse order &2. Reason: &3 |
| 503 | Assignment of &1 WTs to warehouse order &2 was removed |
| 504 | Warehouse order &1 was confirmed, as it contains no further WTs |
| 505 | Warehouse order &1 was canceled because the last open WT was removed |
| 506 | Warehouse order &1 is summarized with other warehouse orders. Reason &2 |
| 507 | Assignment of HUs to warehouse order &1 changed |
| 508 | Assignment of HU &1 not removed, since WTs are packed in it |
| 509 | Assignment of HU &1 not removed, since WTs are packed in it |
| 510 | Assignment of HU &1 to warehouse order &2 removed |
| 511 | HU &1 deleted, since it was generated by warehouse order creation |
| 512 | HU &1 is not part of warehouse order &2 |
| 513 | Assignment of packaging material &1 to warehouse order removed |
| 514 | Assignment of packaging material &1 not removed, as WTs are packed in it |
| 515 | Warehouse order split started for warehouse order &1 |
| 516 | Warehouse order summarization started for warehouse order &1 |
| 517 | Warehouse order creation started for &1 WTs |
| 518 | HU &1 was reassigned to warehouse order &2 |
| 519 | HU &1 does not exist and will not be added to warehouse order &2 |
| 520 | Specified WT &1 is not part of warehouse order &2 |
| 521 | More WTs must be assigned to warehouse order &1 |
| 522 | Assignment of WTs to warehouse order &1 must be removed |
| 523 | Requested execution item &1 already used by WT &2 |
| 524 | Execution items in WTs adjusted as of WT &1 |
| 525 | No HU identification will be assigned to HU &1 |
| 526 | HU &1 (packaging material &2) assigned HU identification &3 |
| 527 | HU &1 is already assigned to the warehouse order with HU ID &2 |
| 528 | HU &1 not deleted |
| 529 | Execution item of WT &1 in warehouse order &2 changed |
| 530 | Pack. mat. entered &1 for HU &2 is different from the one in database &3 |
| 531 | Execution item &1 of WT &2 is the same as the one in the database |
| 532 | Select only one entry |
| 533 | Select an entry |
| 534 | No log found for warehouse order &1 |
| 535 | You must select at least two warehouse orders to join together |
| 536 | You can only split warehouse tasks from a warehouse order |
| 537 | No log found for warehouse task &1 |
| 538 | You can only process warehouse tasks of one warehouse order |
| 539 | Not all objects will be displayed, due to missing authorizations |
| 540 | Unknown warehouse process category &1 found; context not defined |
| 541 | Unknown internal storage process step; context not defined |
| 542 | HU &1 was transferred for processing several times |
| 543 | WT &1 has status "Waiting" and cannot be confirmed |
| 544 | WT &1 is not assigned to a warehouse order and cannot be confirmed |
| 545 | No warehouse tasks found for HU &1 |
| 546 | Warehouse order &1 was canceled because it contains no further WTs |
| 547 | WO &1 could not be canceled because it contains phys. inventory documents |
| 548 | An HU without packaging material cannot be added to the WO |
| 549 | Warehouse orders with physical inventory documents could not be merged |
| 550 | WO &1 contains PI documents; confirming in background not possible |
| 551 | WOs with WTs and WOs with phys. inventory documents could not be merged |
| 552 | WT &1 is still assigned to WO &2 |
| 553 | Warehouse task &1 is not assigned to a warehouse order |
| 554 | Resetting external outbound message (Queue Name &1) is not supported |
| 555 | Cannot execute external outbound message (Queue Name &1) |
| 556 | Warehouse task &1 could not be unassigned from warehouse order &2 |
| 557 | Limit was reached due to a change in the field that limits WO size |
| 558 | Specified field &1 does not exist and is ignored |
| 559 | Not all warehouse tasks relevant for subsystem, WO creation stopped. |
| 600 | Resource management called with queue &1 |
| 601 | Content provider &1 determined for warehouse order &2 |
| 602 | No resource index entries created |
| 603 | Planned shipping HUs are used for HU determination |
| 604 | Limit &1 is deactivated because planned shipping HUs exist |
| 605 | Creation rule &1 cannot be used with planned shipping HUs |
| 606 | HU is created according to planned shipping HU &1 |
| 607 | WT &1 should be packed into packing proposal &2 of WHO &3 |
| 608 | WT &1 was assigned to packing proposal &2 of WHO &3 |
| 609 | No Packing Proposal assigned to Warehouse Order &1 |
| 610 | Confirmation not possible due to WT &1 and HU requirement in destination. |
| 611 | Incompatible changes in BADI &1 not taken over. |
| 612 | Destination data could not be changed in split or merge process |