How To Fix HRTIM_ABS_REQ035 - The initiator of the request must not change during the session

HRTIM_ABS_REQ035 - Overview

• Message type: E = Error

• Message class: HRTIM_ABS_REQ - Messages for Leave Request

• Message number: 035

• Message text: The initiator of the request must not change during the session

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 HRTIM_ABS_REQ035 - The initiator of the request must not change during the session ?

  The SAP error message HRTIM_ABS_REQ035 indicates that there is an issue with the initiator of a request changing during a session. This typically occurs in the context of time management or absence management in SAP, where the system expects the same user or initiator to remain consistent throughout the session.
  
  Cause:
  
  Session Change: The error usually arises when a user attempts to change the initiator of a request (for example, when submitting an absence request) after the session has already started. This can happen if the user navigates away from the initial screen or if there are multiple users involved in the process.
  Technical Issues: Sometimes, technical issues such as session timeouts or incorrect configurations can lead to this error.
  User Role Changes: If a user’s role or authorizations change during the session, it may also trigger this error.
  
  
  Solution:
  
  Consistent User Session: Ensure that the same user is logged in and remains the initiator throughout