USMD1B - Meldungen: MDF Anschluss
The following messages are stored in message class USMD1B: Meldungen: MDF Anschluss.
It is part of development package USMD1B in software component CA-MDG-AF. This development package consists of objects that can be grouped under "Data Modeling: MDG MDF Connection".
It is part of development package USMD1B in software component CA-MDG-AF. This development package consists of objects that can be grouped under "Data Modeling: MDG MDF Connection".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Program error |
| 001 | Data model &1: Persistence layer needs to be regenerated |
| 002 | Critical changes to object &1 |
| 003 | &1 &2 &3 &4 |
| 004 | Program error: MDF roles cannot be created for &1 |
| 005 | Roles for &1 are locked and cannot be created |
| 006 | Data model &1 has errors |
| 007 | Table conversion in background job: Transaction will be stopped |
| 008 | Error occurred while generating object &1 &2 |
| 009 | Converting data from table &1 (&4 / &3) to table &2 |
| 010 | Data model &1 is currently being edited by user &2 |
| 011 | ABAP Dictionary object &1 is not active |
| 012 | Data model &1: Data element &2 does not exist in active form |
| 013 | Table &1 has been converted to &2 |
| 014 | Table conversion from &1 to &2 was unsuccessful |
| 016 | Data model &1: Error while deleting database tables |
| 017 | No active data model exists |
| 018 | Data model &1 could not be activated |
| 019 | Data model &1 for activation postprocessing locked by user &2 |
| 020 | An open change adjustment exists in client &1 for data model &2 |
| 021 | Data model &1: Internal table &2 activated |
| 022 | Data model &1: Revise the generated structures |
| 023 | Data model &1: Structure name &4 assigned twice for &2 and &3 |
| 024 | Data record &1 for field name &2 still exists |
| 025 | Mapping entry for data record &1 for field name &2 is still in use |
| 026 | Entity type &1: Mapping entry with technical key &2 not found |
| 027 | Entity type &1: Technical key &2 added to change request &3 |
| 028 | Entity type &1: Technical key &2 is referenced in mapping table |
| 029 | Mapping write buffer of entity &1 is not empty |
| 030 | Data model &1: UI configuration cannot be locked |
| 031 | Data model &1: Dependent UI configuration variants cannot be deleted |
| 040 | Change requests must be adjusted because data model &1 has been modified |
| 041 | There are no data model changes that require adjustments |
| 042 | Key can not be assigned to the change request |
| 043 | Key is not yet assigned to any change request |
| 050 | Data model &1 could not be activated during import |
| 051 | Data model &1: SMT mapping could not be imported: &2 |
| 052 | Data model &1: SMT mapping does not exist |
| 053 | Data model &1: SMT mapping could not be saved |
| 060 | Change of generated database tables for model &1 started |
| 061 | Display/maintenance not allowed |
| 062 | Display/maintenance allowed with restrictions |
| 063 | Buffering not allowed, log switched off |
| 064 | Buffering allowed, log switched on |
| 065 | Change of display/maintenance status for table &1 successful |
| 066 | Change of display/maintenance status for table &1 failed |
| 067 | Change of generated database tables for model &1 finished |
| 068 | Change of buffering/log for table &1 successful |
| 069 | Change of buffering/log for table &1 failed |
| 070 | Index EDN on table &1 created successfully |
| 071 | Creation of index EDN on table &1 failed |
| 072 | Index TXT on table &1 created successfully |
| 073 | Creation of index TXT on table &1 failed |
| 100 | Error while writing change document |
| 101 | Data model changes have made parts of the change document irrelevant |
| 102 | Data model changes have made parts of the change document irrelevant |
| 103 | Change document &1 is too big (only first &2 items are read) |
| 200 | **** Messages for accessing hierarchies ******************************* |
| 202 | Predecessor node &1/&2 does not have parent node &3/&4 |
| 204 | &1 is not a valid value for &2 |
| 205 | Hierarchy &3, version &4: &1 is not a valid value for &2 |
| 206 | Version &3: &1 is not a valid value for &2 |
| 207 | Hierarchy &3: &1 is not a valid value for &2 |
| 208 | The used hierarchy is in process within change request &3 |
| 210 | Node cannot be inserted below itself |
| 211 | Node &1 is underneath itself in hierarchy &2 |
| 212 | Version &3: Node &1 is underneath itself in hierarchy &2 |
| 213 | Node cannot be moved or copied |
| 214 | &1 &2 already exists under node &3 &4 |
| 215 | &1 is not valid value for &2 |
| 216 | Hierarchy/Version &3: &1 is not a valid value for &2 |
| 217 | Version &3: &1 is not a valid value for &2 |
| 218 | Hierarchy &3: &1 is not a valid value for &2 |
| 219 | Version &1 is not a valid version |
| 220 | &2 is an invalid value for hierarchy attribute &2 |
| 221 | Hierarchy &3, version &4: &1 is an invalid value for hier. attribute &2 |
| 222 | Version &3: &1 is an invalid value for hierarchy attribute &2 |
| 223 | Hierarchy &3: &1 is an invalid value for hierarchy attribute &2 |
| 225 | &1 must not have lower-level nodes |
| 226 | &1 must not represent a range |
| 231 | Child of the edge is initialized |
| 232 | Parent of the edge is initialized |
| 233 | Parent &1 is not assigned in hierarchy &2 |
| 234 | &1 &2 already covered by a range node under node &3 &4 |
| 235 | Range node overlaps with node &1 &2 under node &3 &4 |
| 236 | Range node overlaps with range node &1 &2 under node &3 &4 |
| 300 | *********** MDGF-specific Error Messages in MDF **************** |
| 301 | &1 &2: A master record with value &4 does not exist for attribute &3 |
| 302 | &1 &2: Enter a value for attribute &3 |
| 303 | Data enrichment or derivation uses incorrect entity type |