Do you have any question about this error?
Message type: E = Error
Message class: HRGB_GBSXP - Message for GBSXP
Message number: 053
Message text: No part day valuation class exists (T5GPBS25:MOLGA &1 KLBEW &2)
The part of GBSXP that deals with offsetting SXP against OXP requires
that all OXP valuation rules used throughout your OXP schemes are
customised in the table <ZK>Absence valuation </>(T554C). This ensures
that these rules create a notional OXP payment wage type on every day
of absence, when the employee would normally have been paid if they had
not been absent.
This implies that during the processing of the function <ZK>Process
Table AB</> (PAB) , the wage type will automatically be put into the
relevant Input Table.
There is one exception to this rule and that is Part Day Absences, in
cases where your schemes are based on calendar days. If you have the
requirement to reduce an employee's entitlements by less than a day,
then they will receive payment for less than a day. Unfortunately PAB
does not support this, so in order to allow UK customers to still
perform this step, a copy of function <ZK>Refinement of Absences
</>(XNAB) was created, namely function GPNAB.
GPNAB recognises part days as it places a "Part Day" valuation rule
against the AB entry, instead of against the normal "Whole Day"
valuation rule. In table T554C, the "Part Day" valuation rule does not
reduce any counting classes or create any wage types. It simply
executes the Personnel Calculation Rule (PCR) <ZK>Absence Valuation for
GB OSP and OMP Part Days </>(GORD). This PCR looks to the "Whole Day"
counterpart for the current "Part Day" valuation rule in the table
T5GPBS25. If it finds this entry in table T5GPBS25, the PCR GORD
re-reads table T554C deriving the customising from the "Whole Day"
counterpart and then performs the processing of PAB using that
customising, but applying the appropriate "Part Day" fraction that has
been stored on COVER for that absence.
If the "Part Day" valuation rule is not specified in table T5GPBS25,
then this error message is generated.
An error has occurred during the processing of the payroll for this
employee. Payroll processing has stopped and the employee has been
rejected.
This error is due to an error in the customising of your OXP schemes.
Three possible scenarios may be applicable:
1) You may have missed a necessary entry in table T5GPBS25.
2) You may have mistakenly specified PCR GORD against a "Whole Day"
valuation rule in table T554C.
3) You may have mistakenly activated part day processing in table
T5GPBS29.
Ensure that none of the above scenarios applies to your customising
settings. Should this error still occur, then raise an appropriate OSS
message.
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_GBSXP053
- No part day valuation class exists (T5GPBS25:MOLGA &1 KLBEW &2) ?The SAP error message HRGB_GBSXP053 indicates that there is no part-day valuation class defined for the specified country grouping (MOLGA) and valuation class (KLBEW). This error typically arises in the context of payroll processing, particularly when dealing with part-day absences or time evaluations.
Cause:
Missing Configuration: The primary cause of this error is that the necessary configuration for part-day valuation classes is missing in the system. This could be due to:
- The valuation class not being defined in the table T5GPBS25 for the specified MOLGA.
- Incorrect or incomplete configuration in the payroll schema or absence types.
Incorrect Data Entry: There may be incorrect or incomplete data entries in the employee's master data or time data that reference a part-day absence.
Solution:
To resolve this error, you can follow these steps:
Check Configuration in T5GPBS25:
- Go to transaction code SE11 (Data Dictionary) and check the table T5GPBS25.
- Verify if there is an entry for the specified MOLGA (country grouping) and KLBEW (valuation class).
- If there is no entry, you will need to create one. This typically involves defining the part-day valuation class for the relevant country grouping.
Define Part-Day Valuation Class:
- If you have the necessary authorizations, navigate to the configuration path for payroll (usually under SPRO).
- Look for the section related to "Payroll" and then "Valuation" or "Time Management".
- Define the part-day valuation class for the relevant MOLGA and ensure it is correctly linked to the absence types that require it.
Check Absence Types:
- Ensure that the absence types being used in the payroll run are correctly configured to handle part-day valuations.
- Check if the absence types are set up to use the correct valuation class.
Test the Configuration:
- After making the necessary changes, run a test payroll or time evaluation to ensure that the error no longer occurs.
Consult Documentation: If you are unsure about the configuration, refer to SAP documentation or consult with a functional consultant who specializes in SAP HR/Payroll.
Related Information:
By following these steps, you should be able to resolve the HRGB_GBSXP053 error and ensure that your payroll processing can handle part-day valuations correctly.
Get instant SAP help. Start your 7-day free trial now.
HRGB_GBSXP052
Entry in table T554C has no wage type (MOLGA &1 MOABW &2 KLBEW &3 on &4)
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
HRGB_GBSXP051
No entry in table T554C (MOLGA &1 MOABW &2 KLBEW &3 on &4)
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
HRGB_GBSXP054
No 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 tha...
HRGB_GBSXP055
OSP scheme &1 and absence subtype &2 not defined in table T5G26 on &3
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.