Do you have any question about this error?
Message type: E = Error
Message class: 5K - HR: Messages for Canada
Message number: 712
Message text: Retroactive accounting has not been deactivated
Retroactive accounting has not been de-activated for Infotypes 0461,
0462, 0463 and/or 0464.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
During a Production run, the Conversion program will stop processing
while retroactive accounting is active for the Tax Framework Infotypes.
Without this check, the Infotype 0003 field "'Earliest Change in Master
Data Since Last Payroll' would be set to the Begin Date of the
earliest Tax Framework Infotype created. Such a setting would trigger
a retro-active Payroll Run back this date for every employee converted.
To avoid this, the retroactive accouting switch for the Tax Framework
Infotypes should be deactivated during conversion.
Deactivate retroactive accounting for the Tax Framework Infotypes
before running the Conversion report in Production mode.
Field RUREC ("Retroactive accounting relevance for payroll")
in Table T582A must set to value blank for Infotypes 0461, 0462, 0463
and 0464. Use transaction SM30, view "V_582A_D" to set these values.
Once conversion is complete, return this value to its original setting.
(Value 'R' - "Change triggers retroactive accounting"
or 'T' - "Retro accounting is field-dependent according to T588G".)
Error message extract from SAP system. Copyright SAP SE.
The SAP error message 5K712, which states "Retroactive accounting has not been deactivated," typically occurs in the context of payroll processing or when dealing with employee master data changes that affect payroll calculations. This error indicates that there are pending retroactive accounting entries that need to be addressed before proceeding with the payroll run or other related processes.
Cause:
The error is usually caused by one of the following reasons:
- Pending Retroactive Accounting: There are changes in employee data (like salary changes, position changes, etc.) that have retroactive effects, and the system is still processing these changes.
- Configuration Issues: The system may not be configured correctly to handle retroactive accounting for the specific payroll area or employee group.
- Open Payroll Periods: There may be open payroll periods that have not been closed, which can prevent the deactivation of retroactive accounting.
Solution:
To resolve the error, you can take the following steps:
Check Retroactive Accounting Entries:
- Use transaction code PA30 (Maintain HR Master Data) to check the employee's master data for any changes that might have triggered retroactive accounting.
- Review the infotypes (especially infotype 0008 for Basic Pay) to see if there are any changes that need to be processed.
Process Retroactive Accounting:
- If there are pending retroactive accounting entries, you may need to run the payroll for the affected period to process these changes. Use transaction code PC00_MXX_CALC (where MXX is your country-specific payroll driver) to run the payroll.
Deactivate Retroactive Accounting:
- If you have confirmed that there are no pending changes or if you want to deactivate retroactive accounting, you can do this in the payroll control record. Use transaction code PC00_MXX_CRC to access the payroll control record and ensure that retroactive accounting is deactivated for the relevant payroll area.
Check Configuration:
- Ensure that the configuration settings for retroactive accounting in the payroll schema are correct. This may require assistance from your SAP HR consultant or system administrator.
Close Open Payroll Periods:
- If there are open payroll periods that are causing the issue, consider closing them if they are no longer needed.
Related Information:
By following these steps, you should be able to resolve the error message 5K712 and proceed with your payroll processing or related activities.
Get instant SAP help. Start your 7-day free trial now.
Feature | Free Access | Free Trial |
---|---|---|
Basic SAP error explanation | ![]() |
![]() |
Step-by-Step Usage Guide | ![]() |
![]() |
Interactive SAP Coach Assistance | ![]() |
![]() |
AI Troubleshooting for T-Code Errors | ![]() |
![]() |
5K711 &4 - End date extended to high date
What causes this issue? The End Date of the proposed record did not conform to ...
5K710 &4 - Record(s) committed to database
What causes this issue? The report was executed in Production mode, and the pro...
5K713 &4 - Error during User Exit conversion
What causes this issue? An error has been encountered during the conversion of ...
5K714 All existing tax infotypes will be deleted for selected employees
What causes this issue? The Conversion report has been executed in Production m...
SAP messages fall into 3 different categories: Error messages
(message type = E), Warnings (W) or Informational (I) messages.
An error message will prevent you from continuing your work - it is a hard stop and you need to fix the error before you can proceed. A warning message will stop your work, however, you can then bypass the warning by pressing the Enter key on your keyboard. That said, it is still good practice to investigate the cause of the warning message and address it. An information message will not stop your work and is truly just for informational purposes.
Click on this link to search all SAP messages.