How To Fix HRGB_GBSXP062 - Fill RT Error; On &1, MSA exists without a corresponding AB record

SAP Error Message - Details

• Message type: E = Error

• Message class: HRGB_GBSXP - Message for GBSXP

• Message number: 062

• Message text: Fill RT Error; On &1, MSA exists without a corresponding AB record

What causes this issue?

During the third phase of GBSXP processing, Statutory Absence Table
PC27J (MSA) entries are created from the National Calendar Table NCALE
(PCNAT)entries and then those MSA entries are transferred to the
Results Table PC207 (RT) or the Input Table PC207 (IT) as SXP notional
payments. (That is, wage types /MPY and /SPY are created in the IT,
and /PPY and /GPY are created in the RT.)
However, the cost object information and work place basic pay
information is derived from the absence that caused the NCALE entries
in the first place.
If an MSA entry exists without an AB entry, then this error message is
raised.

System Response

A permanent error has occurred during the processing of the payroll for
this employee. Payroll processing for the employee is terminated.

How to fix this error?

1) Re-process the employee through payroll after checking that the
Master Data Change Date (IT0003-RRDAT) has been updated to re-process
this date.
2) Check that your payroll subschema for "Up to Gross" (i.e. ZT00)
respects the order and structure of the SAP- delivered payroll
subschema GT00.
3) If you cannot resolve this issue, then raise an OSS message stating
that this error has occurred.

Procedure for System Administrators

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message HRGB_GBSXP062 - Fill RT Error; On &1, MSA exists without a corresponding AB record ?

  The SAP error message HRGB_GBSXP062 indicates that there is a mismatch between the Master Data (MSA) and the corresponding Absence (AB) records in the system. This typically occurs in the context of Human Resources (HR) and Payroll processing, particularly when dealing with time management and absence records.
  Cause:
  The error arises when the system finds a Master Data record (MSA) for an employee that does not have a corresponding Absence record (AB). This can happen due to several reasons:
  
  Data Entry Errors: Manual entry mistakes where an absence was not recorded properly.
  System Configuration Issues: Incorrect configuration in the time management module that leads to inconsistencies.
  Data Migration Issues: Problems during data migration from legacy systems to SAP, where some records may not have been transferred correctly.
  Timing Issues: If the MSA record is created or modified after the AB record, it may lead to this error if the system expects a corresponding absence record.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check the Records: 
  
  Use transaction codes like PA20 (Display HR Master Data) or PA30 (Maintain HR Master Data) to check the MSA and AB records for the employee in question.
  Verify if the absence records are missing or if there are discrepancies in the data.
  
  
  
  Create Missing Absence Records:
  
  If you find that the absence records are indeed missing, you can create them using transaction code PA61 (Maintain Time Data) or through the appropriate time management transactions.
  
  
  
  Correct Data Entry:
  
  If there are errors in the existing records, correct them to ensure that the MSA and AB records are aligned.
  
  
  
  Review Configuration:
  
  Check the configuration settings in the time management module to ensure that they are set up correctly. This may involve consulting with your SAP HR functional consultant.
  
  
  
  Data Migration Review:
  
  If this issue arose after a data migration, review the migration process to ensure that all necessary records were transferred correctly.
  
  
  
  Consult SAP Notes:
  
  Look for relevant SAP Notes or Knowledge Base Articles (KBAs) that may address this specific error. SAP frequently updates its documentation and may have specific fixes or recommendations.
  
  
  
  Testing:
  
  After making corrections, perform testing to ensure that the error does not reoccur and that the system processes the records correctly.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as PA20, PA30, PA61, and others related to HR data management.
  SAP HR Module: Understanding the structure of the SAP HR module, particularly how Master Data and Absence records interact, can help in troubleshooting similar issues in the future.
  Documentation: Refer to SAP Help documentation for detailed explanations of the HR processes and data structures.
  
  If the issue persists after following these steps, it may be beneficial to engage with your SAP support team or consult with an SAP HR expert for further assistance.