PYC_CONF_WB -
The following messages are stored in message class PYC_CONF_WB: .
It is part of development package PAOC_PAY_PYD_PCC_CONF_WB_FND in software component PY-XX-PYP. This development package consists of objects that can be grouped under "Configuration Workbench: Foundation".
It is part of development package PAOC_PAY_PYD_PCC_CONF_WB_FND in software component PY-XX-PYP. This development package consists of objects that can be grouped under "Configuration Workbench: Foundation".
Message Nr ▲ | Message Text |
|---|---|
| 000 | & & & & |
| 001 | A technical error occurred. Please contact technical support. |
| 002 | Rule logic does not exist. Enter an existing class as rule logic. |
| 003 | Rule logic not activated. Activate your rule logic in transaction SE24. |
| 004 | Rule logic must inherit from base class CL_PYD_CHK_FP4_BASE. |
| 005 | Enter a name for the validation rule. |
| 006 | Specify the country/region for the validation rule. |
| 007 | Alert entity �&1� is not allowed. |
| 008 | Make sure that only one alert entity is assigned to the validation rule. |
| 009 | Enter mandatory parameter �&1�. |
| 010 | Parameter &1 is not allowed. |
| 011 | Enter the value for parameter &1. |
| 012 | Make sure that only one value is entered for parameter &1. |
| 013 | Root cause analysis "&1" is not allowed. |
| 014 | Solution &1 does not exist. Enter an existing solution. |
| 015 | Make sure only one adjustment type is assigned to the validation rule. |
| 016 | Alert operation �&1" contains reason codes. Delete reason codes first. |
| 017 | Alert operation �&1� is not allowed. |
| 018 | Semantic value &1 is deprecated for alert dependency. |
| 019 | Validation rule "&1" is not allowed for the alert dependency. |
| 020 | This validation rule is used by validation rule &1 to suppress alerts. |
| 021 | Please select an alert entity. |
| 022 | Validation rule &1 already exists. |
| 023 | contains inconsistent data. |
| 024 | &1 &2 saved. |
| 025 | &1 &2 was not saved. |
| 026 | &1 &2 copied. |
| 027 | &1 &2 created. |
| 028 | Please enter a request number. |
| 029 | &1 &2 deleted. |
| 030 | Congratulations! No error is detected. |
| 031 | Validation rule is being used in policy &1. Remove it from policies first |
| 032 | Select only one row. |
| 033 | Please select one row. |
| 034 | The selected row is the topmost. |
| 035 | Please select one row to copy from it. |
| 036 | Please select a row. |
| 037 | Validation rules &1 and &2 have the same semantic value &3. |
| 038 | Reason &1 already exists. |
| 039 | Validate your changes first. |
| 040 | Object &1 is being edited by &2. |
| 041 | Action is not supported. |
| 042 | Action canceled. |
| 043 | Validation rule &1 uses other validation rules to filter its results. |
| 044 | Please enter the object ID that you want to copy to. |
| 045 | Please enter the object ID that you want to create. |
| 046 | Make sure that only one context type is assigned to validation rule. |
| 047 | Invalid country/region. Please select a value from the value help. |
| 048 | Please enter the authorization prefix for the process you want to create. |
| 049 | Enter a name for the solution. |
| 050 | Solution parameters are inconsistent. |
| 051 | Policy &1 does not exist. Enter an existing policy. |
| 052 | Validation rule &1 is inconsistent. Remove it from policy and try again. |
| 053 | Policy &1 already exists. |
| 054 | Policy &1 does not contain any folders. |
| 055 | Folder &1 does not exist. |
| 056 | Policy is being used in processes. Remove it from processes first. |
| 057 | Policy &1 contains multiple folders. These folders will be merged. |
| 058 | Validation rule "&1" is not allowed. |
| 059 | Validation rule &1 has a different country/region &1 from the policy. |
| 060 | Policy &1 can only be maintained in Policy Configuration application. |
| 061 | Enter a name for the policy. |
| 062 | Specify the country/region for the policy. |
| 063 | Assign validation rules to the policy. |
| 065 | You are not authorized to use Configuration Workbench. |
| 066 | You are not authorized to edit objects. |
| 067 | |
| 069 | Semantic value &1 is deprecated for alert dependency. |
| 070 | Semantic value & is deprecated for defining filter validation rule. |
| 071 | Country/region &1 of validation rule &2 is inconsistent with policy. |
| 072 | Country/region &1 of analytics chart &2 is inconsistent with analytics. |
| 073 | Root cause analysis &1 is marked as Hide. It will be removed upon saving. |
| 074 | Policy &1 contains multiple folders. These folders will be merged. |
| 075 | Specify the country/region. |
| 076 | Semantic value &1 is invalid. |
| 080 | Business function for Configuration Workbench is not activated. |
| 081 | Action canceled. No request is selected. |
| 100 | Stack is empty. |
| 101 | No object is selected. |
| 102 | Object not found |
| 103 | Do not make any change (SAP entry). |
| 104 | &1 &2 is not supported in Configuration Workbench. |
| 105 | &1 &2 is read-only in Configuration Workbench. |
| 111 | Chart logic does not exist. Enter an existing class as chart logic. |
| 112 | Chart logic &1 must inherit from base class CL_PYC_KPI_BASE. |
| 113 | Analytics chart &1 already exists. |
| 114 | Analytics chart &1 is being used in analytics. Remove it from analytics. |
| 115 | Enter a name for the analytics chart. |
| 116 | Specify the country/region for the analytics chart. |
| 117 | Unknown chart type due to chart logic not inheriting from base classes. |
| 118 | Invalid country/Region. Please select a value from the value help. |
| 119 | Chart logic &1 must implement interface IF_PYD_TY_RT. |
| 131 | Step template &1 already exists. |
| 132 | Enter a name for the step template. |
| 133 | Specify the country/region for the step template. |
| 134 | Step category does not match the step logic. |
| 135 | Step logic does not exist. Enter an existing class as step logic. |
| 136 | Step logic must inherit from base class CL_PYC_STT_BASE. |
| 137 | Parameter "&1" is not allowed. |
| 138 | There are validation rules requiring data from this process step. |
| 139 | The step template contains multiple context types. |
| 140 | The provided data &1 is not defined in table PYC_D_PROV. |
| 141 | Context type &1 is used by step templates. |
| 142 | Solution &1 is used by validation rules. |
| 143 | Parameter type &1 should not be a key for step results. |
| 171 | Enter a name for analytics &1. |
| 172 | Specify the country/region for the analytics. |
| 174 | Analytics is being used in processes. Remove it from processes first. |
| 175 | Select a section first. |
| 176 | Select a section or an analytics chart before you adjust its position. |
| 177 | Section &1 does not contain any analytics charts. Add analytic charts. |
| 178 | Category is not correct. Edit the object in Customizing. See long text. |
| 179 | Analytics &1 can only be edited in Customizing activity. See long text. |
| 180 | Analytics chart &1 is inconsistent. Remove it from section and try again. |
| 182 | Analytics chart "&1" has an invalid country/region. |
| 183 | Analytics &1 already exists. |
| 184 | Analytics does not contain any sections or charts. Add sections or charts |
| 185 | Enter a name for the section. |
| 186 | Select at least one row. |
| 187 | All charts under selected section will be removed from the analytics. |
| 188 | Select a section or an analytics chart that you want to remove. |
| 189 | Analytics chart &1 under section &2 is not allowed. |
| 200 | Enter a name for the process. |
| 201 | Specify the country/region for the process. |
| 202 | Specify the selection type for the process. |
| 203 | Selection type is not allowed. |
| 204 | Specify the recurrence type for the process. |
| 205 | Recurrence type is not allowed. |
| 206 | Specify the category for the process. |
| 207 | Process category cannot be changed after saving. |
| 208 | Enter an authorization prefix for the process. |
| 209 | Authorization prefix cannot be changed after saving. |
| 210 | Process does not contain any steps. Add steps to the process. |
| 211 | Step "&1" is not allowed. |
| 212 | Enter mandatory value for step &1 parameter &2. |
| 213 | Process must contain an initiate policy step. |
| 214 | Process must contain a monitoring step. |
| 215 | Monitoring step must follow the initiate policy step. |
| 216 | Program &1 does not exist. Enter an existing program. |
| 217 | Variant &1 for program &2 does not exist. Enter an existing variant. |
| 218 | Process does not contain any &1. |
| 219 | &1 &2 is not allowed. |
| 220 | Payroll areas must have the same frequency. |
| 221 | Process does not contain any policies. Add policies to the process. |
| 222 | Policy "&1" is not allowed. |
| 223 | There is a duplicate for validation rules &1. |
| 224 | Specify the admin group for alert assignment. |
| 225 | Assign analytics for the monitoring step of the process. |
| 226 | Analytics "&1" is not allowed. |
| 227 | Invalid relevance check logic. Please select from the value help. |
| 228 | Preceding monitoring process &1 has different selections. |
| 229 | Process does not contain any team dimensions. Add team dimensions. |
| 230 | Team dimension "&1" is not allowed. |
| 231 | Invalid selection logic. Please select from the value help. |
| 232 | Select a planned off-cycle productive payroll process as parent process. |
| 233 | Parent off-cycle process &1 is not allowed. |
| 234 | No off-cycle reason is assigned. Assign an off-cycle reason. |
| 235 | Off-cycle reason "&1" is not allowed. |
| 236 | There is a duplicate for step &1. |
| 237 | Process recurrence has already been generated. |
| 238 | Team has already been created for the process. |
| 239 | Team dimension &1 depends on &2, which is missing. |
| 240 | Process &1 already exists. |
| 241 | Invalid country/region. Please select a value from the value help. |
| 242 | Specify a program first. |
| 243 | Combination of authorization prefix and process ID exceeds 30 characters. |
| 244 | Maintain Dependent Parameter Type first |
| 245 | Process &1 contains multiple folders. These folders will be merged. |
| 270 | Policy type &1 already exists. |
| 271 | Enter a name for the policy type. |
| 272 | Specify the country/region for the policy type. |
| 274 | Policy type &1 is being used in policies. Remove it from policies first. |
| 300 | Enter a name for the process type. |
| 301 | Specify the country/region for the process type. |
| 302 | Specify the selection type for the process type. |
| 304 | Specify the recurrence type for the process type. |
| 306 | Specify the category for the process type. |
| 307 | Specify the period parameter for payroll area. |
| 308 | Enter an authorization prefix for the process type. |
| 310 | Process type does not contain any steps. Add steps to the process type. |
| 313 | Process type must contain an Initiate Policies step. |
| 314 | Process type must contain a monitoring step. |
| 321 | Process type does not contain any policy types. Add policy types. |
| 322 | Policy type "&1" is not allowed. |
| 329 | Process type does not contain any team dimensions. Add team dimensions. |
| 340 | Process type "&1" already exists. |
| 341 | Process type "&1" is used in processes. Remove it from processes first |
| 350 | Step template "&1" has a new parameter "&2". |
| 351 | Step template "&1" has parameter "&2" removed. |
| 400 | Enter a name for the validation rule type. |
| 401 | Specify the country/region for the validation rule type. |
| 402 | Validation rule type "&1" already exists. |
| 403 | Rule logic must inherit from base class CL_PYC_TSK_VR_BASE_1. |
| 404 | Variable ID &1 is duplicated in method &2. Update the method. |
| 405 | Alert entity �&1� is not allowed. |
| 407 | Alert entity "&1" must be maintained as a result variable in rule logic. |
| 408 | Validation rule type is being used. Remove it from val. rules first. |
| 409 | All variables below '&1' will be deleted too. |
| 410 | Unsupported dimensions have been selected. Double-click to locate them. |
| 411 | Unsupported results have been selected. Double-click to locate them. |
| 412 | No dimensions are selected. Drag dimensions from the right side. |
| 413 | Dimension group &1 is empty. Drag dimensions under this group. |
| 414 | No results are selected. Drag results from the right side. |
| 415 | &1 cannot be used as rule logic. |
| 416 | Result group &1 is empty. |
| 417 | Dimension &1 has missing dependencies. |
| 418 | Result &1 has missing dependencie. |
| 499 | Enter a name. |
| 500 | Enter a name for the KPI type. |
| 502 | KPI type &1 already exists. |
| 503 | KPI type logic must inherit from base class CL_PYC_TSK_KPI_BASE. |
| 504 | KPI type is being used in KPIs. Remove it from KPIs first. |
| 505 | &1 cannot be used as KPI logic. |
| 506 | Specify the country/region for the KPI type. |
| 600 | Enter a name for the solution. |
| 601 | Solution &1 already exists. |