SAP ABAP Message Class MDG_MDF (Master Data: Messages)
Basic Data
Hierarchy
☛
MDG_FND (Software Component) MDG Foundation
⤷ CA-MDG-AF (Application Component) Application Framework
⤷ MDG_MDF0 (Package) Master Data
⤷ CA-MDG-AF (Application Component) Application Framework
⤷ MDG_MDF0 (Package) Master Data
Attributes
Message class | MDG_MDF | |
Short Description | Master Data: Messages | |
Changed On | 20130531 | |
Last Changed At | 123605 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | Program error(s) | Space: object requires documentation | |
2 | 001 | No documentation available | Space: object requires documentation | |
3 | 003 | Value is not numeric | Space: object requires documentation | |
4 | 004 | Customizing settings are inconsistent | Space: object requires documentation | |
5 | 008 | Definition of Field &1 is inconsistent | Space: object requires documentation | |
6 | 015 | &1 is not a valid value for &2 | Space: object requires documentation | |
7 | 016 | The value &2 is invalid for characteristic &1 | Space: object requires documentation | |
8 | 017 | The value &2 is invalid for characteristic &1 | Space: object requires documentation | |
9 | 020 | &1: Fixed Values cannot be changed | Space: object requires documentation | |
10 | 021 | &1&2&3&4 | Space: object requires documentation | |
11 | 024 | Characteristic &3: The value is too long (&1 is greater than &2) | Space: object requires documentation | |
12 | 027 | The value &2 is invalid for characteristic &1 (character &3) | Space: object requires documentation | |
13 | 028 | Entry is required for for characteristic &1 | Space: object requires documentation | |
14 | 030 | The value &2 is invalid for characteristic &1 (character &3) | Space: object requires documentation | |
15 | 036 | Unknown application: &1 | Space: object requires documentation | |
16 | 037 | Enter a numeric value (field name &1, &2) | The short text describes the object sufficiently | |
17 | 038 | Conversion not possible (field name &1, &2) | The short text describes the object sufficiently | |
18 | 041 | Conversion not possible; number of decimal places does not match currency | Space: object requires documentation | |
19 | 042 | Conversion not possible; number of decimal places does not match unit | Space: object requires documentation | |
20 | 048 | Conversion is not possible; number of decimal places is invalid | Space: object requires documentation | |
21 | 075 | Field &1 is still registered and cannot be deleted | The short text describes the object sufficiently | |
22 | 078 | Value &3 is invalid for &1 (&2) - ALPHA conversion | The short text describes the object sufficiently | |
23 | 079 | Value &3 is invalid for &1 (&2) - wrong date | The short text describes the object sufficiently | |
24 | 080 | Value &3 is invalid for &1 (&2) - wrong time | The short text describes the object sufficiently | |
25 | 099 | ************ Messages for Characteristic Registration/Management ****** | Space: object requires documentation | |
26 | 100 | Field &1 already exists under a different domain | Space: object requires documentation | |
27 | 101 | Field name &1 is already reserved for role &2 | Space: object requires documentation | |
28 | 102 | Create fields with role &2 using field name &3 | Space: object requires documentation | |
29 | 104 | Role &1 is invalid; see long text | Space: object requires documentation | |
30 | 105 | A data element does not exist for field &1 | Space: object requires documentation | |
31 | 107 | DDIC structures are being regenerated | Space: object requires documentation | |
32 | 108 | DDIC structures are being regenerated | Space: object requires documentation | |
33 | 109 | DDIC structures are being regenerated | Space: object requires documentation | |
34 | 110 | Regenerating DDIC structures (change in role &1) | Space: object requires documentation | |
35 | 111 | Time stamp of imported role &1 has been raised | Space: object requires documentation | |
36 | 113 | Field &1 has the wrong role assignment; see long text | Space: object requires documentation | |
37 | 114 | In application area &4, field &1 is already linked to basis field &3 | Space: object requires documentation | |
38 | 115 | Field &1 cannot be a node in hierarchies of characteristic &2 | Space: object requires documentation | |
39 | 118 | The key of field &1 is too long | Space: object requires documentation | |
40 | 120 | Field &1 does not exist | Space: object requires documentation | |
41 | 122 | The background job must finish first | Space: object requires documentation | |
42 | 123 | An error occurred during the generation; see the log | Space: object requires documentation | |
43 | 125 | The area must contain the required characteristic &1 | Space: object requires documentation | |
44 | 126 | The area uses an unknown characteristic &1 | Space: object requires documentation | |
45 | 127 | Definition of role &1 has changed | Space: object requires documentation | |
46 | 128 | Definition of characteristic &1 has changed | Space: object requires documentation | |
47 | 134 | &4 records copied to table &3 | Space: object requires documentation | |
48 | 137 | Unable to assign data element &1 | Space: object requires documentation | |
49 | 138 | Key figure &1 (type &2) has no unit field | Space: object requires documentation | |
50 | 140 | Field &1 does not exist; see long text | Space: object requires documentation | |
51 | 141 | Input value &1 is invalid | Space: object requires documentation | |
52 | 145 | Properties of validity check have been changed for field &1 | Space: object requires documentation | |
53 | 150 | =========== Area UGMDCHK0: 150-199 ================================== | Space: object requires documentation | |
54 | 199 | ********** Messages for the Transport Tool ***************** | Space: object requires documentation | |
55 | 200 | No information exists for table &1 | Space: object requires documentation | |
56 | 201 | Characteristic &1 does not exist | Space: object requires documentation | |
57 | 202 | Characteristic &1 has no sub-structure &2 | Space: object requires documentation | |
58 | 203 | Generating tables for characteristic &1 | Space: object requires documentation | |
59 | 204 | Table &2 does not contain the SIDs for characteristic &1 | Space: object requires documentation | |
60 | 205 | Internal error &1 &2 &3 &4 | Space: object requires documentation | |
61 | 206 | Cannot determine SID table for characteristic &1 | Space: object requires documentation | |
62 | 207 | Field with SID &1 does not exist | Space: object requires documentation | |
63 | 208 | No SID exists for the value &1 of characteristic &2 | Space: object requires documentation | |
64 | 209 | &2: Unable to determine the value with SID &1 | Space: object requires documentation | |
65 | 212 | Objects belonging to transport object &1 can not be maintained | Space: object requires documentation | |
66 | 213 | Cannot create field &1 | Space: object requires documentation | |
67 | 214 | Field &1 created | Space: object requires documentation | |
68 | 215 | Could not create or determine an SID for value &1 of characteristic &2 | Space: object requires documentation | |
69 | 216 | Cannot determine which field in the original system has the SID &1 | Space: object requires documentation | |
70 | 217 | Field &1 does not exist | Space: object requires documentation | |
71 | 218 | Complex selection conditions are not supported | Space: object requires documentation | |
72 | 219 | Cannot determine which field in the original system has the SID &1 | Space: object requires documentation | |
73 | 220 | Field &1 does not exist | Space: object requires documentation | |
74 | 221 | Unable to create the combination characteristic | Space: object requires documentation | |
75 | 224 | Application area &1/&2 will not be copied | Space: object requires documentation | |
76 | 225 | Value SID for invalid field name with SID 0 | Space: object requires documentation | |
77 | 227 | Table &1 does not exist | Space: object requires documentation | |
78 | 228 | Request type &1 not supported | The short text describes the object sufficiently | |
79 | 229 | Table &1 is no longer in use | Space: object requires documentation | |
80 | 237 | Unnamed object &1 has the name &2 in the target system | Space: object requires documentation | |
81 | 238 | Object name of field name &1 differs from the target system (&2 vs. &3) | Space: object requires documentation | |
82 | 239 | Customizing entries have been added to transport request &1 | The short text describes the object sufficiently | |
83 | 299 | ************** Messages for Hierarchy Maintenance *****************+ | Space: object requires documentation | |
84 | 300 | Leaf &1 belongs to type &2 | Space: object requires documentation | |
85 | 301 | Hierarchies can only be top nodes | Space: object requires documentation | |
86 | 302 | No hierarchies are allowed for characteristic &1 | Space: object requires documentation | |
87 | 304 | Hierarchy &1 has more than one root node | Space: object requires documentation | |
88 | 305 | Hierarchy &1 has more than one root node | Space: object requires documentation | |
89 | 306 | Delta leaf &1 cannot be deleted manually | Space: object requires documentation | |
90 | 308 | Error while saving a hierarchy and/or link attrubutes | Space: object requires documentation | |
91 | 309 | Data is inconsistent in hierarchy table &2 | Space: object requires documentation | |
92 | 310 | Error while reading the metadata for database table &1 | Space: object requires documentation | |
93 | 311 | &1 is already used in hierarchies; assignment not possible | Space: object requires documentation | |
94 | 312 | &1 is a delta node; assignment not possible | Space: object requires documentation | |
95 | 314 | Entry is invalid | The short text describes the object sufficiently | |
96 | 315 | Only one hierarchy is allowed for characteristic &1 | Space: object requires documentation | |
97 | 316 | Invalid higher-level characteristic | Space: object requires documentation | |
98 | 317 | Invalid entry of a higher-level characteristic | Space: object requires documentation | |
99 | 320 | No more entries are permitted under &1 | Space: object requires documentation | |
100 | 321 | &1 is not a valid hierarchy entry | Space: object requires documentation | |
101 | 322 | &2 cannot be inserted under &1 | Space: object requires documentation | |
102 | 323 | Node &1 is underneath itself in hierarchy &2 | Space: object requires documentation | |
103 | 327 | Conversion of hierarchy data is necessary - see long text | Space: object requires documentation | |
104 | 328 | Error while writing hierarchies in system &3 - see long text | Space: object requires documentation | |
105 | 399 | ************** Messages for ENQUEUE/DEQUEUE Method ******************* | Space: object requires documentation | |
106 | 400 | Parameter for ENQUEUE/DEQUEUE contains an error | Space: object requires documentation | |
107 | 402 | Values for characteristic &2 already locked by user &1 | Space: object requires documentation | |
108 | 403 | System error while setting the lock | Space: object requires documentation | |
109 | 404 | &2 &3 already locked by user &1 | Space: object requires documentation | |
110 | 405 | DDIC structures already being generated by user &1 | Space: object requires documentation | |
111 | 409 | **** More messages for characteristic registration/management ****** | The short text describes the object sufficiently | |
112 | 411 | Error while replicating data - see long text | Space: object requires documentation | |
113 | 418 | Field &1: Data conversion is necessary | Space: object requires documentation |
History
Last changed on/by | 20130531 | SAP | |
SAP Release Created in | 702 |