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