How To Fix HRGB_GBSXP780 - SPLIT Day absence subtype &1 has not been customised as such (T5GPBS33)

SAP Error Message - Details

• Message type: E = Error

• Message class: HRGB_GBSXP - Message for GBSXP

• Message number: 780

• Message text: SPLIT Day absence subtype &1 has not been customised as such (T5GPBS33)

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message HRGB_GBSXP780 - SPLIT Day absence subtype &1 has not been customised as such (T5GPBS33) ?

  The SAP error message HRGB_GBSXP780 indicates that there is an issue with the configuration of absence types in the SAP system, specifically related to the absence subtype that has not been customized properly. This error typically arises in the context of the SAP Human Capital Management (HCM) module, particularly when dealing with absence management.
  Cause:
  The error message "SPLIT Day absence subtype &1 has not been customised as such (T5GPBS33)" suggests that the system is trying to process an absence subtype that has not been defined or configured in the system. This could happen due to:
  
  Missing Configuration: The absence subtype in question has not been set up in the customizing settings.
  Incorrect Configuration: The subtype may exist, but it is not configured correctly to handle split days.
  Data Entry Error: There may be an error in the data entry where an invalid or unconfigured subtype is being referenced.
  
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Check Customizing Settings:
  
  Go to the SAP Customizing Implementation Guide (IMG).
  Navigate to Personnel Management > Time Management > Absences > Define Absence Types.
  Verify that the absence subtype in question is defined and configured correctly.
  
  
  
  Configure the Absence Subtype:
  
  If the absence subtype is missing, you will need to create it.
  If it exists but is not configured for split days, you may need to adjust its settings to allow for this functionality.
  
  
  
  Review the Absence Type Configuration:
  
  Ensure that the absence type is linked to the correct absence subtype and that all necessary parameters are set correctly.
  
  
  
  Test the Configuration:
  
  After making changes, test the configuration by trying to enter an absence using the subtype in question to ensure that the error no longer occurs.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for specific details on configuring absence types and subtypes.
  
  
  
  Seek Help from SAP Support:
  
  If you are unable to resolve the issue, consider reaching out to SAP support or consulting with an SAP HCM expert for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes: You may use transaction codes like SPRO to access the IMG or PA30 to manage personnel actions related to absences.
  SAP Notes: Check for any relevant SAP Notes that might address known issues or provide additional guidance on configuring absence types.
  User Exits and BAdIs: If custom logic is involved, review any user exits or Business Add-Ins (BAdIs) that might affect absence processing.
  
  By following these steps, you should be able to identify and resolve the issue related to the absence subtype configuration in your SAP system.