Id | Title |
---|---|
UGMD553 | Conversion not necessary: The fiscal year variants are the same |
UGMD554 | Step: &1 |
UGMD555 | Cannot set lock for field name &1; terminating program |
UGMD556 | Exporting transport request &1 |
UGMD557 | Master data and customizing for &1 recorded to transport request |
UGMD558 | Hierarchies for &1 recorded to transport request |
UGMD559 | Preparing for conversion of fiscal year variant for &1 |
UGMD560 | Conversion not necessary for table &1 |
UGMD561 | Conversion of table &1 started |
UGMD562 | Conversion of table &1 finished |
UGMD563 | &1 has time-dependent hierarchies, but the time fields are blank |
UGMD564 | Converting FY variant &1 to FY variant &2 (&3 --> &4) |
UGMD565 | Error in conversion of FY variant &1 to &2 occurred at year/period &3 |
UGMD566 | Starting period &2 is greater than ending period &3 in table &1 |
UGMD567 | Data loss in the records with the identical key &2 in table &1 |
UGMD568 | Data records were lost during the conversion of table &1 |
UGMD569 | Table &1 excluded by user |
UGMD570 | Table &1 excluded due to role settings |
UGMD571 | Table &1 excluded due to inversion of role settings |
UGMD600 | Application area &1/&2 is unknown |
UGMD6000 | Program error |
UGMD601 | Hierarchy depends on the version. Version entry is mandatory |
UGMD602 | You must set the fiscal year and period |
UGMD603 | Field &1 does not exist |
UGMD604 | No hierarchy found |
UGMD7001 | &1&2 (&3) |
UGMD7002 | No authorization for DataSource '&1' in destination '&2' |
UGMD7003 | DataSource error: &1 in destination &2 cannot be used |
UGMD7004 | Setting/programming error: DataSource &1 does not exist in &2 |
UGMD7005 | No connection to target system &1 |
UGMD7006 | Initialized target system is not permitted when accessing remote systems |
UGMD7007 | Setting/programming error: DS field &1 is inconsistent |
UGMD7008 | &1 could not be initialized |
UGMD7009 | Target system &1 cannot be used |
UGMD7010 | Cannot access DataSource &1 in target system &2 |
UGMD7011 | DataSource &1 is inactive in target system &2 |
UGMD7012 | Problems generating a program for DataSource &1 in RFC dest. &2 |
UGMD7013 | RFC destination &1: &2 |
UGMD7014 | RFC destination &1: PlugIn Release >= 2002_2_470 cannot be found |
UGMD7015 | DataSource field &1 cannot be initialized |
UGMD7016 | Program error: DataSource field &1 is not known |
UGMD7017 | Program error: Input parameters have errors or do not exist |
UGMD7018 | Format conflict while reading data with DataSource &1 |
UGMD7101 | Assign DataSource field &1 once only |
UGMD7102 | Assign DataSource &1 once only |
UGMD7103 | DataSource field &1 does not exist |
UGMD7104 | Assign function &2 in DataSource field &1 only once each time |
UGMD7105 | DataSource field/DataSource &1/&2 do not exist |
UGMD7106 | Assign field &3 in DataSource field/DataSource &1/&2 once only each time |
UGMD7107 | Number DataSource field/DataSource &1/&2 consecutively (without gaps) |
UGMD7108 | DataSource field/DataSource &1/&2 requires DataSource function &3 |
UGMD8000 | Internal error(s) &1 &2 &3 &4 |
UGMD8001 | Data model synchronization is blocked by user &1 |
UGMD8002 | Table &1: &2 records being checked for changes |
UGMD8003 | Table &1: &2 records were changed |
UGMD8004 | No authorization for data model synchronization |
UGMD8005 | Background processing: Synchronization monitor cannot be executed |
UGMD8006 | Data model synchronization canceled by user |
UGMD8007 | Data is consistent: Synchronzation not necessary |
UGMD8008 | Synchronization Monitor cannot be started |
UGMD8009 | No authorization for MDF Garbage Collector |
UGMD8010 | Data model cannot be synchronized; see long text |
UGMD8011 | There is no object to be deleted |
UGMD8012 | Error in APPLICATION &1 AREAID &2 |
UGMD8013 | Simulation is finisehd; loss of data is no longer pending |
UGMD8020 | First convert the data of the fields named |
UGMD8021 | Delete mapping of attributes |
UGMD8022 | First delete the mapping of attributes; then run the data conversion |
UGMD8049 | ------ Error Messages for MDF Garbage Collector. ------- |
UGMD8050 | Field &1: &2 (&3) not deleted |
UGMD8051 | &1 is refered to in &2 &3 of field &4 |
UGMD8052 | No fields have been flagged for deletion |
UGMD8053 | &1 still in use in &2 &3 and cannot be deleted |
UGMD8054 | Deleting data for field &1. user &2, date &3, time &4 |
UGMD8055 | &1 &2 has been flagged for deletion |
UGMD8056 | Problem while deleting &2 &3 for field &1 |
UGMD8100 | ------ Error Messages for Converting/Checking Tables ------------ |
UGMD8101 | Changing &1 causes duplicate keys &2 |
UGMD8102 | Deleted field &1 contains various data &2 |
UGMD8103 | Field &1 cannot be converted without loss of data: &2 |
UGMD8104 | Field &1 will not be used |
UGMD8105 | Field &1 &2 cannot be converted; data types are incompatible |
UGMD8106 | Simulation of table conversion did not produce any errors |
UGMD8107 | New key fields are not possible |
UGMD8108 | Renaming of fields is not possible |
UGMD8109 | Start of simulation for table &1 |
UGMD8110 | Table &1 has no data |
UGMD8111 | Conversion generates inconsistent SID tables or check tables |
UGMD8112 | Characteristic values of the characteristic changes cannot be converted |
UGMD8113 | Start simulation for field &1 |
UGMD8120 | Internal error: Result of simulation cannot be displayed |
UGMD8121 | Internal error during building of GUI objects |
UGMD8122 | Internal error: Tables cannot be interpreted |
UGMD8123 | Conversion damages unique indexes |
UGMD8124 | Conversion can cause inconsistent database tables! |
UGMD8125 | Conversion may contain errors due to use of a conversion exit |
UGMD8126 | RFC conversion exits are not supported |
UGMD8127 | No target table specified |
UGMD8128 | Conversion unnecessary; the existing table has no data |
UGMD8150 | ------ Messages for Conversion of Hierarchy Tables ------- |