SAP ABAP Message Class IUID (Messages Class for Unique Item Identification)
Basic Data
Hierarchy
☛
SAP_APPL (Software Component) Logistics and Accounting
⤷
LO-MD-UID (Application Component) Unique Identification
⤷
IUID (Package) Item Unique Identification
⤷
⤷
Attributes
| Message class | IUID | |
| Short Description | Messages Class for Unique Item Identification | |
| Changed On | 20110908 | |
| Last Changed At | 171710 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | & & & & | The short text describes the object sufficiently | ||
| 2 | SerUsage for procedure MMSL of profile &1 has to be obligatory | Space: object requires documentation | ||
| 3 | Serial number profile cannot be used with IUID handling | Space: object requires documentation | ||
| 4 | Same enterprise identifier already exists in other client | The short text describes the object sufficiently | ||
| 5 | Choose serial number profile for IUID-relevant material | The short text describes the object sufficiently | ||
| 6 | Choose IUID type for IUID-relevant material | The short text describes the object sufficiently | ||
| 7 | Material &1 is not IUID-relevant in the plant &2 | The short text describes the object sufficiently | ||
| 8 | Specify the plant responsible for the UII | The short text describes the object sufficiently | ||
| 9 | A UII cannot be created for this plant | The short text describes the object sufficiently | ||
| 10 | UII is obligatory for material &1 in plant &2 | The short text describes the object sufficiently | ||
| 11 | Serialization level of explicitness is not allowed for IUID type 'UID1' | Space: object requires documentation | ||
| 12 | Material no. &1 does not equal material no. &2 in equipment master data | The short text describes the object sufficiently | ||
| 13 | Specify Issuing Agency Code and Enterprise Identifier in Customizing | The short text describes the object sufficiently | ||
| 14 | Serial no. &1 does not equal serial no. &2 in equipment master data | The short text describes the object sufficiently | ||
| 15 | Automatic ser. no. creation not allowed with external UII assignment | The short text describes the object sufficiently | ||
| 16 | There is no UII for equipment & | The short text describes the object sufficiently | ||
| 17 | No separation of components possible for externally created UII &3 | Space: object requires documentation | ||
| 18 | UII does not fit creation rules of corresponding IUID type & | Space: object requires documentation | ||
| 19 | UII is set to external creation; internal creation of UIIs not possible | Space: object requires documentation | ||
| 20 | UII &1 was created for material &2 | The short text describes the object sufficiently | ||
| 21 | UII &1 was changed for material &2 | The short text describes the object sufficiently | ||
| 22 | UII &1 already exists | The short text describes the object sufficiently | ||
| 23 | Range handling only allowed for IUID type 'UID1' or 'UID2' and not for &1 | The short text describes the object sufficiently | ||
| 24 | There are pieces of equipment (e.g. &2) in plant &1 without UII | Space: object requires documentation | ||
| 25 | IUID type missing in material master for material &1 in plant &2 | Space: object requires documentation | ||
| 26 | For IUID type UID1 and UID2 a numeric serial number is required | The short text describes the object sufficiently | ||
| 27 | UII or equipment number is missing | The short text describes the object sufficiently | ||
| 28 | Unable to determine the components of the UII &1 | The short text describes the object sufficiently | ||
| 29 | Serial number cannot be separated by UII & | The short text describes the object sufficiently | ||
| 30 | &1 UIIs created and assign to equipment &2 &3 &4 | The short text describes the object sufficiently | ||
| 31 | Equipment does not exist for UII & | The short text describes the object sufficiently | ||
| 32 | UII &1 is not included in the object list | The short text describes the object sufficiently | ||
| 33 | UII &1 is already in the object list | The short text describes the object sufficiently | ||
| 34 | Enter a material first | The short text describes the object sufficiently | ||
| 35 | UII & does not exist | The short text describes the object sufficiently | ||
| 36 | IUID Type &1 differs from IUID Type &2 defined in material master | The short text describes the object sufficiently | ||
| 37 | Material can not be changed because of already entered iuid data | The short text describes the object sufficiently | ||
| 38 | No equipment stock found | The short text describes the object sufficiently | ||
| 39 | IUID type missing in equip. master for mat. &1 and ser.no. &2 combination | The short text describes the object sufficiently | ||
| 40 | UII &1 is already assigned to material &2 | The short text describes the object sufficiently | ||
| 41 | Serial number &1 differs from serial number &2 already assigned to UII &3 | The short text describes the object sufficiently | ||
| 42 | UII & is internally created and cannot be changed | The short text describes the object sufficiently | ||
| 43 | No authorization | The short text describes the object sufficiently | ||
| 44 | Construct of UII & is used for internal creation, but master data missing | Space: object requires documentation | ||
| 45 | UII &1 requires serial number synchronous to equipment number | The short text describes the object sufficiently | ||
| 46 | Embedded items are only allowed for IUID relevant main items | The short text describes the object sufficiently | ||
| 47 | UII &1 differs from UII &2 assigned to serial number &3 of material &4 | The short text describes the object sufficiently | ||
| 48 | Only the leading & characters of UII have been considered for search | The short text describes the object sufficiently | ||
| 49 | Internal creation of UIIs only in transactions IQ01 and IQ04 possible | The short text describes the object sufficiently | ||
| 50 | Maximum length of UII exceeded | The short text describes the object sufficiently | ||
| 51 | Conflict regarding IUID relevant flag: Vendor does not provide UII. | The short text describes the object sufficiently | ||
| 52 | UII &1 contains invalid characters | Space: object requires documentation | ||
| 53 | Exactly &1 serial numbers/UIIs must be selected (instead of &2) | Space: object requires documentation | ||
| 54 | All serial numbers/UIIs have been entered | The short text describes the object sufficiently | ||
| 55 | Material &1 related to UII &2 differs from material &3 of item &4 | The short text describes the object sufficiently | ||
| 56 | Serial number &1 differs from serial number &2 related to UII &3 | The short text describes the object sufficiently | ||
| 57 | Invalid combination of importing parameters UII and equipment number | The short text describes the object sufficiently | ||
| 58 | No superior UII found | The short text describes the object sufficiently | ||
| 59 | UII &1 has a superior UII and therefore could not be used as main item | The short text describes the object sufficiently | ||
| 60 | Status "UII Status Undefined" cannot be assigned to UII &1 | Space: object requires documentation | ||
| 61 | UII & cannot be sent to registry | Space: object requires documentation | ||
| 62 | PM order &1 is not technically completed. UII &2 cannot be attached | The short text describes the object sufficiently | ||
| 63 | PM order &1 is technical incomplete. UII &2 cannot be sent to registry | The short text describes the object sufficiently | ||
| 64 | PM order &1 (related to UII &2) cannot be found | The short text describes the object sufficiently | ||
| 65 | UII &1 is not confirmed by registry yet | The short text describes the object sufficiently | ||
| 66 | Profile &1 is already assigned to IUID-relevant material | Space: object requires documentation | ||
| 67 | SerUsage for procedure MMSL of profile &1 has to be obligatory | Space: object requires documentation | ||
| 68 | UII &1 is already assigned plant maintenance order &2 | The short text describes the object sufficiently | ||
| 69 | UII &1 requires a related serial number. | The short text describes the object sufficiently | ||
| 70 | The short text describes the object sufficiently | |||
| 71 | OBJK-entry not found for MATNR/SERNR: &1 or EQUNR: &2 or UII: &3&4 | The short text describes the object sufficiently | ||
| 72 | Inconsistence (different UIIs) in OBJK; MATNR: &1 / SERNR: &2 | The short text describes the object sufficiently | ||
| 73 | UII in OBJK-Set updated. MATNR: &1, SERNR: &2; old UII: &3&4 | The short text describes the object sufficiently | ||
| 74 | UII in EQUI-Set updated. EQUNR: &1, old UII: &2&3 | The short text describes the object sufficiently | ||
| 75 | UII in &4-Set updated. EQUNR: &1, old UII: &2&3 | The short text describes the object sufficiently | ||
| 76 | UII in OBJK-Set updated. MATNR: &1, SERNR: &2; new UII: &3&4 | The short text describes the object sufficiently | ||
| 77 | UII in EQUI-Set updated. EQUNR: &1, new UII: &2&3 | The short text describes the object sufficiently | ||
| 78 | UII in &4-Set updated. EQUNR: &1, new UII: &2&3 | The short text describes the object sufficiently | ||
| 79 | &1 OBJK-Set(s) updated | The short text describes the object sufficiently | ||
| 80 | &1 EQUI-Set(s) updated | The short text describes the object sufficiently | ||
| 81 | &1 IBSP-Set(s) updated | The short text describes the object sufficiently | ||
| 82 | &1 &2-Set(s) updated | The short text describes the object sufficiently | ||
| 83 | &1 UII(s) generated | The short text describes the object sufficiently | ||
| 84 | &1 OBJK-Set(s) inconsistent | The short text describes the object sufficiently | ||
| 85 | &1 OBJK-Set(s) not found | The short text describes the object sufficiently | ||
| 86 | Internal error; &1&2&3&4 | The short text describes the object sufficiently | ||
| 87 | Using existing UII (&1&2) from OBJK instead of generated UII (&3&4) | The short text describes the object sufficiently | ||
| 88 | Changes written to database. (COMMIT) &1&2&3&4 | The short text describes the object sufficiently | ||
| 89 | IUID_TYPE (&1) and/or UII_PLANT (&2) written to EQUI-set. | The short text describes the object sufficiently | ||
| 90 | Serial number/UII quantity does not match purchase order quantity | The short text describes the object sufficiently | ||
| 91 | Object link between IDoc(&1) and equipment(&2) cannot be created | The short text describes the object sufficiently | ||
| 92 | Object link between IDoc(&1) and outbound delivery(&2) cannot be created | The short text describes the object sufficiently | ||
| 93 | External UII &1 has already been sent. No change allowed. | Space: object requires documentation | ||
| 94 | Create serial numbers and UIIs for each individual item | Space: object requires documentation | ||
| 95 | Select at least one UII | The short text describes the object sufficiently | ||
| 96 | No application log existing | The short text describes the object sufficiently | ||
| 97 | Messages occurred; see application log | Space: object requires documentation | ||
| 98 | Select one UII only | The short text describes the object sufficiently | ||
| 99 | Top-level UII is not unique in the hierarchy | Space: object requires documentation | ||
| 100 | Selected UII is not in a hierarchy | The short text describes the object sufficiently | ||
| 101 | Inconsistent configuration of IUID message fields | Space: object requires documentation | ||
| 102 | Field &1 is mandatory | The short text describes the object sufficiently | ||
| 103 | Message cannot be sent due to missing status "UII Attached" | Space: object requires documentation | ||
| 104 | &1 is an invalid entry for field &2; use the input help | The short text describes the object sufficiently | ||
| 105 | UII is external but no entry was found in the pedigree database | Space: object requires documentation | ||
| 106 | UIIs in the hierarchy with status "UII Sent" have been resent | The short text describes the object sufficiently | ||
| 107 | UII &1 does not have the required status "Sent" or "Confirmed" | The short text describes the object sufficiently | ||
| 108 | Receiver system cannot be determined; check distribution model | The short text describes the object sufficiently | ||
| 109 | eSOA proxy call returns an error | The short text describes the object sufficiently | ||
| 110 | Functional location &2 is locked by user &1 | The short text describes the object sufficiently | ||
| 111 | Higher-level functional location is locked by user &1 | The short text describes the object sufficiently | ||
| 112 | EHP5 IUID functions are active; cannot execute transaction &1 | The short text describes the object sufficiently | ||
| 113 | Registry system could not be reached; no data retrieved from registry | Space: object requires documentation | ||
| 114 | IDoc not created; check filter objects in the distribution model | The short text describes the object sufficiently | ||
| 115 | Manual message &1&2 for UII &3 sent to registry | The short text describes the object sufficiently | ||
| 116 | Parent UII and UII are identical; parent UII must be different to UII | The short text describes the object sufficiently | ||
| 117 | Unspecified or incorrect field name | Space: object requires documentation | ||
| 118 | Pedigree data cannot be displayed | Space: object requires documentation | ||
| 119 | Entry &1 is invalid for the "Configuration Action" field | Space: object requires documentation | ||
| 120 | Entry &1 is invalid for the "Item Type" field | Space: object requires documentation | ||
| 121 | Messages for the IUID consistency check | The short text describes the object sufficiently | ||
| 122 | Message cannot be sent | Space: object requires documentation | ||
| 123 | Enter a serial number and UII first | Space: object requires documentation | ||
| 124 | Serial number &1 or UII does not exist yet for material &2 | Space: object requires documentation |
History
| Last changed on/by | 20110908 | SAP | |
| SAP Release Created in | 603 |