SAP ABAP Message Class /SPE/ID_HANDLING (Inbound Delivery Handling)
Basic Data
Hierarchy
☛
SAP_APPL (Software Component) Logistics and Accounting
⤷
LO-SPM-INB (Application Component) Goods Receipt Process
⤷
/SPE/ID_HANDLING (Package) Inbound delivery handling
⤷
⤷
Attributes
| Message class | /SPE/ID_HANDLING | |
| Short Description | Inbound Delivery Handling | |
| Changed On | 20130531 | |
| Last Changed At | 100115 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | & & & & | Space: object requires documentation | ||
| 2 | Class & does not exist | Space: object requires documentation | ||
| 3 | Problem with creation of class & | Space: object requires documentation | ||
| 4 | Inbound delivery & is marked for deletion; no follow-on function possible | Space: object requires documentation | ||
| 5 | You cannot create the delivery because & already exists | Space: object requires documentation | ||
| 6 | Posting GR is not possible for a delivery with HOLD or TMP status | Space: object requires documentation | ||
| 7 | Posting GR is not possible for a delivery item & with HOLD status | Space: object requires documentation | ||
| 8 | If the header is in HOLD status, then all items should also be in HOLD | Space: object requires documentation | ||
| 9 | Inbound delivery &1 has a deletion indicator and cannot be displayed | Space: object requires documentation | ||
| 10 | You cannot change the warehouse number in item & | Space: object requires documentation | ||
| 11 | ID &1 is already packed, so can be deleted only with delete indicator | Space: object requires documentation | ||
| 12 | Because of previous error, dispatching is not possible for ID &1 | Space: object requires documentation | ||
| 13 | TA &1 is not supported for this process; use TA &2 | Space: object requires documentation | ||
| 14 | Inconsistency between parameters of the collected messages | Space: object requires documentation | ||
| 15 | Bad validation result without error messages | Space: object requires documentation | ||
| 16 | Inbound delivery has a linked temporary delivery. Only display possible | Space: object requires documentation | ||
| 17 | Sender method &1 not supported | Space: object requires documentation | ||
| 18 | Save the inbound delivery before posting goods receipt | The short text describes the object sufficiently | ||
| 19 | You can only display this inbound delivery | Space: object requires documentation | ||
| 20 | Inbound delivery was created in external Warehouse.Only display possible. | The short text describes the object sufficiently | ||
| 21 | *** Pre-Validation Errors *** | Space: object requires documentation | ||
| 22 | Duplicate key in field LIFEX: &1 | Space: object requires documentation | ||
| 23 | DUPKEY in LIFEX: &1, in process | Space: object requires documentation | ||
| 24 | Action &1 not supported for sender type &2 | Space: object requires documentation | ||
| 25 | Inbound delivery: &1 does not exist | Space: object requires documentation | ||
| 26 | Temporary ID &1 for inbound delivery &2 already exists | Space: object requires documentation | ||
| 27 | Inbound delivery: &1 already in process (IY/GR) | Space: object requires documentation | ||
| 28 | No active inbound delivery found for LIFEX &1 | Space: object requires documentation | ||
| 29 | Action: &1 not supported | Space: object requires documentation | ||
| 30 | No temporary ID exists for ACK/REJ of ID &1 | Space: object requires documentation | ||
| 31 | The value of the field delivery item number must be unique &1 | The short text describes the object sufficiently | ||
| 32 | ASN &1 has been created in EWM. No changes possible! | The short text describes the object sufficiently | ||
| 33 | Item &1 of ASN &2 has been created in EWM. No Item changes possible! | The short text describes the object sufficiently | ||
| 34 | Invalid delivery date | The short text describes the object sufficiently | ||
| 35 | Invalid ASN shipping date | The short text describes the object sufficiently | ||
| 36 | Invalid transportation planning date | The short text describes the object sufficiently | ||
| 37 | Invalid document date | The short text describes the object sufficiently | ||
| 38 | Error in calculation of cumulative quantity for SA &1, item &2 | Space: object requires documentation | ||
| 39 | No UOM found for calculation of cumulative quantity for SA &1, item &2 | Space: object requires documentation | ||
| 40 | No output UOM spec. for calc. of cumulative quantity for SA &1, item &2 | Space: object requires documentation | ||
| 41 | No base UOM found for item &1; no calc. of CQ in transit possible | Space: object requires documentation | ||
| 42 | UOM conversion not possible; no calc. of CQ in transit for item &1 | Space: object requires documentation | ||
| 43 | UOM conversion not possible; no calc. of CQ in transit for item &1 | Space: object requires documentation | ||
| 44 | Field overflow in &1 during conversion of value &2 in program &3 | The short text describes the object sufficiently | ||
| 45 | The difference (&1,&2) between ERP and EWM quantity is higher than &3 | The short text describes the object sufficiently | ||
| 46 | No UOM found for calc. of CQ received for SA &1, item &2 | Space: object requires documentation | ||
| 47 | UOM conversion not possible; no calc. of CQ received for item &1 | Space: object requires documentation | ||
| 48 | Error in calculation of CQ received for SA &1, item &2 | Space: object requires documentation | ||
| 49 | Item &1 of inbound delivery &2 could not be deleted | The short text describes the object sufficiently | ||
| 50 | Only one inbound delivery on hold can be processed at a time | The short text describes the object sufficiently | ||
| 51 | Item &1 of inbound delivery &2 remains in status "on hold" | The short text describes the object sufficiently | ||
| 52 | You cannot change status of inbound delivery &1 item &2 to 'hold' | Space: object requires documentation | ||
| 53 | You cannot change status of inb.dlv. head &1 from 'non-hold' to 'hold' | The short text describes the object sufficiently | ||
| 54 | Posting GR is not possible for a delivery | The short text describes the object sufficiently | ||
| 55 | Internal error &1 &2 &3 &4 | Space: object requires documentation | ||
| 56 | Action code &1 not supported | Space: object requires documentation | ||
| 57 | Qualifier &1 in segment &2 not supported | Space: object requires documentation | ||
| 58 | ******* Dispatching messages ******* | The short text describes the object sufficiently | ||
| 59 | dispatched &1 &2 to: &3 &4 | The short text describes the object sufficiently | ||
| 60 | Inbound delivery creation is successful | The short text describes the object sufficiently | ||
| 61 | Error during the inbound delivery creation | The short text describes the object sufficiently | ||
| 62 | Inbound delivery modification is successful | The short text describes the object sufficiently | ||
| 63 | Error during inbound delivery modification | The short text describes the object sufficiently | ||
| 64 | Return delivery creation is successful | The short text describes the object sufficiently | ||
| 65 | Error during the return delivery creation | The short text describes the object sufficiently | ||
| 66 | Goods receipt posting is successful | The short text describes the object sufficiently | ||
| 67 | Error during goods receipt posting | The short text describes the object sufficiently | ||
| 68 | Quantity difference posting is successful | The short text describes the object sufficiently | ||
| 69 | Error during quantity difference posting | The short text describes the object sufficiently | ||
| 70 | Cancel goods receipt posting is successful | The short text describes the object sufficiently | ||
| 71 | Error during cancellation of goods receipt posting | The short text describes the object sufficiently | ||
| 72 | Delete inbound delivery is successful | The short text describes the object sufficiently | ||
| 73 | Error during inbound delivery deletion | The short text describes the object sufficiently | ||
| 74 | Purge inbound delivery is successful | The short text describes the object sufficiently | ||
| 75 | Error during inbound delivery purging | The short text describes the object sufficiently | ||
| 76 | Split inbound delivery is successful | The short text describes the object sufficiently | ||
| 77 | Error during inbound delivery split | The short text describes the object sufficiently | ||
| 78 | ASN already contains packing items - no changes possible from ICH-side | The short text describes the object sufficiently | ||
| 79 | Automatic GR posting is not possible for the delivery &1. | The short text describes the object sufficiently | ||
| 80 | No messages issued during check | The short text describes the object sufficiently | ||
| 81 | No inbound deliveries found for purging | Space: object requires documentation | ||
| 82 | Package size greater than &1 not allowed. Size was set to maximum | Space: object requires documentation | ||
| 83 | Package size greater than 10000 not allowed. Size was set to maximum | The short text describes the object sufficiently | ||
| 84 | Expected GR document &1 is successfully created | The short text describes the object sufficiently | ||
| 85 | Expected GR document is successfully simulated | The short text describes the object sufficiently | ||
| 86 | Faulty expected GR documents for PO or SA | The short text describes the object sufficiently | ||
| 87 | Error free expected GR documents for PO or SA | The short text describes the object sufficiently | ||
| 88 | Faulty expected GR documents for production order | The short text describes the object sufficiently | ||
| 89 | Error free expected GR documents for production order | The short text describes the object sufficiently | ||
| 90 | The number of the faulty EGR doc. for PO or SA is &1 | The short text describes the object sufficiently | ||
| 91 | The number of the error free EGR doc. for PO or SA is &1 | The short text describes the object sufficiently | ||
| 92 | The number of the faulty EGR doc. for production order is &1 | The short text describes the object sufficiently | ||
| 93 | The number of the error free EGR doc. for production order is &1 | The short text describes the object sufficiently | ||
| 94 | Messages for the document & | The short text describes the object sufficiently | ||
| 95 | Check that the EGR documents from previous runs are deleted | The short text describes the object sufficiently | ||
| 96 | IDOC &1 was split | The short text describes the object sufficiently | ||
| 97 | IDOC &1 was created | The short text describes the object sufficiently | ||
| 98 | Problem with receiver finding | The short text describes the object sufficiently | ||
| 99 | No function module is found for delivery replication | The short text describes the object sufficiently | ||
| 100 | Sales UoM &1 of subitem are not the same as in main item &2 | The short text describes the object sufficiently | ||
| 101 | Business function SPE_CI_1 required for STO additional item discrepancy | The short text describes the object sufficiently | ||
| 102 | Split request is across HUs, which is not allowed | Space: object requires documentation | ||
| 103 | Requested delivery could not be split correctly | The short text describes the object sufficiently | ||
| 104 | Serialnumber update is not possible in &1/&2 during split | The short text describes the object sufficiently | ||
| 105 | HU update is not possible in &1 during split | The short text describes the object sufficiently | ||
| 106 | Deletion of already posted HUs (&2) in &1 is not allowed | Space: object requires documentation | ||
| 107 | New qty (&3) for the orig ID (&1/&2) is less than the posted qty | The short text describes the object sufficiently | ||
| 108 | Unknown item (&1) in the original ID | The short text describes the object sufficiently | ||
| 109 | Qty (&3) in split ID (&1/&2) is greater than free qty (&4) in the orig ID | The short text describes the object sufficiently | ||
| 110 | Order &1 has already been final delivered | The short text describes the object sufficiently | ||
| 111 | Space: object requires documentation |
History
| Last changed on/by | 20130531 | SAP | |
| SAP Release Created in | 100 |