How To Fix ESH_SEARCH147 - Template &1, response attribute &2: Relation references are missing

ESH_SEARCH147 - Overview

• Message type: E = Error

• Message class: ESH_SEARCH - ESH Search

• Message number: 147

• Message text: Template &1, response attribute &2: Relation references are missing

What causes this issue?

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

System Response

In this context relation references are missing.

How to fix this error?

A certain attribute of a specific template and node in a response refers
to another attribute that is either within the same template in a
different node or even in a different template and node and the
references (the path) to reach it are not given.
Maintain the missing references (see interface):
o,,SearchBusinessTemplate or SearchVirtualTemplate
o,,SearchQueryInterface
o,,SearchRequest
o,,ResponseAttribute
o,,NodeAttributeID
o,,<ZH>OrderedRelationReferences</>

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

ESH_SEARCH147 - Details

• The SAP error message ESH_SEARCH147 indicates that there is an issue with a search template in the SAP Enterprise Search (ESH) framework. Specifically, it points out that a template (identified by &1) has a response attribute (identified by &2) that is missing relation references. This can occur when the configuration of the search template is incomplete or incorrect.
  
  Cause:
  
  Missing Relation References: The error typically arises when the response attribute in the search template is expected to reference certain relations (like database tables or fields) that are not defined or are incorrectly configured.
  
  Configuration Issues: There may be issues in the configuration of the search template, such as missing or incorrect mappings between the attributes and the underlying data model.
  Changes in Data Model: If there have been recent changes to the data model or the underlying database structure, the search template may not have been updated accordingly.
  
  
  Solution:
  
  
  Check Template Configuration:
  
  Go to the ESH configuration