ESH_OM_OBJ_MODEL_ODP - ODP-Related Messages
The following messages are stored in message class ESH_OM_OBJ_MODEL_ODP: ODP-Related Messages.
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 | &1&2&3&4 |
| 001 | ODP field &1 is longer than 12 characters |
| 002 | ODP field &1 (data type &2) not supported as key figure |
| 003 | ODP field &1 (data type &2) not supported as characteristic |
| 004 | ODP field &1 (data type &2) not supported in the query |
| 005 | ODP ID &1 does not have a valid semantics (F, P, Q, or T) |
| 006 | ODP language code field &1 only expected in text ODP (semantics T) |
| 007 | Text ODP &1 (semantics T) does not have text containing field |
| 008 | Text ODP &1 (semantics T) does not have a language code |
| 009 | Valid From field &1 only expected in ODP with semantics T or Q |
| 010 | Valid To field &1 only expected in ODP with semantics T or Q |
| 011 | Valid From field &1 does not have the expected data type 'DATS' |
| 012 | Valid To field &1 does not have the expected data type 'DATS' |
| 013 | Time-dependent ODP &1 (semantics Q) does not have a Valid From field |
| 014 | Time-dependent ODP &1 (semantics Q) does not have a Valid To field |
| 015 | Language code &1 does not have the expected data type 'LANG' |
| 016 | ODP name &1 is longer than 12 characters |
| 017 | Relation to object type &1, node &2: no ODP defined |
| 018 | Unexpected relation to ODP &1, object type &2 |
| 019 | ODP &1 with semantics &2 already exists in object type &3, node &4 |
| 020 | ODP &1 cannot support DirectAccess due to DataSource &2 |
| 021 | ODP &1 already exists in object type &2, node &3 |
| 022 | ODP &1 has no valid semantics |
| 023 | ODP &1 already exists in object type &2, node &3, SWC &4 |
| 024 | Relation to ODP &1, semantics &2: Cardinality not supported |
| 025 | To-1-relation to ODP &1, semantics &2: Key not completely supplied |
| 026 | Arbitrary relation to ODP &1, semantics &2: Full key supplied |
| 027 | Arbitrary relation to ODP &1 (&2) without language or time dependency |
| 028 | ODP field (InfoObject) &1 does not have a description |
| 029 | SWC for ODP ID &1, semantics &2 cannot be determined unambiguously |
| 030 | OPD ID &1 in SAP content system must begin with 0-9 |
| 031 | ODP ID &1 cannot be assigned to dev. class (not defined in model) |
| 032 | ODP ID &1: The name has to consist of A-Z, 0-9 or '_' only |
| 033 | ODP ID &1, semantics &2: Software component cannot be found |
| 034 | ODP ID &1, semantics &2 does not exist |
| 035 | OPD ID &1 in customer system must begin with Y, Z |
| 036 | ODP ID &1 already exists in system &2 in package &3 |
| 037 | ODP ID &1: Invalid semantics &2 -> see long text |
| 038 | No ODP ID defined |
| 039 | |
| 040 | SWC of ODP ID &1, semantics &2 not found |
| 041 | Node field &1 not mapped to the expected InfoObject &2 |
| 042 | ODP field &1 is shorter than 3 characters |
| 043 | ODP field &1: name must not begin or end with '_' |
| 044 | ODP field &1: name must not contain '__' |
| 045 | ODP based on DataSource: no fields with path to other nodes allowed |
| 046 | ODP field &1: InfoObject &3 already used at ODP field &2 |
| 047 | Node field &1: Relation from &2 to &3 cannot be considered |
| 048 | Node field &1 is a key field but not part of ODP &2 |
| 049 | ODP field &1: Data provider field &2 is a pure selection field |
| 050 | ODP field &1: Key figure without specified aggregation mode |
| 051 | ODP &1 (semantics &2): Node does not have representative key field |
| 052 | ODP &1 (semantics &2): No semantical key field |
| 053 | |
| 054 | |
| 055 | |
| 101 | Function &1 not supported |
| 102 | Error when writing ODP &1 to GTADIR |
| 103 | Error accessing search metadata, software component &1 |
| 104 | Cannot call modelling client via RFC destination &1 (OSS note 1764978) |
| 105 | Projection ODP &1 (&2) updated from extraction ODP &3(&4) |
| 200 | ***** navigation attributes ******************************************** |
| 201 | Navigation attribute &1 must refer to a node attribute in model &2 |
| 202 | Navigation attribute &1 should not refer to a key field of a node |
| 203 | Navigation attribute &1 must have the role characteristic |
| 204 | Navigation attribute &1 might cause performance problems |
| 205 | Navigation attribute &1 must refer to an ODP field with selection support |
| 206 | Navigation attribute &1 must be a field of ODP for master data attributes |
| 207 | Navigation attribute &1 must refer to nav. attr. in data extraction view |
| 250 | ***** header checks **************************************************** |
| 251 | View type &3 not supported for ODP &1 with semantics &2 |
| 252 | Extraction view missing for ODP &1 with semantics &2 and view type &3 |
| 253 | ODP &1 with semantics &2 on same node as ODP &3 with semantics &4 |
| 254 | ODP &1 and ODP &2 not supported as extraction views on same node |