/SCWM/CORE
156 Meldungen in diesem Anwendungsbereich
Jede Zeile enthält Meldungsnummer und englischen Text. Deep Links z. B. mit #msg-123.
| Meldung | Meldungstext |
|---|---|
| 1 | HU &1 cannot be reversed |
| 2 | HU reversal for delivery &1 not possible; item &2 has no manufact. order |
| 3 | HU reversal for delivery &1 not possible; item &2 has VAS order |
| 4 | No goods receipt correction posted |
| 5 | HU &1 is not a planned handling unit or an existing handling unit |
| 6 | Warehouse tasks could not be re-created after reversal |
| 7 | HU &1 has no delivery reference |
| 8 | Cannot determine unique expected goods receipt item |
| 9 | HU reversal not possible; HU is a nested HU |
| 10 | HU reversal not possible; exception code &1 not valid for HU reversal |
| 11 | HU &1 has a reference to a document other than inbound delivery |
| 12 | Enter serial numbers to be reversed |
| 13 | Error during goods receipt correction; reverse canceled for all HUs |
| 14 | Partial reversal not possible; catch weight material |
| 15 | Cannot adjust or reverse delivery item for HU &1 |
| 16 | Error during cancellation of whse tasks; reverse canceled for all HUs |
| 17 | You are not authorized to reverse HUs in warehouse number &1 |
| 18 | Exception during call of manufacturing receiving API |
| 19 | |
| 20 | Remaining bin depth of the storage bin is not sufficient |
| 21 | Required bin depth &1 of HU &2 checked against remaining bin depth &3 |
| 22 | Enter bin depth of destination storage bin |
| 23 | Production date in the future not possible |
| 25 | Required bin depth must not be initial |
| 26 | Unit of measure &1 from pack.spec. &2 not maintained for material &3 |
| 27 | HU &1 is already on bin &2 |
| 28 | Handling unit &1 moved to bin &2 |
| 29 | Handling unit &1 loaded |
| 30 | Cannot delete handling unit &1 because it is already loaded |
| 31 | Cannot delete HU because &1 is not a transit warehouse HU |
| 32 | HU &1 is posted goods issue. Changing the HU is not possible |
| 33 | Can't run this report, table /SCWM/WHO is locked by another user |
| 34 | The number of entries updated for table &1 is &2 |
| 35 | Update of tables failed |
| 36 | Updating entries for warehouse &3 started at date &1 and time &2 |
| 37 | Updating entries for warehouse &3 completed at date &1 and time &2 |
| 38 | |
| 40 | Provide missing parameters. |
| 41 | Recipient location key is not complete. |
| 42 | Error during update of table &1 |
| 43 | Mapping of recipient location key is not complete. |
| 44 | Can't determine a staging area. |
| 45 | Can't find recipient location &1 for warehouse &2. |
| 46 | Can't find recipient location for warehouse &1. |
| 47 | Can't find recipient location mapping for warehouse &1. |
| 48 | Database table &1 is not used with embedded EWM. |
| 50 | Service &1 not defined; check the code |
| 51 | API is not correctly initialized; check the code |
| 52 | Cannot change screening methods for handling unit &1 |
| 53 | Cannot change handling unit &1 |
| 54 | &1 handling units changed |
| 55 | &1 handling units cannot be changed |
| 56 | Country/region-specific air cargo security status &1 does not exist |
| 57 | Exemption &1 for air cargo security status does not exist |
| 58 | Screening method &1 does not exist |
| 59 | Screening method &1 has been entered mutliple times |
| 60 | Exemption &1 has been entered, do not enter screening methods too |
| 61 | Screening method not updated for HU &1 due to exemption &2 |
| 62 | Changing the air cargo security status is not allowed in storage type &1 |
| 63 | Air cargo security information cannot be changed for some HUs |
| 64 | You are not authorized to set a higher ACS status for HU &1 |
| 65 | Non-secure HU &1 cannot be moved to a secure area in storage type &2 |
| 66 | You are moving a secure HU &1 to a non-secure area in storage type &2 |
| 67 | HU &1 requires higher air cargo security status; loading not allowed |
| 68 | HU &1 is already loaded; changing air cargo security data not allowed |
| 69 | No historical data found for HU &1 ; re-creation not possible |
| 70 | Error during goods movement posting for HU &1 |
| 71 | HU &1 skipped; it is contained in a HU container |
| 72 | Error during goods movement posting |
| 73 | Non-secure HU &1 is moved to a secure area in storage type &2 |
| 74 | HU &1 is in a completed HU container; changing ACS data not allowed |
| 75 | HU container &1 cannot be completed; screening is not yet finished |
| 76 | Work center &1 cannot be used for loading secure cargo on HU container &2 |
| 77 | You can enter units for weight, volume, length, and time only once |
| 78 | HU &1 skipped due to process-oriented storage control |
| 79 | WT to be created for HU &1 due to process-oriented storage control |
| 80 | Warehouse task for HU &1 added to warehouse order &2 |
| 81 | Don't create WT for HU &1; create WT for highest-level HU instead |
| 82 | You must enter a pick-handling unit for distribution equipment picking |
| 83 | You cannot confirm pick WTs with different final bins into one pick-HU |
| 84 | No packaging material found for sub pick-HU of distribution equipment |
| 100 | All selected handling units reversed |
| 101 | Cannot reverse all selected handling units; see log for details |
| 102 | Enter a warehouse number |
| 103 | Finish time &1 is before start time &2 of requested time range |
| 200 | A seal with the same number already exist for this object |
| 201 | Seal &1 not found |
| 202 | Mismatch between seal &1 and technical key; check program code |
| 250 | Screening method &1 already set |
| 251 | Screening method &1 not found |
| 252 | &1 is not a valid screening method |
| 253 | Description cannot be set for screening method &1; delete description |
| 270 | &1 entries deleted in relationship table between HU and delivery |
| 271 | &1 entries updated in relationship table between HU and delivery |
| 272 | Can't open this document; access to &1 documents is not supported |
| 273 | Relationship between HU &1 and delivery &2 updated |
| 274 | Relationship between HU &1 and delivery &2 saved |
| 300 | -- The numbers between 300 and 349 are reserved for EMW licensing -- |
| 301 | &1 entries created on or before day &2 can be deleted |
| 302 | &1 entries created on or before day &2 are deleted |
| 303 | More than &1 entries created on or before day &2 can be deleted |
| 304 | More than &1 entries created on or before day &2 are deleted |
| 305 | Compliant; warehouse &1 used basic functions |
| 306 | Compliant; warehouse &1 used advanced functions with acknowlegement |
| 307 | Not compliant; whse &1 used advanced functions with no acknowledgment |
| 308 | You are not authorized to perform license auditing in warehouse &1 |
| 309 | Cannot switch back to No Acknowledgement |
| 310 | Material flow system used; count: &1 in warehouse &2 |
| 311 | Shipping and Receiving used; count: &1 in warehouse &2 |
| 312 | Warehouse Billing used; count: &1 in warehouse &2 |
| 313 | Value-Added Services used; count: &1 in warehouse &2 |
| 314 | Wave used; count: &1 in warehouse &2 |
| 315 | Slotting used; count: &1 in warehouse &2 |
| 316 | Cartonization Planning used; count: &1 in warehouse &2 |
| 317 | Labor Management used; count: &1 in warehouse &2 |
| 318 | |
| 319 | You can’t use this Customizing activity in decentralized EWM |
| 320 | --- Start of automatic warehouse task creation upon goods receipt |
| 321 | --- End of automatic warehouse task creation upon goods receipt |
| 322 | Warehouse process type &1 determined for product &2 |
| 323 | Automatic warehouse task creation is active for process type &1 |
| 324 | Automatic warehouse task creation is inactive for process type &1 |
| 325 | Automatic warehouse task creation is active for storage type &1 |
| 326 | Automatic warehouse task creation is inactive for storage type &1 |
| 327 | Process type &1 to decide on warehouse task creation in storage type &2 |
| 328 | No warehouse process type determined for product &1 |
| 329 | No storage type could be determined for receipt in bin &1 for product &2 |
| 330 | Determine relevance for warehouse task creation for item with product &1 |
| 331 | Number of warehouse task creation relevant items: &1 |
| 332 | No automatic task creation for storage type &1 and process type &2 |
| 333 | Warehouse process type changed to &1 by BAdI implementation |
| 334 | Warehouse task creation set to inactive by BAdI implementation |
| 335 | Warehouse task creation set to active by BAdI implementation |
| 336 | --- Start of undo warehouse task created at goods receipt |
| 337 | --- End of undo warehouse task created at goods receipt |
| 338 | Number of warehouse tasks to undo: &1 |
| 339 | Undo warehouse task created for product &1 |
| 340 | No storage type could be determined for receipt in bin &1 for HU &2 |
| 341 | No warehouse process type determined for handling unit &1 |
| 342 | Warehouse process type &1 determined for handling unit &2 |
| 343 | Determine relevance for warehouse task creation for item with HU &1 |
| 344 | Undo warehouse task created for HU &1 |
| 345 | Services of JIT processing used; count: &1 in warehouse &2 |
| 346 | Services of distribution equipment used; count: &1 in warehouse &2 |
| 347 | Services of package building in UPB used; count: &1 in warehouse &2 |
| 350 | There is still stock in warehouse &1 |
| 351 | There is still stock in table &1 |
| 352 | Assign number range interval for stock transf. cons. group in customizing |
| 353 | Maintain number range interval &1 for consolidation groups in customizing |
| 354 | Can’t use SAP predelivered storage types. |
| 355 | Enter a non-initial value in field &1 |
| 356 | Enter a valid partner group |
| 357 | Enter a valid stock type |
| 358 | Enter a score between 0 and 100 |
| 380 | Unloading WT creation was changed by BAdI from top HU to HU level &1 |
| 381 | Top HU is used because level &1 doesn't exist in HU hierarchy |
Meldungstexte dienen als technische Referenz in Beratung und Schulung. SAP, SAP TM, SAP EWM, SAP GTS, SAP S/4HANA und andere Produktnamen sind Marken der SAP SE.