RS_ADSO_MODEL - Messages related to the Datastore Object Backend
The following messages are stored in message class RS_ADSO_MODEL: Messages related to the Datastore Object Backend.
It is part of development package RSO_ADSO_MODEL in software component BW-WHM-MTD. This development package consists of objects that can be grouped under "BW: Backend Model for Datastore Object".
It is part of development package RSO_ADSO_MODEL in software component BW-WHM-MTD. This development package consists of objects that can be grouped under "BW: Backend Model for Datastore Object".
Message Nr ▲ | Message Text |
|---|---|
| 000 | The input XML does not contain any model information |
| 001 | Required XML attribute '&1' not found in element '&2' |
| 002 | Field '&1' is not compatible with a BW InfoObject |
| 003 | No change log when reporting on union of inbound and active table |
| 004 | DataStore claims to be &1, but model content refers to &2 |
| 005 | DataStore &1 is consistent |
| 006 | "Do not delete data after activation" cannot be set in this scenario |
| 007 | Change log cannot be set without "Activate Data" |
| 008 | Setting invalid: "Do not delete data after activation" without activation |
| 009 | Non-Cum. Value Change key figure &1 missing for inventory key figure &2 |
| 010 | Flow key figure &1 missing for inventory key figure &2 |
| 011 | Validity characteristic &1 is not a key element of the object |
| 012 | Validity characteristic &1 is a time characteristic |
| 013 | Partitioning only allowed on one field |
| 014 | Inventory reference characteristic missing |
| 015 | "All Characteristics are Key" is set. No further key definition allowed. |
| 016 | Non-cum. not supported yet |
| 017 | Key definition missing |
| 018 | SID determination mode '&1', field &2 not allowed |
| 019 | SID determination mode '&1' for field &2 not valid |
| 020 | Field name &1 used multiple times. InfoObject &2 and field &1. |
| 021 | Advanced DataStore object only supported with SAP HANA database |
| 022 | "Activate Data" has to be set with "Reporting on Union..." |
| 023 | InfoObject &1 defined more than once in the object |
| 024 | The associated InfoObject has to be specified for object &1 |
| 025 | "Keep Inbound Data" not possible together with "Write Change Log" |
| 026 | Field &1: Data type allows maximum length 31. The length defined is &2. |
| 027 | Field &1: The maximum length for data type &2 is &3 |
| 028 | Field &1: Data type allows maximum &2 digits (scale). &3 have been set. |
| 029 | Field name cannot be initial |
| 030 | Field &1: Field name cannot start with "/BI0/". |
| 031 | Field name &1 is reserved |
| 032 | Field &1: Maximum length for a field name of data type '&3' is &2 |
| 033 | Field &1: Invalid namespace. |
| 034 | Data type &1 is not valid |
| 035 | Extended storage of activation queue is not possible with activation |
| 036 | DataStore object &1 is not consistent |
| 037 | Key figure &1 with aggregation type &2 not allowed |
| 038 | You have to add a field or InfoObject to the DataStore object |
| 039 | Partitioning criterion &1 is not in InfoProvider |
| 040 | Partitioning criterion &1 must be in the key of the DataStore object |
| 041 | At least one characteristic of field without aggregation is mandatory |
| 042 | Field &1: A currency must have at least one decimal place |
| 043 | Validity characteristic &1 is not a characteristic |
| 044 | Validity characteristic &1 is a transient InfoObject |
| 045 | Prerequisites for inventory handling not fulfilled |
| 046 | '&1' cannot be a key element as it is a key figure or XXL characteristic |
| 047 | &1 is a key element. Compound element &2 also has to be in the key. |
| 048 | NCUM time reference characteristic is set but no inventory key figures |
| 049 | Field &1 is of type Currency. Length has to be 5. |
| 050 | Field &1 is of type Quantity. Length has to be 3. |
| 051 | Field &1 is of type Currency. Aggregation has to be maintained. |
| 052 | Field &1 is of type Quantity. Aggregation has to be maintained. |
| 053 | Field &1 is of type Quantity. Unit has to be maintained. |
| 054 | Field &1 is of type Currency. Currency key has to be maintained. |
| 055 | Partitioning criteria &1:'&2' not consistent; lower bound > upper bound |
| 056 | Field &2: object must not contain fields of type &1 |
| 057 | Field &2: Key or index must not contain fields of data type &1 |
| 058 | "All Characteristics are Key" is set; "Unique data records" not allowed |
| 059 | "Activate/Compress Data" is not set; "Unique data records" not allowed |
| 060 | "Activate/Compress Data" is not set; key definition not allowed |
| 061 | "Direct update" attribute set. Key definition missing. |
| 062 | "Direct update" set. "Activate Data" not allowed. |
| 063 | "Direct update" set. "Write Change Log" not allowed. |
| 064 | "Direct update" set. "Keep Inbound Data" not allowed. |
| 065 | "Direct update" set. "Unique Data Records" not allowed. |
| 066 | "Direct update" set. "All Char. are Key" not allowed. |
| 067 | "Direct update" set. "Inbound Table as extended Table" not allowed. |
| 068 | |
| 069 | Master data check for &1 must be 'STAGING' or 'STAGING_WITH_MAT' |
| 070 | "All Characteristics are Key" is set. Def. of hash partition not allowed. |
| 071 | "Activate/Compress Data" is not set. Key definition not allowed. |
| 072 | Hash element &1 is not defined in InfoProvider &2 |
| 073 | |
| 074 | Index &1 is equal to primary key |
| 075 | Same secondary index defined twice: &1 and &2 |
| 076 | Secondary index &1 does not contain any objects |
| 077 | Key figure &1 of type &3 with aggregation type &2 not allowed |
| 078 | Planning is not allowed on aDSOs of the current flavor |
| 079 | Planning only supported on InfoObject-based aDSO objects |
| 080 | "Navigational attributes" can only be switched on for characteristics |
| 081 | Setting for master data check of father &1 and child &2 is not compatible |
| 082 | Master data check of unit/currency &1 cannot be 'No Reporting' |
| 083 | Object &1 needs reference to currency object or fixed currency |
| 084 | Object &1 needs reference to unit object or fixed unit |
| 085 | Technical InfoObject &1 cannot be added to the object |
| 086 | Master data check for &1 must not be 'STAGING' or 'STAGING_WITH_MAT' |
| 087 | Compound father &1 of InfoObject &2 is missing |
| 088 | There must be at least one hash-able element |
| 089 | Hash definition contains element (&1) of invalid data type: &2 |
| 090 | Hash definition contains element (&1) of invalid object type: &2 |
| 091 | The partition criteria &1:'&2' and &3:'&4' overlap one another |
| 092 | InfoObject &1 does not exist |
| 093 | "Snapshot Scenario" is set. "Activate Data", "Write Change Log" missing. |
| 094 | "Snapshot Scenario" is set. "Keep Inbound Data" cannot be set. |
| 095 | "Snapshot Scenario" is set. "Unique Data records" cannot be set. |
| 096 | "Snapshot Scenario" is set. "Planning Mode" cannot be set. |
| 097 | "Snapshot Scenario" is set, "Direct Update" cannot be set. |
| 098 | "Snapshot Scenario" is set. "All Characteristics are key" cannot be set. |
| 099 | "Snapshot Scenario" is set. "Extended Storage" cannot be set. |
| 100 | Inventory time reference characteristic has to be set with inventory |
| 101 | Inventory time reference characteristic set, inventory setting missing |
| 102 | Field &1: Length must be larger than &2 |
| 103 | Model reference cannot be resolved. Resource = '&1', UID= '&2' |
| 104 | Partitioning criteria &1: Illegal character in value: &2 |
| 105 | Data type '&1' is not allowed for partitioning |
| 106 | Object '&1' has illegal type for planning on direct-update aDSO |
| 107 | '&1': 'Characteristic as key figure' not allowed in current aDSO flavor |
| 108 | '&1': Illegal object type '&2' for 'Characteristic as key figure' |
| 109 | '&1': 'Characteristic as key figure' is not allowed on key fields |
| 110 | '&1': Compounding error on 'Characteristic as key figure' characteristic |
| 111 | Name of object '&1' too long (>12 characters) for planning |
| 112 | Illegal temperature '&1' for dynamic tiering |
| 113 | Global name must be used for InfoObject '&1' |
| 114 | No partitions specified: "dynamic tiering per partition" not possible |
| 115 | Dynamic tiering not active: "dynamic tiering per partition" not possible |
| 116 | Field &1 of type 'DEC' must not have unit or currency specification |
| 117 | Master data check 'NEVER' not allowed for '&1' due to authorization |
| 118 | Inventory key figure (&1) found, but inventory flag is not activated |
| 119 | '&1' is also needed due to partial time characteristic '&2' |
| 120 | Field &2: key or index must not contain fields of InfoObject type &1 |
| 121 | Defining "ranges" on key figures ('&1') is not permitted |
| 122 | NLS archiving not possible because of data type (&2) of element '&1' |
| 123 | DataStore not modificable as it is generated from InfoObject '&1' |
| 124 | Field &1: precision must not be less than 1. |
| 125 | Field &1: precision less than 16; D16D type can be used instead of D34D |
| 126 | Field &1: number of decimals must not be less than 0. |
| 127 | Field &1 of type &2 must not have currency specification |
| 128 | '&1' not in reporting view; 'Characteristic as key figure' not possible |
| 129 | '&1' is a field; 'Characteristic as key figure' not possible |
| 130 | '&1' has only local SIDs; 'Characteristic as key figure' not possible |
| 131 | DataStore '&1' cannot be added as a PartProvider to a CompositeProvider |
| 132 | Master data check for &1 must be equal to 'NEVER' |
| 133 | 'Characteristic as key figure' can only be used on 'direct update' DSOs |
| 134 | Too many key fields: &1 (max = &2) |
| 135 | Key is too long: &1 (max = &2) |
| 136 | |
| 137 | |
| 141 | Snapshot Scenario is set. Non-cumulative key figures cannot be used. |
| 142 | Object '&1' is of illegal InfoObject type ('&2') for planning |
| 143 | Too many fields fields in index '&1': &2 (max = &3) |
| 144 | Index '&1' is too long: &2 (max = &3) |
| 145 | The lower value of partition '&1' is too long. Max. length: '&2'. |
| 146 | The upper value of partition '&1' is too long. Max. length: '&2'. |
| 147 | The interval value of partition '&1' is too long. Max length: '&2'. |
| 150 | Lower bound of partition '&1' must not contain initial value |
| 153 | |
| 154 | Master data check for '&1' will be changed to '&2' during activation |
| 155 | '&1': Only alpha-numeric characters and '_' are allowed in field names |
| 156 | Having both a hash definition and a key definition is not supported |
| 157 | - Superfluous hash definition has been deleted |
| 158 | - Superfluous hash definition will be deleted |
| 159 | - Remodelling pending on and must be completed first |
| 160 | Field '&1': Prefix '&2' not allowed for fields |
| 161 | "All Char. are Key" is set. Field '&1' with type '&2' is not allowed. |
| 162 | Name of ADSO contains '__'. Therefore no fields are allowed. |
| 165 | Conversion exit '&2' of field '&1' will be ignored in transformation |
| 166 | Field '&1': Conversion exit '&2' cannot be used with data type '&3'. |
| 167 | Field '&1': Conversion exit not allowed because of aggregation '&2' |
| 168 | |
| 210 | Ext. storage cannot be used because of long boundary of partition '&1' |
| 214 | Time reference characteristic '&1' is not a key element of the object |
| 215 | Too many partitions: &1 (max = &2) |
| 216 | '&1': compounding with time characteristic is not allowed |
| 217 | '&1': illegal 'Master Data Check'-mode for TIME characteristic |
| 220 | Unload priority of table '&1' will be changed from &2 to &3 |
| 221 | Unload priority of table '&1' has been changed from &2 to &3 |
| 225 | |
| 226 | Temporal hierarchy join InfoObj. '&1' is not allowed in DataStore Object |
| 227 | Error during table-width check for DB platform '&1' |
| 228 | Critical table/view width &1 for DB platform '&2' (see long text) |
| 229 | Transient InfoObject '&1' is not allowed in DataStore Object |
| 232 | '&1': A field name must not contain sequences of '_'. |
| 237 | Characteristic &1 is of type &2. Nav. attributes ignored in extraction. |