How To Fix WS_TOOL870 - &1 exception &2 is not available in the service definition

SAP Error Message - Details

• Message type: E = Error

• Message class: WS_TOOL - Message Class for Web Services and Virtual Endpoints

• Message number: 870

• Message text: &1 exception &2 is not available in the service definition

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 WS_TOOL870 - &1 exception &2 is not available in the service definition ?

  Certainly! Here's a detailed explanation for the SAP error message:
  
  SAP Error Message:
  WS_TOOL870 &1 exception &2 is not available in the service definition
  
  Meaning / Cause:
  This error occurs when a web service client or tool tries to handle an exception that is not defined in the WSDL (Web Service Definition Language) service definition of the web service it is consuming.
  
  &1: The name of the tool or client component trying to process the exception.
  &2: The name of the exception that is missing in the service definition.
  
  In other words, the client expects the web service to declare a certain exception in its WSDL, but this exception is not listed there. This mismatch causes the runtime to throw this error.
  
  Common Scenarios:
  
  The web service interface was changed, but the client was not updated accordingly.
  The WSDL used by the client is outdated or incomplete.
  Custom exceptions are thrown by the service but not declared in the WSDL.
  The service definition (WSDL) does not include all exceptions that the service implementation can raise.
  
  
  Solution / How to Fix:
  
  
  Check the WSDL:
  
  Verify the WSDL of the web service to see if the exception (&2) is declared.
  You can do this by accessing the WSDL URL or using transaction SOAMANAGER or SE80 in SAP.
  
  
  
  Update the Service Definition:
  
  If the exception is missing, update the service interface to include the missing exception.
  This usually means modifying the Web Service Definition (e.g., in SE80 or via the Web Service tools) to declare the exception properly.
  
  
  
  Regenerate the Client Proxy:
  
  If the service interface was changed, regenerate the client proxy or consumer proxy to reflect the updated WSDL.
  This ensures the client knows about all exceptions declared in the service.
  
  
  
  Synchronize Service and Client:
  
  Make sure both the service and the client use the same version of the WSDL.
  If you have multiple environments (DEV, QA, PROD), ensure the WSDLs are consistent.
  
  
  
  Check for Custom Exceptions:
  
  If the service throws custom exceptions, ensure they are properly declared in the service interface and WSDL.
  In ABAP, exceptions must be declared in the interface methods and exposed in the WSDL.
  
  
  
  Transport and Deploy Changes:
  
  After changes, transport and deploy the updated service and client proxies to the relevant systems.
  
  
  
  
  Additional Information:
  
  
  Transaction / Tools:
  
  SOAMANAGER: Manage and test web services.
  SE80: ABAP Development Workbench, to check and modify service interfaces.
  SPROXY: Proxy generation and management.
  SEIWS: Web service runtime analysis.
  
  
  
  Related Notes / SAP OSS:
  
  Check SAP Notes related to web service exceptions and WSDL synchronization.
  Sometimes, SAP Notes provide patches or corrections for known issues with web service exception handling.
  
  
  
  Debugging:
  
  Enable trace for web service runtime to see detailed error messages.
  Use transaction SICF to test the web service endpoint.
  
  
  
  
  Summary:
  
  
  
  Aspect
  Description
  
  
  
  
  Cause
  Exception &2 is not declared in the WSDL service definition, causing client mismatch.
  
  
  Effect
  Runtime error WS_TOOL870 thrown when client tries to handle an unknown exception.
  
  
  Solution
  Update service interface to declare the exception, regenerate client proxy, synchronize WSDL.
  
  
  Tools
  SOAMANAGER, SE80, SPROXY, SICF
  
  
  
  
  If you provide the exact exception name (&2) and the service/tool (&1), I can help you with more specific instructions.
  
  Let me know if you need help with the steps to update the service interface or regenerate the client proxy!