HRPADKZ_EHR - HRPADKZ_EHR
The following messages are stored in message class HRPADKZ_EHR: HRPADKZ_EHR.
It is part of development package PBKZ in software component PA-PA-KZ. This development package consists of objects that can be grouped under "HR Master Data: Kazakhstan".
It is part of development package PBKZ in software component PA-PA-KZ. This development package consists of objects that can be grouped under "HR Master Data: Kazakhstan".
Message Nr ▲ | Message Text |
|---|---|
| 000 | & & & & |
| 001 | Reporting Area is a required field |
| 002 | No processing logic type is assigned to class category &1 |
| 003 | Processing logic for object with ID &1 and class categ. &2 does not exist |
| 004 | No entries chosen |
| 005 | Search result exceeds the limit of &3 rows, &1 of &2 employees processed |
| 006 | Reporting Area &1 is not defined for Report Type &2 |
| 007 | Entered Class Category is not applicable for E-HR |
| 008 | XML generation BADI implementation is incorrect |
| 009 | ---------------------------------------------------------------------- |
| 010 | Authorization missing for report &1, area &2, category &3, oper. &4 |
| 011 | Authorization missing for report &1, area &2, operation &3 |
| 012 | Contract obligatory field '&1' is initial |
| 013 | Additional Agreement obligatory field '&1' is initial |
| 014 | Unable to save processing log. &1 |
| 015 | Grouping value &1 is assigned to different Reporting Areas &2 and &3 |
| 016 | Program logic for operation &1 is not implemented |
| 017 | &1 open items exists in NT |
| 018 | No items found in NT log |
| 019 | Personnel number &1 is locked by &2 |
| 020 | Failed to process operation &1 for document no. '&2' |
| 021 | Failed to create XML for document no. '&1' |
| 022 | Failed to sign document no. '&1' |
| 023 | Failed to send document no. '&1' |
| 024 | Document is successfully processed |
| 025 | Document is successfully signed |
| 026 | Document is successfully send |
| 027 | XML is successfully created |
| 028 | All documents successfully processed |
| 029 | All documents successfully signed |
| 030 | All documents successfully send |
| 031 | All XMLs successfully created |
| 032 | Operation successfully completed |
| 033 | Operation failed |
| 034 | Successfully processed: &1 |
| 035 | Failed to process: &1 |
| 036 | Document is not prepared |
| 037 | Document is not signed |
| 038 | Attachment key &1 is invalid |
| 039 | Failed to create digital signature |
| 040 | Web Service call fault for operation &1 with error code &2. &3 |
| 041 | Remote response is &1 &2 &3 &4 |
| 042 | SOAP-Header format is invalid. &1 |
| 043 | Operation '&1' is successfully processed for document no. '&2' |
| 044 | Workplace is undefined |
| 045 | Oper.processor is not defined for oper. &1 and Cl.Category &2 |
| 046 | Employer data '&1' is missing |
| 047 | Employee Position is missing |
| 048 | Contract ID is missing |
| 049 | Can't parse XML from authorities WS response. Error code is &1. |
| 050 | Employee IIN is missing |
| 051 | Employee Established Position is missing |
| 052 | Legal contract is undefined for contract type &1 |
| 053 | Document no. '&1' is not relevant for current operation |
| 054 | HTML parsing error occured. &1 &2 &3 &4 |
| 055 | XML document with Signature data is invalid (&1) |
| 056 | XML document creation not required |
| 057 | Correction cannot be submitted; use Mistake Correction operation instead |
| 058 | Mistake Correction cannot be submitted; use Prepare operation instead |
| 059 | Failed to create XML with Mistake Corrections for document no. '&1' |