UGMD8 - Change Management
The following messages are stored in message class UGMD8: Change Management.
It is part of development package UGMD8 in software component FIN-FB-MDF. This development package consists of objects that can be grouped under "FIN General: Master Data: Change Management".
It is part of development package UGMD8 in software component FIN-FB-MDF. This development package consists of objects that can be grouped under "FIN General: Master Data: Change Management".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Internal error(s) &1 &2 &3 &4 |
| 001 | Data model synchronization is blocked by user &1 |
| 002 | Table &1: &2 records being checked for changes |
| 003 | Table &1: &2 records were changed |
| 004 | No authorization for data model synchronization |
| 005 | Cannot start Synchronization Monitor |
| 006 | Data model synchronization canceled by user |
| 007 | Data is consistent: Synchronzation not necessary |
| 008 | Synchronization Monitor cannot be started |
| 009 | No authorization for MDF Garbage Collector |
| 010 | Data model cannot be synchronized; see long text |
| 011 | There is no object to be deleted |
| 012 | Error in APPLICATION &1 AREAID &2 |
| 013 | Simulation is finished; loss of data is no longer pending |
| 014 | Copying not supported: source table &1 &2, target table &3 &4 |
| 015 | Table unknown or not supported: &1 |
| 016 | SID table was not filled: &1 |
| 020 | First convert the data of the fields named |
| 021 | Delete mapping of attributes |
| 022 | First delete the mapping of attributes; then run the data conversion |
| 049 | ------ Error Messages for MDF Garbage Collector. ------- |
| 050 | Field &1: &2 (&3) not deleted |
| 051 | &1 is refered to in &2 &3 of field &4 |
| 052 | No fields have been flagged for deletion |
| 053 | &1 still in use in &2 &3 and cannot be deleted |
| 054 | Deleting data for field &1. user &2, date &3, time &4 |
| 055 | &1 &2 has been flagged for deletion |
| 056 | Problem while deleting &2 &3 for field &1 |
| 100 | ------ Error Messages for Converting/Checking Tables ------------ |
| 101 | Changing &1 causes duplicate keys &2 |
| 102 | Deleted field &1 contains various data &2 |
| 103 | Field &1 cannot be converted without loss of data: &2 |
| 104 | Field &1 will not be used |
| 105 | Field &1 &2 cannot be converted; data types are incompatible |
| 106 | Simulation of table conversion did not produce any errors |
| 107 | New key fields are not possible |
| 108 | Renaming of fields is not possible |
| 109 | Start of simulation for table &1 |
| 110 | Table &1 has no data |
| 111 | Conversion generates inconsistent SID tables or check tables |
| 112 | Characteristic values of the characteristic changes cannot be converted |
| 113 | Start simulation for field &1 |
| 120 | Internal error: Result of simulation cannot be displayed |
| 121 | Internal error during building of GUI objects |
| 122 | Internal error: Tables cannot be interpreted |
| 123 | Conversion damages unique indexes |
| 124 | Conversion can cause inconsistent database tables! |
| 125 | Conversion may contain errors due to use of a conversion exit |
| 126 | RFC conversion exits are not supported |
| 127 | No target table specified |
| 128 | Conversion unnecessary; the existing table has no data |
| 150 | ------ Messages for Conversion of Hierarchy Tables ------- |
| 151 | Converting hierarchy data for characteristic &1; see long text |
| 152 | User canceled conversion of hierarchy data |