IUID - Messages Class for Unique Item Identification
The following messages are stored in message class IUID: Messages Class for Unique Item Identification.
It is part of development package IUID in software component LO-MD-UID. This development package consists of objects that can be grouped under "".
It is part of development package IUID in software component LO-MD-UID. This development package consists of objects that can be grouped under "".
Message Nr ▲ | Message Text |
|---|---|
| 000 | & & & & |
| 001 | SerUsage for procedure MMSL of profile &1 has to be obligatory |
| 002 | Serial number profile cannot be used with IUID handling |
| 003 | Same enterprise identifier already exists in other client |
| 004 | Choose serial number profile for IUID-relevant material |
| 005 | Choose IUID type for IUID-relevant material |
| 006 | Material &1 is not IUID-relevant in the plant &2 |
| 007 | Specify the plant responsible for the UII |
| 008 | A UII cannot be created for this plant |
| 009 | UII is obligatory for material &1 in plant &2 |
| 010 | Serialization level of explicitness is not allowed for IUID type 'UID1' |
| 011 | Material no. &1 does not equal material no. &2 in equipment master data |
| 012 | Specify Issuing Agency Code and Enterprise Identifier in Customizing |
| 013 | Serial no. &1 does not equal serial no. &2 in equipment master data |
| 014 | Automatic ser. no. creation not allowed with external UII assignment |
| 015 | There is no UII for equipment & |
| 016 | No separation of components possible for externally created UII &3 |
| 017 | UII &2 does not fit creation rules of corresponding IUID type &1 |
| 018 | UII is set to external creation; internal creation of UIIs not possible |
| 019 | UII &1 was created for material &2 |
| 020 | UII &1 was changed for material &2 |
| 021 | UII &1 already exists |
| 022 | Range handling only allowed for IUID type 'UID1' or 'UID2' and not for &1 |
| 023 | There are pieces of equipment (e.g. &2) in plant &1 without UII |
| 024 | IUID type missing in material master for material &1 in plant &2 |
| 025 | For IUID type UID1 and UID2 a numeric serial number is required |
| 026 | UII or equipment number is missing |
| 027 | Unable to determine the components of the UII &1 |
| 028 | Serial number cannot be separated by UII & |
| 029 | &1 UIIs created and assign to equipment &2 &3 &4 |
| 030 | Equipment does not exist for UII & |
| 031 | UII &1 is not included in the object list |
| 032 | UII &1 is already in the object list |
| 033 | Enter a material first |
| 034 | UII & does not exist |
| 035 | IUID Type &1 differs from IUID Type &2 defined in material master |
| 036 | Material can not be changed because of already entered iuid data |
| 037 | No equipment stock found |
| 038 | IUID type missing in equip. master for mat. &1 and ser.no. &2 combination |
| 039 | UII &1 is already assigned to material &2 |
| 040 | Serial number &1 differs from serial number &2 already assigned to UII &3 |
| 041 | UII & is internally created and cannot be changed |
| 042 | No authorization |
| 043 | Construct of UII & is used for internal creation, but master data missing |
| 044 | UII &1 requires serial number synchronous to equipment number |
| 045 | Embedded items are only allowed for IUID relevant main items |
| 046 | UII &1 differs from UII &2 assigned to serial number &3 of material &4 |
| 047 | Only the leading & characters of UII have been considered for search |
| 048 | Internal creation of UIIs only in transactions IQ01 and IQ04 possible |
| 049 | Maximum length of UII exceeded |
| 050 | Conflict regarding IUID relevant flag: Vendor does not provide UII. |
| 051 | UII &1 contains invalid characters |
| 052 | Exactly &1 serial numbers/UIIs must be selected (instead of &2) |
| 053 | All serial numbers/UIIs have been entered |
| 054 | Material &1 related to UII &2 differs from material &3 of item &4 |
| 055 | Serial number &1 differs from serial number &2 related to UII &3 |
| 056 | Invalid combination of importing parameters UII and equipment number |
| 057 | No superior UII found |
| 058 | UII &1 has a superior UII and therefore could not be used as main item |
| 059 | Status "UII Status Undefined" cannot be assigned to UII &1 |
| 060 | UII & cannot be sent to registry |
| 061 | PM order &1 is not technically completed. UII &2 cannot be attached |
| 062 | PM order &1 is technical incomplete. UII &2 cannot be sent to registry |
| 063 | PM order &1 (related to UII &2) cannot be found |
| 064 | UII &1 is not confirmed by registry yet |
| 065 | Profile &1 is already assigned to IUID-relevant material |
| 066 | SerUsage for procedure MMSL of profile &1 has to be obligatory |
| 067 | UII &1 is already assigned plant maintenance order &2 |
| 068 | UII &1 requires a related serial number. |
| 069 | |
| 070 | OBJK-entry not found for MATNR/SERNR: &1 or EQUNR: &2 or UII: &3&4 |
| 071 | Inconsistence (different UIIs) in OBJK; MATNR: &1 / SERNR: &2 |
| 072 | UII in OBJK-Set updated. MATNR: &1, SERNR: &2; old UII: &3&4 |
| 073 | UII in EQUI-Set updated. EQUNR: &1, old UII: &2&3 |
| 074 | UII in &4-Set updated. EQUNR: &1, old UII: &2&3 |
| 075 | UII in OBJK-Set updated. MATNR: &1, SERNR: &2; new UII: &3&4 |
| 076 | UII in EQUI-Set updated. EQUNR: &1, new UII: &2&3 |
| 077 | UII in &4-Set updated. EQUNR: &1, new UII: &2&3 |
| 078 | &1 OBJK-Set(s) updated |
| 079 | &1 EQUI-Set(s) updated |
| 080 | &1 IBSP-Set(s) updated |
| 081 | &1 &2-Set(s) updated |
| 082 | &1 UII(s) generated |
| 083 | &1 OBJK-Set(s) inconsistent |
| 084 | &1 OBJK-Set(s) not found |
| 085 | Internal error; &1&2&3&4 |
| 086 | Using existing UII (&1&2) from OBJK instead of generated UII (&3&4) |
| 087 | Changes written to database. (COMMIT) &1&2&3&4 |
| 088 | IUID_TYPE (&1) and/or UII_PLANT (&2) written to EQUI-set. |
| 089 | Serial number/UII quantity does not match purchase order quantity |
| 090 | Object link between IDoc(&1) and equipment(&2) cannot be created |
| 091 | Object link between IDoc(&1) and outbound delivery(&2) cannot be created |
| 092 | External UII &1 has already been sent. No change allowed. |
| 093 | UII & is already being used by another item |
| 099 | Create serial numbers and UIIs for each individual item |
| 100 | Select at least one UII |
| 101 | No application log existing |
| 102 | Messages occurred; see application log |
| 103 | Select one UII only |
| 104 | Top-level UII is not unique in the hierarchy |
| 105 | Selected UII is not in a hierarchy |
| 106 | Inconsistent configuration of IUID message fields |
| 107 | Field &1 is mandatory |
| 108 | Message cannot be sent due to missing status "UII Attached" |
| 109 | &1 is an invalid entry for field &2; use the input help |
| 110 | UII is external but no entry was found in the pedigree database |
| 111 | UIIs in the hierarchy with status "UII Sent" have been resent |
| 112 | UII &1 does not have the required status "Sent" or "Confirmed" |
| 113 | Receiver system cannot be determined; check distribution model |
| 114 | eSOA proxy call returns an error |
| 115 | Functional location &2 is locked by user &1 |
| 116 | Higher-level functional location is locked by user &1 |
| 117 | EHP5 IUID functions are active; cannot execute transaction &1 |
| 118 | Registry system could not be reached; no data retrieved from registry |
| 119 | IDoc not created; check filter objects in the distribution model |
| 120 | Manual message &1&2 for UII &3 sent to registry |
| 121 | Parent UII and UII are identical; parent UII must be different to UII |
| 122 | Unspecified or incorrect field name |
| 123 | Pedigree data cannot be displayed |
| 124 | Entry &1 is invalid for the "Configuration Action" field |
| 125 | Entry &1 is invalid for the "Item Type" field |
| 126 | Messages for the IUID consistency check |
| 127 | Message cannot be sent |
| 128 | Transfer Type &1 Content Type &2 is not valid. |
| 129 | No fields defined for Transfer Type &1 Content Type &2 |
| 215 | Enter a serial number and UII first |
| 223 | Serial number &1 or UII does not exist yet for material &2 |