SAP ABAP Message Class UGMD (FIN Master Data: Messages)
Basic Data
Hierarchy
☛
FINBASIS (Software Component) Fin. Basis
⤷ FIN-FB (Application Component) Financials Basis
⤷ UGMD0 (Package) FIN General: Master Data
⤷ FIN-FB (Application Component) Financials Basis
⤷ UGMD0 (Package) FIN General: Master Data
Attributes
Message class | UGMD | |
Short Description | FIN Master Data: Messages | |
Changed On | 20041006 | |
Last Changed At | 145632 |
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 | 002 | Program could not be generated | Space: object requires documentation | |
4 | 003 | Value is not numeric | Space: object requires documentation | |
5 | 004 | Customizing settings are inconsistent | Space: object requires documentation | |
6 | 005 | Customizing settings are inconsistent | Space: object requires documentation | |
7 | 006 | Error while reading definition of an InfoObject: &1&2&3&4 | Space: object requires documentation | |
8 | 007 | System error while calling up a function module at destination &1 | Space: object requires documentation | |
9 | 008 | Definition of Field &1 is inconsistent | Space: object requires documentation | |
10 | 009 | Data element of characteristic &1 changed | Space: object requires documentation | |
11 | 010 | System error during RFC communication with &1 | Space: object requires documentation | |
12 | 011 | System error &1 during RFC communication with &2 | Space: object requires documentation | |
13 | 012 | Communication error during RFC communication with &1 | Space: object requires documentation | |
14 | 013 | Communication error &1 during RFC communication with &2 | Space: object requires documentation | |
15 | 014 | InfoObject &1 does not exist in BW system &2 | Space: object requires documentation | |
16 | 015 | &1 is not a valid value for &2 | Space: object requires documentation | |
17 | 016 | The value &2 is invalid for characteristic &1 | Space: object requires documentation | |
18 | 017 | The value &2 is invalid for characteristic &1 | Space: object requires documentation | |
19 | 018 | Could not determine SID of the value of the higher-level characteristic | Space: object requires documentation | |
20 | 019 | Maintenance is done in another transaction | Space: object requires documentation | |
21 | 020 | &1: Fixed Values cannot be changed | Space: object requires documentation | |
22 | 021 | &1&2&3&4 | Space: object requires documentation | |
23 | 022 | Hierarchy &1 is not being written to BW System &2 | Space: object requires documentation | |
24 | 023 | &1&2 | Space: object requires documentation | |
25 | 024 | Characteristic &3: The value is too long (&1 is greater than &2) | Space: object requires documentation | |
26 | 025 | A value for characteristic &2 was expected, not a value for char. &1 | Space: object requires documentation | |
27 | 026 | This functionality has not yet been implemented | Space: object requires documentation | |
28 | 027 | The value &2 is invalid for characteristic &1 (character &3) | Space: object requires documentation | |
29 | 028 | Entry is required for for characteristic &1 | Space: object requires documentation | |
30 | 029 | Maximum number of columns has been reached | Space: object requires documentation | |
31 | 030 | The value &2 is invalid for characteristic &1 (character &3) | Space: object requires documentation | |
32 | 031 | Messages while saving data in destination ( &1 ) | Space: object requires documentation | |
33 | 032 | Hierarchy &1 not yet activated | Space: object requires documentation | |
34 | 033 | Master data or hierarchies for characteristic &1 are time-dependent | Space: object requires documentation | |
35 | 034 | List of possible entries not available for key figures | Space: object requires documentation | |
36 | 035 | No possible entries available | Space: object requires documentation | |
37 | 036 | Unknown application: &1 | Space: object requires documentation | |
38 | 037 | Enter a numeric value (field name &1, &2) | The short text describes the object sufficiently | |
39 | 038 | Conversion not possible (field name &1, &2) | The short text describes the object sufficiently | |
40 | 039 | Char. &3: &1 is being used in BW &4 and cannot be deleted | Space: object requires documentation | |
41 | 040 | &1: &2 is still in use and cannot be deleted | Space: object requires documentation | |
42 | 041 | Conversion not possible; number of decimal places does not match currency | Space: object requires documentation | |
43 | 042 | Conversion not possible; number of decimal places does not match unit | Space: object requires documentation | |
44 | 043 | Error during processing; see long text | Space: object requires documentation | |
45 | 044 | Definition of RFC destination &1 is incorrect; see long text | Space: object requires documentation | |
46 | 045 | RFC destination &1 does not exist; see long text | Space: object requires documentation | |
47 | 046 | &1: Deletion not possible; &2 is still in use | Space: object requires documentation | |
48 | 047 | Key not unique for value &2 in field &1 | Space: object requires documentation | |
49 | 048 | Conversion is not possible; number of decimal places is invalid | Space: object requires documentation | |
50 | 049 | &1: &2 being used by &3 &4 | Space: object requires documentation | |
51 | 050 | ODS object &1 cannot be used (see long text) | Space: object requires documentation | |
52 | 051 | ODS object &1 is not transactional | Space: object requires documentation | |
53 | 052 | &1 is used in a hierarchy and cannot be deleted | Space: object requires documentation | |
54 | 053 | &1 is used in a hierarchy and cannot be deleted | Space: object requires documentation | |
55 | 054 | &1 is used in a hierarchy and cannot be deleted | Space: object requires documentation | |
56 | 055 | &1 is used in a hierarchy and cannot be deleted | Space: object requires documentation | |
57 | 056 | &1 is used in hierarchy &2 in hierarchy version &3 starting at &4 | The short text describes the object sufficiently | |
58 | 057 | &1 is used in hierarchy &2 in hierarchy version &3 | The short text describes the object sufficiently | |
59 | 058 | &1 is used in hierarchy &2 starting at &3 | The short text describes the object sufficiently | |
60 | 059 | &1 is used in hierarchy &2 | The short text describes the object sufficiently | |
61 | 060 | &1 is used by &2 in validity version &3 starting at &4 | The short text describes the object sufficiently | |
62 | 061 | &1 is used by &2 in validity version &3 | The short text describes the object sufficiently | |
63 | 062 | &1 is used by &2 starting at &3 | The short text describes the object sufficiently | |
64 | 063 | &1 is used in the hierarchy and cannot be deleted | Space: object requires documentation | |
65 | 064 | &1 is used in the hierarchy and cannot be deleted | Space: object requires documentation | |
66 | 065 | &1 is used in the InfoCube and cannot be deleted | Space: object requires documentation | |
67 | 066 | &1 is used in ODS object &2 and cannot be deleted | Space: object requires documentation | |
68 | 067 | &1 is used as a navigation attribute and cannot be deleted | Space: object requires documentation | |
69 | 068 | &1 is used in query &2 and cannot be deleted | Space: object requires documentation | |
70 | 069 | &1 is used in the hierarchy and cannot be deleted | Space: object requires documentation | |
71 | 070 | Value &2 for characteristic &1 cannot be checked correctly | Space: object requires documentation | |
72 | 071 | Value &2 for characteristic &1 is invalid; only capital letters allowed | Space: object requires documentation | |
73 | 072 | Value &2 for characteristic &1 is invalid; only capital letters allowed | The short text describes the object sufficiently | |
74 | 073 | Error in mapping class &1 | Space: object requires documentation | |
75 | 074 | Value '#' is invalid for &1 (&2) - has a special meaning in BW system | The short text describes the object sufficiently | |
76 | 075 | Field &1 is still registered and cannot be deleted | The short text describes the object sufficiently | |
77 | 076 | Error while writing values of characteristic &1/&2 (RFC destination &3) | Space: object requires documentation | |
78 | 077 | Error while deleting values of characteristic &1/&2 (RFC destination &3) | Space: object requires documentation | |
79 | 078 | Value &3 is invalid for &1 (&2) - ALPHA conversion | The short text describes the object sufficiently | |
80 | 079 | Value &3 is invalid for &1 (&2) - wrong date | The short text describes the object sufficiently | |
81 | 080 | Value &3 is invalid for &1 (&2) - wrong time | The short text describes the object sufficiently | |
82 | 081 | &1: A characteristic value is still in use and cannot be deleted | Space: object requires documentation | |
83 | 082 | &1 is used in a hierarchy and cannot be deleted | Space: object requires documentation | |
84 | 083 | &1 is used in a hierarchy and cannot be deleted | Space: object requires documentation | |
85 | 084 | &1 is used in a hierarchy and cannot be deleted | Space: object requires documentation | |
86 | 085 | &1 is used in a hierarchy and cannot be deleted | Space: object requires documentation | |
87 | 086 | Attribute &3 is contained in both DataStore objects | Space: object requires documentation | |
88 | 087 | Also allocate a time-independent DataStore object | Space: object requires documentation | |
89 | 088 | &1: Allocate two different DataStore objects | The short text describes the object sufficiently | |
90 | 091 | &1 is used at hierarchy edge &2 and cannot be deleted | Space: object requires documentation | |
91 | 099 | ************ Messages for Characteristic Registration/Management ****** | Space: object requires documentation | |
92 | 100 | Field &1 already exists under a different domain | Space: object requires documentation | |
93 | 101 | Field name &1 is already reserved for role &2 | Space: object requires documentation | |
94 | 102 | Create fields with role &2 using field name &3 | Space: object requires documentation | |
95 | 103 | Field &1 is used in different roles | Space: object requires documentation | |
96 | 104 | Role &1 is invalid; see long text | Space: object requires documentation | |
97 | 105 | A data element does not exist for field &1 | Space: object requires documentation | |
98 | 106 | No entries exist | Space: object requires documentation | |
99 | 107 | DDIC structures are being regenerated | Space: object requires documentation | |
100 | 108 | DDIC structures are being regenerated | Space: object requires documentation | |
101 | 109 | DDIC structures are being regenerated | Space: object requires documentation | |
102 | 110 | DDIC structures are being regenerated | Space: object requires documentation | |
103 | 111 | Time stamp of imported role &1 has been raised | Space: object requires documentation | |
104 | 112 | Lock key for role &1 is too long | Space: object requires documentation | |
105 | 113 | Field &1 has the wrong role assignment; see long text | Space: object requires documentation | |
106 | 114 | In application area &4, field &1 is already linked to basis field &3 | Space: object requires documentation | |
107 | 115 | Field &1 cannot be a node in hierarchies of characteristic &2 | Space: object requires documentation | |
108 | 116 | Field &1 does not actively exist or cannot be used in system &2 | Space: object requires documentation | |
109 | 117 | No RFC destination is assigned to application area &1 | Space: object requires documentation | |
110 | 118 | The key of field &1 is too long | Space: object requires documentation | |
111 | 119 | InfoObject &1 does not exist | Space: object requires documentation | |
112 | 120 | Field &1 does not exist | Space: object requires documentation | |
113 | 121 | Navigation attributes are not permitted for characteristic &2 | Space: object requires documentation | |
114 | 122 | The background job must finish first | Space: object requires documentation | |
115 | 123 | An error occurred during the generation; see the log | Space: object requires documentation | |
116 | 124 | Database conversion may cause loss of data | Space: object requires documentation | |
117 | 125 | The area must contain the required characteristic &1 | Space: object requires documentation | |
118 | 126 | The area uses an unknown characteristic &1 | Space: object requires documentation | |
119 | 127 | Definition of role &1 has changed | Space: object requires documentation | |
120 | 128 | Definition of characteristic &1 has changed | Space: object requires documentation | |
121 | 129 | Change or update the table entries in transaction UG01 | Space: object requires documentation | |
122 | 130 | Registration made with invalid property of RFC destination &1 | Space: object requires documentation | |
123 | 131 | Supply all field names for role &1 | Space: object requires documentation | |
124 | 132 | Define RFC destination &1 with connection type "R/3 connection" | Space: object requires documentation | |
125 | 133 | A heading cannot be entered for field &1; see long text | Space: object requires documentation | |
126 | 134 | &4 records copied to table &3 | Space: object requires documentation | |
127 | 135 | Definition of characteristic &1 has changed | Space: object requires documentation | |
128 | 136 | Cannot synchronize characteristic &1 | Space: object requires documentation | |
129 | 137 | Unable to assign data element &1 | Space: object requires documentation | |
130 | 138 | Key figure &1 (type &2) has no unit field | Space: object requires documentation | |
131 | 139 | Field &1: This compound differs from that of basic field &2 | Space: object requires documentation | |
132 | 140 | Field &1 does not exist; see long text | Space: object requires documentation | |
133 | 141 | Input value &1 is invalid | Space: object requires documentation | |
134 | 142 | Converting combination characteristics from table &1 to table &2 | Space: object requires documentation | |
135 | 143 | No value for SID &2 from field name &1; conversion failed | Space: object requires documentation | |
136 | 144 | Conflict in keys of field name &1; conversion failed | Space: object requires documentation | |
137 | 145 | Properties of validity check have been changed for field &1 | Space: object requires documentation | |
138 | 146 | Error '&3' in data conversion to table &2. | Space: object requires documentation | |
139 | 147 | Conversion to table &2 has finished with &3 error(s) | Space: object requires documentation | |
140 | 148 | Conversion to table &2 is complete (&3 entries) | Space: object requires documentation | |
141 | 149 | The value SID cannot be determined for value &2 (field name &1) | The short text describes the object sufficiently | |
142 | 150 | =========== Area UGMDCHK0: 150-199 ================================== | Space: object requires documentation | |
143 | 151 | Table &, role &: Class & does not exist | Space: object requires documentation | |
144 | 152 | Table &, role &: Interface & is missing in class & | Space: object requires documentation | |
145 | 153 | Table &, role &: Entry on class & is missing | Space: object requires documentation | |
146 | 154 | Table &, transport object &: Interface & is missing in class & | Space: object requires documentation | |
147 | 155 | Table &, transport object &: Class & does not exist | Space: object requires documentation | |
148 | 156 | Table &, transport object &: Entry on class & is missing | Space: object requires documentation | |
149 | 157 | Table &, role &: Field & cannot be & | Space: object requires documentation | |
150 | 158 | Table &, role &, field &: Data element & does not exist | Space: object requires documentation | |
151 | 159 | Table &, local role &: Required field & is empty | Space: object requires documentation | |
152 | 160 | Table &, local role &: Check table for & must have & in key | Space: object requires documentation | |
153 | 161 | Table &, role &: Required entry field & is empty | Space: object requires documentation | |
154 | 162 | Table &, role &: Field &: Data element & must have domain UG_SID | Space: object requires documentation | |
155 | 163 | Table &, role &: Field &: Transport object & must be in SOBJ | Space: object requires documentation | |
156 | 164 | Table &, role &: Field & must be in key of table & | Space: object requires documentation | |
157 | 165 | Table &, role &: Table name & must also be entered in & | Space: object requires documentation | |
158 | 166 | Table &, role &: Field &: Structure & does not exist in DDIC | Space: object requires documentation | |
159 | 167 | Table &, role &: Field & occurs in both structures & | Space: object requires documentation | |
160 | 168 | Table &, role &: Attribute & does not occur in any of tables & | Space: object requires documentation | |
161 | 169 | Table &, role &: Field & in table & must be set | Space: object requires documentation | |
162 | 170 | Table &, role &: Must be local | Space: object requires documentation | |
163 | 171 | Table &, role &: Field &: Data element & must have domain GUID | Space: object requires documentation | |
164 | 172 | Table &, role & is missing in table & | Space: object requires documentation | |
165 | 173 | Table &, role & must have check table in table & | Space: object requires documentation | |
166 | 174 | Table &, role &: Field & is missing in table & | Space: object requires documentation | |
167 | 175 | Table &, role &: Key flags on field &, table & are not disjunct | Space: object requires documentation | |
168 | 176 | Warning: Another role change needed; see long text | Space: object requires documentation | |
169 | 177 | Time conversion for non-local role &1 cannot be switched off | The short text describes the object sufficiently | |
170 | 178 | Table &2 for role &1 requires fields FROMPERIOD and FROMYEAR | The short text describes the object sufficiently | |
171 | 179 | Role &1, structure &2: Time conversion with keys only | The short text describes the object sufficiently | |
172 | 180 | Key &2 for role &1 requires fields FROMPERIOD and FROMYEAR | The short text describes the object sufficiently | |
173 | 181 | Key &2 for role &1 requires one more field (or more) | The short text describes the object sufficiently | |
174 | 182 | Time conversion must be identical for keys &2 and &3 (role &1) | The short text describes the object sufficiently | |
175 | 183 | Time conversion must be identical for structures &1 and &2 (role &3) | The short text describes the object sufficiently | |
176 | 199 | ********** Messages for the Transport Tool ***************** | Space: object requires documentation | |
177 | 200 | No information exists for table &1 | Space: object requires documentation | |
178 | 201 | Characteristic &1 does not exist | Space: object requires documentation | |
179 | 202 | Characteristic &1 has no sub-structure &2 | Space: object requires documentation | |
180 | 203 | Generating tables for characteristic &1 | Space: object requires documentation | |
181 | 204 | Table &2 does not contain the SIDs for characteristic &1 | Space: object requires documentation | |
182 | 205 | Internal error &1 &2 &3 &4 | Space: object requires documentation | |
183 | 206 | Cannot determine SID table for characteristic &1 | Space: object requires documentation | |
184 | 207 | Field with SID &1 does not exist | Space: object requires documentation | |
185 | 208 | No SID exists for the value &1 of characteristic &2 | Space: object requires documentation | |
186 | 209 | &2: Unable to determine the value with SID &1 | Space: object requires documentation | |
187 | 210 | Characteristic &1 does not have a text table | Space: object requires documentation | |
188 | 211 | Transport object &1 may not be changed | Space: object requires documentation | |
189 | 212 | Objects belonging to transport object &1 can not be maintained | Space: object requires documentation | |
190 | 213 | Cannot create field &1 | Space: object requires documentation | |
191 | 214 | Field &1 created | Space: object requires documentation | |
192 | 215 | Could not create or determine an SID for value &1 of characteristic &2 | Space: object requires documentation | |
193 | 216 | Cannot determine which field in the original system has the SID &1 | Space: object requires documentation | |
194 | 217 | Field &1 does not exist | Space: object requires documentation | |
195 | 218 | Complex selection conditions are not supported | Space: object requires documentation | |
196 | 219 | Cannot determine which field in the original system has the SID &1 | Space: object requires documentation | |
197 | 220 | Field &1 does not exist | Space: object requires documentation | |
198 | 221 | Unable to create the combination characteristic | Space: object requires documentation | |
199 | 222 | The sequence of the tasks in comb.characteristic &1 has changed | Space: object requires documentation | |
200 | 223 | Navigation attribute &3 is unknown | Space: object requires documentation | |
201 | 224 | Application area &1/&2 will not be copied | Space: object requires documentation | |
202 | 225 | Value SID for invalid field name with SID 0 | Space: object requires documentation | |
203 | 226 | A unique role cannot be assigned to table &1 | Space: object requires documentation | |
204 | 227 | Table &1 does not exist | Space: object requires documentation | |
205 | 228 | Request type &1 not supported | Space: object requires documentation | |
206 | 229 | Table &1 is no longer in use | Space: object requires documentation | |
207 | 230 | After Import: Mapping missing for InfoObject &1 | Space: object requires documentation | |
208 | 231 | Master data for &1 successfully replicated in BW | Space: object requires documentation | |
209 | 232 | Error &1 during replication of hierarchies in BW | Space: object requires documentation | |
210 | 233 | Errors occurred while replicating hierarchies for &1 in BW | Space: object requires documentation | |
211 | 234 | Hierarchies for &1 successfully replicated in BW | Space: object requires documentation | |
212 | 235 | Error &1 during replication of master data in BW | Space: object requires documentation | |
213 | 236 | Errors occurred while replicating master data for &1 in BW | Space: object requires documentation | |
214 | 237 | Unnamed object &1 has the name &2 in the target system | Space: object requires documentation | |
215 | 238 | Object name of field name &1 differs from the target system (&2 vs. &3) | Space: object requires documentation | |
216 | 239 | Customizing entries have been added to transport request &1 | The short text describes the object sufficiently | |
217 | 240 | Data element and basis field are both missing for field name &1 | The short text describes the object sufficiently | |
218 | 241 | Field name &1: Cannot determine sequence no. of navigation attribute &2 | Space: object requires documentation | |
219 | 299 | ************** Messages for Hierarchy Maintenance *****************+ | Space: object requires documentation | |
220 | 300 | Leaf &1 belongs to type &2 | Space: object requires documentation | |
221 | 301 | Hierarchies can only be top nodes | Space: object requires documentation | |
222 | 302 | No hierarchies are allowed for characteristic &1 | Space: object requires documentation | |
223 | 303 | The independent characteristic is already defined with another value | Space: object requires documentation | |
224 | 304 | Hierarchy &1 has more than one root node | Space: object requires documentation | |
225 | 305 | Hierarchy &1 has more than one root node | Space: object requires documentation | |
226 | 306 | Delta leaf &1 cannot be deleted manually | Space: object requires documentation | |
227 | 307 | Delta leaf &1 already being used in &2 &3 | Space: object requires documentation | |
228 | 308 | Error while saving a hierarchy and/or link attrubutes | Space: object requires documentation | |
229 | 309 | Data is inconsistent in hierarchy table &2 | Space: object requires documentation | |
230 | 310 | Error while reading the metadata for database table &1 | Space: object requires documentation | |
231 | 311 | &1 is already used in hierarchies; assignment not possible | Space: object requires documentation | |
232 | 312 | &1 is a delta node; assignment not possible | Space: object requires documentation | |
233 | 313 | Internal error: The independent characteristic for &1 was not passed on | Space: object requires documentation | |
234 | 314 | The entry is invalid | Space: object requires documentation | |
235 | 315 | Only one hierarchy is allowed for characteristic &1 | Space: object requires documentation | |
236 | 316 | Invalid higher-level characteristic | Space: object requires documentation | |
237 | 317 | Invalid entry of a higher-level characteristic | Space: object requires documentation | |
238 | 318 | Node &1 occurs more than once in hierarchy &2 | Space: object requires documentation | |
239 | 319 | Entry &1 occurs more than once in hierarchy &2 | Space: object requires documentation | |
240 | 320 | No more entries are permitted under &1 | Space: object requires documentation | |
241 | 321 | &1 is not a valid hierarchy entry | Space: object requires documentation | |
242 | 322 | &2 cannot be inserted under &1 | Space: object requires documentation | |
243 | 323 | Node &1 is underneath itself in hierarchy &2 | Space: object requires documentation | |
244 | 324 | Master data for characteristic &1 is missing in target system | Space: object requires documentation | |
245 | 325 | Definition of characteristic &1 concerning hierarchies is ambiguous | Space: object requires documentation | |
246 | 326 | First enter a value | Space: object requires documentation | |
247 | 327 | Conversion of hierarchy data is necessary - see long text | Space: object requires documentation | |
248 | 328 | Error while writing hierarchies in system &3 - see long text | Space: object requires documentation | |
249 | 329 | Hierarchy &1: Characteristic &2 is not permitted; see long text | Space: object requires documentation | |
250 | 330 | Select a characteristic to be synchronized, first | The short text describes the object sufficiently | |
251 | 349 | ************** Messages for Authorization Checks **************** | Space: object requires documentation | |
252 | 350 | You have no authorization to change characteristic &1 | Space: object requires documentation | |
253 | 351 | You have no authorization to display characteristic &1 | Space: object requires documentation | |
254 | 352 | Insufficient authorization for changing the value '&2&3&4' of char. &1 | Space: object requires documentation | |
255 | 353 | Insufficient authorization for displaying the value '&2&3&4' of char. &1 | Space: object requires documentation | |
256 | 354 | You have no authorization to delete the value of characteristic &1 | Space: object requires documentation | |
257 | 355 | Authorization object '&1' does not exist in your profile | Space: object requires documentation | |
258 | 360 | Authorization object was created for characteristic &1 | Space: object requires documentation | |
259 | 361 | Error while creating authorization object for characteristic &1 | Space: object requires documentation | |
260 | 362 | Internal error in '&1' &2 &3 &4 | Space: object requires documentation | |
261 | 363 | Authorization object for characteristic &1 does not exist | Space: object requires documentation | |
262 | 389 | ************** Messages for CL_UG_FIELDINFO_LOCAL *************** | The short text describes the object sufficiently | |
263 | 390 | Object is too large for shared memory | Space: object requires documentation | |
264 | 391 | Overflow of shared memory | Space: object requires documentation | |
265 | 399 | ************** Messages for ENQUEUE/DEQUEUE Method ******************* | Space: object requires documentation | |
266 | 400 | Parameter for ENQUEUE/DEQUEUE contains an error | Space: object requires documentation | |
267 | 401 | Key fields of the UGMDENQUEUE table are incomplete | Space: object requires documentation | |
268 | 402 | Values for characteristic &2 already locked by user &1 | Space: object requires documentation | |
269 | 403 | System error while setting the lock | Space: object requires documentation | |
270 | 404 | &2 &3 already locked by user &1 | Space: object requires documentation | |
271 | 405 | DDIC structures already being generated by user &1 | Space: object requires documentation | |
272 | 409 | **** More messages for characteristic registration/management ****** | The short text describes the object sufficiently | |
273 | 410 | Attribute &2 cannot be mapped to &3 - see long text | Space: object requires documentation | |
274 | 411 | Error while replicating data - see long text | Space: object requires documentation | |
275 | 412 | Field &1 cannot be used with role &2 - role requires local field | The short text describes the object sufficiently | |
276 | 413 | Field &1 cannot be used with role &2 | Space: object requires documentation | |
277 | 414 | Data type of field &1 is incompatible with role &2 | Space: object requires documentation | |
278 | 415 | Length of field &1 is incompatible with role &2 | Space: object requires documentation | |
279 | 416 | Field &1 has incompatible hierarchy settings | Space: object requires documentation | |
280 | 417 | Field &1: Critical change in attribute mapping | Space: object requires documentation | |
281 | 418 | Field &1: Data conversion is necessary | Space: object requires documentation | |
282 | 419 | Mapping class &4 cannot be used; see long text | Space: object requires documentation | |
283 | 420 | Error while replicating data - see long text | Space: object requires documentation | |
284 | 421 | Field &1: Revoking the mapping of attribute &2 to &3 | Space: object requires documentation | |
285 | 422 | Field &2 not specified as an external characteristic in hierarchies of &1 | Space: object requires documentation | |
286 | 449 | ************** Messages for Program UGMD_DB_LOG_DISPLAY ************** | The short text describes the object sufficiently | |
287 | 450 | Processing canceled by user | The short text describes the object sufficiently | |
288 | 451 | Background processing has begun | The short text describes the object sufficiently | |
289 | 452 | Error while attempting to start background processing | The short text describes the object sufficiently | |
290 | 500 | Higher-level characteristic is ambiguous | Space: object requires documentation | |
291 | 501 | Higher-level characteristic is not homogeneous | Space: object requires documentation | |
292 | 502 | No values are yet defined for characteristic &1 | Space: object requires documentation | |
293 | 503 | Choose only one table entry | Space: object requires documentation | |
294 | 504 | Value &2 of characteristic &1 is out of workbench parameters range | Space: object requires documentation | |
295 | 505 | Node &1 has an ambiguous substructure - see long text | Space: object requires documentation | |
296 | 506 | Node &1 has an ambiguous sequence of subnodes | Space: object requires documentation | |
297 | 507 | Error while expanding ranges; see long text | Space: object requires documentation | |
298 | 510 | GUID type is invalid | The short text describes the object sufficiently | |
299 | 511 | Could not find any inconsistencies | The short text describes the object sufficiently | |
300 | 549 | ************** Messages for Program UGMD_CONV_MDF_FYV_CHANGE *********** | The short text describes the object sufficiently | |
301 | 550 | Choose at least one option for the data to be converted | The short text describes the object sufficiently | |
302 | 551 | Fiscal year variant does not exist | The short text describes the object sufficiently | |
303 | 552 | Specify a field name | The short text describes the object sufficiently | |
304 | 553 | Conversion not necessary: The fiscal year variants are the same | The short text describes the object sufficiently | |
305 | 554 | Step: &1 | The short text describes the object sufficiently | |
306 | 555 | Cannot set lock for field name &1; terminating program | Space: object requires documentation | |
307 | 556 | Exporting transport request &1 | The short text describes the object sufficiently | |
308 | 557 | Master data and customizing for &1 recorded to transport request | The short text describes the object sufficiently | |
309 | 558 | Hierarchies for &1 recorded to transport request | The short text describes the object sufficiently | |
310 | 559 | Preparing for conversion of fiscal year variant for &1 | The short text describes the object sufficiently | |
311 | 560 | Conversion not necessary for table &1 | Space: object requires documentation | |
312 | 561 | Conversion of table &1 started | The short text describes the object sufficiently | |
313 | 562 | Conversion of table &1 finished | The short text describes the object sufficiently | |
314 | 563 | &1 has time-dependent hierarchies, but the time fields are blank | Space: object requires documentation | |
315 | 564 | Converting FY variant &1 to FY variant &2 (&3 --> &4) | Space: object requires documentation | |
316 | 565 | Error in conversion of FY variant &1 to &2 occurred at year/period &3 | Space: object requires documentation | |
317 | 566 | Starting period &2 is greater than ending period &3 in table &1 | Space: object requires documentation | |
318 | 567 | Data loss in the records with the identical key &2 in table &1 | Space: object requires documentation | |
319 | 568 | Data records were lost during the conversion of table &1 | Space: object requires documentation | |
320 | 569 | Table &1 excluded by user | The short text describes the object sufficiently | |
321 | 570 | Table &1 excluded due to role settings | Space: object requires documentation | |
322 | 571 | Table &1 excluded due to inversion of role settings | Space: object requires documentation | |
323 | 600 | Application area &1/&2 is unknown | The short text describes the object sufficiently | |
324 | 601 | Hierarchy depends on the version. Version entry is mandatory | The short text describes the object sufficiently | |
325 | 602 | You must set the fiscal year and period | The short text describes the object sufficiently | |
326 | 603 | Field &1 does not exist | The short text describes the object sufficiently | |
327 | 604 | No hierarchy found | The short text describes the object sufficiently |
History
Last changed on/by | 20041006 | SAP | |
SAP Release Created in | 3.1A |