Message type: E = Error
Message class: HRGB_GBSXP - Message for GBSXP
Message number: 071
Message text: Fill IT Error; On &1, MSA exists with no corresponding AB record
During the fourth phase of GBSXP processing, Input Table PC207 (IT)
entries are created for SXP notional payments from Statutory Absence
Table PC27J (MSA) entries.
However, the cost object information and work place basic pay
information is derived from the absence that caused the National
Calendar Table NCALE (PCNAT) entries originally.
If an MSA entry exists without a table AB entry, then this error is
raised.
A permanent error has occurred during the processing of the payroll for
this employee. Payroll processing for the employee has been 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" (that is, a
copy of GT00) 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_GBSXP071 indicates that there is a mismatch between the Master Data (MSA) and the corresponding Absence (AB) record in the Human Resources module. This typically occurs in the context of time management or payroll processing when the system expects a corresponding absence record for a given master data entry, but it cannot find one.
Cause: Missing Absence Record: The most common cause is that there is an absence record (e.g., sick leave, vacation) that has been created in the system, but the corresponding master data record (e.g., employee's MSA) does not have a matching entry. Data Entry Errors: There may have been an error during data entry, leading to inconsistencies between the MSA and AB records. Incorrect Configuration: The configuration settings in the SAP system may not be aligned properly, leading to discrepancies in how records are linked. Data Migration Issues: If data was migrated from another system, there may have
Get instant SAP help. Sign up for our Free Essentials Plan.
HRGB_GBSXP070 Wage type &1 is defined in more than one OXP Wage Type Group
What causes this issue? The wage type groups OAPP, OMPP, OPPP and OSPP are absence specific. No payment OXP wage type should be in more than one of t...
HRGB_GBSXP069 Wage type &1 must be in table &2 to perform offsetting on &3
What causes this issue? During the fourth processing phase of GBSXP, Statutory Absence Table PC27J (MSA) entries have the OXP and Full Pay informatio...
HRGB_GBSXP072 Incorrect valuation basis in table T512W (MOLGA &1 LGART &2 on &3)
What causes this issue? The customising of the OxP payment solution is based on the principle of using valuation bases. For example, a wage type that...
HRGB_GBSXP073 OXP wage type not in table IT; Check PCRs (ABZNR &1 LGART &2).
What causes this issue? During the fourth processing phase of GBSXP, OXP entries are derived from table AB via a check that establishes whether the w...
Click on this link to search all SAP messages.