PYD_FND - Payroll Data Source Framework
The following messages are stored in message class PYD_FND: Payroll Data Source Framework.
It is part of development package PCPYD_FND in software component PY-XX-PYP. This development package consists of objects that can be grouped under "PYDS: Foundation".
It is part of development package PCPYD_FND in software component PY-XX-PYP. This development package consists of objects that can be grouped under "PYDS: Foundation".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Class &1 does not exist |
| 001 | No authorization for Class &1 |
| 002 | Filter property &1 not supported |
| 003 | Precondition failed: ETag &1 does not match |
| 004 | Session expired |
| 005 | Session-specific user variants cannot be directly maintained or deleted |
| 006 | No authorization for activity &1 when accessing variants of other users |
| 007 | COMMIT WORK or ROLLBACK WORK not allowed at this point in time. |
| 008 | No recursive call of run time facade allowed |
| 010 | Program cannot be initialized |
| 011 | Business Function HCM_LOC_CI_62 is not active |
| 012 | Business Function HCM_LOC_CI_68 is not active |
| 013 | Unsupported characters found |
| 014 | Action log entry manually created |
| 015 | Result Details Type requested but does not exist |
| 016 | Result Details Type requested but is not allowed for Data Source Type &1 |
| 017 | Inconsistent status; refresh your session first |
| 018 | Shadow ID &1 could not be locked |
| 019 | Business Function HCM_LOC_CI_72 is not active |
| 020 | Business Function HCM_LOC_CI_76 is not active |
| 021 | Shadow ID &1 does not exist |
| 022 | Data Source Instance could not be executed |
| 023 | Exception raised during regular scheduling of wrap-up report &1 |
| 024 | Shadow Type &1 does not exist |
| 025 | ID contains invalid characters |
| 026 | DLM Group &1 does not use parameter type |
| 027 | Business Function HCM_LOC_CI_89 is not active |
| 028 | Reversal not possible for Payroll Control Center Managed Adhoc Offcycle |
| 031 | Selection option should contain only one line |
| 032 | Selection option should follow the pattern "I EQ <value>" |
| 033 | Cannot find lines containing property value &1 |
| 034 | Class &1 contains syntax error. |
| 035 | Class &1 is not inherited from class &2. |
| 036 | Class &1 is not allowed. |
| 041 | Could not lock result object, please try later again |
| 050 | Set to Resolved is not allowed. |
| 051 | Set to Solution Applied is not allowed. |
| 052 | Set to Unresolved is not allowed. |
| 053 | Remove Solution is not allowed. |
| 100 | Transaction type &1 is not supported |
| 101 | Transaction type &1 does not exist |
| 102 | Mock level &1 is not supported |
| 103 | Technical error occured |
| 104 | Mock level &1 does not exist |
| 105 | Mock level can only be set if transaction type is 'mocked' |
| 106 | More than one transaction instance only supported for type 'mocked' |
| 107 | Mock level cannot be changed if transaction instances already exist |
| 108 | Transaction type cannot be changed if transaction instances already exist |
| 109 | Technical error '&1' occured in class &2, method &3, details: &4 |
| 110 | Session ID cannot be changed |
| 111 | No authorization to start report (authorization object P_PYD_AAUT) |
| 112 | No authorization to debug daemon (authorization object P_PYD_AAUT) |
| 150 | Folder with ID &1 and ClassID &2 does not exist |
| 151 | Instance &1 does not exist |
| 200 | Data source instances might be invalidated by change of country grouping |
| 201 | Please make corresponding changes in Details of Data Source Instance |
| 202 | Parameter type &1 is not allowed |
| 203 | Parameter type &1 already exists |
| 204 | Class &1 does not exist. Do you want to create it? |
| 205 | Duplicate data source type &1 in different folders |
| 206 | Country grouping &1 does not exist |
| 207 | Maintain dependent rollname for parameter type &1 |
| 300 | Value of instance input parameter(s) is not set correctly |
| 301 | Enter valid values for Event Type |
| 302 | The policy namespace already exists; use another namespace |
| 303 | The process namespace already exists; use another namespace |
| 304 | Namespace must meet customer namespace reservations in table PYD_D_CLS |
| 305 | The policy cannot be edited because it falls in defined policy namespace |
| 306 | Process cannot be edited because it falls in defined process namespace |
| 307 | The policy ID does not exist |
| 308 | Policy namespace is not maintained; maintain policy namespace first |
| 309 | Process namespace is not maintained; maintain process namespace first |
| 401 | Enter DLM groups of the same category |
| 402 | Data deleted successfully |
| 403 | Error calling a method of tree control; try again later, or contact admin |
| 404 | Table content cannot be displayed for object type &1 |
| 405 | Cannot open root node; if this continues to happen, contact system admin |
| 406 | No data found |
| 407 | Key value of &1 is displayed |
| 408 | Content of table &1 is displayed |
| 409 | solution applied &1 |
| 410 | executed check, alert resolved |
| 411 | executed check, alert identified |
| 412 | validated alert |
| 413 | added a note |
| 414 | assigned alert to &1 as default processor |
| 415 | set alert to &1 |
| 416 | assigned alert to &1 |
| 417 | set alert to solution applied |
| 418 | removed solution from alert |
| 419 | set alert to resolved |
| 420 | set alert to unresolved |
| 421 | claimed alert |
| 422 | executed check, alert set to resolved |
| 423 | &1&2&3&4 |
| 424 | changed processor assignment to "not assigned" |
| 425 | added an attachment |
| 426 | claimed alert and set alert to unresolved |
| 427 | assigned alert to &1 and set alert to unresolved |
| 428 | assigned alert to "not assigned" and set alert to unresolved |
| 429 | executed validation rule. Alert identified but suppressed by &1 |