How To Fix ESH_SEARCH123 - Template &1, node &2: More than one attribute exists for MIME type

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_SEARCH - ESH Search

• Message number: 123

• Message text: Template &1, node &2: More than one attribute exists for MIME type

What causes this issue?

If you want to use binary content in DPS it is only possible to use URLs
to reference this content. In this case there are further restrictions
as there should be only one attribute referencing an URL per node.
Moreover a pair of attributes is needed: one referencing the URL and
another giving the correct mime type of the content. The attribute for
the URL needs to have the "ContentURLIndicator" set to true and must be
of datatype string. The latter is also true for the mime type attribute
which is designated to be a mime type by using the semantics code
"MimeType".

System Response

Only one attribute per node is allowed to be marked for being the
MimeType attribute as described above.

How to fix this error?

Change the model so that only one attribute is marked for being the
MimeType.

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 ESH_SEARCH123 - Template &1, node &2: More than one attribute exists for MIME type ?

  The SAP error message ESH_SEARCH123 typically indicates that there is a conflict in the configuration of the Enterprise Search (ESH) system regarding the attributes associated with a specific MIME type. This error occurs when more than one attribute is defined for a given MIME type, which can lead to ambiguity in how the system processes search queries.
  Cause:
  
  
  Multiple Attributes for a MIME Type: The primary cause of this error is that the system has been configured with more than one attribute that corresponds to the same MIME type. This can happen during the configuration of the search model or when defining the attributes in the data source.
  
  
  Incorrect Configuration: There may be an incorrect or incomplete configuration in the search model or the data source that leads to this conflict.
  
  
  Data Source Issues: If the data source is not properly set up or if there are changes in the data structure that have not been reflected in the search model, this error can occur.
  
  
  Solution:
  To resolve the ESH_SEARCH123 error, you can follow these steps:
  
  
  Check the Search Model Configuration:
  
  Go to the SAP system and navigate to the configuration of the search model.
  Identify the attributes that are defined for the MIME type in question.
  Ensure that there is only one attribute defined for each MIME type. If there are duplicates, remove or consolidate them.
  
  
  
  Review Data Source Settings:
  
  Check the data source configuration to ensure that it is correctly set up and that there are no conflicting definitions.
  If necessary, update the data source to reflect the correct structure and attributes.
  
  
  
  Adjust Attribute Definitions:
  
  If you find multiple attributes for the same MIME type, decide which attribute should be retained and remove the others.
  Make sure that the remaining attribute is correctly configured to handle the data associated with the MIME type.
  
  
  
  Rebuild the Index:
  
  After making changes to the configuration, it may be necessary to rebuild the search index to ensure that the changes take effect.
  This can usually be done through the administration tools in the SAP system.
  
  
  
  Test the Configuration:
  
  After making the necessary adjustments, perform a test search to ensure that the error no longer occurs and that the search functionality works as expected.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may provide additional guidance or patches related to this error.
  Documentation: Refer to the official SAP documentation for Enterprise Search configuration to understand best practices and common pitfalls.
  Support: If the issue persists after following the above steps, consider reaching out to SAP support for further assistance.
  
  By carefully reviewing the configuration and ensuring that there are no conflicting attributes for MIME types, you should be able to resolve the ESH_SEARCH123 error effectively.