SAP ABAP Message Class ESH_OM_OBJ_MODEL_ODP (ODP-Related Messages)
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
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-EIM-ESH (Application Component) NetWeaver Enterprise Search⤷
S_ESH_ENG_OBJ_MOD_REP (Package) Model Repository 
Attributes
| Message class |  |
ESH_OM_OBJ_MODEL_ODP |
| Short Description |  |
ODP-Related Messages |
| Changed On |  |
20130531 |
| Last Changed At |  |
091221 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  000 |
&1&2&3&4 | The short text describes the object sufficiently | |
| 2 | 001 |
ODP field &1 is longer than 12 characters | The short text describes the object sufficiently | |
| 3 | 002 |
ODP field &1 (data type &2) not supported as key figure | The short text describes the object sufficiently | |
| 4 | 003 |
ODP field &1 (data type &2) not supported as characteristic | The short text describes the object sufficiently | |
| 5 | 004 |
ODP field &1 (data type &2) not supported in the query | The short text describes the object sufficiently | |
| 6 | 005 |
ODP ID &1 does not have a valid semantics (F, P, Q, or T) | Space: object requires documentation | |
| 7 | 006 |
ODP language code field &1 only expected in text ODP (semantics T) | The short text describes the object sufficiently | |
| 8 | 007 |
Text ODP &1 (semantics T) does not have text containing field | The short text describes the object sufficiently | |
| 9 | 008 |
Text ODP &1 (semantics T) does not have a language code | The short text describes the object sufficiently | |
| 10 | 009 |
Valid From field &1 only expected in ODP with semantics T or Q | The short text describes the object sufficiently | |
| 11 | 010 |
Valid To field &1 only expected in ODP with semantics T or Q | The short text describes the object sufficiently | |
| 12 | 011 |
Valid From field &1 does not have the expected data type 'DATS' | The short text describes the object sufficiently | |
| 13 | 012 |
Valid To field &1 does not have the expected data type 'DATS' | The short text describes the object sufficiently | |
| 14 | 013 |
Time-dependent ODP &1 (semantics Q) does not have a Valid From field | The short text describes the object sufficiently | |
| 15 | 014 |
Time-dependent ODP &1 (semantics Q) does not have a Valid To field | The short text describes the object sufficiently | |
| 16 | 015 |
Language code &1 does not have the expected data type 'LANG' | The short text describes the object sufficiently | |
| 17 | 016 |
ODP name &1 is longer than 12 characters | The short text describes the object sufficiently | |
| 18 | 017 |
Relation to object type &1, node &2: no ODP defined | The short text describes the object sufficiently | |
| 19 | 018 |
Unexpected relation to ODP &1, object type &2 | The short text describes the object sufficiently | |
| 20 | 019 |
ODP &1 with semantics &2 already exists in object type &3, node &4 | The short text describes the object sufficiently | |
| 21 | 020 |
ODP &1 cannot support DirectAccess due to DataSource &2 | The short text describes the object sufficiently | |
| 22 | 021 |
ODP &1 already exists in object type &2, node &3 | The short text describes the object sufficiently | |
| 23 | 022 |
ODP &1 has no valid semantics | The short text describes the object sufficiently | |
| 24 | 023 |
ODP &1 already exists in object type &2, node &3, SWC &4 | The short text describes the object sufficiently | |
| 25 | 024 |
Relation to ODP &1, semantics &2: Cardinality not supported | Space: object requires documentation | |
| 26 | 025 |
To-1-relation to ODP &1, semantics &2: Key not completely supplied | Space: object requires documentation | |
| 27 | 026 |
Arbitrary relation to ODP &1, semantics &2: Full key supplied | Space: object requires documentation | |
| 28 | 027 |
Arbitrary relation to ODP &1 (&2) without language or time dependency | Space: object requires documentation | |
| 29 | 028 |
ODP field (InfoObject) &1 does not have a description | The short text describes the object sufficiently | |
| 30 | 029 |
SWC for ODP ID &1, semantics &2 cannot be determined unambiguously | The short text describes the object sufficiently | |
| 31 | 030 |
OPD ID &1 in SAP content system must begin with 0-9 | The short text describes the object sufficiently | |
| 32 | 031 |
ODP ID &1 cannot be assigned to dev. class (not defined in model) | Space: object requires documentation | |
| 33 | 032 |
ODP ID &1: The name has to consist of A-Z, 0-9 or '_' only | The short text describes the object sufficiently | |
| 34 | 033 |
ODP ID &1, semantics &2: Software component cannot be found | The short text describes the object sufficiently | |
| 35 | 034 |
ODP ID &1, semantics &2 does not exist | The short text describes the object sufficiently | |
| 36 | 035 |
OPD ID &1 in customer system must begin with Y, Z | The short text describes the object sufficiently | |
| 37 | 036 |
ODP ID &1 already exists in system &2 in package &3 | The short text describes the object sufficiently | |
| 38 | 037 |
ODP ID &1: Invalid semantics &2 -> see long text | Space: object requires documentation | |
| 39 | 038 |
No ODP ID defined | The short text describes the object sufficiently | |
| 40 | 039 |
The short text describes the object sufficiently | ||
| 41 | 040 |
SWC of ODP ID &1, semantics &2 not found | The short text describes the object sufficiently | |
| 42 | 041 |
Node field &1 not mapped to the expected InfoObject &2 | The short text describes the object sufficiently | |
| 43 | 042 |
ODP field &1 is shorter than 3 characters | The short text describes the object sufficiently | |
| 44 | 043 |
ODP field &1: name must not begin or end with '_' | The short text describes the object sufficiently | |
| 45 | 044 |
ODP field &1: name must not contain '__' | The short text describes the object sufficiently | |
| 46 | 045 |
ODP based on DataSource: no fields with path to other nodes allowed | The short text describes the object sufficiently | |
| 47 | 046 |
ODP field &1: InfoObject &3 already used at ODP field &2 | Space: object requires documentation | |
| 48 | 047 |
Node field &1: Relation from &2 to &3 cannot be considered | The short text describes the object sufficiently | |
| 49 | 048 |
Node field &1 is a key field but not part of ODP &2 | The short text describes the object sufficiently | |
| 50 | 049 |
ODP field &1: Data provider field &2 is a pure selection field | The short text describes the object sufficiently | |
| 51 | 050 |
ODP field &1: Key figure without specified aggregation mode | The short text describes the object sufficiently | |
| 52 | 051 |
ODP &1 (semantics &2): Node does not have representative key field | Space: object requires documentation | |
| 53 | 052 |
ODP &1 (semantics &2): No semantical key field | Space: object requires documentation | |
| 54 | 053 |
The short text describes the object sufficiently | ||
| 55 | 054 |
The short text describes the object sufficiently | ||
| 56 | 055 |
The short text describes the object sufficiently | ||
| 57 | 101 |
Function &1 not supported | The short text describes the object sufficiently | |
| 58 | 102 |
Error when writing ODP &1 to GTADIR | The short text describes the object sufficiently | |
| 59 | 103 |
Error accessing search metadata, software component &1 | The short text describes the object sufficiently | |
| 60 | 104 |
Cannot call modelling client via RFC destination &1 (OSS note 1764978) | Space: object requires documentation | |
| 61 | 105 |
Projection ODP &1 (&2) updated from extraction ODP &3(&4) | The short text describes the object sufficiently | |
| 62 | 200 |
***** navigation attributes ******************************************** | The short text describes the object sufficiently | |
| 63 | 201 |
Navigation attribute &1 must refer to a node attribute in model &2 | The short text describes the object sufficiently | |
| 64 | 202 |
Navigation attribute &1 should not refer to a key field of a node | The short text describes the object sufficiently | |
| 65 | 203 |
Navigation attribute &1 must have the role characteristic | The short text describes the object sufficiently | |
| 66 | 204 |
Navigation attribute &1 might cause performance problems | Space: object requires documentation | |
| 67 | 205 |
Navigation attribute &1 must refer to an ODP field with selection support | The short text describes the object sufficiently | |
| 68 | 206 |
Navigation attribute &1 must be a field of ODP for master data attributes | The short text describes the object sufficiently | |
| 69 | 207 |
Navigation attribute &1 must refer to nav. attr. in data extraction view | The short text describes the object sufficiently | |
| 70 | 250 |
***** header checks **************************************************** | The short text describes the object sufficiently | |
| 71 | 251 |
View type &3 not supported for ODP &1 with semantics &2 | The short text describes the object sufficiently | |
| 72 | 252 |
Extraction view missing for ODP &1 with semantics &2 and view type &3 | The short text describes the object sufficiently | |
| 73 | 253 |
ODP &1 with semantics &2 on same node as ODP &3 with semantics &4 | The short text describes the object sufficiently | |
| 74 | 254 |
ODP &1 and ODP &2 not supported as extraction views on same node | The short text describes the object sufficiently |
History
| Last changed on/by | |
20130531 | SAP |
| SAP Release Created in | 730 |
