How To Fix /SCMTMS/SCH147 - Processing of deletion strategy &1 started for &2

/SCMTMS/SCH147 - Overview

• Message type: E = Error

• Message class: /SCMTMS/SCH -

• Message number: 147

• Message text: Processing of deletion strategy &1 started for &2

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.

/SCMTMS/SCH147 - Details

• The SAP error message /SCMTMS/SCH147 Processing of deletion strategy &1 started for &2 is related to the Transportation Management (TM) module in SAP. This message typically indicates that a deletion strategy is being processed for a specific object, such as a transportation request or a shipment.
  
  Cause:
  
  Deletion Strategy Initiation: The message indicates that a deletion strategy has been initiated for a specific object. This could be due to a manual action or a scheduled job that is set to clean up or delete certain data.
  Data Integrity Issues: If there are issues with the data integrity or if the object being processed is locked or in use, it may lead to this message being displayed.
  
  Configuration Issues: Incorrect configuration of the deletion strategy in the system can also lead to this message being triggered.
  
  
  Solution:
  
  Check the Status of the Object: Verify the status of the object for which the deletion strategy is being processed.