How To Fix WEBI_CHECKS027 - Serv. Def. &1, wrong entry in table &2, expected '&3' actual '&4'

SAP Error Message - Details

• Message type: E = Error

• Message class: WEBI_CHECKS - WEBI Checks

• Message number: 027

• Message text: Serv. Def. &1, wrong entry in table &2, expected '&3' actual '&4'

What causes this issue?

Service Definition &V1& is inconsitent.
wrong entry in table &V2&, expected '&V3&' actual '&V4'

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

System Response

How to fix this error?

Error message might be incomplete (cut off).
Run report <DS:REPN.WEBI_CHECK_REPAIR>WEBI_CHECK_REPAIR</> for &V1& to
get the complete error message and to check for further inconsitency
within the same service definition ( <DS:RE.WEBI_CHECK_REPAIR>report
documentation</> ).
Use Report <DS:REPN.WEBI_REPAIR>WEBI_REPAIR</> to repair the service
definition (<DS:RE.WEBI_REPAIR>report documentation</> ) directly.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message WEBI_CHECKS027 - Serv. Def. &1, wrong entry in table &2, expected '&3' actual '&4' ?

  The SAP error message:
  WEBI_CHECKS027 Serv. Def. &1, wrong entry in table &2, expected '&3' actual '&4'
  typically occurs in the context of SAP BusinessObjects Web Intelligence (WebI) when there is a mismatch or inconsistency in service definitions or metadata entries between the WebI server and the underlying repository or database tables.
  
  Cause
  
  Metadata or service definition mismatch: The error indicates that a service definition (identified by &1) has an incorrect or unexpected entry in a specific table (&2). The system expected a certain value (&3) but found a different one (&4).
  This can happen due to:
  
  Corruption or inconsistency in the CMS (Central Management Server) repository database.
  Version mismatch or incomplete upgrade/patch where service definitions were not properly updated.
  Manual changes or inconsistencies in the underlying database tables related to WebI services.
  Cache or synchronization issues between the WebI server and the CMS repository.
  
  
  
  
  Solution
  
  
  Check the CMS database consistency:
  
  Run CMS database consistency checks using the ccm tool or BI platform management tools.
  Look for inconsistencies or corrupt entries related to WebI services.
  
  
  
  Restart services:
  
  Restart the CMS and WebI Processing Servers to clear any cache or temporary inconsistencies.
  
  
  
  Apply patches or upgrade fixes:
  
  Ensure that your SAP BusinessObjects platform and WebI components are fully patched and upgraded to the latest supported version.
  Sometimes, SAP Notes address such inconsistencies after upgrades.
  
  
  
  Review and correct database entries:
  
  If you have access and expertise, review the entries in the indicated table (&2) in the CMS database.
  Compare the expected value (&3) with the actual value (&4) and correct if necessary.
  Warning: Direct database modifications should be done only under SAP support guidance.
  
  
  
  Clear WebI cache:
  
  Clear the WebI server cache and temporary files to ensure no stale data is causing the mismatch.
  
  
  
  Contact SAP Support:
  
  If the issue persists, open a support ticket with SAP, providing the full error message and system logs.
  SAP may provide a specific patch or script to fix the inconsistency.
  
  
  
  
  Related Information
  
  This error is related to the internal consistency of the BusinessObjects repository database and WebI service definitions.
  It is often seen after upgrades, patches, or manual interventions in the CMS database.
  SAP Notes and Knowledge Base Articles (KBAs) related to WebI service definitions and CMS database consistency may provide additional guidance.
  Always backup your CMS database before attempting any direct modifications.
  
  
  Summary:
  
  
  
  Aspect
  Details
  
  
  
  
  Cause
  Mismatch in WebI service definition entries in CMS database tables (expected vs actual).
  
  
  Solution
  Check CMS DB consistency, restart services, apply patches, clear cache, contact SAP.
  
  
  Related
  Occurs after upgrades/patches, linked to CMS DB integrity, consult SAP Notes/KBAs.
  
  
  
  
  If you provide the actual values for &1, &2, &3, and &4, I can help analyze the specific service and table involved.