Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: HRPFD02 - HR-PF: Pension Fund Switzerland
Message number: 013
Message text: Posting was already updated in DME; deletion no longer possible
It is not possible to change the non-recurring payments infotype after
the final DME posting.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
HRPFD02013
- Posting was already updated in DME; deletion no longer possible ?The SAP error message HRPFD02013, which states "Posting was already updated in DME; deletion no longer possible," typically occurs in the context of payroll processing and the Data Medium Exchange (DME) functionality. This error indicates that a payroll posting has already been processed and recorded in the DME, making it impossible to delete or modify that posting.
Cause:
- DME Processing: The error arises when an attempt is made to delete a payroll posting that has already been included in a DME file. Once a posting is processed and sent to the DME, it is considered finalized.
- Data Integrity: SAP enforces data integrity rules to prevent inconsistencies in payroll data. If a posting has been finalized, the system does not allow changes to ensure that the payroll records remain accurate.
Solution:
- Check DME Status: Verify the status of the DME file to confirm whether the posting has indeed been processed. You can do this by checking the DME logs or the relevant transaction codes (e.g., PC00_MXX_DME).
- Reversal Posting: If you need to correct a posting that has already been processed, you may need to create a reversal posting instead of trying to delete the original posting. This can be done through the appropriate payroll transaction.
- Consult Documentation: Review the SAP documentation or help files related to payroll processing and DME to understand the correct procedures for handling postings.
- Contact Support: If you are unable to resolve the issue, consider reaching out to your SAP support team or consulting with an SAP expert who can provide guidance based on your specific configuration and requirements.
Related Information:
By following these steps, you should be able to address the HRPFD02013 error effectively.
Get instant SAP help. Sign up for our Free Essentials Plan.
HRPFD02012
Caution: Posting was already prepared for DME with RPCDTPC0
What causes this issue? You are trying to delete an infotype record that has already prepared the DME posting status. Since postings are not updated ...
HRPFD02011
For filled in EMFSL, manually entered payee data is deleted
What causes this issue? If you have entered a recipient key, all other recipient data is overwritten using the data from table T521B.System Response ...
HRPFD02014
Posting was already updated in DME; change no longer possible
What causes this issue? It is not possible to change the non-recurring payments infotype after the final DME posting.System Response The system issu...
HRPFD02015
Not possible to delimit infotype 3230
What causes this issue? Since the expiration date of the non-recurring payments infotype (3230) is always the key date of the selected posting, it is...
Click on this link to search all SAP messages.