SAP ABAP Message Class ESH_OM_PC (Plausibility Check)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-EIM-ESH (Application Component) NetWeaver Enterprise Search
⤷ S_ESH_ENG_OBJ_MOD_REP (Package) Model Repository
⤷ BC-EIM-ESH (Application Component) NetWeaver Enterprise Search
⤷ S_ESH_ENG_OBJ_MOD_REP (Package) Model Repository
Attributes
Message class | ESH_OM_PC | |
Short Description | Plausibility Check | |
Changed On | 20110908 | |
Last Changed At | 153016 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | Model &2 has package $$TMP assigned | Space: object requires documentation | |
2 | 001 | Model &2 lacks package assignment | Space: object requires documentation | |
3 | 002 | Model &2 must not start with Y or Z | Space: object requires documentation | |
4 | 003 | Model &2 lacks authorization check for read/search access | Space: object requires documentation | |
5 | 004 | Model &2 lacks authorization at the root node | Space: object requires documentation | |
6 | 005 | Model &2 lacks authorization for analytics | Space: object requires documentation | |
7 | 006 | Model &2 lacks search request | Space: object requires documentation | |
8 | 007 | Node &3 of model &3 lacks response | Space: object requires documentation | |
9 | 008 | Model &2 lacks sub-queries | Space: object requires documentation | |
10 | 009 | Model &2 lacks ODPs | Space: object requires documentation | |
11 | 010 | Node &3 of model &2 lacks ODP | Space: object requires documentation | |
12 | 011 | ODP &4 of model &2 lacks navigational attributes | Space: object requires documentation | |
13 | 012 | Node &3 of model &2 lacks UI area assignment for the response | Space: object requires documentation | |
14 | 013 | Node &3 of model &2 lacks UI area 'title' | Space: object requires documentation | |
15 | 014 | Subnode &3 of model &2 lacks UI area 'title'/'summary' | Space: object requires documentation | |
16 | 015 | Model &2 lacks back-end navigations | Space: object requires documentation | |
17 | 016 | Model &2: back-end navigations defined in a single UI technology | Space: object requires documentation | |
18 | 017 | Package $$TMP must not be used with transportable software comp. | The short text describes the object sufficiently | |
19 | 018 | Package has to be assigned | The short text describes the object sufficiently | |
20 | 019 | Model ID must not be in customer name space | The short text describes the object sufficiently | |
21 | 020 | Data access via read/search must be secure | The short text describes the object sufficiently | |
22 | 021 | Root node data has to be secure | The short text describes the object sufficiently | |
23 | 022 | Reporting has to be secure | The short text describes the object sufficiently | |
24 | 023 | Search access has to be provided | The short text describes the object sufficiently | |
25 | 024 | Response has to be defined | The short text describes the object sufficiently | |
26 | 025 | Sub-queries ought to be defined | The short text describes the object sufficiently | |
27 | 026 | ODPs have to be defined | The short text describes the object sufficiently | |
28 | 027 | ODPs ought to be defined for sub nodes | The short text describes the object sufficiently | |
29 | 028 | ODPs ought to have navigational attributes | The short text describes the object sufficiently | |
30 | 029 | UI behaviour of response has to be defined | The short text describes the object sufficiently | |
31 | 030 | Title presentation for UI has to be defined | The short text describes the object sufficiently | |
32 | 031 | UI behaviour of sub nodes has to be defined | The short text describes the object sufficiently | |
33 | 032 | Backend navigations have to be defined | The short text describes the object sufficiently | |
34 | 033 | Back-end navigations should be provided in several UI technologies | The short text describes the object sufficiently | |
35 | 034 | Application models must have language-specific data | The short text describes the object sufficiently | |
36 | 035 | Add a text node to model &2 | Space: object requires documentation | |
37 | 036 | Request usage has to be specified | The short text describes the object sufficiently | |
38 | 037 | Request &4 of model &2 lacks usage specification | Space: object requires documentation | |
39 | 038 | Check criteria yield no results | The short text describes the object sufficiently | |
40 | 039 | &1 is not a checkable software component | The short text describes the object sufficiently | |
41 | 040 | &1 is not a valid user ID | The short text describes the object sufficiently | |
42 | 041 | Attribute relevancy has to be defined | The short text describes the object sufficiently | |
43 | 042 | Add relevancy settings to request &4 of model &2 | Space: object requires documentation | |
44 | 043 | Classification model has to be complete | The short text describes the object sufficiently | |
45 | 044 | Add an association to a data type model to property model &2 | Space: object requires documentation | |
46 | 045 | Add an association to a property model to valuation node &3 | Space: object requires documentation | |
47 | 046 | Add an association to a data type model to valuation node &3 | Space: object requires documentation | |
48 | 047 | Exemption successfully created | The short text describes the object sufficiently | |
49 | 048 | Model &2 has only one node | Space: object requires documentation | |
50 | 049 | Model &2: Wrong setup of Business Models | Space: object requires documentation | |
51 | 050 | Model must be cut correctly | The short text describes the object sufficiently | |
52 | 051 | Model &2 is void | Space: object requires documentation |
History
Last changed on/by | 20110908 | SAP | |
SAP Release Created in | 703 |