HRASR00_DT_PROC_DATA - Nachrichten der Datenklasse f�r Prozesse
The following messages are stored in message class HRASR00_DT_PROC_DATA: Nachrichten der Datenklasse f�r Prozesse.
It is part of development package PAOC_ASR_DESIGN_TIME in software component PA-AS. This development package consists of objects that can be grouped under "HR Administrative Services: Design Time".
It is part of development package PAOC_ASR_DESIGN_TIME in software component PA-AS. This development package consists of objects that can be grouped under "HR Administrative Services: Design Time".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Technical name for process &1 copied to description |
| 001 | Process name and process description must be specified |
| 002 | "Process Can Expire More Than Once in Parallel" must be Yes (X) or No ( ) |
| 003 | "Permission to Withdraw Process" must be Yes (X) or No ( ) |
| 004 | Scenario type for starting a process must be form (FORM) |
| 005 | Sample ID &1 for reference numbers does not exist |
| 006 | Process group &1 for authorization check does not exist |
| 007 | Form scenario &1 does not exist |
| 008 | Form scenario version &1 does not exist |
| 009 | Scenario step &1 does not exist in form scenario &2 |
| 010 | "No Start Object" must be Yes (X) or No ( ) |
| 011 | Workflow template &1 does not exist |
| 012 | Process group &1 does not exist |
| 013 | Message &1 for collision check at process start is not permitted |
| 014 | Relevance for user interface must be Yes (X) or No ( ) |
| 015 | Relevance for collision check must be Yes (X) or No ( ) |
| 016 | Initiator role &1 does not exist |
| 017 | Object group &1 does not exist |
| 018 | Validity indicator must be Yes (X) or No ( ) |
| 019 | Form scenario field &1 does not exist |
| 020 | Attachment type &1 is not assigned to form scenario &2 |
| 021 | Name &1 cannot start with 'HRASR' |
| 022 | Name &1 can only contain letters, digits, and underscore |
| 023 | Name &1 must start with a letter or a number |
| 024 | No authorization to change process. |
| 025 | Process group &1 permits only processes without start objects |
| 026 | Process group &1 permits only processes with start objects |
| 027 | Process &1 already exists; select another name |
| 028 | End date must be greater than the start date |
| 029 | Setting for "Start Object" does not agree with the process group &1 |
| 030 | Enter a message that is output if a collision occurs |
| 031 | Process &1 was saved |
| 032 | Enter a form scenario for the process start |
| 033 | Validity period [&1 - &2] is deleted |
| 034 | Validity period [&1 - &2] is split |
| 035 | Validity period [&1 - &2] is delimited |
| 036 | Process &1 does not exist |
| 037 | Enter a process |
| 038 | Enter a validity period for the new process |
| 039 | Select a validity period that you want to copy |
| 040 | Validity period no longer exists; tool was closed |
| 041 | Process &1 was deleted |
| 042 | Start scenario &1 is replaced by start scenario &2 |
| 043 | Version &2 of start scenario &1 is replaced by version &3 |
| 044 | Scenario step &2 of start scenario &1 is replaced by step &3 |
| 045 | Form scenario &1 was removed and is also the start scenario |
| 046 | Form scenario version &2 does not exist in scenario &1 |
| 047 | Scenario step &3 does not exist in form scenario &1 (version &2) |
| 048 | Form scenario &1 is already embedded with version &2 |
| 049 | Step &3 does not exist in version &2; start scenario &1 is not changed |
| 050 | Plan version not active |
| 051 | Workflow template &1 does not exist |
| 052 | Start scenario &1 cannot be deleted |
| 053 | Process &1 has not been saved yet |
| 054 | Collision group &1 is already assigned |
| 055 | Process group &1 is already assigned |
| 056 | Enter the name of the collision group |
| 057 | Collision group &1 is already defined |
| 058 | Process group must be specified |
| 059 | Initiator role must be specified |
| 060 | Object group must be specified |
| 061 | Enter a scenario step for the process start |
| 062 | Specify a form scenario |
| 063 | Form scenario &1 is already assigned |
| 064 | Form scenario &1 is already assigned as start scenario |
| 065 | Specify the name of the form scenario |
| 066 | Workflow template &1 does not contain any other form scenarios |
| 067 | Form scenario &1 version &2 is contained in the workflow template |
| 068 | Form scenario &1 is contained in WF template with different version &2 |
| 069 | Start scenario &1 is contained in WF template with different version &2 |
| 070 | Non-existent form scenario &1 version &2 is contained in the WF template |
| 071 | Workflow template &1 is not active; reconciliation is not possible |
| 072 | Enter the name of the initiator role |
| 073 | Initiator role &1 is already defined |
| 074 | No workflow templates have been defined for the process &1 |
| 075 | Error when reading workflow template &1; Reconciliation not possible |
| 076 | Select a valid entry for "Restriction" |
| 077 | Enter the name of the object group |
| 078 | Object group &1 was already defined |
| 079 | Role &1 exists but is not an initiator role |
| 080 | No object groups exist; The "restriction" is withdrawn |
| 081 | Enter the target form scenario |
| 082 | Enter an attachment type |
| 083 | Target form scenario &1 with attachment type &2 is already defined |
| 084 | Enter the source form scenario |
| 085 | Target form scenario and source form scenario are identical |
| 086 | Target form scenario &1 does not exist |
| 087 | Source form scenario &1 does not exist |
| 088 | Specify the field of the target form scenario |
| 089 | Specify the field of the source form scenario |
| 090 | Cannot delete the assignment; at least one field must be assigned |
| 091 | Enter a field of the target form scenario |
| 092 | Process &1 does not contain errors |
| 093 | Target form scenario &1 with field &2 is already defined |
| 094 | Invalid validity period [&1 - &2] in table &3 |
| 095 | Not possible to propose name as no ISR scenario has been specified |
| 096 | Process &1 is already locked by its own transaction |
| 097 | New form scenario &1 is already defined |
| 098 | Process &1 validity period &2 does not contain errors |
| 099 | Process &1 was included in transport request &2 |
| 100 | New form &1 is already defined |
| 101 | Enter the name of the processor role |
| 102 | Processor role &1 is already defined |
| 103 | Processor role &1 does not exist |
| 104 | Process &1 successfully reconciled |
| 105 | Error - could not reconcile process &1 |
| 106 | Validity period &1successfully reconciled |
| 107 | Error, could not reconcile validity period &1 |
| 110 | File &1 could not be opened |
| 111 | File &1 could not be loaded |
| 112 | File &1 could not be written |
| 113 | Process could not be read |
| 114 | File &1 does not contain any Customizing of a process |
| 117 | Process &1 is not assigned to an Initiator role |
| 118 | Form type of processes within group &1 does not match |
| 130 | Enter a start date |
| 131 | Enter the maximum frequency for carrying out the process. |
| 132 | Enter a complete time interval. |
| 133 | Inconsistent. No start date or time interval entered. |
| 134 | Process &1 does not exists in the remote system. |
| 135 | No authorization to change processes. |
| 136 | No authorization to read process &1 in remote system |
| 137 | Select the processes that you want to reconcile |
| 138 | Process &1 is not written to the order; data current |
| 139 | Error - could not reconcile process &1 |
| 140 | Process &1 successfully reconciled |
| 141 | Select the processes that you want to compare |
| 142 | Process &1 does not exist in current system |
| 143 | Process &1 is identical in remote system and in current system |
| 144 | Process &1 shows differences in remote system |
| 145 | Can only load process from XML file in change mode |
| 146 | Alternative UI switch is deactivated; process &1 cannot be displayed |
| 147 | Process &1 cannot be performed; switch HRASR_SFWS_UI_ENH_09 is inactive |
| 151 | Specify whether you want a mass start (yes (X), no ( )) |
| 152 | Define the PERNR field for form scenario &1 |
| 153 | Place the PERNR field at the first position in form scenario &1 |
| 154 | Give the PERNR field the 'For Display Only' attribute |
| 155 | DPF is not supported for processes of form type FPM |
| 222 | Proces &1 with form scenario &2 successful |
| 223 | No workflow defined; send variant configured incorrectly |
| 224 | Personnel action &1 is not of type "Hiring" |
| 225 | Data is incorrect; process was saved anyway |
| 226 | Action type hiring; process type not set as 'without start object' |
| 227 | No personnel action configured |
| 228 | Operation not permitted |