Message type: E = Error
Message class: HRGB_GBSXP - Message for GBSXP
Message number: 060
Message text: SAP payment; No SSP paid during SAP week (&1 - &2), so SAP paid on &3
Current legislation governing Statutory Absences states that Statutory
Adoption Pay (SAP) cannot be paid to an employee who receives Statutory
Sick Pay (SSP) in any part of the SAP week.
In your SAP system, for an employee to receive SSP and therefore <ZH>not
</> receive SAP payment, an SSP'able absence must be entered during the
SAP week for him or her.
If this SSP absence does not overlap with the SAP payment day, then the
SAP payment day will be processed by the standard rules because:
a) If the employee did receive any SSP, the SAP mark is non-payment
b) If the employee did <ZH>not</> receive any SSP, the SAP mark is
payment.
In either case, the SSP in the SAP week is handled during the creation
of the National Calendar Table NCALE (PCNAT).
If this SSP absence <ZH>does</> overlap with the SAP payment day, then
the SAP payment day will not be processed at all, because no National
Calendar Table NCALE (PCNAT) entry for SAP will exist on this day. In
this case, if the SSP'able day is allocated an SSP payment, then no SAP
can be due.
However, if the SSP'able day is not paid SSP, then SAP may be due if no
SSP has been paid during the SAP week <ZH>and</> there are some SAP
qualifying days in the SAP week.
The check that the current day in question is SSP'able is made with
reference to the last day of the SAP week, and a check is made that the
employee has not received any SSP payments in that SAP week and that
SAP qualifying days have been processed and the check has been passed.
The employee should then receive SAP.
This is simply an information message stating that even though the
employee has not been absent all week on an SAP'able absence, they are
still due to receive SAP.
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_GBSXP060 indicates that there was no Statutory Sick Pay (SSP) paid during a specific SAP week, which is identified by the dates provided in the message. As a result, SAP has processed the payment on a different date.
Cause: No SSP Recorded: The primary cause of this error is that there were no SSP payments recorded for the specified SAP week. This could happen due to various reasons, such as: The employee did not qualify for SSP during that week. There were errors in the payroll processing that prevented SSP from being calculated or recorded. The employee was on leave or not eligible for SSP during that period.
Configuration Issues: There may be issues with the configuration of the payroll system, such as incorrect settings for SSP eligibility or calculation. Data Entry Errors: Incorrect data entry related to the employee's sick leave or payroll information could lead to this error.
Solution: Review Employee Records: Check
Get instant SAP help. Sign up for our Free Essentials Plan.
HRGB_GBSXP059 No MODIF split exists for WPBP split &1 on &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
HRGB_GBSXP058 No WPBP split exists on &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
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_GBSXP062 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 Calenda...
Click on this link to search all SAP messages.