/SCWM/ERPINTEGRATION
409 messages in this application area
Each row lists the SAP message number and the English message text as provided in the source extract. Use anchors (e.g. #msg-123) to deep-link to a specific message on this page.
| Message | Message text |
|---|---|
| 0 | ----------------Messages for Errors During Mapping----------------------- |
| 1 | No document type found for delivery type &1 from system &2 |
| 2 | No document type found for delivery type &1 from system &2 |
| 3 | Document type &1 does not exist |
| 4 | Delivery document type &1 has the wrong document category &2 |
| 5 | No item type found for delivery item category &1, system &2 |
| 6 | No item type found for delivery item category &1, system &2 |
| 7 | Item type &1 does not exist |
| 8 | Item type &1 has the wrong item category &2 |
| 9 | &1 &2 &3 &4 |
| 10 | No business partner found |
| 11 | Application log &1: Could not convert queue &2 |
| 12 | Could not create header data delivery &1, system &2 |
| 13 | Cannot create item &1 of delivery &2 from system &3 |
| 14 | Cannot convert handling unit &1 for delivery &2, system &3 |
| 15 | Could not determine a logical system for system &1 |
| 16 | The logical system for &1 is not unique |
| 17 | Could not create an instance for class &1 |
| 18 | Could not determine a supply chain unit for ERP warehouse number &1 |
| 19 | Could not find a warehouse number for ERP whse number &1, system &2 |
| 20 | No location found for warehouse number &1 |
| 21 | ERP delivery item category &1 not flagged as returns |
| 22 | No ERP warehouse number found for system &2 for warehouse number &1 |
| 23 | Dependent queues &1 and &2 will be called in a LUW |
| 24 | Delivery &1 blocked due to errors from ERP system &2 |
| 25 | Mapping delivery &1 from system &2 was successful |
| 26 | ERP: Delivery message was sent to ERP system &1 |
| 27 | No configuration found in table &2 for ERP system &1 |
| 28 | No delivery requests to process |
| 29 | Parameter &1 is initial for method &2 |
| 30 | No assignment possible of business partner &1 to ERP vendor |
| 31 | No assignment possible of business partner &1 to ERP customer |
| 32 | No assignment possible of business partner &1 to ERP role &2 |
| 33 | Time zone not found for location |
| 34 | The business system for logical system &1 is not unique |
| 35 | Differentiation attribute must not be left empty |
| 36 | Delivery output could not be sent to ERP system |
| 37 | ERP document type &1 is not marked as relevant for cross-docking |
| 38 | External number &1 of WBS element already exists (ERP-internal:&2) |
| 39 | No WBS element found in EWM for internal number &1 from ERP &2 |
| 40 | No WBS element found in ERP for internal number &1 from EWM |
| 41 | External number of WBS element from ERP missing |
| 42 | Internal number of WBS element from ERP is missing |
| 43 | External number of WBS element is missing |
| 44 | Time zone for warehouse number &1 is not maintained |
| 45 | Packaging material &1 not created in the EWM system. |
| 46 | No ERP plant is assigned to party entitled to dispose &1 |
| 47 | Reading valuation data function module does not exist in ERP system &1 |
| 48 | No corresponding initiator process code found |
| 49 | Mandatory date &1 could not be mapped for document type &2 |
| 50 | Supply chain unit &1 found for ERP warehouse number &2 |
| 51 | EWM document type &1 for ERP delivery type &2 found |
| 52 | Business partner &1 (role:&2) for ERP partner &3 (role:&4) found |
| 53 | No business partner found for ERP partner &3 (role:&4) |
| 54 | No date/time type found for ERP date/time &1 |
| 55 | Date/time type &1 found for ERP date/time &2 |
| 56 | Delivery with initiator process code &1 |
| 57 | Assignment of internal <-> external business partner (&1/&2) not possible |
| 58 | No processing class assigned for message type &1 |
| 59 | Class &1 could not be instantiated |
| 60 | Unable to read LIME collection sets |
| 61 | Logical System &1 is not mapped to an RFC destination |
| 62 | Storage location data identical to &1. Attributes must be unique. |
| 63 | EWM as an add-on to ERP: Entitled &1 from external ERP &2 not allowed |
| 64 | Select at least one processing option |
| 65 | Staging information cannot be maintained without "Entitled" |
| 66 | &1 production supply area(s) created |
| 67 | No business partner found for Consignee &3 |
| 68 | No PSA found in EWM for ERP PSA &1 plant &2 |
| 69 | No unique partner found for vendor &1: &2 &3 |
| 70 | PSA &1 is not unique |
| 71 | Item category &1 does not support follow-up code &2 |
| 72 | &1 production supply area(s) deleted |
| 73 | Staging information for &1 production supply area(s) created |
| 74 | Provide storage location together with plant |
| 75 | Specify staging information after replication (Tx.:/SCWM/PSASTAGE) |
| 76 | Number of production supply areas found: &1 |
| 77 | Error deleting mapping of PSA |
| 78 | Error updating mapping of PSA |
| 79 | Error when reading the initiator process list |
| 80 | Initiator process &1 is unknown |
| 81 | Error reading HU &1 |
| 82 | Concurrent change in EWM, start again |
| 83 | No PoD reason found in ERP system &1 |
| 84 | Transportation planning type set to &1 by ERP interface |
| 85 | Document category &1 missing in reference profile &2 |
| 86 | Expected goods receipt not supported for material to be discontinued |
| 87 | Document type &1 not configured for communication with ERP |
| 88 | Error during mapping: material &1 does not exist |
| 89 | Item &1: No sales quantity is saved for item |
| 90 | Item &1: Sales quantity &2/&3 not configured for profile &4 (no save) |
| 91 | Batch &1 for product &2 does not exist. Batch master required for HU. |
| 92 | System will execute queue for delivery &1 again (RETRY). |
| 93 | ERP requests details in case of a rejection |
| 94 | ERP requests no details in case of a rejection |
| 95 | You cannot change a delivery after it has been split in EWM |
| 96 | Error in implementation of BAdI &1; correct your code |
| 97 | Change of partner &1 with role &2/ &3 not allowed; system ignores change |
| 98 | TU already assigned, adding carrier not allowed; system ignores carrier |
| 99 | Status type DWA is required to change the delivery |
| 100 | *** Messages for goods movements to R/3 via BAPI_GOODSMVT_CREATE*** |
| 101 | Enter logical system |
| 102 | Movement type &1 is not defined. |
| 103 | Movement type &1 is not compatible with posting string &2 |
| 104 | Error setting up RFC connection to &1 |
| 105 | Could not determine ERP stock data for: &1 &2 |
| 106 | Collection not found for transfer line |
| 107 | Warehouse document &2 not found in warehouse number &1 |
| 108 | No logical system maintained for party entitled to dispose &1 |
| 109 | GM_CODE cannot be derived from direction &1 |
| 110 | For ERP movement type &1, the following field cannot be changed: &2 |
| 111 | No control parameter entries found for BSKEY &1 and document type &2 |
| 112 | Could not determine EWM stock data for: &1 &2 |
| 113 | ERP data not supported in EWM: &1 &2 |
| 114 | EWM data not supported for ERP communication: &1 &2 |
| 115 | Error cancelling document &1 in the ERP system |
| 116 | Empty stock types are not allowed |
| 117 | Error in database access: Table &1, operation &2 |
| 118 | Error in method &1 &2: &3 &4 |
| 119 | Pty Entitiled to Dispose for Transfer Postings from 2 ERP Sys Not Allowed |
| 120 | Enter a vendor for the consignment stock or returnable packaging. |
| 121 | Error during mapping: ERP material &1 has been assigned twice |
| 122 | Posting string &1 not intended for goods movement interface |
| 123 | Movement type &1 unknown/has errors in EWM (Customizing ERP Integration) |
| 124 | You have not entered settings for BSKEY &1 |
| 125 | RFC destination for logical system &1 is missing |
| 126 | Target system &1; outbound queues / IDocs still exist in system &2 |
| 127 | Target system &1; inbound queues still exist |
| 128 | Open IDocs/outbound/ERP inbound queues will not be checked |
| 129 | You cannot cancel document &1 |
| 130 | Unable to reach system &1 |
| 131 | Plant &1/stge loc. &2 not linked to warehouse number &3 |
| 132 | Product and entitled assigned to different systems: &1/&2 |
| 133 | Product &1 Inbound delivery &2/&3. Full GR is not sent yet |
| 134 | System &1. Only full GR will be sent. Differences could be incorrect |
| 135 | Business partner &1 has no vendor assignment (no carrier in ERP) |
| 136 | Process not supported in Cloud: &1 &2 |
| 137 | Technical Error in Simulation of LE Update: &1 &2 &3 &4 |
| 138 | No authorization to replicate production supply area for warehouse &1 |
| 139 | Enter a customer for the customer stock. |
| 140 | &1, &2 position is consistent. Quantity adjustment is not necessary. |
| 141 | &1, &2 position is with errors. Quantity adjustment is not possible |
| 142 | &1, &2 position is already submitted at ERP. |
| 143 | &1, &2 position: Quantity adjustmet was already carried out. |
| 144 | Cannot cal. quantity in queue; comm. with sys. &1 is though IDoc |
| 145 | Cannot determine status and quantity in queue for target system &1 |
| 146 | Stock in unprocessed queue exists for seleced row; correction not allowed |
| 147 | Cannot collect queue data; error in target system &1 |
| 148 | Item deleted for goods issue reverse message stuck in queue &1 in sys &2 |
| 149 | qRFC configuration failed for target system &1 |
| 150 | Function module &1 does not exist in target system &2 |
| 151 | Storage location &1 does not exist in plant &2 |
| 152 | No PSA found in EWM for ERP PSA &1 plant &2 whse no. &3 |
| 153 | Kit hierarchy forbidden for Adv. SR; reject queue |
| 154 | Special stock indicator &1 not supported in the warehouse. |
| 155 | Movement reason &1 is not defined for movement type &2 |
| 156 | Movement type &1 is not defined for any movement reason |
| 157 | Posting String Reference &1 is not defined. |
| 158 | Selected recipient location data is already replicated to EWM. |
| 160 | Recipient location successfully replicated. |
| 161 | No recipient location data found for selection criteria. |
| 200 | --------------Messages for Monitoring /SCWM/DOC_SEARCH------------------- |
| 201 | Incorrect document number or document type. Check your entry |
| 202 | Make a selection first |
| 203 | Action not possible. You have not selected an entry |
| 204 | Entry not complete. Check the data |
| 205 | Entry not clear. Check entry type |
| 206 | Entry not complete. Select a document type |
| 207 | Entry not clear. Check your entry |
| 210 | Entry not clear. You have not selected any entries in message log |
| 211 | No update to database was possible for /SCWM/MESSAGELOG |
| 212 | No update was possible to database /LIME/COLL_W2IM |
| 213 | Entry not unique. You have not selected any entries in the PPF |
| 300 | ---------- Messages for PrioP |
| 301 | Start of priority processing |
| 302 | EWM delivery for &1 &2 from &3 not found |
| 303 | Priority for &1 &2 from &3 not relevant as processing has already begun |
| 304 | EWM delivery for &1 &2 from &3 could not be locked |
| 305 | Queue &1 was integrated |
| 306 | Background job &1 was integrated |
| 307 | Priority processing has finished |
| 308 | Warehouse request for SAP EWM delivery &1 exists |
| 309 | Priority for &1 &2 from &3 relevant for update |
| 310 | Priority for &1 &2 from &3 updated successfully |
| 314 | No priority remaining for update |
| 350 | ---------- Messages for GI cancellation |
| 352 | &1 Deliveries locked for processing |
| 400 | -----------Messages for Functions in Delivery Core----------------------- |
| 401 | Number range &1 for object &2 is almost exhausted |
| 402 | The last number has been assigned from number range &1 for object &2 |
| 403 | Could not find the interval for number assignment (object &1) |
| 404 | ASN/BOL reference already exists in document &1. |
| 405 | Cannot activate document &1 because a warehouse activity has been started |
| 406 | Document &1 cannot be distributed into the ERP system |
| 407 | New items can only be created in original system &1 |
| 408 | Warehouse number not changeable (document &1) |
| 409 | Document item &1/&2 blocked due to validation error in ERP |
| 410 | ASN or BOL missing as delivery header references (document &1) |
| 411 | Ship-from party missing in delivery header partners (document &1) |
| 412 | Action cannot be carried out due to the integration with the LE delivery |
| 413 | Product &1 has not been distributed correctly from ERP system &2 |
| 414 | Delivery date is missing (document &1) |
| 415 | Purchase order with item missing as item reference (doc. &1/&2) |
| 416 | Purchase order &1/&2 does not exist in ERP system (document &3/&4) |
| 417 | ERP item reference cannot be locked |
| 418 | ERP/ERO reference cannot be changed (document &1) |
| 419 | Last document item cannot be deleted |
| 420 | Item &1 does not contain a reference to a manufacturing order |
| 421 | Production reference could not be validated in EWM |
| 422 | Production reference was validated successfully in EWM |
| 423 | You cannot reverse full goods receipt; GR mode &1 prohibits it |
| 424 | Items of document &1 are assigned to different PSA |
| 425 | Subitems cannot be transferred into a single outbound delivery |
| 426 | Partner &1 &2 plant (role &3); no delivery creation in EWM |
| 427 | Repetitive manufacturing: Goods receipt at creation is obligatory |
| 428 | Repetitive manufacturing: Activation at creation is obligatory |
| 429 | Only full Goods Receipt Reversal is enabled in the ARM process |
| 430 | Cannot delete handlings units of inbound delivery with ERP document &1 |
| 431 | Specify a batch for serial number and batch managed material |
| 432 | Cannot update document &1; DTD status is Ready For Warehouse Execution |
| 433 | Cannot update document &1; DTR status is In Yard |
| 500 | ----------Messages for IDoc ----------------- |
| 501 | Function module &1 was called |
| 502 | IDoc successfully generated and distributed |
| 503 | IDoc was generated successfully for logical system &1 |
| 504 | Partner profile &1 does not have a message type in outbound parameters |
| 505 | Conversion error in segments & |
| 506 | Function & successfully completed |
| 507 | IDOC processing was cancelled for the purpose of debugging |
| 508 | System setting makes it impossible to create an inbound delivery locally |
| 509 | Logical system &1; no IDOC processing in simulation mode. |
| 510 | Rounding Residuals posted to Difference Analyzer with Warehouse Task &1 |
| 511 | Errors occurred when posting Rounding Residuals to Difference Analyzer |
| 512 | Rounding Residuals skipped, because they are not relevant for simulation |
| 550 | ----------Messages for External Staging Request------ |
| 551 | Cross-order and single-order import tables cannot both be empty |
| 552 | Error in delivery query for production order &1 |
| 553 | Production order &1 not found |
| 554 | Invalid reservation item &2 for production order &1 |
| 555 | No staging warehouse tasks can be created for given input |
| 556 | Enter consistent input data |
| 557 | System ignored line &2 of input table &1 |
| 558 | System ignored line &2 of input table &1 |
| 559 | &1 warehouse tasks created but errors occurred; see ET_BAPIRET |
| 560 | Production order &1, reservation item &2 is not single-order staging |
| 561 | UoM &1 is not valid for product &2 |
| 562 | &1&2&3&4 |
| 563 | UoM &1 is not valid for product &2 (prod. order &3, reservation item &4) |
| 564 | System could not read batch for product &1 |
| 565 | System could not read UoM for products |
| 566 | Fill in all mandatory parameters |
| 567 | Order &1, reserv. item &2 is MES-relevant; create tasks from whse request |
| 600 | ----------------------- Messages from ERP Part 2 ------------------------ |
| 601 | Quantity reduction from &1 to &2 &3 for item &4 |
| 602 | Order reduction: Quantity role &1 set to &2 &3 for item &4 |
| 603 | Unexpected value &1 in parameter &2 field &3 |
| 604 | Unexpected value &1 in parameter &2 field &3 for item &4 |
| 605 | Unexpected value &1 in parameter &2 |
| 606 | No EWM-relevant changes; no update required |
| 607 | TM planning indicator &1 not supported w/o GTS integration; reject queue |
| 700 | --------------- Error Messages for Customizing--------------------------- |
| 701 | There is already an entry with the same secondary key |
| 702 | Lower case letters in the business system can cause problems with mapping |
| 703 | Date/time type &1 is not used for document type &2 |
| 704 | Document type &1 not intended |
| 705 | Item type &1 for document type &2 not intended |
| 706 | Date/time type &1 is not used for item type &2 with document category &3 |
| 707 | Maintain differentiation profile for document and/or item type |
| 708 | The table row contains entries in invisible fields |
| 709 | The table row contains entries in invisible fields |
| 710 | An entry with the same business key already exists |
| 711 | You cannot report the delivery date to ERP |
| 712 | Recommended SAP system settings have been changed |
| 713 | No corresponding entry in table &1 for indicators |
| 714 | Initiator process for document &1 does not match initiator from ERP &2 |
| 715 | Initiator process &1 not defined (domain &2) |
| 716 | There is already an entry on header/item level with same date settings |
| 717 | Communication of batch split with partial goods receipt is not supported |
| 718 | ERP Partner role &1 cannot be used. Standard mapping is used. |
| 719 | Partner role &1 cannot be used. Standard mapping is used. |
| 720 | Definition of own business system is missing |
| 721 | Enter an EWM warehouse number for business system &1, ERP warehouse &2 |
| 722 | &1 is SAP S/4HANA Cloud; set system &2 as cloud or correct version |
| 723 | ERP warehouse &1 is not configured as EWM (decentralized WMS) |
| 724 | ERP warehouse &1 is not configured as S/4HANA Cloud embedded |
| 725 | Exactly one storage location should be assgined to ERP warehouse &1 |
| 726 | ERP warehouse &1 does not exist |
| 727 | Entry not possible; ERP warehouse &1 already assigned to warehouse &2 |
| 728 | Entering a business system is not allowed; delete value in field |
| 729 | Import VDAT /SCWM/V_TMAPSTLO: Entry with LOGSYS &1 changed for &2 &3. |
| 730 | Cannot cancel material document containing HUs. |
| 731 | Synchronous goods movement is not supported for this process. |
| 732 | IDoc-based delivery integration for SAP ERP &1 not supported |
| 733 | Enter an Identification Type or a Partner Type, but not both. |
| 734 | Import VDAT /SCWM/V_TMAPSTLO: Entry with LOGSYS &1 deleted for &2 &3. |
| 735 | Import VDAT /SCWM/V_TMAPSTLO: &1 entries to convert. |
| 736 | Import VDAT /SCWM/V_TMAPSTLO: Entry with LOGSYS &1 created for &2 &3. |
| 737 | Import VDAT /SCWM/V_TMAPSTLO: Creation of &1 entries failed. |
| 750 | -------------------- Messages for TM Integration ------------------------ |
| 751 | Transportation Management data read. |
| 752 | Delivery updated |
| 753 | Partner role &1 not active in delivery profile (&2 &3) |
| 754 | Delivery set to Ready for Warehouse Processing |
| 755 | Delivery set to Registered In Yard |
| 756 | Delivery set to In Transit |
| 757 | No Transportation Management data read |
| 758 | The Transportation Management data is inconsistent |
| 759 | Transportation Management data for &1 inconsistent |
| 760 | Delivery set to Pending |
| 800 | ---------------Messages for the message log------------------------------ |
| 801 | Error determining message &1 |
| 802 | Error during determination action code &1 for message &2 |
| 803 | Goods issue posting was not performed yet in the ERP system |
| 804 | Error 2 |
| 805 | Error 3 |
| 806 | Error 4 |
| 807 | ERP: No unprocessed entries in message log |
| 808 | ERP: Start of message processing |
| 809 | ERP: End of message processing |
| 810 | ERP: LIME collection records received |
| 811 | ERP: Setup of message IBDLV_CONFIRM_DEC &1 &2 |
| 812 | ERP: Setup of message IBDLV_REPLACE &1 &2 |
| 813 | ERP: Setup of message IBDLV_SAVEREPLICA &1 &2 |
| 814 | ERP: Setup of message IBDLV_RESPONSE &1 &2 |
| 815 | ERP: Setup of message IBDLV_SPLIT_DEC &1 &2 |
| 816 | ERP: Setup of message OBDLV_CHANGE &1 &2 |
| 817 | ERP: Setup of message OBDLV_CONFIRM_DEC &1 &2 |
| 818 | ERP: Setup of message OBDLV_SPLIT_DEC &1 &2 |
| 819 | Message &1 with action code &2 to system &3 was determined |
| 820 | Message &1 is not sent to SAP ERP system |
| 821 | PPF action is not executed automatically |
| 822 | Inbound delivery split prevented |
| 823 | Full GR cannot be sent due to open items |
| 824 | Zero GI cannot be sent due to open items |
| 825 | Item &1 could not be positively validated in ERP &2 |
| 826 | ERP has the following message for item &1 &2&3&4 |
| 827 | ERP: Setup of message &1 &2 &3 |
| 828 | ERP: Setup of message &1 &2 &3 |
| 829 | Means of transport &1 not configured for ERP confirmation |
| 830 | Date/time &1 not configured for ERP confirmation |
| 831 | Initiator process code &1 found |
| 832 | Partner &1 not configured for ERP confirmation |
| 833 | Unable to send zero GI cancelation due to open items |
| 834 | Unable to process PPF action (header:&1 item:&2) num.of items:&3 |
| 835 | Inspection document not found |
| 836 | Another PPF action of same kind is already running |
| 837 | Execution of action terminated |
| 838 | Processing of prerequisite message log entries belonging to &1 &2 failed |
| 839 | Processing of message logs belonging to current doc. cannot be continued |
| 840 | Processing of message logs repeated to ensure successful execution |
| 841 | Execution being repeated due to newly found message log entries |
| 842 | PPF trigger cannot be retrieved for document &1 &2 |
| 843 | No trigger for document &1 &2 |
| 844 | Prerequisite message log entries belonging to &1 &2 processed. |
| 845 | ERP: The content of the message log changed during execution |
| 846 | ERP: The content of the LIME collection changed during execution |
| 847 | Processing of partial GR is delayed for collective message sending |
| 848 | &1 IDoc failed with Shipment &2 |
| 849 | Processing of inspection result is delayed until full goods receipt |
| 850 | GM reversal and line entries processed together (guid_coll_group = &1) |
| 851 | Document &1 is being processed via IDoc |
| 852 | Queue name: &1 has been set for the further processing of document &2 |
| 853 | Unable to send PCGM message |
| 854 | No authorization to show application log of queue &1 in SAP ERP |
| 855 | Function &1 of queue &2 does not exist in SAP ERP |
| 856 | Replay function of fuction &1 of queue &2 does not exist in SAP ERP |
| 857 | Error calling function module &1 |
| 858 | Message &1 sent to ERP |
| 859 | Dialog destination for logical system &1 is missing |
| 860 | Communication to logical system &1 via RFC is not supported |
| 861 | Wait until updates of dependant data are completed |
| 862 | Wait until updates of dependant data are completed in LE |
| 863 | Either enter a logical system or mark plant &1 as local. |
| 864 | Enter a party entitled to dispose. |
| 865 | Enter a plant. |
| 866 | The warehouse entered (&1) does not match the determined warehouse (&2) |
| 867 | You cannot use synchronous goods movement in decentralized EWM. |
| 868 | You can't post to embedded and decentralized warehouses at the same time. |
| 869 | You can't post synchronous goods movement to EWM for movement from EWM |
| 870 | You can only post synchronous goods movement to one warehouse at a time |
| 871 | The item with material &1 in plant &2 and warehouse &3 was not checked |
| 872 | Update failed for item with material &1 in plant &2 and warehouse &3 |
| 873 | Enter serial numbers for material &1. |
| 874 | You can't perform this action, synchronous goods movement is not active. |
| 875 | The item with material &1 in plant &2 and warehouse &3 is faulty. |
| 876 | There are no valid goods movement items to be created. |
| 877 | The item with material &1 is not relevant for synchronous goods movement. |
| 878 | Enter a material document or posting year. |
| 879 | You can't perform a posting change, synchronous goods movement is active. |
| 880 | You can't transfer the stock because synchronous goods movement is active |
| 881 | There are no cancel relevant goods movement items for document &1/&2 |
| 882 | You can't post synchronous goods movement to the difference analyzer. |
| 883 | The item with material &1 contains errors. The item was not changed. |
| 884 | Enter the warehouse number. |
| 885 | Not all of the goods movement items belong to order number &1. |
| 886 | The goods movement items belong to different order numbers, &1 and &2. |
| 887 | This posting item is not relevant for backflush. |
| 888 | There is a mismatch between the storage bin and the posting item. |
| 889 | Several PMR documents found for order number &1. |
| 890 | Delay message sending of locally created and blocked delivery |
| 891 | You can't cancel a reversal or cancellation posting based on HUs. |
| 892 | HU to be saved is not created yet in HU buffer. |
| 893 | Catch weight UoM of HU item is not equal to CW UoM of GM item (&1:&2). |
| 894 | Catch weight quantity of HU item is not equal to GM item quantity (&1:&2) |
| 895 | Quantity of HU item is not equal to quantity of GM item (&1:&2). |
| 896 | Quantity UoM of HU item is not equal to quantity UoM of GM item (&1:&2). |
| 897 | HU item quantity differs from requested HU item quantity (&1:&2). |
| 898 | HU item catch weight quantity differs from requested HU item (&1:&2). |
| 899 | HU item stock key differs from requested HU item stock key. |
Message texts are shown for technical reference in consulting and education contexts. SAP, SAP TM, SAP EWM, SAP GTS, SAP S/4HANA and other SAP product and service names are trademarks or registered trademarks of SAP SE in Germany and other countries.