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