How To Fix ESH_OM_PC004 - Model &2 lacks authorization at the root node

ESH_OM_PC004 - Overview

• Message type: E = Error

• Message class: ESH_OM_PC - Plausibility Check

• Message number: 004

• Message text: Model &2 lacks authorization at the root node

What causes this issue?

Application model &v2& of software component &v1& has no authorization
check located at the root node. This means that unauthorized access to
the main data of the object might be possible.

System Response

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

How to fix this error?

Check whether the root node of the model ought to be subject to
authorization; check whether the authorization checks of sub nodes are
located correctly (or whether they should be located at the root node).

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 ESH_OM_PC004 - Model &2 lacks authorization at the root node ?

  The SAP error message ESH_OM_PC004 indicates that a user lacks the necessary authorization to access a specific model at its root node in the SAP Enterprise Search (SAP ESH) environment. This typically occurs when a user attempts to execute a search or access a model that they do not have permission to view.
  
  Cause:
  
  Authorization Issues: The user does not have the required authorizations assigned to access the model or its root node.
  Role Configuration: The roles assigned to the user may not include the necessary permissions for the specific model.
  Model Configuration: The model itself may have restrictions that prevent certain users from accessing it.
  
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after encountering the error to analyze the authorization check. This will show which authorization object failed.
  Review the user’s roles and authorizations in transaction SU01 or PFCG.
  
  
  
  Assign Necessary Roles:
  
  If the user lacks the required roles, assign the appropriate roles that include access to