ESH_OM_PC - Plausibility Check

The following messages are stored in message class ESH_OM_PC: Plausibility Check.
It is part of development package S_ESH_ENG_OBJ_MOD_REP in software component BC-EIM-ESH. This development package consists of objects that can be grouped under "Model Repository".
Message Nr
Message Text
000Enterprise Search - Model Checks
001Model &2 lacks package assignment
002Model &2 must not start with Y or Z
003Model &2 lacks authorization check for read/search access
004Model &2 lacks authorization at the root node
005Model &2 lacks authorization for analytics
006Model &2 lacks search request
007Node &3 of model &3 lacks response
008Model &2 lacks sub-queries
009Model &2 lacks ODPs
010Node &3 of model &2 lacks ODP
011ODP &4 of model &2 lacks navigational attributes
012Node &3 of model &2 lacks UI area assignment for the response
013Node &3 of model &2 lacks UI area 'title'
014Subnode &3 of model &2 lacks UI area 'title'/'summary'
015Model &2 lacks back-end navigations
016Model &2: back-end navigations defined in a single UI technology
017Local package must not be used with transportable software comp.
018Package has to be assigned
019Model ID must not be in customer name space
020Data access via read/search must be secure
021Root node data has to be secure
022Reporting has to be secure
023Search access has to be provided
024Response has to be defined
025Sub-queries ought to be defined
026ODPs have to be defined
027ODPs ought to be defined for sub nodes
028ODPs ought to have navigational attributes
029UI behaviour of response has to be defined
030Title presentation for UI has to be defined
031UI behaviour of sub nodes has to be defined
032Backend navigations have to be defined
033Back-end navigations should be provided in several UI technologies
034Application models must have language-specific data
035Add a text node to model &2
036Request usage has to be specified
037Request &4 of model &2 lacks usage specification
038Check criteria yield no results
039&1 is not a checkable software component
040&1 is not a valid user ID
041Attribute relevancy has to be defined
042Add relevancy settings to request &4 of model &2
043Classification model has to be complete
044Add an association to a data type model to property model &2
045Add an association to a property model to valuation node &3
046Add an association to a data type model to valuation node &3
047Exemption successfully created
048Model &2 has only one node
049Model &2: Wrong setup of Business Models
050Model must be cut correctly
051Model &2 is void
052Model &1, node &2 lacks client-attribute
053Node has to have a client-attribute
054Transportable Package must be compliant with program-generation
055Transportable Package &1 must be compliant with program-generation
056Package must have a valid appl. comp. to create customer messages
057Language relevancy of package must be maintained
058Package content shall get translated
059Software components shall be in sync for all clients
060SW comp. &1 has most modeling data (data provider: &2) in client(s) &3
061SW comp. &1 has same number of data providers (&2) in top clients
062The latest transport request of SW Comp. &1 is &2
063Response field &2 of model &1 is not freestyle searchable
064Response fields on the search result must be freestyle searchable
065Title response field &2 of model &1 is not freestyle searchable
066Model &2 has local package &3 assigned
Privacy Policy