USMD1 - Datenmodel
The following messages are stored in message class USMD1: Datenmodel.
It is part of development package USMD1 in software component CA-MDG-AF. This development package consists of objects that can be grouped under "Master Data: Data Modeling".
It is part of development package USMD1 in software component CA-MDG-AF. This development package consists of objects that can be grouped under "Master Data: Data Modeling".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Program error |
| 001 | ***** MESSAGES FOR DATA MODEL CHECKING ********************************** |
| 002 | Data model &1, entity type &2: Data element &3 does not exist |
| 003 | Data model &1, entity type &2: Inconsistent indicators |
| 004 | Data model &1: Entity type &2 was removed |
| 005 | Data model &1 does not exist (inactive version does not exist either) |
| 006 | Data model &1, entity type &2: Select a storage and use type |
| 007 | An active data model already exists for &1 |
| 008 | Data model &1, entity type &2: Entry of a data element is invalid |
| 009 | Data model &1, entity type &2: Specify a data element |
| 010 | Data model &1, entity type &2: Data element is invalid |
| 011 | Data model &1, entity type &2, attribute &3: Entity type does not exist |
| 012 | Data model &1, entity type &2, attribute &3: Specify a data element |
| 013 | Data model &1, entity type &2, attr. &3: Data element &4 does not exist |
| 014 | Data model &1: Data element of (hierarchy) attribute &2 is not unique |
| 015 | Data model &1, entity type &2, relat. &3: Data element &4 does not exist |
| 016 | Data model &1, entity type &2, relat. &3: Data element &4 is invalid |
| 017 | Data model &1, entity type &2, relationship &3: Select the cardinality |
| 018 | Data model &1, entity type &2, relationship &3: Data element specified |
| 019 | Data model &1, entity type &2: Invalid data element &3 |
| 020 | Data model &1: From-entity type &2 and relationship have the same name |
| 021 | Data model &1, entity type &2, relat. &3: Specify To-entity type |
| 022 | Data model &1, entity type &2, relat. &3: Entity type &4 does not exist |
| 023 | Data model &1, entity type &2: Attribute &3 is assigned more than once |
| 024 | Data model &1, entity type &2: Relationship &3 is assigned more than once |
| 025 | First save data model &1 |
| 026 | First save data model &1 and activate it without errors |
| 027 | Select a data model in the table |
| 028 | Data model &1, &2 &3: Selected name invalid; adhere to naming convention |
| 029 | Data model &1, &2 &3: Data element &4 is invalid |
| 030 | Data model &1: Entity type &2 and attribute of ent.type &3 have same name |
| 031 | Data model &1: Entity type &2 and the relationship have the same name |
| 032 | Data model &1: Attr. &2 of ent.type &3 and relationship have same name |
| 033 | Data model &1, entity type &2: Too many key fields |
| 034 | Data model &1, entity type &2: Entire key is too long |
| 035 | Data model &1, entity type &2: Entity types &3 and &4 are identical |
| 036 | Data model &1: Multiple relationships between entity type &2 and &3 |
| 037 | Entity type &1, rel. &2: Further relationship to entity type &3 missing |
| 038 | Data model &1: Valid entity type in attribute is inconsistent: &2/&3 |
| 039 | Transport request will be deleted: model name is in customer namespace |
| 040 | Data model &1, entity type &2: Leading entity type &3 is invalid |
| 041 | Data model &1, entity type &2: Leading entity types are invalid |
| 042 | Data model &1, entity type &2: Number of leading entity types is invalid |
| 043 | Select at least one entry. |
| 044 | There is no active version of data model &1 |
| 045 | Data model &1: Data element of relationship &2 is ambiguous |
| 046 | Data model &1, entity type &2: Relationship is recursive |
| 047 | Data model &1, entity type &2: Leading entity type &3 cannot be assigned |
| 048 | Data model &1: Search help for (hierarchy) attribute &2 is not unique |
| 049 | Data model &1, entity type &2, relationship &3: Cardinality is invalid |
| 050 | Data model &1 will not be transported |
| 051 | Data model &1 activated |
| 052 | Definition of data model &1 is consistent |
| 053 | Data model &1, entity type &2, relationship &3: No data element valid |
| 054 | Data model &1: Storage and use type of entity types &2 and &3 is invalid |
| 055 | Data model &1, entity type &2, relat. &3: Relationship type is invalid |
| 056 | Data model &1, ent. type &2: Entity type for hierarchy name is ambiguous |
| 057 | Data model &1: Attributes must not be assigned to entity type &2 |
| 058 | Data model &1: Relationship &2 assigned to incorrect entity type &3 |
| 059 | Data model &1: Entity type &2 has leading relationship to entity type &3 |
| 060 | Data model &1, ent. type &2: Relationship of type "leading" inconsistent |
| 061 | Data model &1, ent.type &2, attr. &3, data elem. &4: No change documents |
| 062 | Data model &1, entity type &2, data element &3: No change documents |
| 063 | Data model &1, entity type &2: Not enough "leading" relationships |
| 064 | Data model &1: Define a "qualifying" relationship for entity type &2 |
| 065 | Data model &1: Entity type &2 must not have a search help |
| 066 | Data model &1, entity type &2: Search help &3 does not exist |
| 067 | Data model &1: Entity type &2 has higher-level entity types |
| 068 | Data model &1, entity type &2: Invalid relationship with entity type &3 |
| 069 | Data model &1, entity type &2: Invalid relationship with entity type &3 |
| 070 | Data model &1, entity type &2, attr. &3: Search help &4 does not exist |
| 071 | Data model &1, relationship &2 used for different From entity types |
| 072 | No authorization for activating data model &1 |
| 073 | Data model &1, entity type &2: Additional entity type &3 not allowed |
| 074 | Data model &1, entity type &2 has invalid higher-level entity types |
| 075 | Data model &1, entity type &2: Invalid check table |
| 076 | Data model &1, ent.type &2, rela. &3: Deselect 'No Existence Check" |
| 077 | Data model &1, ent. type &2: Check table of data elem. &3 does not exist |
| 078 | D.model &1, e.type &2, attr.&3: Check table of d.elem. &4 does not exist |
| 079 | Data model &1, entity type &2, attribute &3: Invalid check table |
| 080 | Ent.type &1: Currency/unit-supplying attr. &2 is invalid for attr. &3 |
| 081 | Data model &1, entity type &2, attribute &3: Not key figure-like |
| 082 | Data model &1, entity type &2, attribute &3: No reference field |
| 083 | Data model &1, entity type &2: Invalid relationship with entity type &3 |
| 084 | Data model &1, From-entity typ &2: Relationship not entered |
| 085 | Data model &1, entity type &2: Assign a different data element |
| 086 | Data model &1, &2 &3: Deselect 'No Existence Check' |
| 087 | Data model &1 could not be activated during import |
| 088 | Data model &1, entity type &2, attribute &3: Data type &4 is invalid |
| 089 | Data model &1, ent.type &2, hier. attribute &3: Data type &4 is invalid |
| 090 | Entity type &1, relationship &2: Leading entity type &3 is not unique |
| 091 | Invalid name &1 |
| 092 | Data model &1, ent.type &2, attr. &3: Attribute missing for currency/unit |
| 093 | Data model &1, entity type &2: Long full key |
| 094 | Data model &1, entity type &2: Complete key in hierarchy is too long |
| 095 | Data model &1: Entity type &2 has no attributes |
| 096 | Data model &1: Entity type &2: Search help assigned |
| 097 | You have no authorization for displaying data models |
| 098 | Select only one data model |
| 099 | Save the changed data first |
| 100 | *********** MESSAGES ABOUT CHANGES TO A DATA MODEL ********************** |
| 101 | Data model &1: Changes as compared to active version |
| 102 | Data model &1, entity type &2: Change of storage and use type |
| 103 | Data model &1, entity type &2: Change of data element |
| 104 | Data model &1, entity type &2: Change of hierarchy configuration |
| 105 | Data model &1, entity type &2: Change of language dependency of texts |
| 106 | Data model &1: Entity type &2 was removed |
| 107 | Data model &1, entity type &2: Change of permitted hierarchy nodes |
| 108 | Data model &1, entity type &2: Attribute &3 was removed |
| 109 | Data model &1, entity type &2: Relationship &3 was removed |
| 110 | Data model &1, entity typ &2, attribute &3: Change of data element |
| 111 | Data model &1, entity typ &2, relationship &3: Change of data element |
| 112 | Data model &1, entity typ &2, relat. &3: Change of relationship type |
| 113 | Required status change of entity type &1: &2 |
| 114 | Required status change of entity type &1: &2 |
| 115 | Required status change of entity type &1: &2 |
| 116 | Optional status change of entity type &1: &2 |
| 117 | System settings do not permit changes to the model |
| 118 | Data model &1, entity type &2: Selected standard status not permitted |
| 119 | Essential deletion of variant &1 in UI configuration &2 |
| 120 | ************* MESSAGES FOR STRUCTURE GENERATION ************************* |
| 121 | Data model &1: Enter only one package per data model |
| 122 | Data model &1: SAP packages can be changed only in SAP's own systems |
| 123 | Deletion of change requests for data model &1 with status &2 completed |
| 124 | Change requests for data model &1 found in client &2 |
| 125 | No authorization for changing/deleting data models |
| 126 | No authorization for changing client-independent objects |
| 127 | Data model &1, entity type &2: No structure found for reference attribute |
| 128 | Data model &1: Foreign key relationship &2 has DDIC table assignment |
| 129 | Data model &1: Foreign key relationship &2 has DDIC field assignment |
| 130 | ********* MESSAGES FOR RESTRICTED USE OF DATA MODELING ****************** |
| 131 | Activation not possible; active data model &1 already exists |
| 132 | Creating of a data model without copy template is not possible |
| 133 | Data model &1, entity type &2: Creation not possible |
| 134 | Transport from system &1 is not possible |
| 135 | Data model activation not possible: Upgrade in progress |
| 136 | Generation of structures impossible: Upgrade in progress |
| 137 | Activation of data model &1 not supported |
| 140 | Access to database tables of a data model is not possible |
| 141 | Data model &1: No BAdI implementation to fill &2 of attribute &3 |
| 142 | Entity type &1, Attribute &2: currency/unit &4 &3 is invalid |
| 150 | ******** MESSAGES FOR AUTHORIZATIONS ************************************ |
| 151 | Data model &1: Higher-level entity type &2 for entity type &3 is missing |
| 152 | Data model &1: Higher-level ent. type &2 of &3 is authorization relevant |
| 153 | Data model &1: Attribute &2 of entity type &3 is unknown |
| 154 | Data model &1: Attribute &2 of entity type &3 is invalid |
| 155 | Entity type &1 does not exist in active data model |
| 156 | Customizing settings for authorization model are inconsistent |
| 157 | Data model &1: No authorization for entity type &2 - activity &3 |
| 158 | Model &1 has more than 7 authorization-relev. entity types or attributes |
| 159 | Authorization is inconsistent |
| 160 | Entity type &1 is invalid |
| 161 | Data model &1 does not exist (in active version) |
| 162 | Activity set to default value |
| 163 | Activity &1 is not intended for USMD_MDAT |
| 164 | Entity types must not be further restricted |
| 165 | No authorization for executing UI model &1 |
| 166 | No authorization &2 for edition of type &1 |
| 167 | No authorization &2 for change request of type &1 |
| 168 | User name &1 is invalid; contact SAP |
| 169 | Internal error: &1 &2 &3 &4 |
| 170 | Activity &1 is not intended for USMD_MDATH |
| 171 | Data mod. &1: Ent.type/attr. &2 has unsuitable data type f. authorization |
| 172 | No authorization for single processing with UI configuration &1 |
| 173 | Data model &1: No entity types defined as authorization relevant |
| 174 | Hierarchy nodes must not be further restricted |
| 175 | Hierarchies must not be further restricted |
| 176 | Hierarchy version must not be further restricted |
| 177 | Attribute &1 does not exist in active data model |
| 178 | Entity type &1 cannot be used for a hierarchy node |
| 179 | Hierarchy name is not defined consistently |
| 180 | Entity type &1 is not permitted for hierarchy authorizations |
| 181 | Data model &1: No authorization for hierarchy type &2 - activity &3 |
| 182 | Value for data model authorization field will be set to '*' |
| 183 | Hierarchy nodes filled inconsistently |
| 184 | Data model &1: No authorization for entity type &2 - activity &3 |
| 185 | Insufficient authorization for copying the data of entity type &1 |
| 186 | Change request &1: Data already activated |
| 187 | Entity type &1: Duplicate data record &2 cannot be written |
| 188 | No authorization &2 for data model &1 |
| 189 | No authorization &1 for transports |
| 190 | Enable�authorization�of�one�key�element�of�entity�&1 |
| 200 | ****** MESSAGES ABOUT EDITIONS ****************************************** |
| 201 | Specify a data model for edition type &1, and save |
| 202 | Specify the edition type first |
| 203 | Convertion of period to date unsuccessful for &1 / &3 / &2 |
| 204 | Edition type &3: Entity type &2 does not exist in data model &1 |
| 205 | Entity type &2 of data model &1 used in multiple edition types |
| 206 | Enter at least one entity type for edition type &1 |
| 207 | Edition type &1 used by edition &2; deletion not possible |
| 208 | Deleting the edition type could result in inconsistencies |
| 209 | Edition type &1 used by edition &2 |
| 210 | Edition type &1 already in use; change not possible |
| 211 | Specify a fiscal year variant for edition type &1 |
| 212 | Specify a the validity for edition type &1, and save the data |
| 213 | Edition type &1 cannot be deleted |
| 214 | Edition type &2 must be specified in edition &1 |
| 215 | Entity type &2 cannot be used in edition type &1 |
| 216 | You cannot create an edition type for data model &1 |
| 217 | Invalid entity type &1 in data slice of edition type &2 |
| 218 | Invalid entity type &1 in data slice of edition type &2; see long text |
| 219 | Invalid entity type &1 in data slice of edition type &2; see long text |
| 220 | Invalid entity type &1 for definition of data slices; see long text |
| 221 | For entity type &1, a data slice must be defined in edition type &2 |
| 222 | Edition type &1 still in use and cannot be retired |
| 223 | Edition type &1 already retired; reactivation not possible |
| 224 | Edition type &2: Use entity type &1 to remove the data slice |
| 225 | Data slices for entity type &1 of edition types &2 and &3 overlap |
| 226 | Edit.type &2: Data slice for entity type &1 cannot be further restricted |
| 227 | Invalid entity type &1 in data slice of edition type &2; see long text |
| 228 | Entity type &1 cannot be deleted |
| 230 | ********* Messages for Custom Structures ***************************** |
| 231 | Data model &1, entity type &2: Namespace &3 has an error |
| 232 | Data model &1: Entity type &2 does not exist in activated data model |
| 233 | Data model &1: Structure cannot be generated for entity type &2 |
| 234 | Data model &1, entity type &2: Structure name &3 is too long |
| 235 | Data model &1, entity type &2: Use of structure &3 is unknown |
| 236 | Data model &1: Definitions of generated structures are consistent |
| 237 | Data model &1, entity type &2: Namespace missing |
| 238 | Data model &1, entity type &2: No structure specified |
| 239 | Data model &1: Cannot activate generated structures |
| 240 | Data model &1, ent.type &2: Structure for SMT mapping cannot be generated |
| 241 | Data model &1: Structure name &4 assigned twice for &2 and &3 |
| 242 | &1/&2: Prefix/namespace &3 is too short |
| 243 | Delivered structures in namespace /MDG* are not generated |
| 244 | Data model &1 does not reside within SAP namespace |
| 245 | Data model &1, entity type &2: Structure will not be generated |
| 246 | Data model &1: Structure &2 activated |
| 247 | Data model &1: Internal table &2 activated |
| 248 | Package &1 resides within SAP namespace |
| 249 | Entries for Customizing includes are not permitted in SAP systems |
| 250 | Data model &1, entity type &2: Application field is still empty |
| 251 | Data model &1: Package column is empty |
| 252 | Data model &1, Structure &2: No Package assigned |
| 253 | Data model &1, ent.type &2: Structure cannot be generated |
| 254 | Data model &1, entity type &2: Structure name is too long |
| 255 | Data model &1: fill namespace/prefix for automatic structure generation |
| 256 | Data model &1: technical problems with automatic structure generation |
| 257 | Data model &1: fill package for automatic structure generation |
| 258 | Data model &1: namespace/prefix for structure generation not valid |
| 259 | Data model &1: structures and DataSources successfully generated |
| 260 | Data model &1: namespace or package for structure generation not valid |
| 261 | Data model &1: no structures for automatic structure generation found |
| 262 | Data model &1: no structures and DataSources generated |
| 263 | Data model &1: namespace of package for structure generation is empty |
| 264 | SAP delivered data model &1: no structures and DataSources generated |
| 265 | Please open node 'Data Model-Specific Structures' and save. |
| 300 | Messages for Selections |
| 301 | Program error |
| 302 | Selection conditions cannot be made for field name &1 |
| 303 | Conditions with placeholders (*) are not permitted in field &1 |
| 310 | Data model &1: Incorrect entity type &2 |
| 311 | Data model &1, Entity type &2: Incorrect field name &3 |
| 312 | Data model &1: Entity type &2 used as hierarchy node |
| 313 | Data model &1: Entity type &2 is a hierarchy bearing entity type |
| 314 | Data model &1: Incorrect entity type &2 |
| 400 | ************ Messages for Structure Generation ************** |
| 401 | &1/&2: Delivered structure &3 is no longer current |
| 402 | Data model &1: DDIC structure &2 could not be activated |
| 403 | Data model &1: DDIC table type &2 could not be activated |
| 404 | TADIR entry for &1 could not be created |
| 405 | System or client is set to Not Editable |
| 406 | Data model &1: Structure &2 activated |
| 407 | System cannot schedule conversion program &1 in client &2 (model &3) |
| 408 | Conversion program &1 scheduled in client &2, user &4 (logon with &3) |
| 409 | Data model &1: DDIC structure &2 cannot be automatically modified |
| 410 | Data model &1: Field Prop. not found for Entity &2 - Invalid Data Model |
| 450 | Error in BAdI USMD_UPDATE_EVENT: &1 &2 &3 &4 |
| 500 | ******* More Messages for Data Model Checks ************ |
| 501 | Mod./ent.&1, node ent.&2, hier.attr.fr.ref.&3: No data element allowed |
| 503 | Mod./ent.&1, node ent.&2, hy.attr.fr.ref.&3: Data elem. &4 does not exist |
| 504 | Mod./ent.&1, node ent.&2, hy.attr.fr.ref.&3: Invalid reference entity |
| 506 | Mod./ent.&1, node ent.&2, hy.attr.fr.ref.&3: Refer.ent. &4 does not exist |
| 507 | Mod./ent.&1, node ent.&2, hy.attr.fr.ref.&3: Data element &4 is invalid |
| 508 | Mod./ent.&1, node ent.&2, hy.attr.fr.ref.&3, data elem.&4: No chg.docum. |
| 509 | Model &1, hierarchy attribute from ref. &2 used for diff. ref. entities |
| 510 | Mod./ent.&1, node ent.&2, hy.attribute &3: Entity type does not exist |
| 511 | Mod./ent.&1, node ent.&2, hy.attr.&3: Node entity type does not exist |
| 512 | Mod./ent.&1, node ent.&2, hy.attribute &3: No data element specified |
| 514 | Mod./ent.&1, node ent.&2, h.attr.&3: Check table f.data elem.&4 not found |
| 515 | Mod./ent.&1, node ent.&2, h.attr.&3: Data element &4 does not exist |
| 516 | Mod./ent.&1, node ent.&2, hierarchy attr. &3: Check table is invalid |
| 517 | Mod./ent.&1, node ent.&2, h.attr.&3, data elem.&4: No change documents |
| 518 | Mod./ent.&1, node ent.&2, h.attribute &3: Search help &4 does not exist |
| 519 | Mod./ent.&1, node ent.&2: Initialized name for hierarchy attribute |
| 520 | Mod./ent.&1, node ent.&2: Initial. name for hierarchy attribute from ref. |
| 521 | Mod./ent.&1, node ent.&2: Assignment of hierarchy attributes not allowed |
| 522 | Data model &1: Entity type &2 and hier.attribute from ref. have same name |
| 523 | Mod./ent.&1, node ent.&2: H.attr. &3 and h.attr. from ref. have same name |
| 524 | Model &1: Relationship and h.attr. fr. ref. &2 used in diff.entity types |
| 525 | Mod./ent.&1, node ent.&2, h.attr.fr.ref.&3: Missing h.attr. fr.ref. to &4 |
| 526 | Mod./ent.&1, node ent.&2: Hier.attr.&3 has same name as hy.attr. fr. ref. |
| 527 | Data model &, entity type &2: Cannot be used as a hierarchy node |
| 528 | Data model &1, entity type &2: Hierarchy indicator is not allowed |
| 529 | Data model &1, entity type &2: Description is missing |
| 530 | Data model &1, entity type &2: Invalid use of validity concept |
| 531 | Validity concept of entity type &1 must not be changed |
| 532 | Hierarchy &1: Invalid use of validity concept |
| 533 | Entity type &1 and &2 relationship: Invalid use of validity concept |
| 534 | Data model &1, entity type &2: Type of key assignment changed |
| 535 | Data model &1, entity type &2: Invalid use in hierarchy |
| 536 | Data model/entity type &1: Invalid hierarchy attribute |
| 537 | Data model &1, entity type &2: Description is missing |
| 538 | Data model &, entity type &2: Invalid use of keys in hierarchy |
| 540 | Data model &1, entity type &2, attribute &3: Data element type is invalid |
| 550 | Model &1, entity type &2: Source fields for texts must not be entered |
| 551 | Model &1, entity type &2: Attribute &3 must not be a key field |
| 557 | Data model &1: Key attributes must not be assigned to entity type &2 |
| 560 | Model &1, reuse active area &2: ABAP class &3 cannot be used |
| 561 | Model &1: Name of a reuse active area is invalid |
| 562 | Model &1: Active area &2 does not exist; use input help to select value |
| 563 | Model &1, entity type &2: Active area &3 does not exist |
| 564 | Model &1, entity type &2: Reuse of tables is not possible |
| 565 | Model &1, entity type &2: Remove the active area |
| 566 | Model &1, entity type &2: Use of active area has been switched |
| 567 | Model &1, reuse active area &2: ABAP class &3 is not within SAP standard |
| 568 | Model &1, custom entity type &2: Check the reuse active area |
| 569 | Model &1: Enter a value for active area; use input help to select value |
| 580 | Model &1, entity type &2: Invalid key treatment |
| 581 | Model &1, entity type &2: Missing number range object |
| 582 | Model &1, entity type &2: Deletion of entities not allowed |
| 583 | Model &1, entity type &2: Invalid deletion setting |
| 584 | Model &1, entity type &2: Invalid data element |
| 585 | Model &1, entity type &2: No change documents |
| 586 | Model &1, entity type &2: Internal key assignment; enter a reuse area |
| 587 | Data model &1, entity type &2: Number range object is not required |
| 588 | Model &1: Name of data model is incorrect |
| 590 | Data model &1, foreign key relationship &2: Field assignment missing |
| 591 | Model &1, ent.type &2: Only 1 foreign key relationship for attribute &3 |
| 592 | Data model &1, to-entity type &2: Invalid foreign key relationship &3 |
| 593 | Data model &1, from-entity type &2: Invalid relationship |
| 594 | Model &1, ent.type &2: Relationship &3 is not a foreign key relationship |
| 595 | Data model &1, entity type &2: Data element is missing |
| 596 | Data model &1, relationship &2: Value &3 is not valid as a from-field |
| 597 | Data model &1, relationship &2: Value &3 is not valid as a to-field |
| 598 | Data model &1, relationship &2: One or more From-fields are missing |
| 599 | Data model &1, relationship &2: Value &3 exists twice |
| 600 | Data model &1: SMT mapping could not be imported: &2 |
| 601 | Cannot determine logical name for source table &1 |
| 602 | No target table exists for source table &1 (logical name &2) |
| 605 | Data model &1: Business object type &2 is used in data model &3 |
| 610 | Model &1: Generated entity type &2 must not be deleted |
| 611 | Model &1: Entity type &2 contains generated fields; must not be deleted |
| 612 | Model &1, entity type &2: Generated attribute &3 must not be deleted |
| 613 | Model &1, from-ent.type &2: Generated relationship &3 must not be deleted |
| 614 | Model &1, from-ent.type &2: Generated relationship &3 must not be changed |
| 615 | Data model &1: Attribute &3 for generated entity type &2 |
| 616 | Model &1: Generated entity type &2 must not be enhanced with rel. &3 |
| 617 | Data model &1, entity type &2: Number range assignments are not supported |
| 618 | Data model &1, entity type &2: Reuse active areas are not supported |
| 619 | Data model &1, entity type &2: Language-dependent texts are not possible |
| 620 | Data model &1, entity type &2: Attribute &3 is a key field |
| 621 | Data model &1, entity type &2: Reference attribute &3 is a key field |
| 630 | Data model Customizing settings invalid for application of data model &1 |
| 631 | Entity &1 not in scope - navigation to attribute maintenance impossible |
| 649 | Navigation not possible; entity not set up for required field inputs |
| 650 | Navigation not possible; entity is flagged as not relevant |
| 651 | Check for required field cannot be set |
| 652 | Navigation not possible, relationship is no foreign key relationship |
| 653 | Please choose first a relationship |
| 700 | Active version of data model &1 deleted |
| 701 | Data for data model &1 deleted |
| 750 | Data not saved |
| 751 | Data model &1, entity type &2: Prefix is irrelevant |
| 752 | Data model &1, entity type &2: Prefix is invalid |
| 753 | Data model &1, entity type &2: Change of prefix |
| 754 | Data model &1, entity type &2: Prefix to be deleted |
| 797 | "&1" requires the same Message Output as "&2" |
| 798 | Error for Change Request Type &1 and Step &2 detected. |
| 799 | "&1" requires "&2" as relevant check |
| 800 | * Archiving for Change Documents |
| 801 | No entries to be archived were found with current selection criteria |
| 802 | No entries were found in archive with current selection criteria |
| 803 | Enter all required parameters |