How To Fix /SCWM/TW_WT079 - BAdI called to adjust determination procedure from &1 to &2

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCWM/TW_WT -

• Message number: 079

• Message text: BAdI called to adjust determination procedure from &1 to &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.

Smart SAP Assistant

• What is the cause and solution for SAP error message /SCWM/TW_WT079 - BAdI called to adjust determination procedure from &1 to &2 ?

  The SAP error message /SCWM/TW_WT079 indicates that a BAdI (Business Add-In) was called to adjust the determination procedure for a warehouse task (WT) from one value (&1) to another value (&2). This message typically arises in the context of SAP Extended Warehouse Management (EWM) when there is a need to modify the default behavior of the system regarding how warehouse tasks are determined.
  Cause:
  
  BAdI Implementation: The error suggests that there is a custom implementation of a BAdI that is trying to change the determination procedure for warehouse tasks. This could be due to a misconfiguration or an issue in the custom code.
  Configuration Issues: There may be inconsistencies in the configuration settings related to warehouse task determination procedures.
  Data Issues: The data being processed may not meet the expected criteria for the determination procedure, leading to the BAdI being triggered.
  
  Solution:
  
  
  Check BAdI Implementation: Review the implementation of the BAdI that is being called. Ensure that the logic within the BAdI is correct and that it is handling the determination procedure as intended.
  
  You can find the BAdI implementation in transaction SE19 or SE80.
  
  
  
  Review Configuration: Check the configuration settings for warehouse task determination in the EWM settings. Ensure that the determination procedures are correctly defined and that there are no conflicts.
  
  Use transaction SPRO to navigate to the relevant configuration settings.
  
  
  
  Debugging: If the issue persists, consider debugging the process to see what values are being passed to the BAdI and how they are being processed. This can help identify any logical errors or data inconsistencies.
  
  
  Check Logs: Review the application logs (transaction SLG1) for any additional error messages or warnings that may provide more context about the issue.
  
  
  Consult Documentation: Refer to SAP documentation or notes related to the specific BAdI and warehouse task determination procedures for any known issues or additional guidance.
  
  
  Testing: After making changes, conduct thorough testing to ensure that the determination procedure works as expected without triggering the error message.
  
  
  Related Information:
  
  BAdI Documentation: Look for SAP notes or documentation related to the specific BAdI being used for warehouse task determination.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  SAP Support: If the issue cannot be resolved internally, consider reaching out to SAP Support for assistance, providing them with detailed information about the error and the context in which it occurs.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.