How To Fix BOR01201 - According to check routine tracking is not allowed

BOR01201 - Overview

• Message type: E = Error

• Message class: BOR01 - Message class for ETA calculation and route simulation

• Message number: 201

• Message text: According to check routine tracking is not allowed

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 BOR01201 - According to check routine tracking is not allowed ?

  The SAP error message BOR01201, which states "According to check routine tracking is not allowed," typically occurs in the context of Business Object Repository (BOR) or when dealing with Business Workflow in SAP. This error indicates that the system has encountered a situation where tracking of a particular object or process is not permitted due to the defined check routines.
  
  Cause:
  
  Check Routine Configuration: The error is often caused by a check routine that has been configured to disallow tracking for certain business objects or processes. This could be due to business rules or specific configurations set by the organization.
  Object Status: The object or process you are trying to track may be in a status that does not allow tracking. For example, it might be completed, canceled, or in a state that is not eligible for tracking.
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to track the object, leading