UGMD - FIN-Stammdaten: Nachrichten
The following messages are stored in message class UGMD: FIN-Stammdaten: Nachrichten.
It is part of development package UGMD0 in software component FIN-FB-MDF. This development package consists of objects that can be grouped under "FIN General: Master Data".
It is part of development package UGMD0 in software component FIN-FB-MDF. This development package consists of objects that can be grouped under "FIN General: Master Data".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Program error(s) |
| 001 | No documentation available |
| 002 | Program could not be generated |
| 003 | Value is not numeric |
| 004 | Customizing settings are inconsistent |
| 005 | Customizing settings are inconsistent |
| 006 | Error while reading definition of an InfoObject: &1&2&3&4 |
| 007 | System error while calling up a function module at destination &1 |
| 008 | Definition of Field &1 is inconsistent |
| 009 | Data element of characteristic &1 changed |
| 010 | System error during RFC communication with &1 |
| 011 | System error &1 during RFC communication with &2 |
| 012 | Communication error during RFC communication with &1 |
| 013 | Communication error &1 during RFC communication with &2 |
| 014 | InfoObject &1 does not exist in BW system &2 |
| 015 | &1 is not a valid value for &2 |
| 016 | The value &2 is invalid for characteristic &1 |
| 017 | The value &2 is invalid for characteristic &1 |
| 018 | Could not determine SID of the value of the higher-level characteristic |
| 019 | Maintenance is done in another transaction |
| 020 | &1: Fixed Values cannot be changed |
| 021 | &1&2&3&4 |
| 022 | Hierarchy &1 is not being written to BW System &2 |
| 023 | &1&2 |
| 024 | Characteristic &3: The value is too long (&1 is greater than &2) |
| 025 | A value for characteristic &2 was expected, not a value for char. &1 |
| 026 | This functionality has not yet been implemented |
| 027 | The value &2 is invalid for characteristic &1 (character &3) |
| 028 | Entry is required for for characteristic &1 |
| 029 | Maximum number of columns has been reached |
| 030 | The value &2 is invalid for characteristic &1 (character &3) |
| 031 | Messages while saving data in destination ( &1 ) |
| 032 | Hierarchy &1 not yet activated |
| 033 | Master data or hierarchies for characteristic &1 are time-dependent |
| 034 | List of possible entries not available for key figures |
| 035 | No possible entries available |
| 036 | Unknown application: &1 |
| 037 | Enter a numeric value (field name &1, &2) |
| 038 | Conversion not possible (field name &1, &2) |
| 039 | Char. &3: &1 is being used in BW &4 and cannot be deleted |
| 040 | &1: &2 is still in use and cannot be deleted |
| 041 | Conversion not possible; number of decimal places does not match currency |
| 042 | Conversion not possible; number of decimal places does not match unit |
| 043 | Error during processing; see long text |
| 044 | Definition of RFC destination &1 is incorrect; see long text |
| 045 | RFC destination &1 does not exist; see long text |
| 046 | &1: Deletion not possible; &2 is still in use |
| 047 | Key not unique for value &2 in field &1 |
| 048 | Conversion is not possible; number of decimal places is invalid |
| 049 | &1: &2 being used by &3 &4 |
| 050 | ODS object &1 cannot be used; see long text |
| 051 | ODS object &1 is not suitable for direct writing |
| 052 | &1 is used in a hierarchy and cannot be deleted |
| 053 | &1 is used in a hierarchy and cannot be deleted |
| 054 | &1 is used in a hierarchy and cannot be deleted |
| 055 | &1 is used in a hierarchy and cannot be deleted |
| 056 | &1 is used in hierarchy &2 in hierarchy version &3 starting at &4 |
| 057 | &1 is used in hierarchy &2 in hierarchy version &3 |
| 058 | &1 is used in hierarchy &2 starting at &3 |
| 059 | &1 is used in hierarchy &2 |
| 060 | &1 is used by &2 in validity version &3 starting at &4 |
| 061 | &1 is used by &2 in validity version &3 |
| 062 | &1 is used by &2 starting at &3 |
| 063 | &1 is used in the hierarchy and cannot be deleted |
| 064 | &1 is used in the hierarchy and cannot be deleted |
| 065 | &1 is used in the InfoCube and cannot be deleted |
| 066 | &1 is being used in ODS object &2 and cannot be deleted |
| 067 | &1 is used as a navigation attribute and cannot be deleted |
| 068 | &1 is used in query &2 and cannot be deleted |
| 069 | &1 is used in the hierarchy and cannot be deleted |
| 070 | Value &2 for characteristic &1 cannot be checked correctly |
| 071 | Value &2 for characteristic &1 is invalid; only capital letters allowed |
| 072 | Value &2 for characteristic &1 is invalid; only capital letters allowed |
| 073 | Error in mapping class &1 |
| 074 | Value '#' is invalid for &1 (&2) - has a special meaning in BW system |
| 075 | Field &1 is still registered and cannot be deleted |
| 076 | Error while writing values of characteristic &1/&2 (RFC destination &3) |
| 077 | Error while deleting values of characteristic &1/&2 (RFC destination &3) |
| 078 | Value &3 is invalid for &1 (&2) - ALPHA conversion |
| 079 | Value &3 is invalid for &1 (&2) - wrong date |
| 080 | Value &3 is invalid for &1 (&2) - wrong time |
| 081 | &1: A characteristic value is still in use and cannot be deleted |
| 082 | &1 is used in a hierarchy and cannot be deleted |
| 083 | &1 is used in a hierarchy and cannot be deleted |
| 084 | &1 is used in a hierarchy and cannot be deleted |
| 085 | &1 is used in a hierarchy and cannot be deleted |
| 086 | Attribute &3 is contained in both DataStore objects |
| 087 | Also allocate a time-independent DataStore object |
| 088 | &1: Allocate two different DataStore objects |
| 089 | Connection to BW system has not yet been established |
| 091 | &1 is used at hierarchy edge &2 and cannot be deleted |
| 099 | ************ Messages for Characteristic Registration/Management ****** |
| 100 | Field &1 already exists under a different domain |
| 101 | Field name &1 is already reserved for role &2 |
| 102 | Create fields with role &2 using field name &3 |
| 103 | Field &1 is used in different roles |
| 104 | Role &1 is invalid; see long text |
| 105 | A data element does not exist for field &1 |
| 106 | No entries exist |
| 107 | DDIC structures are being regenerated |
| 108 | DDIC structures are being regenerated |
| 109 | DDIC structures are being regenerated |
| 110 | Regenerating DDIC structures (change in role &1) |
| 111 | Time stamp of imported role &1 has been raised |
| 112 | Lock key for role &1 is too long |
| 113 | Field &1 has the wrong role assignment; see long text |
| 114 | In application area &4, field &1 is already linked to basis field &3 |
| 115 | Field &1 cannot be a node in hierarchies of characteristic &2 |
| 116 | Field &1 does not actively exist or cannot be used in system &2 |
| 117 | No RFC destination is assigned to application area &1 |
| 118 | The key of field &1 is too long |
| 119 | InfoObject &1 does not exist |
| 120 | Field &1 does not exist |
| 121 | Navigation attributes are not permitted for characteristic &2 |
| 122 | The background job must finish first |
| 123 | An error occurred during the generation; see the log |
| 124 | Database conversion may cause loss of data |
| 125 | The area must contain the required characteristic &1 |
| 126 | The area uses an unknown characteristic &1 |
| 127 | Definition of role &1 has changed |
| 128 | Definition of characteristic &1 has changed |
| 129 | Change or update the table entries in transaction UG01 |
| 130 | Registration made with invalid property of RFC destination &1 |
| 131 | Enter all field names for role &1 |
| 132 | Define RFC destination &1 with connection type "R/3 connection" |
| 133 | A heading cannot be entered for field &1; see long text |
| 134 | &4 records copied to table &3 |
| 135 | Definition of characteristic &1 has changed |
| 136 | Cannot synchronize characteristic &1 |
| 137 | Unable to assign data element &1 |
| 138 | Key figure &1 (type &2) has no unit field |
| 139 | Field &1: This compound differs from that of basic field &2 |
| 140 | Field &1 does not exist; see long text |
| 141 | Input value &1 is invalid |
| 142 | Converting combination characteristics from table &1 to table &2 |
| 143 | No value for SID &2 from field name &1; conversion failed |
| 144 | Conflict in keys of field name &1; conversion failed |
| 145 | Properties of validity check have been changed for field &1 |
| 146 | Error '&3' in data conversion to table &2. |
| 147 | Conversion to table &2 has finished with &3 error(s) |
| 148 | Conversion to table &2 is complete (&3 entries) |
| 149 | The value SID cannot be determined for value &2 (field name &1) |
| 150 | =========== Area UGMDCHK0: 150-199 ================================== |
| 151 | Table &, role &: Class & does not exist |
| 152 | Table &, role &: Interface & is missing in class & |
| 153 | Table &, role &: Entry on class & is missing |
| 154 | Table &, transport object &: Interface & is missing in class & |
| 155 | Table &, transport object &: Class & does not exist |
| 156 | Table &, transport object &: Entry on class & is missing |
| 157 | Table &, role &: Field & cannot be & |
| 158 | Table &, role &, field &: Data element & does not exist |
| 159 | Table &, local role &: Required field & is empty |
| 160 | Table &, local role &: Check table for & must have & in key |
| 161 | Table &, role &: Required entry field & is empty |
| 162 | Table &, role &: Field &: Data element & must have domain UG_SID |
| 163 | Table &, role &: Field &: Transport object & must be in SOBJ |
| 164 | Table &, role &: Field & must be in key of table & |
| 165 | Table &, role &: Table name & must also be entered in & |
| 166 | Table &, role &: Field &: Structure & does not exist in DDIC |
| 167 | Table &, role &: Field & occurs in both structures & |
| 168 | Table &, role &: Attribute & does not occur in any of tables & |
| 169 | Table &, role &: Field & in table & must be set |
| 170 | Table &, role &: Must be local |
| 171 | Table &, role &: Field &: Data element & must have domain GUID |
| 172 | Table &, role & is missing in table & |
| 173 | Table &, role & must have check table in table & |
| 174 | Table &, role &: Field & is missing in table & |
| 175 | Table &, role &: Key flags on field &, table & are not disjunct |
| 176 | Warning: Another role change needed; see long text |
| 177 | Time conversion for non-local role &1 cannot be switched off |
| 178 | Table &2 for role &1 requires fields FROMPERIOD and FROMYEAR |
| 179 | Role &1, structure &2: Time conversion with keys only |
| 180 | Key &2 for role &1 requires fields FROMPERIOD and FROMYEAR |
| 181 | Key &2 for role &1 requires one more field (or more) |
| 182 | Time conversion must be identical for keys &2 and &3 (role &1) |
| 183 | Time conversion must be identical for structures &1 and &2 (role &3) |
| 184 | Application &1: Original storage of master data/hierarchies must be local |
| 199 | ********** Messages for the Transport Tool ***************** |
| 200 | No information exists for table &1 |
| 201 | Characteristic &1 does not exist |
| 202 | Characteristic &1 has no sub-structure &2 |
| 203 | Generating tables for characteristic &1 |
| 204 | Table &2 does not contain the SIDs for characteristic &1 |
| 205 | Internal error &1 &2 &3 &4 |
| 206 | Cannot determine SID table for characteristic &1 |
| 207 | Field with SID &1 does not exist |
| 208 | No SID exists for the value &1 of characteristic &2 |
| 209 | &2: Unable to determine the value with SID &1 |
| 210 | Characteristic &1 does not have a text table |
| 211 | Transport object &1 may not be changed |
| 212 | Objects belonging to transport object &1 can not be maintained |
| 213 | Cannot create field &1 |
| 214 | Field &1 created |
| 215 | Could not create or determine an SID for value &1 of characteristic &2 |
| 216 | Cannot determine which field in the original system has the SID &1 |
| 217 | Field &1 does not exist |
| 218 | Complex selection conditions are not supported |
| 219 | Cannot determine which field in the original system has the SID &1 |
| 220 | Field &1 does not exist |
| 221 | Unable to create the combination characteristic |
| 222 | The sequence of the tasks in comb.characteristic &1 has changed |
| 223 | Navigation attribute &3 is unknown |
| 224 | Application area &1/&2 will not be copied |
| 225 | Value SID for invalid field name with SID 0 |
| 226 | A unique role cannot be assigned to table &1 |
| 227 | Table &1 does not exist |
| 228 | Request type &1 not supported |
| 229 | Table &1 is no longer in use |
| 230 | After Import: Mapping missing for InfoObject &1 |
| 231 | Master data for &1 successfully replicated in BW |
| 232 | Error &1 during replication of hierarchies in BW |
| 233 | Errors occurred while replicating hierarchies for &1 in BW |
| 234 | Hierarchies for &1 successfully replicated in BW |
| 235 | Error &1 during replication of master data in BW |
| 236 | Errors occurred while replicating master data for &1 in BW |
| 237 | Unnamed object &1 has the name &2 in the target system |
| 238 | Object name of field name &1 differs from the target system (&2 vs. &3) |
| 239 | Customizing entries have been added to transport request &1 |
| 240 | Data element and basis field are both missing for field name &1 |
| 241 | Field name &1: Cannot determine sequence no. of navigation attribute &2 |
| 299 | ************** Messages for Hierarchy Maintenance *****************+ |
| 300 | Leaf &1 belongs to type &2 |
| 301 | Hierarchies can only be top nodes |
| 302 | No hierarchies are allowed for characteristic &1 |
| 303 | The independent characteristic is already defined with another value |
| 304 | Hierarchy &1 has more than one root node |
| 305 | Hierarchy &1 has more than one root node |
| 306 | Leaf &1 cannot be deleted nor moved manually |
| 307 | Leaf &1 already being used in &2 &3 |
| 308 | Error while saving a hierarchy and/or link attrubutes |
| 309 | Data is inconsistent in hierarchy table &2 |
| 310 | Error while reading the metadata for database table &1 |
| 311 | &1 is already used in hierarchies; assignment not possible |
| 312 | &1 is already dynamically included in hierarchy; assignment not possible |
| 313 | Internal error: The independent characteristic for &1 was not passed on |
| 314 | The entry is invalid |
| 315 | Only one hierarchy is allowed for characteristic &1 |
| 316 | Invalid higher-level characteristic |
| 317 | Invalid entry of a higher-level characteristic |
| 318 | Node &1 occurs more than once in hierarchy &2 |
| 319 | Entry &1 occurs more than once in hierarchy &2 |
| 320 | No more entries are permitted under &1 |
| 321 | &1 is not a valid hierarchy entry |
| 322 | &2 cannot be inserted under &1 |
| 323 | Node &1 is underneath itself in hierarchy &2 |
| 324 | Master data for characteristic &1 is missing in target system |
| 325 | Definition of characteristic &1 concerning hierarchies is ambiguous |
| 326 | First enter a value |
| 327 | Conversion of hierarchy data is necessary - see long text |
| 328 | Error while writing hierarchies in system &3 - see long text |
| 329 | Hierarchy &1: Characteristic &2 is not permitted; see long text |
| 330 | Select a characteristic to be synchronized, first |
| 331 | Hierarchies need to be synchronized (see long text) |
| 332 | Unable to assign &1 (see long text) |
| 349 | ************** Messages for Authorization Checks **************** |
| 350 | You have no authorization to change characteristic &1 |
| 351 | You have no authorization to display characteristic &1 |
| 352 | Insufficient authorization for changing the value '&2&3&4' of char. &1 |
| 353 | Insufficient authorization for displaying the value '&2&3&4' of char. &1 |
| 354 | You have no authorization to delete the value of characteristic &1 |
| 355 | Authorization object '&1' does not exist in your profile |
| 356 | You are not authorized to change replication to the BW system |
| 360 | Authorization object was created for characteristic &1 |
| 361 | Error while creating authorization object for characteristic &1 |
| 362 | Internal error in '&1' &2 &3 &4 |
| 363 | Authorization object for characteristic &1 does not exist |
| 389 | ************** Messages for CL_UG_FIELDINFO_LOCAL *************** |
| 390 | Object is too large for shared memory |
| 391 | Overflow of shared memory |
| 399 | ************** Messages for ENQUEUE/DEQUEUE Method ******************* |
| 400 | Parameter for ENQUEUE/DEQUEUE contains an error |
| 401 | Key fields of the UGMDENQUEUE table are incomplete |
| 402 | Values for characteristic &2 already locked by user &1 |
| 403 | System error while setting the lock |
| 404 | &2 &3 already locked by user &1 |
| 405 | DDIC structures already being generated by user &1 |
| 409 | **** More messages for characteristic registration/management ****** |
| 410 | Attribute &2 cannot be mapped to &3 - see long text |
| 411 | Error while replicating data - see long text |
| 412 | Field &1 cannot be used with role &2 - role requires local field |
| 413 | Field &1 cannot be used with role &2 |
| 414 | Data type of field &1 is incompatible with role &2 |
| 415 | Length of field &1 is incompatible with role &2 |
| 416 | Field &1 has incompatible hierarchy settings |
| 417 | Field &1: Critical change in attribute mapping |
| 418 | Field &1: Data conversion is necessary |
| 419 | Mapping class &4 cannot be used; see long text |
| 420 | Error while replicating data - see long text |
| 421 | Field &1: Revoking the mapping of attribute &2 to &3 |
| 422 | Field &2 not specified as an external characteristic in hierarchies of &1 |
| 449 | ************** Messages for Program UGMD_DB_LOG_DISPLAY ************** |
| 450 | Processing canceled by user |
| 451 | Background processing has begun |
| 452 | Error while attempting to start background processing |
| 500 | Higher-level characteristic is ambiguous |
| 501 | Higher-level characteristic is not homogeneous |
| 502 | No values are yet defined for characteristic &1 |
| 503 | Choose only one table entry |
| 504 | Value &2 of characteristic &1 is not valid for the current parameters |
| 505 | Node &1 has an ambiguous substructure - see long text |
| 506 | Node &1 has an ambiguous sequence of subnodes |
| 507 | Error while expanding ranges; see long text |
| 510 | GUID type is invalid |
| 511 | No inconsistencies found |
| 549 | ************** Messages for Program UGMD_CONV_MDF_FYV_CHANGE *********** |
| 550 | Choose at least one option for the data to be converted |
| 551 | Fiscal year variant does not exist |
| 552 | Specify a field name |
| 553 | Conversion not necessary: The fiscal year variants are the same |
| 554 | Step: &1 |
| 555 | Cannot set lock for field name &1; terminating program |
| 556 | Exporting transport request &1 |
| 557 | Master data and customizing for &1 recorded to transport request |
| 558 | Hierarchies for &1 recorded to transport request |
| 559 | Preparing for conversion of fiscal year variant for &1 |
| 560 | Conversion not necessary for table &1 |
| 561 | Conversion of table &1 started |
| 562 | Conversion of table &1 finished |
| 563 | &1 has time-dependent hierarchies, but the time fields are blank |
| 564 | Converting FY variant &1 to FY variant &2 (&3 --> &4) |
| 565 | Error in conversion of fiscal year variant &1 to &2 for year/period &3 |
| 566 | Starting period &2 is greater than ending period &3 in table &1 |
| 567 | Data loss in the records with the identical key &2 in table &1 |
| 568 | Data records were lost during the conversion of table &1 |
| 569 | Table &1 excluded by user |
| 570 | Table &1 excluded due to role settings |
| 571 | Table &1 excluded due to inversion of role settings |
| 599 | ************** Messages for Program UGMD_HRY_EXPORT ******************** |
| 600 | Application area &1/&2 is unknown |
| 601 | Hierarchy is version-dependent; enter a version |
| 602 | You must set the fiscal year and period |
| 603 | Field &1 does not exist |
| 604 | No hierarchy found |
| 619 | ************** Messages for Report UGMD_HRY_COPY ************************ |
| 620 | Characteristic &1 is not registered |
| 621 | Characteristic &1 has no hierarchies |
| 622 | Hierarchies of characteristic &1 are not version dependent |
| 623 | Original data for characteristic &1 is in BW; copying is not purposeful |
| 624 | Hierarchy version of target is the same as hierarchy version of source |
| 625 | Hierarchy version &1 does not exist |
| 626 | Processing was terminated |
| 627 | Number of deleted data rows in table &1: &2 |
| 628 | Number of copied data rows in table &1: &2 |
| 629 | Source and target data in table &1 is already identical |
| 630 | Messages during hierarchy synchronization: |
| 631 | Hierarchy synchronization completed without errors |
| 632 | Hierarchy synchronization is not required |
| 633 | Manually transport the changes later if required |
| 634 | Processing has completed |