RODPS - Operation Data Provider
The following messages are stored in message class RODPS: Operation Data Provider.
It is part of development package RODPS in software component BC-EIM-ODP. This development package consists of objects that can be grouped under "Operational Data Provider Services".
It is part of development package RODPS in software component BC-EIM-ODP. This development package consists of objects that can be grouped under "Operational Data Provider Services".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Unexpected Error |
| 001 | Program error in the Operational Data Provisioning Services area |
| 002 | Error while reading DataSource &1 |
| 003 | &1 &2 &3 &4 |
| 004 | DataSource &1 does not have any key fields |
| 005 | Field &1 for import defined as a key field. Correction required |
| 006 | Error while accessing metadata |
| 007 | Error while accessing data: &1 |
| 008 | Data access with data type &1 is not supported |
| 009 | Error while extracting data: DataSource &1 |
| 010 | Error with extractor call &1 |
| 011 | ODP &1 does not exist |
| 012 | Error while reading DataSource &1 |
| 013 | No DataSource exists for ODP &1 |
| 014 | Error: DataSource &1 does not contain any fields |
| 015 | Check ODP &1 (Part) |
| 016 | Check ODP &1 |
| 017 | DataSource &1 not released (table RODPS_OS_EXPOSE) |
| 018 | Extraction finished (NO_MORE_DATA) after &1 calls of a maximum &2 |
| 019 | Extraction finished: End (NO_MORE_DATA) not reached after &1 calls |
| 020 | Error while accessing ESH with software component &1 |
| 021 | No valid destination maintained for BW client |
| 022 | Runtime class &1 not actively available |
| 023 | ODP &1, semantic &2 cannot be uniquely identified |
| 024 | No unique sysrel as an enhancement of ODP &1 (semantic &2) |
| 025 | Aggregate function '&1' for component '&2' of type '&3' not supported |
| 026 | Inconsistency in ESH repository &1 &2 &3 &4 |
| 027 | Field &1 (DataSource &2) does not exist |
| 028 | Change field properties of field &1 (DataSource or Search Repository) |
| 029 | Checks in software component &1 |
| 030 | Extraction completed. &1 records extracted |
| 031 | No data package extracted |
| 032 | Empty data package (zero records) extracted |
| 033 | DataSource &1 does not support direct access (VIRTCUBE=D) |
| 034 | Check ODPs |
| 035 | - Check: ESH metadata |
| 036 | - Check: ODP metadata |
| 037 | - Check: ODP runtime |
| 038 | - Check: TransientProvider |
| 039 | - Check: &1 |
| 040 | -- Extraction without filter |
| 041 | --- Extraction from ODP &1 |
| 042 | -- Creating filter |
| 043 | -- Extraction with filter |
| 044 | --- Extraction from DataSource: &1 |
| 045 | --- Extraction from &1 (&2) |
| 046 | -- Messages related to ODP &1 |
| 047 | Continue display without a preview of the transient provider |
| 048 | DataSource &1 does not have the supported data type &2 |
| 049 | ODP &1 for hierarchy ODP &2 does not exist |
| 050 | - Check: General |
| 051 | ESH metadata: Check in client &1 |
| 052 | BW DataSource must be consistent |
| 053 | BW DataSource must be consistent with the model data |
| 054 | Check ODP &1 (View) |
| 055 | Check ODP &1 (&2) |
| 056 | ODP activation is only possible in client &1 |
| 057 | ODPs can only be activated in the ESH_COCKPIT |
| 058 | DataSource &1 is already active |
| 059 | DataSource &1 not found |
| 060 | ODP &1 Activated |
| 061 | Paths with cardinality &1 are not supported here |
| 062 | Hierarchy DataSource &1 cannot be imported from customer systems |
| 063 | ODP activation is locked |
| 064 | The metadata for ODP &1 contains errors |
| 065 | You do not have authorization for administration of connectors |
| 066 | No errors found |
| 067 | Local connection for search & analytics created |
| 068 | Creation of connectors scheduled for SWC &1 |
| 069 | ODP &1 is unchanged |
| 070 | BWA index for ODP &1 (&2) cannot be used |
| 071 | BWA index for ODP &1 (&2) does not contain all the data requested |
| 072 | ODP &1 (&2) reads data from the BWA |
| 073 | ODP &3 associated with &1 is not indexed in BWA |
| 074 | Field &3 does not exist in ODP &1 with semantic &2 |
| 075 | ODP &1 (&2) reads data in direct access |
| 076 | Temporal join in direct access for ODP &1 (&2) with ODP &3 |
| 077 | Metadata for ODP &1 are not in the shared buffer |
| 078 | Navigation attributes in direct access for ODP &1 (&2) from ODP &3 |
| 079 | ODP &1 cannot be transported. Manual transport required |
| 080 | Customer enhancement in direct access for ODP &1 (&2) on DataSource &3 |
| 081 | Restrictions on ODP &1(&2) return &4 values for attribute &3 |
| 082 | ODP &1(&2): Transported version cannot be overwritten |
| 083 | Field &1 is defined differently |
| 084 | Association &1 is different |
| 085 | Authorizations are different |
| 086 | Runtime object for ODP &1 (&2) activated with messages |
| 087 | Runtime object for ODP &1 (&2) activated without messages |
| 088 | Runtime object for ODP &1 (&2) deleted |
| 089 | Runtime object for ODP &1 (&2) does not have any errors |
| 090 | Runtime object for ODP &1 (&2) is not up to date |
| 100 | Maximum number of nodes (&1) reached |
| 101 | Table/view &1 does not actively exist |
| 102 | No hierarchy selection specified |
| 103 | Error in follow-up processing of selected results set |
| 104 | Hierarchy element ID &1: Component &2 is missing from the semantic key |
| 105 | Global and enhanced selections cannot be combined |
| 301 | Node &1 not found in iterator of template &2 |
| 302 | Node &1 not supported by iterator |
| 303 | Error while creating the internal table for DataSource &1 |
| 304 | Error while reading the metadata for Provider &1 |
| 305 | Error while reading the metadata for ODP &1 |
| 306 | Error while determining the TREX destination |
| 307 | Error while checking TREX destination &1 |
| 308 | No valid pointer for delta replication |
| 309 | Data package &1 cannot be requested again |
| 310 | Confirm data package &1 first |
| 311 | Error while retrieving data from queue &1 |
| 320 | Retrieved data package &1 with &3 records for &2 |
| 321 | Data package &1 confirmed for &2 |
| 322 | Data package &1 contains &3 changes and &4 deletions for &2 |
| 600 | * -------------------------- ODP SQL ----------------------------------- |
| 601 | Key word "&1" is missing |
| 602 | Token "&2" found instead of the key word "&1" |
| 603 | "&1" is not a valid aggregate function |
| 604 | "&1" is not a whole number |
| 605 | &1 is not in the permitted value range |
| 606 | Reserved key word "&1" instead of a label |
| 607 | "&1" is not a valid label |
| 608 | Token "&2" found instead of the symbol "&1" |
| 609 | Field name "&1" is used more than once |
| 610 | Alias name "&1" is not unique |
| 611 | "&1" clause is not required |
| 612 | Label "&1" appears more than once in the "&2" clause |
| 613 | Label "&1" not specified in the "&2" clause |
| 614 | Statement is incomplete |
| 615 | Aggregate functions in "&1" clause require a "&2" clause |
| 616 | You are not authorized to display data from operational data providers |
| 800 | Field &1 in ODP &2 cannot be used as a navigation attribute |
| 801 | Association for field &1 (ODP &2) is ignored for navigation attribute &3 |
| 802 | The representative key field of ODP &1 cannot be determined |