RSSEM - Nachrichten f�r SEM
The following messages are stored in message class RSSEM: Nachrichten f�r SEM.
It is part of development package RSSEM in software component BW-WHM-DBA. This development package consists of objects that can be grouped under "SEM Connection to BW".
It is part of development package RSSEM in software component BW-WHM-DBA. This development package consists of objects that can be grouped under "SEM Connection to BW".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Program error &1 &2 &3 &4 |
| 001 | Program is inconsistent -> see long text |
| 002 | The document could not be deleted |
| 003 | The document could not be updated |
| 004 | No URL document could be created |
| 005 | Insufficient authorization for RFC function module '&1' |
| 020 | &1&2&3&4 |
| 021 | System failure when calling destination &1 |
| 022 | Communication failure when calling destination &1 |
| 023 | Insufficient authorization for activity: &1 |
| 024 | Back destination &1 not found |
| 025 | Back destination &1 not supported in remote conversion |
| 050 | ----------------- Master Data / Hierarchy Access ------------------------ |
| 051 | Remote InfoObject &1 does not have a usable hierarchy DataSource |
| 052 | Remote InfoObject &1 does not have a unique hierarchy DataSource |
| 053 | RFC destination for logical system &1 could not be determined |
| 054 | Error during access to hierarchies of &1 (DataSource &2/&3) |
| 055 | System error during access to DataSource &1 in System &2 |
| 056 | Communication error during access to DataSource &1 in System &2 |
| 057 | Messages during access to DataSouce &1 in system &2: |
| 058 | Error while executing transfer rules (&1, DataSource &2/&3) |
| 059 | Transfer rule for hierarchy for &1 is not defined/not supported |
| 060 | InfoObject &1 is not type-compatible with field &2 |
| 061 | Transfer rule for node segment for &1 is not defined/not supported |
| 100 | ----------------- SEM-Business Information Collection ------------------- |
| 101 | Error while loading document |
| 150 | ----------------- SEM Business Consolidation ---------------------------- |
| 151 | No SEM destination is known for virtual cube &1 |
| 152 | Virtual cube unknown in SEM destination &2 |
| 153 | Error &1 while calling SEM destination "&2". See SAP Note 2651241. |
| 160 | Error during access to SEM destination |
| 161 | Wrong format used to request InfoObject &1 |
| 162 | Remote transfer scope change no longer possible, already transported |
| 163 | Copy method &1/&2 references source consolidation area &3 |
| 164 | Delete copy method &1/&2 or also select consolidation area &3 |
| 165 | Messages from check of SEM-BCS consolidation area &1: |
| 166 | Messages from check of SEM-BCS data basis &1: |
| 200 | No authority to access BCS data model: system &1 / user &2 |
| 201 | BCS transport &1 has not arrived in this system (&2) |
| 202 | No compatible version of add-on BCS4HANA installed on system &1 |
| 203 | Databasis &1 has not yet been imported into this system (&2) |
| 204 | Databasis &1: Conversion post processing pending in this system (&2) |
| 205 | Consolidation area &1 has not been imported into this system (&2) yet |
| 206 | Import status of request &1: &2 (&3), return code: &4 |
| 207 | Installation error: Function module &1 missing in target &2 |
| 208 | BCS4HANA not reached at back destination &1: &2 |
| 209 | Another remote transfer scope is currently active: &1 not &2 |
| 210 | No active remote transfer scope found |
| 211 | Remote transfer scope &1 not active in BCS destination &2 |
| 212 | Error in BCS source/target table mapping for remote transfer scope &1 |
| 213 | Function module &1 missing or not current in RFC destination '&2' |
| 214 | Consolidation area &1 is not correctly generated (&2) |
| 215 | Error when preparing SID mapping for field name &1 in target (&2) |
| 216 | Remote transfer scope &1 does not contain any BCS objects yet |
| 217 | Use BCS request &1 which has been recorded before |
| 218 | BCS transport recording cancelled |
| 219 | Request &1 "&2" recorded successfully |
| 220 | No authorization to transport BCS objects |
| 221 | Remote transfer scope &1 inconsistent. BCS transport cannot be recorded. |
| 222 | BCS transport &1 has been imported successfully into the target |
| 223 | BCS transport &1 has not yet been imported successfully into the target |
| 224 | The SEM-BCS system is now locked against changes |
| 225 | The SEM-BCS system is now unlocked, changes possible |
| 226 | No authorization to lock or unlock SEM-BCS |
| 227 | No read authorization for SEM-BCS consolidation areas |
| 228 | Assigned BCS transport &1 does not exist |
| 229 | Previous request &1 not found or inconsistent |
| 230 | Transfer scope &1 inconsistent: Contained cons. area &2 no longer exists |
| 231 | Selected cons. areas/data bases cannot be in the same tranfer scope |
| 232 | Type of request &1 is wrong (must be Transport of Copies) |
| 233 | BCS Data basis &1 already exists in target, cannot be selected |
| 234 | BCS consolidation area &1 already exists in target, cannot be selected |
| 235 | Databasis &1 successfully re-linked to its converted BW4 InfoProviders |
| 236 | Databasis &1 failed to re-link to its converted BW4 InfoProviders |
| 237 | Databasis &1 is locked by another user or process, post process pending |
| 238 | Some intervals already exist in target for number range object &1 |
| 239 | Update of all BCS number range intervals from source system stopped |
| 240 | To take over number ranges from source, first delete intervals in target |
| 241 | Number range intervals for object &1 are locked in target &2 |
| 242 | Source intervals for object &1 are inconsistent. No update in target. |
| 243 | Intervals for number range object &1 were updated successfully |
| 244 | All BCS number ranges copied successfully to target &1 |
| 245 | Assignment of role "Document Type" must be unique |
| 246 | Remote transfer scope &1 has not yet been transported |
| 247 | Back destination has to be unique within one remote transfer scope |
| 248 | Assignment of transport request to transfer scope &1 is not consistent |
| 249 | Cons. area &1 is contained in another transfer scope (request &2) |