MDG_DT_DATA_MODEL - Messages for the Configuration Workbench Model Access API
The following messages are stored in message class MDG_DT_DATA_MODEL: Messages for the Configuration Workbench Model Access API.
It is part of development package MDG_DT_DATA_MODELING in software component CA-MDG-DT. This development package consists of objects that can be grouped under "MDG: Data Modeling parts of Design Time".
It is part of development package MDG_DT_DATA_MODELING in software component CA-MDG-DT. This development package consists of objects that can be grouped under "MDG: Data Modeling parts of Design Time".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Enter a valid enqueue mode |
| 002 | Enter a valid enqueue scope |
| 003 | Enter a valid data model |
| 004 | Enter a valid object status for the data model |
| 005 | Enter a valid table name |
| 006 | Enter a valid entry for &1 |
| 007 | Table &1 does not exist in system &2 |
| 008 | No authorization to access cross-client table &1 |
| 009 | No authorization to display table &1 |
| 010 | No authorization to edit table &1 |
| 011 | Model table is empty |
| 012 | Invalid XML input |
| 013 | Enter a valid data model for the entity or entities |
| 014 | Enter a valid data model for the attribute or attributes |
| 015 | Enter a valid data model for the relationship or relationships |
| 016 | Enter a valid data model for the hierarchy or hierarchies |
| 017 | Enter a valid data model for the reuse active area or areas |
| 018 | Enter a valid data model for the object type code or object type codes |
| 019 | Enter a valid data model for the hierarchy attribute or attributes |
| 020 | Enter a valid data model for the hierarchy relationship or relationships |
| 021 | Model name &1 already exists; provide any other name |
| 022 | Entity &1 used in relationships is invalid; enter a valid entity |
| 023 | Client or data model &1 is being processed by user &2 |
| 024 | Data model name does not exist; enter data model header details first |
| 025 | Cannot modify value in write buffer |
| 026 | Cannot insert value; a duplicate key may exist |
| 027 | Cannot delete value; the key value may be incorrect |
| 028 | Enter a valid data model for the foreign key data |
| 029 | Storage and use type &1 is invalid for entity &2; enter a valid value |
| 030 | Enter a valid key handling value for entity &1 |
| 031 | Enter a valid validity entity value for entity &1 |
| 032 | Enter a valid hierarchy value for entity &1 |
| 033 | Enter a valid validity hierarchy value for entity &1 |
| 034 | Enter a valid entity deletion value for entity &1 |
| 035 | Enter a valid cardinality for relation &1 |
| 036 | Enter a valid relation type for relation &1 |
| 037 | Enter a valid data element for entity type &1 |
| 038 | Enter a valid search help for entity type &1 |
| 039 | Exception when writing to transport or BC request |
| 040 | Active data does not exist for data model &1 |
| 041 | Transport required in this landscape; enter a transport request |
| 042 | &1 was created in another software layer; no edit authorization |
| 043 | You are not authorized to edit &1 |
| 044 | Possible duplicate entry for &1 |
| 045 | Writing to the GTABKEY table failed |
| 046 | GTABKEY table is not configured for the landscape |
| 047 | &1 data model is in SAP namespace; use Z*,Y* or X* |
| 048 | &1 data model is in Customer namespace; do not use Z*,Y*, or X* |
| 049 | &1 is in SAP landscape; use SAP namespace |
| 050 | &1 is in customer landscape; use customer namespace |
| 051 | Data model &1 is not saved |
| 052 | Data model &1 is saved successfully |
| 053 | &1 cannot be deleted |
| 054 | &1 was created in another software layer; no delete authorization |
| 055 | Enter a valid entity |
| 056 | Enter a valid attribute for entity &1 |
| 057 | Enter a valid multi language indicator value for entity &1 |
| 058 | Enter a valid attachment indicator value for entity &1 |
| 059 | Enter a valid set indicator value for entity &1 |
| 060 | Enter a valid entity for attribute &1 |
| 061 | Enter a valid key indicator for attribute &1 |
| 062 | Enter a valid data element for attribute &1 in entity &2 |
| 063 | Enter a valid mandatory attribute indicator for attribute &1 in entity &2 |
| 064 | Enter a valid search help for attribute &1 in entity &2 |
| 065 | Enter a valid data model in hierarchies |
| 066 | Enter a valid entity in hierarchies |
| 067 | Invalid buffer status, read data model again |
| 068 | Enter a valid hierarchy usage value |
| 069 | Error during enqueue of data model &1 |
| 070 | Invalid data model, entity, or attribute: Enter a valid value |
| 071 | Invalid data model, entity, or business object type: Enter a valid value |
| 072 | Invalid data model or entity: Enter a vaild value |
| 073 | Invalid data model, entity, or hierarchy: Enter valid value |
| 074 | Invalid data model, entity, attribute, or hierarchy; Enter a valid value |
| 075 | Invalid data model, entity, or relation hierarchy; Enter a valid value |
| 076 | Either data model, from entity, or relation; Enter a valid value |
| 077 | Either data model or reuse area is invalid. Enter valid value |
| 078 | Enter a valid relationship |
| 079 | Enter a valid from entity for relationship &1 |
| 080 | Enter a valid data element for relationship &1 |
| 081 | Enter a valid data model in hierarchy attributes |
| 082 | Enter a valid entity or foreign entity in hierarchy attributes |
| 083 | Enter a valid data element for hierarchy attribute of entity &1 |
| 084 | Enter a valid search help for hierarchy attribute of entity &1 |
| 085 | Enter a valid attribute in hierarchy attributes |
| 086 | Enter a valid entity for relationships for deriving hierarchy attributes |
| 087 | Enter a valid relation for relationship for deriving hierarchy attributes |
| 088 | Enter a valid data element for derived hierarchy attribute relationships |
| 089 | Enter a valid long name for the entity |
| 090 | Enter a valid long name for the attribute |
| 091 | Enter a valid long name for the relation |
| 092 | Enter a valid long name |
| 093 | Read data model &1 before copying it to the new data model |
| 094 | Data model &1 name already exists; choose a different name |
| 095 | &1 does not exist; Use a valid name |
| 096 | Object names must start with Z* or Y* in development client |
| 097 | Data model &1 does not exist |
| 098 | Object cannot be deleted; &1 not in Z* or Y* namespace |
| 099 | Transport request should be provided to transport switch BC set. |
| 100 | Cannot edit in development landscape; must be in Z* or Y* namespace |
| 101 | Model name should be two characters |
| 102 | Enter valid model package details |
| 103 | Insertion of model package details failed; enter valid data |
| 104 | Model package details updated sucessfully |
| 105 | No changes done; database is not updated |
| 106 | Delete structure generation details first |
| 107 | Deletion of model package details failed; enter valid data |
| 108 | Enter valid structure details |
| 109 | Deletion of structures failed; enter valid data |
| 110 | Enter model package details before entering structure details |
| 111 | Changes to structure details failed; enter valid data |
| 112 | Enter a valid active model |
| 113 | &1 is an invalid value; enter a valid entity |
| 114 | &1 is an invalid value; enter a valid structure usage type |
| 115 | &1 is an invalid value; enter a valid where-used list for structure type |
| 116 | Invalid name used in structure; names must start with Z |
| 117 | Entity must have an SU type of 1 or 4; &1 is invalid |
| 118 | User status can be set only in customer landscape |
| 119 | Error returned when checking the customer namespace |
| 120 | Relationship &1 is not valid |
| 121 | &1 is an invalid model name |
| 122 | Text is only transported in the original language &1 |
| 123 | Activation job is already running for model &1 |
| 124 | Switch BC set &1 does not exist; recheck switch BC set name |
| 125 | Activation of data model &1 is triggered |
| 126 | Enter valid values for activation job |
| 127 | Enqueue job before activation process of model &1 |
| 128 | &1 is not in SAP delivery namespace; edit not possible |
| 129 | &1 and &2 in SAP namespace; relation name must be in customer namespace |
| 130 | Structure(s) are sucessfully deleted |
| 131 | Enter valid transport request/switch bc set details |
| 132 | Models with Y*/Z* names cannot be deleted in delivery landscape |
| 133 | Relationship name &1 is not valid. |
| 134 | Models with X*/Y*/Z* names cannot be edited in delivery landscape |
| 135 | &1, &2 and &3 Combination is not in customer Landscape. |
| 136 | &1 is either an invalid transport request or no required authorization |
| 137 | Switch BC set is locked in &1, All changes will be logged here. |
| 138 | User does not have task in request id &1. |
| 139 | Cannot add data to &1. Please select another Switch BC set. |
| 140 | &1 is not a valid Switch BC set. Please enter a valid SBC request. |
| 141 | &1 table/structure doesn't exist. Enter a valid entry for entity &2 |
| 142 | &1 table/structure is invalid for &2 attribute of &3 entity. |
| 143 | &1 table/structure is invalid for &2 relation. Enter valid value |
| 144 | &1 field is invalid for &2 entity. Enter a valid value |
| 145 | &1 field is invalid for &2 entity &3 attribute. Enter a valid value |
| 146 | Model Package details successfully deleted |
| 147 | Object names must not start with Z* or Y* in delivery client |
| 148 | Attribute names must start with ZZ* or YY* in customer landscape. |
| 149 | Attribute names must not start with ZZ* or YY* in SAP landscape. |
| 150 | Data model specific structures need to be adjusted in separate activity. |