How To Fix /SCWM/CORE335 - Warehouse task creation set to active by BAdI implementation

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCWM/CORE -

• Message number: 335

• Message text: Warehouse task creation set to active by BAdI implementation

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/CORE335 - Warehouse task creation set to active by BAdI implementation ?

  The SAP error message /SCWM/CORE335 typically indicates that a warehouse task creation process has been set to active due to a BAdI (Business Add-In) implementation. This error can occur in the context of SAP Extended Warehouse Management (EWM) when there is a conflict or issue with the custom logic implemented in the BAdI.
  
  Cause:
  
  BAdI Implementation: The error is often caused by a custom BAdI implementation that modifies the standard behavior of warehouse task creation. If the implementation is not correctly configured or if it conflicts with other settings, it can lead to this error.
  
  Configuration Issues: There may be issues with the configuration of the warehouse processes or the settings related to the BAdI.
  Data Issues: Inconsistent or incorrect data in the system can also trigger this error, especially if the BAdI logic relies on specific data conditions.
  
  
  Solution:
  
  Review BAdI Implementation: Check the custom BAdI implementation for any logic that may be causing the