How To Fix WS695 - Check & has been disabled (explicit by BAdI)

SAP Error Message - Details

• Message type: E = Error

• Message class: WS - Supplier Billing Document

• Message number: 695

• Message text: Check & has been disabled (explicit by BAdI)

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 WS695 - Check & has been disabled (explicit by BAdI) ?

  SAP Error Message:
  
  WS695 Check & has been disabled (explicit by BAdI)
  
  Cause:
  This error message occurs when a specific validation or check in a workflow or business process has been explicitly disabled by a Business Add-In (BAdI) implementation. In other words, the standard SAP check that normally runs at a certain point has been turned off intentionally by custom code via a BAdI.
  
  BAdI (Business Add-In): A SAP enhancement technique that allows custom code to be inserted into standard SAP applications without modifying the original code.
  The message indicates that the check (validation or control) was bypassed or disabled explicitly by a BAdI implementation.
  This is typically done to allow certain business scenarios that do not comply with the standard check but are valid for the customer’s business process.
  
  
  When does it occur?
  
  During workflow processing or validation steps in SAP where standard checks are performed.
  When a BAdI implementation returns a flag or parameter that disables the check.
  Common in scenarios like document validations, workflow steps, or custom business logic validations.
  
  
  Solution:
  
  
  Identify the BAdI Implementation:
  
  Use transaction SE18 or SE19 to find the BAdI related to the check.
  Check the BAdI implementations for the relevant object or process where the error occurs.
  Look for code that explicitly disables the check, e.g., setting a flag or returning a parameter that suppresses the check.
  
  
  
  Review the Custom Code:
  
  Analyze why the check was disabled.
  Confirm if disabling the check is still valid for the current business scenario.
  If the check should not be disabled, modify or deactivate the BAdI implementation.
  
  
  
  Adjust or Remove the Disable Flag:
  
  If the check needs to be enabled, change the BAdI code to allow the check to run.
  If the check should remain disabled, ensure that the business process accounts for the implications.
  
  
  
  Testing:
  
  After changes, test the process to ensure that the check behaves as expected.
  Verify that no unintended side effects occur.
  
  
  
  
  Related Information:
  
  BAdI Documentation: Check the documentation of the specific BAdI to understand its purpose and parameters.
  Workflow Logs: Review workflow or application logs to see where the check is triggered and disabled.
  SAP Notes: Search SAP Support Portal for notes related to the specific BAdI or error message WS695.
  Customizing: Sometimes, the disabling of checks is controlled via customizing or configuration parameters linked to the BAdI.
  
  
  Summary:
  
  Cause: The standard SAP check is disabled explicitly by a BAdI implementation.
  Solution: Identify and review the BAdI implementation; adjust or remove the disabling logic if necessary.
  Check: Use SE18/SE19 to find and analyze the BAdI; test changes thoroughly.
  
  
  If you provide the specific BAdI name or the business process context, I can help you with more detailed steps or code examples.