HRPAY99RU_RMS_PL - Reporting management system: Processing layer message class
The following messages are stored in message class HRPAY99RU_RMS_PL: Reporting management system: Processing layer message class.
It is part of development package P99RU_RMS_PL in software component PY-RU. This development package consists of objects that can be grouped under "RMS Processing Layer".
It is part of development package P99RU_RMS_PL in software component PY-RU. This development package consists of objects that can be grouped under "RMS Processing Layer".
Message Nr ▲ | Message Text |
|---|---|
| 000 | * Reporting Session maintenance |
| 001 | Save current session |
| 002 | Data already saved |
| 003 | Logical Reports control cannot be processed in the background |
| 007 | Logical report sucessfully created |
| 008 | Reporting Area &1 does not exist |
| 009 | Report Type &1 for country grouping &2 does not exist |
| 010 | Session for report &1 in area &2 is not found |
| 011 | Reporting session for &1 &2 already created |
| 012 | Reporting session successfully saved |
| 013 | Logical report error. See previous errors in list. |
| 014 | Logical report &1 in area &2 already exists |
| 015 | Reporting session in area &1 for report &2 is closed |
| 016 | Period is not defined for report &1 in area &2 |
| 017 | Reporting session in area &1 for report &2 is already open |
| 018 | Empty period and/or year used to open reporting session |
| 019 | Session for report &1 in area &2 cannot be deleted |
| 020 | Session journal for report &1 in area &2 cannot be deleted |
| 021 | Session in area &1 for report &2 is in unexpected status |
| 022 | Calendar for report type &1 is not defined for period &2 &3 |
| 023 | [not used] |
| 024 | Logical report &1 already linked to session &2 &3 |
| 025 | Session for report &1 in area &2 cannot be updated |
| 026 | Session journal for report &1 in area &2 cannot be updated |
| 030 | Period type is not defined for report type &1 |
| 031 | More than one reporting area for &1 organization key in the &2 table |
| 032 | Reporting session for report &1 in area &2 successfully deleted |
| 034 | Reporting area is not defined for &1 organization key |
| 035 | Logical report &1 in area &2 does not exist |
| 036 | Logical report sucessfully finalized |
| 037 | Logical report finalize error. See previous errors in list. |
| 038 | Connection between &1 and organization data not defined in &2 table |
| 039 | Organization data not defined for &1 type &2 area in &3 table on &4 date |
| 040 | Reporting session for &1 type &2 area is locked by &3 |
| 041 | Reporting session for &1 type &2 area locking failure |
| 042 | To proceed, you have to save the reporting session |
| 043 | Session is consistent |
| 044 | Session &1 &2 could not be closed due to open logical reports |
| 045 | Error appending new Organization &1 |
| 046 | No data exists in &1 table for organization with key '&2' |
| 047 | Operation &1 is forbidden for report type &2 in area &3 |
| 048 | Reporting Session &1 &2 does not contain any open report |
| 049 | No business checks for &1 report type defined on &2 |
| 050 | Wrong processing class &1 for report type &2 (CntryGr &3) on date &4 |
| 051 | Wrong processing class &1 for report type &2 (CntryGr &3) |
| 052 | PERNR belongs to the reporting session based on RMS data only |
| 053 | PERNR belongs to the reporting session based on Master Data only |
| 054 | Select a logical report to execute operation |
| 055 | No payroll data can be read for employee &1 |
| 056 | Business check class &1 cannot be executed due to violated precondition |
| 057 | No documents selected for cancelling for person &1 |
| 058 | Action cancelled |
| 059 | Data is inconsistent in RMS for employee &1 on &2 |
| 060 | No employees in report type &1 and reporting area &2 in both lists |
| 061 | Logical report &1 does not belong to session &2 &3 |
| 062 | Operation &1 sucessfully performed |
| 063 | Fix business check issues and finalize logical report again |
| 064 | You must activate switch HRLOCXX_SFWS_RMS_SC_01. See long text. |
| 065 | Internal Error: &1 &2 &3 &4 |
| 066 | Either PERNR or PERSON is supplied |
| 067 | Reporting Session contains Logical Reports. Deletion is not possible. |
| 068 | Reporting session error. See previous error in list. |
| 070 | No data exists in &1 table for document type '&2' on date &3 |
| 071 | No data found for specified criteria |
| 072 | Could not update the RMS status; country grouping not recognizable |
| 073 | Could not update the RMS status due to technical errors |
| 074 | Earliest retro reporting date set to &1 |
| 075 | Employee is not part of RMS reporting area |
| 076 | Failed to lock link to processes for rep. type &1 and rep. area &2 |
| 077 | Link to processes for rep. type &1 and rep. area &2 is locked by &3 |
| 078 | Line with key &1 already exists in DB table &2 and cannot be inserted |
| 079 | Line with key &1 does not exist in DB table &2 and cannot be deleted |
| 080 | Personnel number &1 could not be locked |
| 081 | No assignment to subtype of IT3400 found for document type &1 on &2 |
| 082 | Wrong sequence of calls of methods |
| 083 | No calendar for report type &1 exists on date &2 |
| 084 | You must activate switch HRLOCXX_SFWS_RMS_SC_03. See long text. |
| 085 | There is an open process for logical report key &1. See long text. |
| 086 | There are no processes to browse |
| 087 | No report execution planners defined in country grouping &1 |
| 088 | Employee list for report type &1 in area &2 is empty on date &3 |
| 089 | Employee &1 is not planned for report execution due to errors above |
| 090 | Assign document type &1 to logical report on date &2 |
| 091 | Assign subtype &1 of RMS Status infotype (3400) to document type on &2 |
| 092 | There are no employees relevant to the processed report |
| 093 | You do not have authorization to run transaction &1 |
| 094 | Process Model ID is undefined for country grp. &1, report type &2 |
| 095 | RMS: rep.area &1, period &2, rep.type &3 |
| 096 | Failed to create process for &1 on date &2 |
| 097 | Failed to initialize process &1 with parameters |
| 098 | Planning of report execution terminated due to severe error. See above. |
| 099 | Scheduling successfully completed |
| 100 | Scheduling successfully completed only for employees without errors. |
| 101 | Scheduling failed |
| 102 | Selection program variant is undefined for report type &2 |
| 103 | Failed to create a background job for RMS Scheduler program |
| 104 | Processed employees: &1 |
| 105 | Rejected employees: &1 |
| 106 | Skipped employees: &1 |
| 107 | Scheduled employees: &1 |
| 108 | Background job &1 successfully created |
| 109 | No authorization to execute data aggregation operation |
| 110 | Operation canceled by the user |
| 111 | The requested reporting area is locked by other scheduling processes |
| 112 | Select another class as implementation for planner for RMS reports |
| 113 | Action canceled as active job &1 exists for rep. area &2, rep. type &3 |
| 114 | Assign report type &1 to at least one document type |
| 115 | Reporting session end date is automatically adjusted |
| 116 | No data for scheduling. All data has been already processed. |
| 117 | No calendar for period type &1 exists on date &2 |
| 118 | Calendar type &4 for report type &1 is not defined from &2 to &3 |
| 119 | Close reporting session for report type &1 in area &2 |
| 120 | Complete data aggregation for this report |
| 121 | Employee has "RMS Status" with subtype &1 and date &2 |
| 122 | Operation does not support employee lists with archived reports |
| 123 | Incorrect Session Period customizing for &1 &2 &3 &4 |
| 124 | Organization data not defined for &1 type on &2 date |
| 125 | Organization data not defined for &1 type |
| 126 | Job started for report type &1 in reporting area &2 on date &3 |
| 127 | New logical report on date &1, version &2 created |
| 128 | No new logical reports created |
| 129 | Open logical report on date &1, version &2 already created |
| 130 | Creating logical reports for report type &1 in reporting area &2 |
| 131 | Activate business function HCM_LOC_CI_93 |
| 132 | Report type &1 is inactive in &2 &3 period |
| 133 | Employees for report type &1 on &2 |
| 134 | Execution of report type &1 on &2 is not needed |
| 135 | Employee is locked. Infotype "RMS Status" (3400) will not be updated. |
| 136 | More than one reporting area defined for organization key &1 &2 &3 &4 |
| 140 | You must activate switch HRLOCXX_SFWS_RMS_SC_05. See long text. |
| 141 | Operation canceled; another HR process is still running |
| 150 | Open reporting session exists in area &1 for report &2 in period &3 - &4 |
| 151 | Another session exists in area &1 for report &2 in period &3 - &4 |
| 152 | Operation not allowed for Migration session |
| 160 | Scheduling failed: &1 &2 |
| 161 | RMS Status (3400) infotype not used |
| 170 | Select a line |
| 180 | The operation is not permitted for this table |
| 181 | Period must start on 1st January |
| 182 | Period year must be equal to the session year |
| 183 | End date must be equal to the session end date &1 |