Do you have any question about this error?
Message type: E = Error
Message class: ESH_OM_OBJ_MODEL_RP2 - Object Model Repository (2)
Message number: 343
Message text: Filter conditions are not valid for application based object type
Object type &v1& is application based.
If you maintain extraction filters in the Modeler for Search and
Analytics, it is not possible to enter an upper limit for intervals or
to use wildcards.
If you maintain node filters via the external interface, the node
filters must obey the following rules:
SIGN must be I
If there is only one entry in node filters for a given FIELD_ID, then
OPT must be EQ, LT, LE, GE, or GT.
If there are several entries in node filters for a given FIELD_ID, then
OPT must be EQ.
HIGH must be left initial
LOW must not be a wildcard *
This is not the case for object type &v1&, node &v2&, field &v3&
(assigned data provider &v4&).
The filter is inconsistent.
Adjust your input according to the rules above.
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.
ESH_OM_OBJ_MODEL_RP2343
- Filter conditions are not valid for application based object type ?The SAP error message ESH_OM_OBJ_MODEL_RP2343 indicates that there are invalid filter conditions applied to an application-based object type in the SAP Enterprise Search (SAP ESH) framework. This error typically arises when the filter criteria specified in a search query do not match the expected format or values for the object type being queried.
Causes:
- Invalid Filter Values: The filter values provided in the search query do not correspond to valid entries in the database for the specified object type.
- Incorrect Filter Configuration: The filter conditions may not be properly configured in the search model or may not be applicable to the object type being queried.
- Data Model Changes: Changes in the underlying data model or object type definitions may lead to previously valid filters becoming invalid.
- Missing Authorization: The user may not have the necessary authorizations to access certain data, leading to filters that cannot be resolved.
Solutions:
- Review Filter Conditions: Check the filter conditions being applied in the search query. Ensure that they are valid and correspond to the expected values for the object type.
- Check Configuration: Verify the configuration of the search model in the SAP ESH. Ensure that the filters are correctly defined and applicable to the object type.
- Update Filters: If there have been changes to the data model, update the filters to align with the new definitions.
- Test with Default Filters: Try running the search without any custom filters to see if the error persists. This can help isolate whether the issue is with specific filters.
- Check Authorizations: Ensure that the user has the necessary authorizations to access the data related to the object type. If not, adjust the user roles accordingly.
- Consult Documentation: Refer to SAP documentation or notes related to the specific object type and search model for any known issues or updates.
Related Information:
ESH_COCKPIT
to access the Enterprise Search Cockpit for further analysis and configuration of search models and filters.If the issue persists after trying the above solutions, consider reaching out to SAP support for further assistance, providing them with detailed information about the error and the context in which it occurs.
Get instant SAP help. Start your 7-day free trial now.
ESH_OM_OBJ_MODEL_RP2342
Object type &1 direct accessible: Authorization check &3 incompatible
What causes this issue? Object type &v1& is directly accessible. Authorization check &v3& assigned to node &v2& refers to an ...
ESH_OM_OBJ_MODEL_RP2341
Object type &1 cannot be directly accessible
What causes this issue? Object type &v1& can only be directly accessible if all nodes have data providers that are directly accessible. This ...
ESH_OM_OBJ_MODEL_RP2344
Client fields cannot be used in association
What causes this issue? The association connects node &v2& of object type &v1& to node &v4& of object type &v3&. The ...
ESH_OM_OBJ_MODEL_RP2345
Client fields cannot be used in composition
What causes this issue? The compositon connects node &v2& and node &v3& of object type &v1&. Object type &v1& is appl...
Click on this link to search all SAP messages.