Message Number list used by SAP ABAP Class CL_USMD_MODEL_CHECK (Checks Consistency of a Data Model)
SAP ABAP Class 
CL_USMD_MODEL_CHECK (Checks Consistency of a Data Model) is using
-
Class (47)
-
Data Element (114)
-
Table/Structure Field (229)
-
Function Module (12)
-
Interface (2)
-
Message Class (18)
-
Message Number (185)
-
Class Method (95)
-
Table (63)
-
View (21)
| # | Object Type | Object Name | Object Description | Note |
|---|---|---|---|---|
 |
|
|||
| 1 | Message Number |
USMD1 - 000 | Program error | |
| 2 | Message Number |
USMD1 - 000 | Program error | |
| 3 | Message Number |
USMD1 - 000 | Program error | |
| 4 | Message Number |
USMD1 - 002 | Data model &1, entity type &2: Data element &3 does not exist | |
| 5 | Message Number |
USMD1 - 003 | Data model &1, entity type &2: Inconsistent indicators | |
| 6 | Message Number |
USMD1 - 006 | Data model &1, entity type &2: Select a storage and use type | |
| 7 | Message Number |
USMD1 - 008 | Data model &1, entity type &2: Entry of a data element is invalid | |
| 8 | Message Number |
USMD1 - 009 | Data model &1, entity type &2: Specify a data element | |
| 9 | Message Number |
USMD1 - 010 | Data model &1, entity type &2: Data element is invalid | |
| 10 | Message Number |
USMD1 - 011 | Data model &1, entity type &2, attribute &3: Entity type does not exist | |
| 11 | Message Number |
USMD1 - 012 | Data model &1, entity type &2, attribute &3: Specify a data element | |
| 12 | Message Number |
USMD1 - 013 | Data model &1, entity type &2, attr. &3: Data element &4 does not exist | |
| 13 | Message Number |
USMD1 - 014 | Data model &1: Data element of (hierarchy) attribute &2 is not unique | |
| 14 | Message Number |
USMD1 - 014 | Data model &1: Data element of (hierarchy) attribute &2 is not unique | |
| 15 | Message Number |
USMD1 - 014 | Data model &1: Data element of (hierarchy) attribute &2 is not unique | |
| 16 | Message Number |
USMD1 - 015 | Data model &1, entity type &2, relat. &3: Data element &4 does not exist | |
| 17 | Message Number |
USMD1 - 016 | Data model &1, entity type &2, relat. &3: Data element &4 is invalid | |
| 18 | Message Number |
USMD1 - 017 | Data model &1, entity type &2, relationship &3: Select the cardinality | |
| 19 | Message Number |
USMD1 - 018 | Data model &1, entity type &2, relationship &3: Data element specified | |
| 20 | Message Number |
USMD1 - 019 | Data model &1, entity type &2: Invalid data element &3 | |
| 21 | Message Number |
USMD1 - 020 | Data model &1: From-entity type &2 and relationship have the same name | |
| 22 | Message Number |
USMD1 - 021 | Data model &1, entity type &2, relat. &3: Specify To-entity type | |
| 23 | Message Number |
USMD1 - 022 | Data model &1, entity type &2, relat. &3: Entity type &4 does not exist | |
| 24 | Message Number |
USMD1 - 023 | Data model &1, entity type &2: Attribute &3 is assigned more than once | |
| 25 | Message Number |
USMD1 - 024 | Data model &1, entity type &2: Relationship &3 is assigned more than once | |
| 26 | Message Number |
USMD1 - 028 | Data model &1, &2 &3: Selected name invalid; adhere to naming convention | |
| 27 | Message Number |
USMD1 - 028 | Data model &1, &2 &3: Selected name invalid; adhere to naming convention | |
| 28 | Message Number |
USMD1 - 028 | Data model &1, &2 &3: Selected name invalid; adhere to naming convention | |
| 29 | Message Number |
USMD1 - 028 | Data model &1, &2 &3: Selected name invalid; adhere to naming convention | |
| 30 | Message Number |
USMD1 - 028 | Data model &1, &2 &3: Selected name invalid; adhere to naming convention | |
| 31 | Message Number |
USMD1 - 029 | Data model &1, &2 &3: Data element &4 is invalid | |
| 32 | Message Number |
USMD1 - 029 | Data model &1, &2 &3: Data element &4 is invalid | |
| 33 | Message Number |
USMD1 - 029 | Data model &1, &2 &3: Data element &4 is invalid | |
| 34 | Message Number |
USMD1 - 029 | Data model &1, &2 &3: Data element &4 is invalid | |
| 35 | Message Number |
USMD1 - 029 | Data model &1, &2 &3: Data element &4 is invalid | |
| 36 | Message Number |
USMD1 - 030 | Data model &1: Entity type &2 and attribute of ent.type &3 have same name | |
| 37 | Message Number |
USMD1 - 031 | Data model &1: Entity type &2 and the relationship have the same name | |
| 38 | Message Number |
USMD1 - 032 | Data model &1: Attr. &2 of ent.type &3 and relationship have same name | |
| 39 | Message Number |
USMD1 - 033 | Data model &1, entity type &2: Too many key fields | |
| 40 | Message Number |
USMD1 - 034 | Data model &1, entity type &2: Entire key is too long | |
| 41 | Message Number |
USMD1 - 035 | Data model &1, entity type &2: Entity types &3 and &4 are identical | |
| 42 | Message Number |
USMD1 - 036 | Data model &1: Multiple relationships between entity type &2 and &3 | |
| 43 | Message Number |
USMD1 - 037 | Entity type &1, rel. &2: Further relationship to entity type &3 missing | |
| 44 | Message Number |
USMD1 - 038 | Data model &1: Valid entity type in attribute is inconsistent: &2/&3 | |
| 45 | Message Number |
USMD1 - 040 | Data model &1, entity type &2: Leading entity type &3 is invalid | |
| 46 | Message Number |
USMD1 - 041 | Data model &1, entity type &2: Leading entity types are invalid | |
| 47 | Message Number |
USMD1 - 042 | Data model &1, entity type &2: Number of leading entity types is invalid | |
| 48 | Message Number |
USMD1 - 046 | Data model &1, entity type &2: Relationship is recursive | |
| 49 | Message Number |
USMD1 - 047 | Data model &1, entity type &2: Leading entity type &3 cannot be assigned | |
| 50 | Message Number |
USMD1 - 048 | Data model &1: Search help for (hierarchy) attribute &2 is not unique | |
| 51 | Message Number |
USMD1 - 048 | Data model &1: Search help for (hierarchy) attribute &2 is not unique | |
| 52 | Message Number |
USMD1 - 048 | Data model &1: Search help for (hierarchy) attribute &2 is not unique | |
| 53 | Message Number |
USMD1 - 049 | Data model &1, entity type &2, relationship &3: Cardinality is invalid | |
| 54 | Message Number |
USMD1 - 053 | Data model &1, entity type &2, relationship &3: No data element valid | |
| 55 | Message Number |
USMD1 - 054 | Data model &1: Storage and use type of entity types &2 and &3 is invalid | |
| 56 | Message Number |
USMD1 - 055 | Data model &1, entity type &2, relat. &3: Relationship type is invalid | |
| 57 | Message Number |
USMD1 - 056 | Data model &1, ent. type &2: Entity type for hierarchy name is ambiguous | |
| 58 | Message Number |
USMD1 - 057 | Data model &1: Attributes must not be assigned to entity type &2 | |
| 59 | Message Number |
USMD1 - 058 | Data model &1: Relationship &2 assigned to incorrect entity type &3 | |
| 60 | Message Number |
USMD1 - 059 | Data model &1: Entity type &2 has leading relationship to entity type &3 | |
| 61 | Message Number |
USMD1 - 060 | Data model &1, ent. type &2: Relationship of type "leading" inconsistent | |
| 62 | Message Number |
USMD1 - 061 | Data model &1, ent.type &2, attr. &3, data elem. &4: No change documents | |
| 63 | Message Number |
USMD1 - 062 | Data model &1, entity type &2, data element &3: No change documents | |
| 64 | Message Number |
USMD1 - 063 | Data model &1, entity type &2: Not enough "leading" relationships | |
| 65 | Message Number |
USMD1 - 064 | Data model &1: Define a "qualifying" relationship for entity type &2 | |
| 66 | Message Number |
USMD1 - 065 | Data model &1: Entity type &2 must not have a search help | |
| 67 | Message Number |
USMD1 - 066 | Data model &1, entity type &2: Search help &3 does not exist | |
| 68 | Message Number |
USMD1 - 067 | Data model &1: Entity type &2 has higher-level entity types | |
| 69 | Message Number |
USMD1 - 068 | Data model &1, entity type &2: Invalid relationship with entity type &3 | |
| 70 | Message Number |
USMD1 - 069 | Data model &1, entity type &2: Invalid relationship with entity type &3 | |
| 71 | Message Number |
USMD1 - 070 | Data model &1, entity type &2, attr. &3: Search help &4 does not exist | |
| 72 | Message Number |
USMD1 - 071 | Data model &1, relationship &2 used for different From entity types | |
| 73 | Message Number |
USMD1 - 073 | Data model &1, entity type &2: Additional entity type &3 not allowed | |
| 74 | Message Number |
USMD1 - 074 | Data model &1, entity type &2 has invalid higher-level entity types | |
| 75 | Message Number |
USMD1 - 075 | Data model &1, entity type &2: Invalid check table | |
| 76 | Message Number |
USMD1 - 076 | Data model &1, ent.type &2, rela. &3: Deselect 'No Existence Check" | |
| 77 | Message Number |
USMD1 - 077 | Data model &1, ent. type &2: Check table of data elem. &3 does not exist | |
| 78 | Message Number |
USMD1 - 078 | D.model &1, e.type &2, attr.&3: Check table of d.elem. &4 does not exist | |
| 79 | Message Number |
USMD1 - 079 | Data model &1, entity type &2, attribute &3: Invalid check table | |
| 80 | Message Number |
USMD1 - 080 | Ent.type &1: Currency/unit-supplying attr. &2 is invalid for attr. &3 | |
| 81 | Message Number |
USMD1 - 081 | Data model &1, entity type &2, attribute &3: Not key figure-like | |
| 82 | Message Number |
USMD1 - 082 | Data model &1, entity type &2, attribute &3: No reference field | |
| 83 | Message Number |
USMD1 - 083 | Data model &1, entity type &2: Invalid relationship with entity type &3 | |
| 84 | Message Number |
USMD1 - 084 | Data model &1, From-entity typ &2: Relationship not entered | |
| 85 | Message Number |
USMD1 - 085 | Data model &1, entity type &2: Assign a different data element | |
| 86 | Message Number |
USMD1 - 086 | Data model &1, &2 &3: Deselect 'No Existence Check' | |
| 87 | Message Number |
USMD1 - 086 | Data model &1, &2 &3: Deselect 'No Existence Check' | |
| 88 | Message Number |
USMD1 - 086 | Data model &1, &2 &3: Deselect 'No Existence Check' | |
| 89 | Message Number |
USMD1 - 086 | Data model &1, &2 &3: Deselect 'No Existence Check' | |
| 90 | Message Number |
USMD1 - 088 | Data model &1, entity type &2, attribute &3: Data type &4 is invalid | |
| 91 | Message Number |
USMD1 - 089 | Data model &1, ent.type &2, hier. attribute &3: Data type &4 is invalid | |
| 92 | Message Number |
USMD1 - 090 | Entity type &1, relationship &2: Leading entity type &3 is not unique | |
| 93 | Message Number |
USMD1 - 092 | Data model &1, ent.type &2, attr. &3: Attribute missing for currency/unit | |
| 94 | Message Number |
USMD1 - 093 | Data model &1, entity type &2: Long full key | |
| 95 | Message Number |
USMD1 - 094 | Data model &1, entity type &2: Complete key in hierarchy is too long | |
| 96 | Message Number |
USMD1 - 095 | Data model &1: Entity type &2 has no attributes | |
| 97 | Message Number |
USMD1 - 096 | Data model &1: Entity type &2: Search help assigned | |
| 98 | Message Number |
USMD1 - 101 | Data model &1: Changes as compared to active version | |
| 99 | Message Number |
USMD1 - 102 | Data model &1, entity type &2: Change of storage and use type | |
| 100 | Message Number |
USMD1 - 103 | Data model &1, entity type &2: Change of data element | |
| 101 | Message Number |
USMD1 - 104 | Data model &1, entity type &2: Change of hierarchy configuration | |
| 102 | Message Number |
USMD1 - 105 | Data model &1, entity type &2: Change of language dependency of texts | |
| 103 | Message Number |
USMD1 - 106 | Data model &1: Entity type &2 was removed | |
| 104 | Message Number |
USMD1 - 107 | Data model &1, entity type &2: Change of permitted hierarchy nodes | |
| 105 | Message Number |
USMD1 - 108 | Data model &1, entity type &2: Attribute &3 was removed | |
| 106 | Message Number |
USMD1 - 109 | Data model &1, entity type &2: Relationship &3 was removed | |
| 107 | Message Number |
USMD1 - 110 | Data model &1, entity typ &2, attribute &3: Change of data element | |
| 108 | Message Number |
USMD1 - 111 | Data model &1, entity typ &2, relationship &3: Change of data element | |
| 109 | Message Number |
USMD1 - 112 | Data model &1, entity typ &2, relat. &3: Change of relationship type | |
| 110 | Message Number |
USMD1 - 128 | Data model &1: Foreign key relationship &2 has DDIC table assignment | |
| 111 | Message Number |
USMD1 - 129 | Data model &1: Foreign key relationship &2 has DDIC field assignment | |
| 112 | Message Number |
USMD1 - 133 | Data model &1, entity type &2: Creation not possible | |
| 113 | Message Number |
USMD1 - 141 | Data model &1: No BAdI implementation to fill &2 of attribute &3 | |
| 114 | Message Number |
USMD1 - 142 | Entity type &1, Attribute &2: currency/unit &4 &3 is invalid | |
| 115 | Message Number |
USMD1 - 250 | Data model &1, entity type &2: Application field is still empty | |
| 116 | Message Number |
USMD1 - 501 | Mod./ent.&1, node ent.&2, hier.attr.fr.ref.&3: No data element allowed | |
| 117 | Message Number |
USMD1 - 503 | Mod./ent.&1, node ent.&2, hy.attr.fr.ref.&3: Data elem. &4 does not exist | |
| 118 | Message Number |
USMD1 - 504 | Mod./ent.&1, node ent.&2, hy.attr.fr.ref.&3: Invalid reference entity | |
| 119 | Message Number |
USMD1 - 506 | Mod./ent.&1, node ent.&2, hy.attr.fr.ref.&3: Refer.ent. &4 does not exist | |
| 120 | Message Number |
USMD1 - 507 | Mod./ent.&1, node ent.&2, hy.attr.fr.ref.&3: Data element &4 is invalid | |
| 121 | Message Number |
USMD1 - 508 | Mod./ent.&1, node ent.&2, hy.attr.fr.ref.&3, data elem.&4: No chg.docum. | |
| 122 | Message Number |
USMD1 - 509 | Model &1, hierarchy attribute from ref. &2 used for diff. ref. entities | |
| 123 | Message Number |
USMD1 - 510 | Mod./ent.&1, node ent.&2, hy.attribute &3: Entity type does not exist | |
| 124 | Message Number |
USMD1 - 511 | Mod./ent.&1, node ent.&2, hy.attr.&3: Node entity type does not exist | |
| 125 | Message Number |
USMD1 - 512 | Mod./ent.&1, node ent.&2, hy.attribute &3: No data element specified | |
| 126 | Message Number |
USMD1 - 514 | Mod./ent.&1, node ent.&2, h.attr.&3: Check table f.data elem.&4 not found | |
| 127 | Message Number |
USMD1 - 515 | Mod./ent.&1, node ent.&2, h.attr.&3: Data element &4 does not exist | |
| 128 | Message Number |
USMD1 - 516 | Mod./ent.&1, node ent.&2, hierarchy attr. &3: Check table is invalid | |
| 129 | Message Number |
USMD1 - 517 | Mod./ent.&1, node ent.&2, h.attr.&3, data elem.&4: No change documents | |
| 130 | Message Number |
USMD1 - 518 | Mod./ent.&1, node ent.&2, h.attribute &3: Search help &4 does not exist | |
| 131 | Message Number |
USMD1 - 519 | Mod./ent.&1, node ent.&2: Initialized name for hierarchy attribute | |
| 132 | Message Number |
USMD1 - 520 | Mod./ent.&1, node ent.&2: Initial. name for hierarchy attribute from ref. | |
| 133 | Message Number |
USMD1 - 521 | Mod./ent.&1, node ent.&2: Assignment of hierarchy attributes not allowed | |
| 134 | Message Number |
USMD1 - 521 | Mod./ent.&1, node ent.&2: Assignment of hierarchy attributes not allowed | |
| 135 | Message Number |
USMD1 - 522 | Data model &1: Entity type &2 and hier.attribute from ref. have same name | |
| 136 | Message Number |
USMD1 - 523 | Mod./ent.&1, node ent.&2: H.attr. &3 and h.attr. from ref. have same name | |
| 137 | Message Number |
USMD1 - 524 | Model &1: Relationship and h.attr. fr. ref. &2 used in diff.entity types | |
| 138 | Message Number |
USMD1 - 525 | Mod./ent.&1, node ent.&2, h.attr.fr.ref.&3: Missing h.attr. fr.ref. to &4 | |
| 139 | Message Number |
USMD1 - 526 | Mod./ent.&1, node ent.&2: Hier.attr.&3 has same name as hy.attr. fr. ref. | |
| 140 | Message Number |
USMD1 - 528 | Data model &1, entity type &2: Hierarchy indicator is not allowed | |
| 141 | Message Number |
USMD1 - 529 | Data model &1, entity type &2: Description is missing | |
| 142 | Message Number |
USMD1 - 530 | Data model &1, entity type &2: Invalid use of validity concept | |
| 143 | Message Number |
USMD1 - 531 | Validity concept of entity type &1 must not be changed | |
| 144 | Message Number |
USMD1 - 532 | Hierarchy &1: Invalid use of validity concept | |
| 145 | Message Number |
USMD1 - 533 | Entity type &1 and &2 relationship: Invalid use of validity concept | |
| 146 | Message Number |
USMD1 - 534 | Data model &1, entity type &2: Type of key assignment changed | |
| 147 | Message Number |
USMD1 - 535 | Data model &1, entity type &2: Invalid use in hierarchy | |
| 148 | Message Number |
USMD1 - 536 | Data model/entity type &1: Invalid hierarchy attribute | |
| 149 | Message Number |
USMD1 - 550 | Model &1, entity type &2: Source fields for texts must not be entered | |
| 150 | Message Number |
USMD1 - 551 | Model &1, entity type &2: Attribute &3 must not be a key field | |
| 151 | Message Number |
USMD1 - 557 | Data model &1: Key attributes must not be assigned to entity type &2 | |
| 152 | Message Number |
USMD1 - 560 | Model &1, reuse active area &2: ABAP class &3 cannot be used | |
| 153 | Message Number |
USMD1 - 561 | Model &1: Name of a reuse active area is invalid | |
| 154 | Message Number |
USMD1 - 562 | Model &1: Active area &2 does not exist; use input help to select value | |
| 155 | Message Number |
USMD1 - 563 | Model &1, entity type &2: Active area &3 does not exist | |
| 156 | Message Number |
USMD1 - 564 | Model &1, entity type &2: Reuse of tables is not possible | |
| 157 | Message Number |
USMD1 - 565 | Model &1, entity type &2: Remove the active area | |
| 158 | Message Number |
USMD1 - 566 | Model &1, entity type &2: Use of active area has been switched | |
| 159 | Message Number |
USMD1 - 568 | Model &1, custom entity type &2: Check the reuse active area | |
| 160 | Message Number |
USMD1 - 569 | Model &1: Enter a value for active area; use input help to select value | |
| 161 | Message Number |
USMD1 - 580 | Model &1, entity type &2: Invalid key treatment | |
| 162 | Message Number |
USMD1 - 581 | Model &1, entity type &2: Missing number range object | |
| 163 | Message Number |
USMD1 - 582 | Model &1, entity type &2: Deletion of entities not allowed | |
| 164 | Message Number |
USMD1 - 583 | Model &1, entity type &2: Invalid deletion setting | |
| 165 | Message Number |
USMD1 - 584 | Model &1, entity type &2: Invalid data element | |
| 166 | Message Number |
USMD1 - 585 | Model &1, entity type &2: No change documents | |
| 167 | Message Number |
USMD1 - 586 | Model &1, entity type &2: Internal key assignment; enter a reuse area | |
| 168 | Message Number |
USMD1 - 587 | Data model &1, entity type &2: Number range object is not required | |
| 169 | Message Number |
USMD1 - 588 | Model &1: Name of data model is incorrect | |
| 170 | Message Number |
USMD1 - 592 | Data model &1, to-entity type &2: Invalid foreign key relationship &3 | |
| 171 | Message Number |
USMD1 - 593 | Data model &1, from-entity type &2: Invalid relationship | |
| 172 | Message Number |
USMD1 - 594 | Model &1, ent.type &2: Relationship &3 is not a foreign key relationship | |
| 173 | Message Number |
USMD1 - 595 | Data model &1, entity type &2: Data element is missing | |
| 174 | Message Number |
USMD1 - 596 | Data model &1, relationship &2: Value &3 is not valid as a from-field | |
| 175 | Message Number |
USMD1 - 597 | Data model &1, relationship &2: Value &3 is not valid as a to-field | |
| 176 | Message Number |
USMD1 - 598 | Data model &1, relationship &2: One or more From-fields are missing | |
| 177 | Message Number |
USMD1 - 599 | Data model &1, relationship &2: Value &3 exists twice | |
| 178 | Message Number |
USMD1 - 605 | Data model &1: Business object type &2 is used in data model &3 | |
| 179 | Message Number |
USMD1 - 615 | Data model &1: Attribute &3 for generated entity type &2 | |
| 180 | Message Number |
USMD1 - 616 | Model &1: Generated entity type &2 must not be enhanced with rel. &3 | |
| 181 | Message Number |
USMD1 - 617 | Data model &1, entity type &2: Number range assignments are not supported | |
| 182 | Message Number |
USMD1 - 618 | Data model &1, entity type &2: Reuse active areas are not supported | |
| 183 | Message Number |
USMD1 - 619 | Data model &1, entity type &2: Language-dependent texts are not possible | |
| 184 | Message Number |
USMD1 - 620 | Data model &1, entity type &2: Attribute &3 is a key field | |
| 185 | Message Number |
USMD1 - 621 | Data model &1, entity type &2: Reference attribute &3 is a key field |
