RSODP - Operational Data Provider: Messages
The following messages are stored in message class RSODP: Operational Data Provider: Messages.
It is part of development package RSODP in software component BW-WHM-DST. This development package consists of objects that can be grouped under "Operational Data Provisioning (BW Part)".
It is part of development package RSODP in software component BW-WHM-DST. This development package consists of objects that can be grouped under "Operational Data Provisioning (BW Part)".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Replication for InfoProvider &1 |
| 001 | InfoSet extraction completed (&1 records read) |
| 002 | Could not extract InfoSet |
| 003 | TREX Indexing Started |
| 004 | TREX Indexing Completed |
| 005 | TREX Indexing Failed |
| 006 | Copying to Enhanced TREX Structure Started |
| 007 | Copying to Enhanced TREX Structure Completed |
| 008 | Error during TREX Indexing |
| 009 | TREX Access for Operational Data Provider &1 Deactivated |
| 010 | TREX Indices for Operational Data Provider &1 Deleted |
| 011 | Create BWA index for operational data provider &1 (&2) |
| 012 | BWA index created for operational data provider &1 (&2) |
| 013 | Error creating BWA index for operational data provider &1 (&2) |
| 014 | Waiting for Separated Processes |
| 015 | Error Splitting Parallel Processes |
| 016 | Termination Due to Errors in a Parallel Process |
| 017 | Replication for InfoProvider &1 completed |
| 018 | TREX error &1: &2 &3 &4 |
| 019 | Loading in delta modus requires partition selection |
| 020 | Parallel Processes Split Under Job Name &1 |
| 021 | This change to the selections requires a rebuild of all partitions |
| 022 | Selected dataset is already in the BIA |
| 023 | Error in lock server |
| 024 | Indexing for InfoProvider &1 is running |
| 025 | Error with Commit &1 |
| 026 | Commit successful |
| 027 | Shared lock could not be assigned |
| 028 | Rollback |
| 029 | Rollback failed |
| 030 | Rollback possible |
| 031 | Rebuild of index required |
| 032 | BIA destination not maintained |
| 033 | Error while creating authorization index |
| 034 | Created logical TREX index &1 |
| 035 | Query does not contain any characteristics or key figures |
| 036 | Minimum TREX version for ODP: 7.20.02 |
| 037 | Maximum number of nodes (&1) reached |
| 038 | Attribute &2 does not exist in TREX index &1 |
| 039 | Error while creating BObj. Explorer Index for ODP &1 (&2) |
| 040 | &1 &2 &3 &4 |
| 041 | Minimum TREX version for join ODPs is 7.2x.11 |
| 042 | ODP &1 (&2) reads data from the BWA |
| 043 | ODP &1 activated |
| 044 | ODP &1 deleted |
| 045 | |
| 046 | -- Messages related to ODP &1 |
| 047 | Continue without preview of transient provider (long text) |
| 048 | ODP &1 does not exist |
| 049 | Association of type &1 for field &2 expected but not found |
| 050 | Association to OPD &2 is missing for field &1 |
| 051 | Definition of ODP &1 is not correct |
| 052 | A key field must have the InfoObject name &1 |
| 053 | Characteristic &1 is used as a key in ODP &2 and ODP &3 |
| 054 | Missing associations in hierarchy element &1 |
| 055 | No fields with text semantics |
| 056 | Cannot derive InfoObject name for field &1 |
| 057 | Field &1 must have a local InfoObject name |
| 058 | Hierarchy ODP &3 does not allow value &1 in field &2 |
| 059 | Intervals are not supported in hierarchies |
| 060 | InfoObject name &1 is not required for field &2 and &3 |
| 061 | Field &1 in join of association between ODP &2 and ODP &3 is not in ODP |
| 062 | Basic chars. for fields &1 (ODP &4) and field &2 (ODP &3) do not match |
| 063 | Total length of the key fields (&1) is longer than 60 characters |
| 064 | Association &1 for field &2 ignored. Field &3 is ignored in view &4. |
| 065 | Association between &1 and &2 ignored. Field &3 not allowed in join |
| 066 | Field &1 (ODP &2) must be mapped to field &3 |
| 067 | ODP contains fields with compulsory selection |
| 068 | InfoProvider &1 does not exist because ODP &2 is not available |
| 069 | Dependency analysis is not possible for InfoProvider &1 |
| 070 | ODP &1(&2) contains a further field (&3) in the transport version |
| 071 | ODP &1(&2) is not compatible with transport version |
| 072 | Field &1 (ODP &2) has to have an association to InfoObject &3 |
| 073 | Field &1 (ODP &2): InfoObject &3 of the association does not exist |
| 074 | Field &1 (ODP &2): InfoObject &3 of the assc. has to be a basic char. |
| 075 | Field &1 (ODP &2): Join definition violates compounding of &3 |
| 076 | Representative key field &1 cannot be mapped to an InfoObject |
| 077 | Field &1 of DDL view &2 does not support hierarchies |
| 078 | ODP &1 is a projection of ODP &2 |
| 079 | Hierarchy &1 not found for DDL view &2 |
| 080 | CDS View &1 not found or it is not a correctly defined analytic view |
| 081 | FROM clause in DDL view &1 is not a CDS view of category CUBE |
| 082 | Hierarchy key field &1 not specified |
| 083 | Error in association &1 from &2 to &3: Field &4 not key in target |
| 084 | Association &1: Field &2 (&3) does not map to representative key &4 |
| 085 | Field &1 ignored: It requires a field with semantics &2 |
| 086 | Field &1 ignored: Type &2 with length &3 not supported |
| 087 | Field &1 ignored: Compounding too complex |
| 088 | Field &1: Association to &2 can't be interpreted and will be ignored |
| 089 | Error in &1 from &2 to &3: Field &4 does not map to InfoObject |
| 090 | Association &1: Field &2 not mapped to InfoObject in target &3 |
| 091 | Association &1: Field &2 in target &3 has to be part of the join |
| 092 | Association &1: Field &2 must be at position &3 in the join |
| 093 | Association &1: Field &2 is not allowed in the join |
| 094 | Error in hierarchy view &1. View will be ignored. |
| 095 | Field &1: Data type &2 not allowed for time stamp semantic |
| 096 | Field &1 (ODP &2): unspecific problem - check semantic of the field |
| 097 | Field &1: Cannot find original CDS name (CamelCase) |
| 098 | Error in hierarchy view &1: Association to &2 used multiple times. |
| 099 | System is not configured correctly - see note 2289865 |
| 100 | Value help view &1 ignored: Field &2 is not a key field |
| 101 | Logical conjunction ANALYTICSFILTER not supported in ESH ODP on SAP HANA |
| 102 | Empty join conditions are not supported in ESH ODP on SAP HANA |
| 103 | Field &1 ignored: Data type &2 not allowed for characteristic |
| 104 | Field &1 ignored: Data type &2 not allowed for measures |
| 105 | Characteristic &1 not allowed in value help |
| 106 | Field &1 in &2 with ALPHA is associated to &3 in &4 with different length |
| 107 | DB hint "&1" will be ignored in Analytics |
| 108 | View is inconsistent since one of the associated views is inconsistent |
| 109 | CHAR or SSTR field &1 in &2 is associated to &3 in &4 with shorter length |
| 110 | SpatialData feature ignored, there is more than one field |
| 111 | CDS Geo Data returned as GEOJSON and with Spatial Reference System 3857 |
| 112 | Field &1: Data type &2 has length &3 greater than max. Chavl length (250) |
| 113 | &1 is associated with &2 but with different data type, length or convexit |
| 114 | Field &1 with conversion exit '&3' is associated to field &2 with '&4' |
| 115 | Association &1 in &2 ignored |
| 116 | Fields &1 and &2 need same target of their foreign key associations |
| 117 | Error in determining the associations of ODP &1; all associations ignored |
| 118 | Chaconst field &1 of type &2 in View &3 not supported |
| 119 | Text semantic of key field &1 ignored |
| 120 | Association of field &1 ignored: Target view &2 is inconsistent |
| 121 | Association of field &1 ignored: Association for field &2 is inconsistent |
| 122 | Annotation &1 ignored: Class &2 doesn't exist |
| 123 | Annotation &1 ignored: Class &2 has to implement interface &3 |
| 124 | Field in CDS view not found for the corresponding InfoObject &1 |
| 125 | Field &1 in association &2 mapped to field with incompatible type |
| 126 | Field &1 in association &2 is shorter than the mapped field |
| 127 | Annotation &1 ignored: Class &2 has a syntax error |
| 128 | Field &1 in assocation &2 not allowed. Hier. structure not timedpendent |
| 129 | Association of field &1 ignored: Semantics for field &2 are inconsistent |
| 133 | Field &1 in View &2 has date semantics. Cannot be used in the Assoc. &3 |
| 134 | There must be a foreign key association with target view &1 |
| 135 | CDS Query Designer API Simulator is relevant for ABAP CDS Context |