SAP ABAP Message Class UGMD8 (Change Management)
Basic Data
Hierarchy
☛
FINBASIS (Software Component) Fin. Basis
⤷ FIN-FB (Application Component) Financials Basis
⤷ UGMD8 (Package) FIN General: Master Data: Change Management
⤷ FIN-FB (Application Component) Financials Basis
⤷ UGMD8 (Package) FIN General: Master Data: Change Management
Attributes
Message class | UGMD8 | |
Short Description | Change Management | |
Changed On | 20041006 | |
Last Changed At | 145633 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | Internal error(s) &1 &2 &3 &4 | Space: object requires documentation | |
2 | 001 | Data model synchronization is blocked by user &1 | Space: object requires documentation | |
3 | 002 | Table &1: &2 records being checked for changes | Space: object requires documentation | |
4 | 003 | Table &1: &2 records were changed | Space: object requires documentation | |
5 | 004 | No authorization for data model synchronization | Space: object requires documentation | |
6 | 005 | Background processing: Synchronization monitor cannot be executed | Space: object requires documentation | |
7 | 006 | Data model synchronization canceled by user | Space: object requires documentation | |
8 | 007 | Data is consistent: Synchronzation not necessary | Space: object requires documentation | |
9 | 008 | Synchronization Monitor cannot be started | Space: object requires documentation | |
10 | 009 | No authorization for MDF Garbage Collector | Space: object requires documentation | |
11 | 010 | Data model cannot be synchronized; see long text | Space: object requires documentation | |
12 | 011 | There is no object to be deleted | The short text describes the object sufficiently | |
13 | 012 | Error in APPLICATION &1 AREAID &2 | The short text describes the object sufficiently | |
14 | 013 | Simulation is finisehd; loss of data is no longer pending | The short text describes the object sufficiently | |
15 | 020 | First convert the data of the fields named | The short text describes the object sufficiently | |
16 | 021 | Delete mapping of attributes | The short text describes the object sufficiently | |
17 | 022 | First delete the mapping of attributes; then run the data conversion | The short text describes the object sufficiently | |
18 | 049 | ------ Error Messages for MDF Garbage Collector. ------- | The short text describes the object sufficiently | |
19 | 050 | Field &1: &2 (&3) not deleted | The short text describes the object sufficiently | |
20 | 051 | &1 is refered to in &2 &3 of field &4 | Space: object requires documentation | |
21 | 052 | No fields have been flagged for deletion | The short text describes the object sufficiently | |
22 | 053 | &1 still in use in &2 &3 and cannot be deleted | Space: object requires documentation | |
23 | 054 | Deleting data for field &1. user &2, date &3, time &4 | The short text describes the object sufficiently | |
24 | 055 | &1 &2 has been flagged for deletion | The short text describes the object sufficiently | |
25 | 056 | Problem while deleting &2 &3 for field &1 | The short text describes the object sufficiently | |
26 | 100 | ------ Error Messages for Converting/Checking Tables ------------ | Space: object requires documentation | |
27 | 101 | Changing &1 causes duplicate keys &2 | Space: object requires documentation | |
28 | 102 | Deleted field &1 contains various data &2 | Space: object requires documentation | |
29 | 103 | Field &1 cannot be converted without loss of data: &2 | Space: object requires documentation | |
30 | 104 | Field &1 will not be used | Space: object requires documentation | |
31 | 105 | Field &1 &2 cannot be converted; data types are incompatible | Space: object requires documentation | |
32 | 106 | Simulation of table conversion did not produce any errors | Space: object requires documentation | |
33 | 107 | New key fields are not possible | Space: object requires documentation | |
34 | 108 | Renaming of fields is not possible | Space: object requires documentation | |
35 | 109 | Start of simulation for table &1 | Space: object requires documentation | |
36 | 110 | Table &1 has no data | Space: object requires documentation | |
37 | 111 | Conversion generates inconsistent SID tables or check tables | Space: object requires documentation | |
38 | 112 | Characteristic values of the characteristic changes cannot be converted | Space: object requires documentation | |
39 | 113 | Start simulation for field &1 | Space: object requires documentation | |
40 | 120 | Internal error: Result of simulation cannot be displayed | Space: object requires documentation | |
41 | 121 | Internal error during building of GUI objects | Space: object requires documentation | |
42 | 122 | Internal error: Tables cannot be interpreted | Space: object requires documentation | |
43 | 123 | Conversion damages unique indexes | Space: object requires documentation | |
44 | 124 | Conversion can cause inconsistent database tables! | Space: object requires documentation | |
45 | 125 | Conversion may contain errors due to use of a conversion exit | Space: object requires documentation | |
46 | 126 | RFC conversion exits are not supported | Space: object requires documentation | |
47 | 127 | No target table specified | The short text describes the object sufficiently | |
48 | 128 | Conversion unnecessary; the existing table has no data | The short text describes the object sufficiently | |
49 | 150 | ------ Messages for Conversion of Hierarchy Tables ------- | The short text describes the object sufficiently | |
50 | 151 | Converting hierarchy data for characteristic &1; see long text | Space: object requires documentation | |
51 | 152 | User canceled conversion of hierarchy data | The short text describes the object sufficiently |
History
Last changed on/by | 20041006 | SAP | |
SAP Release Created in | 150 |