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
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.
A permanent error has occurred during the processing of the payroll for
this employee. Payroll processing for the employee is terminated.
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.
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.
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
Get instant SAP help. Sign up for our Free Essentials Plan.
HRGB_GBSXP061 SPP payment; No SSP paid during SPP week (&1 - &2), so SPP paid on &3
What causes this issue? Current legislation states that Statutory Paternity Pay (SPP) cannot be paid to an employee that receives Statutory Sick Pay ...
HRGB_GBSXP060 SAP payment; No SSP paid during SAP week (&1 - &2), so SAP paid on &3
What causes this issue? Current legislation governing Statutory Absences states that Statutory Adoption Pay (SAP) cannot be paid to an employee who r...
HRGB_GBSXP063 Invalid entry in table T554C (MOABW &1 KLBEW &2 on &3 implies LGART &4)
What causes this issue? During the third processing phase of GBSXP, Statutory Absence Table PC27J (MSA) entries are created. From those MSA entries, ...
HRGB_GBSXP064 SSP/SMP wage type not in table IT, check PCRs (ABZNR &1 LGART &2)
What causes this issue? During the third processing phase of GBSXP, Statutory Absence Table PC27J (MSA) entries are created. From these MSA entries, ...
Click on this link to search all SAP messages.