Do you have any question about this error?
Message type: E = Error
Message class: PG - Error Messages for Master Data Programs
Message number: 138
Message text: Change too far back in payroll past (period &1 &2)
Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.
To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.
Unfortunately, there isn't any extra information in this error notice.
First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).
Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.
You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.
PG138
- Change too far back in payroll past (period &1 &2) ?The SAP error message PG138 "Change too far back in payroll past (period &1 &2)" typically occurs when there is an attempt to make changes to payroll data for a period that is considered too far in the past. This is a safeguard to prevent inconsistencies in payroll processing and reporting.
Cause:
- Time Constraint: SAP has a defined period during which payroll data can be changed. This is often set in the configuration and is meant to protect the integrity of payroll data.
- Payroll Period: The error indicates that the change you are trying to make is for a payroll period that is beyond the allowed timeframe for modifications.
- Data Consistency: Changes to historical payroll data can lead to inconsistencies in reports and financial statements, which is why SAP restricts such changes.
Solution:
- Check Configuration: Review the configuration settings in your SAP system to determine the allowed period for making changes. This can usually be found in the payroll control parameters.
- Use Correct Transaction: Ensure you are using the correct transaction for making changes. If you need to make changes to historical payroll data, you may need to use specific transactions designed for that purpose.
- Consult with Payroll Administrator: If you need to make changes that are outside the allowed period, consult with your payroll administrator or SAP support team. They may have the ability to unlock the period or provide alternative solutions.
- Use Retroactive Accounting: If applicable, consider using retroactive accounting features to make necessary adjustments without directly changing historical data.
- Documentation: Ensure that any changes made are well-documented to maintain a clear audit trail.
Related Information:
If the issue persists or if you need further assistance, it may be beneficial to reach out to SAP support or your internal SAP team for more tailored guidance.
Get instant SAP help. Start your 7-day free trial now.
PG137
Period (&1 &2) already accounted (not permitted according to T582A)
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
PG136
Control record was not created (PA03) for payroll area &1
What causes this issue? A control record has not been created for payroll area &V1&. (Entry with record type &V2& in T569V.)System Re...
PG139
Change before earliest retroactive accounting date (no recalculation)
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
PG140
No entry in table 549Q for specified date
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.