Do you have any question about this error?
Message type: E = Error
Message class: HRGB_GBSXP - Message for GBSXP
Message number: 064
Message text: SSP/SMP wage type not in table IT, check PCRs (ABZNR &1 LGART &2)
During the third processing phase of GBSXP, Statutory Absence Table
PC27J (MSA) entries are created. From these MSA entries, Results Table
PC207 (RT) & Input Table PC207 (IT) entries are created for the
notional payments.
Statutory Adoption Pay (SAP) and Statutory Paternity Pay (SPP) will
have MSA entries created directly from the National Calendar Table
NCALE (PCNAT).
However, during GBSXP Phase 1, Statutory Sick Pay (SSP) and Statutory
Maternity Pay (SMP) are processed using the original methodology. This
implies that the SSP and SMP entries in table AB derive the creation of
MSA.
The AB entries that were created by function GNAB have the first byte
of the country split 1set to 1 - which implies 80 is displayed in the
country split. These entries are then processed by PAB and should
generate "/S??" and "/M??" wage types due to the customising of table
<ZK>Absence Valuation</> (T554C). These are either created in ZL or IT.
These wage types must be resident in the IT by the time GBSXP is
called.
If the payroll has been customised in such a way that the SSP or SMP
wage types are not in the IT when GBSXP is processed, then this message
is raised.
A permanent error has occurred during the processing of the payroll for
this employee. Payroll processing for the employee has been terminated.
This error is due to an error in the customising of your payroll
subschema for "Up to Gross" (that is, your copy of subschema GT00). Two
possible errors that should be investigated are:
1) You may have mistakenly not called the function ZLIT (Importing wage
types from ZL to IT) before GBSXP, which moves the necessary SSP and
SMP wage types from the internal table ZL to the internal table IT.
2) You may have mistakenly added your own Personnel Calculation Rule
(PCR) between function PAB and GBSXP. This PCR may then be moving the
SSP and SMP wage types to the RT, when these two wage types are still
expected to be in the IT. (This could imply that you are using the
redundant PCRs G051 and G052.)
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.
HRGB_GBSXP064
- SSP/SMP wage type not in table IT, check PCRs (ABZNR &1 LGART &2) ?The SAP error message HRGB_GBSXP064 indicates that there is an issue with a wage type (LGART) not being found in the relevant table (IT) during the processing of a payroll calculation. This error typically arises in the context of payroll processing in SAP HR (Human Resources) when the system is unable to find the specified wage type in the relevant internal table.
Cause:
- Missing Wage Type: The wage type specified in the error message is not defined in the system or is not included in the relevant payroll schema.
- Incorrect PCR Configuration: The Personnel Calculation Rules (PCRs) may not be correctly configured to handle the specified wage type.
- Wage Type Not Active: The wage type may not be active for the employee group or the specific payroll area.
- Data Entry Errors: There may be data entry errors in the employee master data or payroll results that reference the wage type.
Solution:
Check Wage Type Configuration:
- Go to the transaction code SM30 or SM31 and check the configuration for the wage type in the relevant tables (e.g., T512W for wage types).
- Ensure that the wage type is defined and active.
Review PCRs:
- Use transaction code PE02 to review the PCRs that are being executed during payroll processing.
- Ensure that the PCRs are correctly configured to include the wage type in question.
Check Employee Master Data:
- Verify the employee master data using transaction code PA20 or PA30 to ensure that the wage type is correctly assigned to the employee.
- Check if the employee belongs to the correct employee group and payroll area.
Run Payroll Simulation:
- Perform a payroll simulation using transaction code PC00_MXX_CALC (replace XX with your country-specific code) to see if the error persists and to gather more information.
Consult Documentation:
- Review SAP documentation or notes related to the specific error message for additional guidance.
Contact SAP Support:
- If the issue persists after checking the above points, consider reaching out to SAP support for further assistance.
Related Information:
Transaction Codes:
Tables:
SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address specific issues related to wage types and payroll processing.
By following these steps, you should be able to identify and resolve the issue related to the HRGB_GBSXP064 error message.
Get instant SAP help. Start your 7-day free trial now.
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_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...
HRGB_GBSXP065
No offsetting possible, no OXP entries exist &1 - &2 (COVER)
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_GBSXP066
No offsetting possible, employee has no OSP scheme on &1 (IT0084)
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.