SAP ABAP Message Class HRPFD02 (HR-PF: Pension Fund Switzerland)
Basic Data
Hierarchy
☛
SAP_HRCCH (Software Component) Sub component SAP_HRCCH of SAP_HR
⤷
PA-PF-CH (Application Component) Pension Fund Switzerland
⤷
P02F (Package) Pension fund: Switzerland
⤷
⤷
Attributes
| Message class | HRPFD02 | |
| Short Description | HR-PF: Pension Fund Switzerland | |
| Changed On | 20130531 | |
| Last Changed At | 124748 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | 000 to 099: Reserved for non-recurring payments | The short text describes the object sufficiently | ||
| 2 | Booking not found | Space: object requires documentation | ||
| 3 | Posting with value type &1 cannot be used in infotype 3230 | Space: object requires documentation | ||
| 4 | Posting does not belong to current person | Space: object requires documentation | ||
| 5 | Posting does not belong to current fund &1 | Space: object requires documentation | ||
| 6 | Posting has already been processed with DTA | Space: object requires documentation | ||
| 7 | Only one infotype record can be generated per posting | Space: object requires documentation | ||
| 8 | Calculation of withholding tax could not be lauched | Space: object requires documentation | ||
| 9 | Variant not created in feature PFDSM | Space: object requires documentation | ||
| 10 | Missing entry for payroll driver in T596F | Space: object requires documentation | ||
| 11 | Invalid recipient key &1 | Space: object requires documentation | ||
| 12 | Payee data entered manually is deleted for filled EMFSL | Space: object requires documentation | ||
| 13 | Caution: Posting has already been processed with RPCDTPC0 for DTA | Space: object requires documentation | ||
| 14 | Posting has already been posted, deletion not possible | Space: object requires documentation | ||
| 15 | Posting has already occurred in DTA, change not possible | Space: object requires documentation | ||
| 16 | Delimiting not possible for infotype 3230 | Space: object requires documentation | ||
| 17 | WHT value type &1 does not have value type property &2 | The short text describes the object sufficiently | ||
| 18 | No write access for account &1 | The short text describes the object sufficiently | ||
| 19 | Locking not possible for account &1 | The short text describes the object sufficiently | ||
| 20 | No value type entered in withholding tax selection screen | The short text describes the object sufficiently | ||
| 21 | Locking not possible for personnel number | The short text describes the object sufficiently | ||
| 22 | Recipient key already exists in T521B, update not possible | The short text describes the object sufficiently | ||
| 23 | EMZ posting not found on &1 with seq. no. &2 in account &3 | The short text describes the object sufficiently | ||
| 24 | Value in EMZ posting &1 from account &2 on &3 does not match IT3230 | The short text describes the object sufficiently | ||
| 25 | EMZ posting on &1 with seq. no. &2 in account &3 canceled | The short text describes the object sufficiently | ||
| 26 | EMZ VT from posting &1 on &2 from account &3 does not have char. 60 | The short text describes the object sufficiently | ||
| 27 | VT characteristic cannot be determined. Reason: No access to PC plan | The short text describes the object sufficiently | ||
| 28 | EMZ booking &1 on &2 from acc. &3 has a diff. value date than in IT3230 | The short text describes the object sufficiently | ||
| 29 | No entry in T5CD2 for fund &1 and value type &2 | The short text describes the object sufficiently | ||
| 30 | DTA value type from T5CD2 with fund &1 and VT &2 does not have char. 61 | The short text describes the object sufficiently | ||
| 31 | Gross amt from pstg &1 on &2 from acc. &3 and net amt in IT3230 are diff | The short text describes the object sufficiently | ||
| 32 | DTA posting in account &1 could not be generated | The short text describes the object sufficiently | ||
| 33 | DTA posting &1 to &2 written to account &3 successfully | The short text describes the object sufficiently | ||
| 34 | WTx posting &1 to &2 written to account &2 successfully | The short text describes the object sufficiently | ||
| 35 | WTx posting in account &1 could not be generated | The short text describes the object sufficiently | ||
| 36 | Status of NrP posting &1 on &2 in account &3 successfully set to '&4' | The short text describes the object sufficiently | ||
| 37 | EMZ posting status for &1 to &2 in account &3 not changed | The short text describes the object sufficiently | ||
| 38 | NrP posting &1 to &2 in account &3 simultaneous DME posting | The short text describes the object sufficiently | ||
| 39 | Status of DME posting &1 on &2 in account &3 successfully set to '&4' | The short text describes the object sufficiently | ||
| 40 | DTA posting status for &1 to &2 in account &3: Status not changed | The short text describes the object sufficiently | ||
| 41 | Unsuccessful update of infotype 3230 | The short text describes the object sufficiently | ||
| 42 | Invalid fund &1 | The short text describes the object sufficiently | ||
| 43 | &1 &2 &3 &4 | The short text describes the object sufficiently | ||
| 44 | EMZ posting &1 to &2 in account &3 has the wrong DTA status | The short text describes the object sufficiently | ||
| 45 | No DTA posting found for EMZ posting &1 on &2 in account &3 | The short text describes the object sufficiently | ||
| 46 | More than one DTA posting found for EMZ posting &1 on &2 in account &3 | The short text describes the object sufficiently | ||
| 47 | Value in DTA posting &1 from account &2 on &3 does not match IT3230 | The short text describes the object sufficiently | ||
| 48 | DTA posting on &1 with seq. no. &2 in account &3 canceled | The short text describes the object sufficiently | ||
| 49 | DTA posting &1 for &2 in account &3 has the wrong DTA status | The short text describes the object sufficiently | ||
| 50 | Recipient bank details from infotype 3230 are incomplete | The short text describes the object sufficiently | ||
| 51 | An error occurred while evaluating the DTAKT feature | The short text describes the object sufficiently | ||
| 52 | Data from T521B could not be read for recipient key &1 | The short text describes the object sufficiently | ||
| 53 | Infotype 0001 could not be evaluated | The short text describes the object sufficiently | ||
| 54 | Data could not be read for company code &1 | The short text describes the object sufficiently | ||
| 55 | Payment amount could not be converted | The short text describes the object sufficiently | ||
| 56 | An error occurred while checking house bank data with ID &1 | The short text describes the object sufficiently | ||
| 57 | An error occurred while checking payment data | The short text describes the object sufficiently | ||
| 58 | An error occurred while transferring payment data to FI | The short text describes the object sufficiently | ||
| 59 | Payment data successfully sent to FI on &1: &2 | The short text describes the object sufficiently | ||
| 60 | Table T521B successfully updated with recipient key &1 | Space: object requires documentation | ||
| 61 | Update of table T521B failed | The short text describes the object sufficiently | ||
| 62 | Update of T521C for recipient key &1 failed | Space: object requires documentation | ||
| 63 | Recipient key &1 cannot be used for infotype 3230 | Space: object requires documentation | ||
| 64 | Company code in T3CD3 does not match that of the person | The short text describes the object sufficiently | ||
| 65 | Infotype 3230 and postings were not updated | The short text describes the object sufficiently | ||
| 66 | An error occurred while checking the data transported to FI | The short text describes the object sufficiently | ||
| 67 | Update of infotype 3230 for posting &1 on &2 to account &3 successful | The short text describes the object sufficiently | ||
| 68 | Update of postings in account &1 successful | The short text describes the object sufficiently | ||
| 69 | Closing of payment run unsuccessful | The short text describes the object sufficiently | ||
| 70 | IT 3230 and posting for all persons were not updated | The short text describes the object sufficiently | ||
| 71 | Canton/State &1 for country &2 does not exist in table T005S | The short text describes the object sufficiently | ||
| 72 | No original posting could be stored for WHT Posting in account &1 | The short text describes the object sufficiently | ||
| 73 | No original posting could be stored for DME posting in account &1 | The short text describes the object sufficiently | ||
| 74 | 100 to 115: Reserved for electronic EHO message | The short text describes the object sufficiently | ||
| 75 | Invalid Customizing settings for EHO file download | The short text describes the object sufficiently | ||
| 76 | Error downloading file | The short text describes the object sufficiently | ||
| 77 | Error selecting file name | The short text describes the object sufficiently | ||
| 78 | Mandatory field does not exist: &1 (&2) | The short text describes the object sufficiently | ||
| 79 | Error accessing table T5C70. Subappl. PF01 and dossier no. &1 | The short text describes the object sufficiently | ||
| 80 | Test mode: No text file created | The short text describes the object sufficiently | ||
| 81 | Cancelled due to an error | The short text describes the object sufficiently | ||
| 82 | Error: Personal data not transferred to file | The short text describes the object sufficiently | ||
| 83 | Unable to access all of the personal data | The short text describes the object sufficiently | ||
| 84 | Communication language not DE, FR, IT: &1 | The short text describes the object sufficiently | ||
| 85 | Unable to determine form of address | The short text describes the object sufficiently | ||
| 86 | No data found for file | The short text describes the object sufficiently | ||
| 87 | File created | The short text describes the object sufficiently | ||
| 88 | Personnel number rejected due to error in insurance plan | The short text describes the object sufficiently | ||
| 89 | Fill all fields for the collective policy holder | The short text describes the object sufficiently |
History
| Last changed on/by | 20130531 | SAP | |
| SAP Release Created in |