RSO_RES_ADSO - Datastore Object
The following messages are stored in message class RSO_RES_ADSO: Datastore Object.
It is part of development package RSO_RES_ADSO in software component BW-WHM-MTD. This development package consists of objects that can be grouped under "BW: ResourceDatastoreObject".
It is part of development package RSO_RES_ADSO in software component BW-WHM-MTD. This development package consists of objects that can be grouped under "BW: ResourceDatastoreObject".
Message Nr ▲ | Message Text |
|---|---|
| 000 | &1 &2 &3 &4 |
| 001 | DataStore object '&1' does not exist |
| 002 | DataStore object '&1' already exists |
| 003 | Version '&2' of DataStore object '&1' does not exist or cannot be loaded |
| 004 | Version '&2' of DataStore object '&1' does not exist in database |
| 005 | Enter a name for the DataStore object |
| 006 | Wrong version '&1' found. Version '&2' was expected. |
| 007 | Providers of type ADSO are only supported on SAP Hana: &1 |
| 008 | Illegal object version: &1 |
| 009 | M and A version of DataStore object '&1' are different |
| 010 | Save DataStore object '&1' |
| 011 | DataStore object '&1' saved |
| 012 | Error while saving DataStore object '&1' |
| 013 | Error while saving dependent object '&1' |
| 014 | Characteristic &1: DataStore object &2 (master data check) does not exist |
| 015 | DataStore object &1 (master data check) must contain characteristic &2 |
| 016 | DataStore object &1 (master data check) must not contain char. &2 in key |
| 017 | No InfoObject name specified for element '&1' |
| 018 | InfoObject '&1' does not exist |
| 019 | Could not save: '&1' |
| 020 | Check DatastoreObject '&1' |
| 021 | DataStore object '&1' checked |
| 022 | Error while checking DataStore object '&1' |
| 023 | |
| 024 | |
| 025 | |
| 026 | |
| 027 | |
| 028 | |
| 029 | |
| 030 | Activate DataStore object '&1' |
| 031 | DataStore object '&1' activated |
| 032 | Error while activating DataStore object '&1' |
| 033 | Cannot activate: DataStore object '&1' has not been checked |
| 034 | DataStore object '&1' needs to be activated; 'M' version exists |
| 035 | &1 (&2) was set to inactive because of impact analysis |
| 036 | DataStore object '&1': DB views recreated successfully |
| 037 | DataStore object '&1': Error during recreation of DB views |
| 038 | |
| 039 | |
| 040 | Deleting DataStore object '&1' |
| 041 | DataStore object '&1' deleted |
| 042 | Error while deleting DataStore object '&1' |
| 043 | Cannot delete: DataStore object '&1' is still being used |
| 050 | DataStore object '&1' is not locked |
| 051 | DataStore object '&1' could not be locked |
| 052 | DataStore object '&1' is locked by another user |
| 053 | DataStore object '&1': lock handle failure |
| 054 | DataStore object '&1' is already part of different transport |
| 060 | Reset DataStore object '&1' to the active version |
| 061 | DataStore object '&1' reset to active version |
| 062 | Error while resetting DataStore object '&1' to active version |
| 070 | You are not authorized to display DataStore object '&1' |
| 071 | You are not authorized to change DataStore object '&1' |
| 075 | Datastore object '&1': check for content merge is not supported |
| 080 | Package of DataStore object '&1' is not transportable |
| 081 | DataStore object '&1' is not transportable |
| 090 | Error while changing the database tables (table &1) |
| 091 | All data in DataStore object '&1' has been deleted |
| 092 | Error while truncating database table '&1' |
| 093 | Propagation of deletion is only possible for providers with Changelog |
| 094 | Value of '&1' changed to '&2' due to propagation of deletion |
| 095 | Overlap between deletion cirteria and archiving criteria |
| 096 | DataStore object &1 is in planning mode. Selective deletion not possible. |
| 097 | Filter object '&2' is not part of DataStore object '&1' |
| 098 | Filter object '&2' is not part of the key (see long text) |
| 099 | No 'selective deletion' possible (see long text) |
| 100 | Invalid URI format. Cannot retrieve name of DataStore object. |
| 101 | Model of DataStore object '&1' could not be loaded |
| 105 | SIDs have to be checked during loading into DataStore object '&1' |
| 106 | DataStore object '&1' contains non-cumulative key figure(s) |
| 110 | Error while building the DTA structure of provider &1 |
| 111 | Error while building the DTA_PRO structure of field &2 of provider &1 |
| 112 | Metadata of InfoObject &2 of provider &1 not found |
| 113 | Field &2 of provider &1 cannot be converted into transient InfoObject |
| 114 | Error '&2' during metadata operation in function '&1' |
| 115 | Metadata inconsistency in method '&1'. Location: '&2' |
| 116 | Field name '&1' is too long |
| 117 | Field '&1' is not visible in reporting |
| 118 | Change data type from &1 to &2 for direct reporting |
| 119 | Change length from &1 to &2 for direct reporting |
| 120 | Invalid URI format. Unable to retrieve DataStore object (advanced) name. |
| 121 | Change decimals from &1 to &2 for direct reporting |
| 122 | InfoObject '&1' is not visible in reporting |
| 123 | - set master data check <> 'No Master Data Check/No Reporting' |
| 124 | Invalid value '&1' for '&2' |
| 125 | - object is XXL-attribute |
| 126 | Association of InfoObject '&1' could not be resolved |
| 127 | - object is defined as attribute-only |
| 128 | - the corresponding unit InfoObject ('&1') is defined as attribute-only |
| 130 | Error while deleting the old remodeling rules for provider &1 |
| 131 | Error while creating a new remodeling rule for provider &1 |
| 132 | Error while adding an operation to a remodeling rule for provider &1 |
| 133 | Error during the activation of the remodeling rule for provider &1 |
| 134 | Remodelling rule &1 has been created instead of activation |
| 135 | Error while scheduling the remodeling rule for provider &1 |
| 136 | DataStore object &1 cannot be changed because of pending remodeling rule |
| 137 | Remodeling rule of DataStore object &1 deleted |
| 138 | - DataStore activation has been switched off |
| 139 | - SID materialization has been switched on for &1 |
| 140 | - &1 (not implemented) |
| 141 | Illegal change of time-reference characteristic: old='&1' new='&2' |
| 142 | Time is inconsistent => Non-cumulative handling cannot be switched on |
| 143 | - non-cumulative handling has been switched on |
| 144 | - validity object '&1' has been added/removed |
| 145 | - time char. '&1' has been added to NCUM ADSO |
| 146 | - &1: Masterdata check has been switched on or new IObj. is compounded |
| 147 | 'FISCVARNT' cannot be added to a NCUM-ADSO that already has entries |
| 148 | - '&1' has been deleted from the key |
| 149 | - '&1' has been added to the key |
| 150 | - data type of '&1' has been changed |
| 151 | - partitioning has been switched on |
| 152 | - partitioning has been switched off |
| 153 | - field for semantic partitioning has been changed |
| 154 | - criteria for semantic partitioning has been changed |
| 155 | Table '&1' filled from shadow table '&2' (#packages = &3) |
| 156 | Table '&1' renamed as shadow table '&2' |
| 157 | Table '&1' deleted (&2) |
| 158 | Error '&2' while deleting table '&1' (&3) |
| 159 | Table '&1' restored from shadow table '&2' |
| 160 | - Conversion between these types of DataStore objects is not allowed |
| 161 | Remodeling of &1 might be necessary after activation |
| 162 | &1 cannot be activated if DataStore is not empty |
| 163 | - key definition has been changed |
| 164 | - hash definition has been changed |
| 165 | - extended storage has been switched on |
| 166 | - extended storage has been switched off |
| 167 | Extended storage is configured but not online |
| 168 | Restrictions on characteristics have been changed |
| 169 | Restrictions on &1 are in conflict with posted data of table &2 |
| 170 | Table '&1' moved to extended storage |
| 171 | - key field &1 has been added |
| 172 | - key field &1 has been removed |
| 173 | No source characteristic for time derivation |
| 174 | InfoObject &1: There is no SID for value '&2' |
| 175 | InfoObject &1: Incorrect materialized SID (&3) found for value '&2' |
| 176 | Further errors will be skipped because of MAX-ERROR-COUNT = &1 |
| 177 | No finest characteristic for time derivation found |
| 178 | No source characteristic for time derivation specified |
| 179 | Source value '&1', Variant &2: Inconsistent derived times: &3 |
| 180 | Messages while checking table &1: |
| 181 | Variant &1: Inconsistent time values: &2 |
| 182 | Remodeling required as compounding of &1 has changed. Check SID. |
| 183 | Remodeling pending on &1 and must be completed before activation |
| 184 | Table &1 already contains data. Cannot copy from shadow table &2. |
| 185 | aDSO '&1' is a member of '&2': No group field name specified |
| 186 | aDSO '&1' is a member of '&2': Deletion of '&3' not allowed |
| 187 | aDSO '&1' is a member of '&2': Ranges on field '&3' must not be changed |
| 188 | NLS not possible; aDSO '&1' contains fields with names greater than &2 |
| 189 | aDSO '&1' is reference object of semantic group '&2' |
| 190 | Dynamic tiering changed: manual changes may be needed (see Note 2292664) |
| 191 | Dynamic tiering is switched on: Usage depends on system settings |
| 192 | Remodelling pending on &1 and must be completed before 'Reset to active' |
| 193 | - extended storage has been changed from mode '&1' to mode '&2' |
| 195 | DB-Views of aDSO '&1' are not up to date. Please run 'RSDG_ADSO_ACTIVATE' |
| 198 | Activation not possible; semantic group specification has been changed |
| 200 | Objects of type '&1' cannot be used as template |
| 201 | Unit/curr. field &1 for field &2 has wrong data type/length: &3, &4 |
| 202 | Field &1, used as unit/currency field for field &2, could not be found |
| 203 | Characteristic &1 has been added to key because of compounding with &2 |
| 204 | Error while deriving partition criteria |
| 205 | Target flavor '&1' is not supported for template '&2' (TLOGO = '&3') |
| 206 | Target flavor specification is not supported for template of type '&1' |
| 210 | Running repair-algorithm '&1' |
| 211 | Running repair-algorithm '&1' in simulation mode |
| 212 | Inconsistency found for '&1': Fields are not only permuted |
| 213 | DataStore object '&1': Start processing |
| 214 | - Key changed in model definition |
| 215 | - Key will be changed in model definition |
| 216 | - Object activated |
| 217 | - Object will be activated |
| 218 | - Processing finished |
| 219 | - Object '&1'(&2) set to inactive because of impact |
| 220 | - Object '&1'(&2) will be set to inactive because of impact |
| 221 | - Object '&1'(&2) activated because of impact |
| 222 | - Object '&1'(&2) will be activated because of impact |
| 223 | DataStore object '&1' (objvers &2): Start processing |
| 224 | - No hash definition found on DB |
| 225 | No simulation possible for repair algorithm '&1' |
| 226 | - Info about semantic group '&1' removed in version '&2' |
| 227 | - Info about semantic group '&1' will be removed in version '&2' |
| 228 | - Info about semantic group '&1' added |
| 229 | - Info about semantic group '&1' will be added |
| 230 | Active version of DataStore object '&1' does not exist. Activate first. |
| 231 | DataStore object '&1' does not exist. Update not possible. |
| 232 | Info about semantic group cannot be changed in the productive system |
| 233 | Correction might be incomplete as not all groups could be locked |
| 234 | - Reference to UOM object '&2' will be added to aDSO '&1' |
| 235 | - Reference to UOM object '&2' has been added to aDSO '&1' |
| 236 | DB view for extraction of aDSO '&1' is corrupt |
| 237 | DB view for reporting of aDSO '&1' is corrupt |
| 238 | - SID Determination Mode of '&1' changed from '&2' to '&3' |
| 239 | - SID Determination Mode of '&1' will be changed from '&2' to '&3' |
| 240 | '&1': Multiple initialization of reference point |
| 241 | '&1': Error when updating in the validity table |
| 242 | '&1': Error when deleting from the validity table |
| 243 | '&1': Error when inserting new reference point records |
| 244 | '&1': Error when updating reference point records |
| 245 | '&1': Error when writing initialization records to the change log |
| 246 | '&1': Error when creating sequence for change log writing |
| 247 | '&1': Error when dropping sequence for change log writing |
| 248 | '&1': Error when deleting records from the reference point table |
| 249 | |
| 250 | |
| 255 | Time derivation: Value '&1' of '0FISCVARNT' is not allowed. |
| 266 | Field &1: Extending a field of type NUMC is not allowed |
| 267 | Field &1: Changing the conversion routine is not allowed |
| 268 | Field &1: Changing data type to or from NUMC is not allowed |
| 269 | - Element '&1' has been deleted |
| 270 | Description table: No dimension with name '&1' found |
| 271 | Description table: No element with name '&1' found |
| 274 | Restrictions on &1 conflict with new (initial) field of table &2 |
| 279 | 'M'-version cannot be read because activation is running |
| 280 | Conversion of flavor only possible as there is no delta DTP. |
| 281 | Conversion of flavor not possible as a delta DTP exists. |
| 300 | Element '&1' with criteria must not be shortened |
| 301 | Partitioning element '&1' must not be shortened |
| 306 | DSO &1: Table '&2' contains &3 duplicate entries |
| 307 | DSO &1: all duplicate entries of table '&2' have been aggregated |
| 644 | Unit of Measure DataStore &1 cannot be created/updated/deleted using API |
| 651 | SQL Error Code &1 during creation of Table/View &2. |
| 652 | Details of SQL Error:&1&2&3&4 |