How To Fix WEBI_CHECKS113 - Consistency of Service Definitions (Table Type SOAP Extension)

WEBI_CHECKS113 - Overview

• Message type: E = Error

• Message class: WEBI_CHECKS - WEBI Checks

• Message number: 113

• Message text: Consistency of Service Definitions (Table Type SOAP Extension)

What causes this issue?

The purpose of this check is to report inconsistencies in Table Types
SOAP Extension of Service Definitions (table VEPTABTYPSOAP).

System Response

Inconsistent entries are reported.

How to fix this error?

Use Report <DS:REPN.WEBI_REPAIR>WEBI_REPAIR</> to repair the service
definition (<DS:RE.WEBI_REPAIR>report documentation</> ).

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message WEBI_CHECKS113 - Consistency of Service Definitions (Table Type SOAP Extension) ?

  SAP Error Message:
  WEBI_CHECKS113 - Consistency of Service Definitions (Table Type SOAP Extension)
  
  Cause
  This error typically occurs in the context of SAP BusinessObjects Web Intelligence (WebI) or SAP BI platform when there is an inconsistency or mismatch in the service definitions related to SOAP extensions. Specifically, it points to a problem with the consistency of the service definitions stored in the system tables, often related to the SOAP web service extensions used by the BI platform.
  Common causes include:
  
  Corrupted or inconsistent service definition entries in the CMS (Central Management Server) database.
  Mismatched or outdated SOAP extension definitions after an upgrade or patch.
  Incomplete or failed deployment of web service extensions.
  Conflicts between different versions of service definitions.
  Manual changes or inconsistencies in the underlying database tables related to SOAP extensions.
  
  
  Solution
  To resolve the WEBI_CHECKS113 error, consider the following steps:
  
  
  Check the CMS Database for Inconsistencies:
  
  Use the Query Builder or direct SQL queries on the CMS database to inspect the