Do you have any question about this error?
Message type: E = Error
Message class: HRPAY99CUMU - Messages for Cumulations
Message number: 161
Message text: Personnel no. & has more PCL2(Rx) data records than entries in RGDIR
In table PCL2, cluster Rx, there are data records that do not have a
corresponding entry in RGDIR.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
This database inconsistency would lead to incorrect cumulations in the
CRT during a conversion. The payroll results for the personnel number
are not converted.
Determine the incorrect payroll result:
Using transaction PC_PAYRESULT, call up the available RGDIR entries.
Use transaction SE16 --> Table PCL2 --> RELID = (for example, RU for
the USA), SRTFD = PERNR* (for example, 00123456* ) --> F8 to display
the entries for the affected personnel number.
In the RGDIR compare the entries in the field SEQNR with the entries in
table PCL2. Here you find the SEQNR in the field SRTFD+8(5). The field
SRTFD contains the personnel number in the first 8 digits and the next
5 digits are the SEQNR. The payroll result for which you could
determine a sequence number in table PCL2, but not in the RGDIR has the
inconsistency.
Analysis of the affected payroll result:
Start report RPUDIR00 with extended log for the affected personnel
number. The log shows you whether the payroll result with the affected
sequence number is available with another sequence number. If this is
the case you can repair the inconsistency by deleting the entry for the
the inconsistent sequence number from table PCL2. Then restart report
RPUDIR00.
If you cannot repair the error in this way, you need to make further
analyses, Contact the hotline with the following data, if the data is
from a live run.
Affected personnel and sequence number
Variant for report H99U_CONVERSION_46C with the affected personnel
number
Variant for report RPUDIR00 with the affected personnel number
In table PCL2 you can see the last "SAP Standard report" with which the
payroll result was processed, but this does not give any information
about the report from which the inconsistency was created originally.
Contact your project leader, or consultant, or create an OSS message
under component XX-RC-PY if the problem is with old results of a test
scenario or if you use your own report to change the payroll results.
Error message extract from SAP system. Copyright SAP SE.
HRPAY99CUMU161
- Personnel no. & has more PCL2(Rx) data records than entries in RGDIR ?The SAP error message HRPAY99CUMU161 indicates that there is a discrepancy between the number of PCL2 (Payroll Cluster 2) data records for a specific personnel number and the entries in the RGDIR (Payroll Data Directory). This typically occurs during payroll processing when the system expects a certain number of records in the RGDIR but finds more records in the PCL2.
Cause:
- Data Inconsistency: The primary cause of this error is often due to inconsistencies in the payroll data. This can happen if there are multiple payroll runs or if the data was not properly updated or deleted in the RGDIR.
- Incorrect Configuration: Misconfiguration in the payroll schema or issues with the payroll processing logic can lead to this error.
- Manual Changes: If manual changes were made to the payroll data or if there were issues during data migration, it could lead to discrepancies.
- Incomplete Payroll Runs: If a payroll run was interrupted or not completed successfully, it might leave behind orphaned records.
Solution:
- Check RGDIR Entries: Verify the entries in the RGDIR for the personnel number in question. Ensure that the number of entries matches the expected number of PCL2 records.
- Reprocess Payroll: If the payroll run was incomplete, consider reprocessing the payroll for the affected personnel number. This may help to synchronize the data.
- Delete Orphaned Records: If there are orphaned records in the PCL2, you may need to delete them or correct the data. This should be done with caution and ideally in a test environment first.
- Use Transaction PC00_M99_CUMU: You can use the transaction code PC00_M99_CUMU to check the cumulative payroll results and see if there are any discrepancies.
- Check for Updates: Ensure that your SAP system is up to date with the latest patches and updates, as some issues may have been resolved in newer versions.
- Consult SAP Notes: Look for relevant SAP Notes that may address this specific error. SAP Notes often provide solutions or workarounds for known issues.
- Engage SAP Support: If the issue persists, consider reaching out to SAP support for assistance. They can provide more detailed analysis and guidance based on your specific system configuration.
Related Information:
Always ensure that you have proper backups and that you are following your organization's change management procedures when making changes to payroll data.
Get instant SAP help. Start your 7-day free trial now.
HRPAY99CUMU160
Personnel number & was therfore not converted
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
HRPAY99CUMU159
Personnel number & could not be locked
What causes this issue? The personnel number in question was locked by another system activity. This could have been master data maintenance, for exa...
HRPAY99CUMU162
Read the long text of message 161 message class HRPAY99CUMU
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
HRPAY99CUMU500
*** 500 - 550 messages for the views V_T56Cx and the generator
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.