CNV_LTHCM_G_10 - LT HCM: General Message Class
The following messages are stored in message class CNV_LTHCM_G_10: LT HCM: General Message Class.
It is part of development package CNV_LTHCM_G_10 in software component CA-LT. This development package consists of objects that can be grouped under "SAP LT HCM: General Functions".
It is part of development package CNV_LTHCM_G_10 in software component CA-LT. This development package consists of objects that can be grouped under "SAP LT HCM: General Functions".
Message Nr ▲ | Message Text |
|---|---|
| 000 | &&&& |
| 001 | Execution only allowed in test system |
| 002 | Error while setting up test data |
| 003 | Insufficient test data available; tests cannot be executed |
| 004 | Insufficient authorization; tests cannot be executed |
| 005 | Messages |
| 006 | Data saved successfully |
| 007 | Error when trying to save data |
| 008 | Data is consistent |
| 009 | Data not changed; saving not necessary |
| 010 | Wrong package ID specified (table &1) |
| 011 | System failure when calling function module '&1' with destination &2: |
| 012 | Communication failure when calling function module '&1', destination &2: |
| 013 | &1&2 |
| 014 | Log-on system (&1) differs from expected system (&2) |
| 015 | Log-on client (&1) differs from client of expected system (&2) |
| 017 | List of tables to be transferred are confirmed |
| 018 | List of tables to be transferred are not confirmed |
| 019 | Readiness for data transfer confirmed |
| 020 | Readiness for data transfer not confirmed |
| 021 | Selection criteria are confirmed |
| 022 | Selection criteria are not confirmed |
| 023 | Preparation of HCM Migration confirmed |
| 024 | Preparation of HCM Migration not confirmed |
| 032 | Conversion settings are confirmed |
| 033 | Conversion settings are not confirmed |
| 034 | Analysis results have been confirmed |
| 035 | Analysis results are not confirmed |
| 036 | Initial entry for activity &1 has not been found in table &2 |
| 037 | Error when getting status for package &1, phase &2, activity &3 |
| 038 | No package, phase or activity specified |
| 040 | Package ID &1 already exists as CWB package &2 '&3' in execution system |
| 041 | Productive usage of receiver system confirmed |
| 042 | Productive usage of receiver system not confirmed |
| 045 | Backup of software status is not done in pairs for sender and rec.system |
| 046 | Step &1 &2 &3 &4 successfully processed |
| 048 | Sender and receiver systems are identical |
| 049 | Removal of activity &1 in phase &2 successful |
| 050 | Error when trying to remove activity &1 in phase &2 |
| 051 | Storing upgrade status successful |
| 052 | Error in storing upgrade status |
| 053 | Success in hiding activity &1 in phase &2 |
| 054 | Error when hiding activity &1 in phase &2 |
| 055 | Success in making visible activity &1 in phase &2 |
| 056 | Error when making visible activity &1 in phase &2 |
| 061 | Success in upload: &1 lines modified, &2 lines added |
| 062 | No data to be uploaded |
| 063 | Data downloaded successfully |
| 064 | &1 lines uploaded successfully |
| 070 | Sender system and receiver system have the same release |
| 071 | Sender system has a lower release than the receiver system |
| 072 | The &1 system differs from the &2 system in a &3 only, that means: |
| 073 | - No upgrade needs to be executed |
| 075 | - A support package difference analysis has to be performed |
| 080 | Upgrade only possible if receiver client does not yet exist |
| 081 | Information about receiver client locked; changes are no longer possible |
| 082 | In HCM Merge scenario, receiver client must exist |
| 083 | In HCM Merge scenario, an upgrade is not possible |
| 084 | In HCM Integration scenario, receiver client must exist |
| 085 | In HCM Integration scenario, an upgrade is not possible |
| 086 | In basic HCM Carve-out scenario, an upgrade is not allowed |
| 087 | In HCM Carve-out with Upgrade scenario, new receiver client is required |
| 088 | In HCM Carve-out with Upgrade scenario, an upgrade is mandatory |
| 089 | In HCM Split with Upgrade scenario, new receiver client is required |
| 090 | Receiver information has been saved on &1 at &2: |
| 091 | Flag 'Receiver is New Client' is active |
| 092 | Flag 'Receiver is Existing Client' is active |
| 093 | Flag 'Upgrade Required' is active |
| 094 | Flag 'No Upgrade Required' is active |
| 095 | In HCM Split with Upgrade scenario, an upgrade is mandatory |
| 098 | &1 has been executed. Some errors have occurred. |
| 099 | &1 has been executed without errors. |
| 100 | Select a valid HCM migration scenario |
| 101 | HCM migration scenario has been saved on &1 at &2: |
| 102 | Selected scenario is HCM merge |
| 103 | Selected scenario is HCM split |
| 104 | Selected scenario is HCM integration |
| 105 | Selected scenario is HCM carve-out |
| 106 | No specific HCM migration scenario selected |
| 107 | HCM migration scenario cannot be changed |
| 108 | Selected scenario is HCM carve-out with upgrade |
| 109 | Selected scenario is HCM split with upgrade |
| 110 | HCM RFC destination &1 created and assigned |
| 111 | HCM RFC destination &1 already existed for package |
| 112 | Existing HCM RFC destination &1 assigned to package |
| 113 | RFC destination to HCM system could not be created |
| 114 | Sender system RFC destination could not be assigned to execution system |
| 115 | RFC destination &1 used for execution system |
| 118 | Upgrade integrated with migration |
| 119 | No upgrade performed with migration |
| 120 | No adjustments of initial settings of control tables |
| 122 | For cluster table &1, RELID &2 is excluded from transfer |
| 123 | A new client is to be created with transfer |
| 126 | Report &1 activated for post-processing, see table &2 |
| 127 | Receiver client already exists |
| 130 | Update of table PLOGI started on &1 at &2 |
| 131 | Update of PLOGI ended on &1 at &2 |
| 132 | Update of table HRITABNR started on &1 at &2 |
| 133 | Update of table HRITABNR ended on &1 at &2 |
| 134 | Update of table HRIADATANR started on &1 at &2 |
| 135 | Update of table HRIADATANR ended on &1 at &2 |
| 136 | Report RHPLOGI0 started |
| 137 | Number of records in table HRITABNR: &1 |
| 138 | Number of records to be added to table HRITABNR due to table &1: &2 |
| 139 | Number of records to be deleted from table HRITABNR: &1 |
| 140 | Number of records in table HRIADATANR: &1 |
| 141 | Number of records to be added to table HRIADATANR due to table &1: &2 |
| 142 | Number of records to be deleted from table HRIADATANR: &1 |
| 143 | Data from table &1 cannot be read |
| 144 | Table group &1 included in transfer |
| 150 | Initial settings for HCM Merge scenario |
| 151 | Initial settings for HCM Split scenario |
| 152 | Initial settings for HCM Integration scenario |
| 153 | Initial settings for HCM Carve-out scenario |
| 154 | Initial settings for HCM Carve-out with Upgrade scenario |
| 155 | Settings adjusted according to scenario; see log for details |
| 156 | Initial settings for HCM Split with Upgrade scenario |
| 200 | Loaded and calculated flags for mass transfer ID &1 have been reset |
| 212 | Table &1 has been changed on &2 at &3 |
| 213 | Table &1 has not been changed in this activity |
| 216 | User &1 not authorized to call function module &2 in system &3/&4 |
| 217 | User &1 not authorized for path determination |
| 218 | No authorization to call function module &1 in control system |
| 219 | RFC calling error in function module &1 |
| 220 | RFC destination error in function module &1 |