BWSD - Nachrichten zum Szenariotransfer
The following messages are stored in message class BWSD: Nachrichten zum Szenariotransfer.
It is part of development package BW_SDATA in software component BW. This development package consists of objects that can be grouped under "Transfer of BW Objects and Scenario Data".
It is part of development package BW_SDATA in software component BW. This development package consists of objects that can be grouped under "Transfer of BW Objects and Scenario Data".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Serialized expression is empty |
| 002 | Deserialization returns empty parameter list |
| 003 | The parameter list must not be left empty for serialization |
| 004 | Error during serialization |
| 005 | Serialization returns empty expression |
| 006 | No header data found for query element &1 |
| 007 | Internal name of query element &1 not found |
| 008 | Error while reading query element information (&1) |
| 009 | InfoProvider type &1 is not supported |
| 010 | InfoProvider &1 is invalid or does not exist |
| 011 | No InfoProvider found for query &1 (&2) |
| 012 | Data request &1 for InfoCube &2 (request ID - &3) |
| 013 | Meta definition for InfoCube &1 |
| 014 | Master data of type 'Attribute' for characteristic &1 |
| 015 | Master data of type 'Text' for characteristic &1 |
| 016 | Hierarchy version (&1) for hierarchy &2 and characteristic &3 |
| 017 | Meta definition for InfoObject &1 |
| 018 | Hierarchy &1 for characteristic &2 |
| 019 | Error during RFC call with destination &1 |
| 020 | &1 |
| 021 | InfoObject &1 is invalid or does not exist |
| 022 | Collection for start object &1 (&2) active (&3/&4) |
| 023 | Status determination for target locations started |
| 024 | Status determination for target locations finished |
| 025 | User &1 is not authorized to load element object &2 (&3) |
| 026 | User &1 is not authorized to save element object &2 (&3) |
| 027 | Target location: External system &1 via RFC destination &2 |
| 028 | System &1 (&2) does not support the services of the BW transfer tool |
| 029 | Upper limit reached for block iteration for &1 (&2) |
| 030 | Error while deleting file &1 |
| 031 | File name cannot be created |
| 032 | Data instance is initial. Saving process will terminate. |
| 033 | Data stream is empty. No further processing required. |
| 034 | Error during file export (error number &1) |
| 035 | Data reference for parameter &1 contains errors |
| 036 | Error while reading master data (&1) |
| 037 | Error while reading transaction data (&1) |
| 038 | Error while reading metadata (&1) |
| 039 | Error while creating the object |
| 040 | Error while creating the object (&1) |
| 041 | Error while writing master data (&1) |
| 042 | Error while writing transaction data (&1) |
| 043 | Error during file import (&1) |
| 044 | Error while decompressing the data (&1) |
| 045 | Error while compressing the data (&1) |
| 046 | Post-processing of writing successful (&1) |
| 047 | Post-processing of writing contained errors (&1) |
| 048 | Error while activating the object (&1) |
| 049 | No InfoObjects found for activation (main object: &1) |
| 050 | Associated database table not found (&1; &2) |
| 051 | Transfer objects are being initialized... |
| 052 | Transfer parameters are being updated... |
| 053 | The data in the element object is initial |
| 054 | New object transformation created (&1 / &2) |
| 055 | Object transformation saved |
| 056 | Name replacements saved (&1) |
| 057 | Saving object transformation ended with errors |
| 058 | Query element &1 not created correctly |
| 059 | Query element &1 created correctly |
| 060 | Data request &1 for DataStore object &2 (request ID - &3) |
| 061 | Meta-definition for DataStore object &1 |
| 062 | Data for DataStore object &1 (table: &2) |
| 063 | Error while writing to DataStore object &1 (table: &2) |
| 064 | Data written to DataStore object (records: &1; table: &2) |
| 065 | Meta-definition for MultiProvider &1 |
| 066 | Error while reading the hierarchy (&1) |
| 067 | Error while writing the hierarchy (&1) |
| 068 | Hierarchy deleted (&1) |
| 069 | Error while deleting hierarchy (&1) |
| 070 | Object &1 does not exist. Data cannot be written. (&2) |
| 071 | Elementary object &1 (&2) not found |
| 072 | Error writing a data package to RFC destination &1 |
| 073 | Elementary object &1 (&2/&3/&4) |
| 074 | Parameters for block handling: &1/&2/&3/&4 |
| 075 | Parameter for data package: &1 |
| 076 | Local system |
| 077 | Remote system &1 using RFC destination &2 |
| 078 | Database storage (local) |
| 079 | Database storage (remote system &1/RFC destination &2) |
| 080 | File storage (PC) |
| 081 | Elementary instance is initial. Loading process canceled. |
| 082 | Could not import transfer parameter |
| 083 | Could not export transfer parameter |
| 084 | Error while reading a data package in RFC destination &1 |
| 085 | Error while preparing transfer (&1) |
| 086 | Transfer active for &1 |
| 087 | Path constellation is not valid |
| 088 | Error while saving the configuration (&1) |
| 089 | Configuration is not bound |
| 090 | Configuration &1 saved |
| 091 | Configuration &1 has not been modified |
| 092 | Configuration not found |
| 093 | Error while deleting configuration (&1) |
| 094 | Configuration &1 deleted |
| 095 | Error while reading the configuration (&1) |
| 096 | Configuration &1 read |
| 097 | Configuration &1 with mode &2 cannot be edited in this system |
| 098 | Name &1 already exists. Choose a different name. |
| 099 | The first name character &1 is reserved. Object not saved. |
| 100 | Log &1 not found |
| 101 | Entries deleted from log table &1: &2 |
| 102 | Prepare exit implementation for variable &1 |
| 103 | Prepare class &1 for master data access |
| 104 | Prepare function module &1 for data access of VirtualProvider |
| 105 | Prepare data transfer process &1 for data access of VirtualProvider |
| 106 | Prepare BAPI on source system &1 for data access of VirtualProvider |
| 107 | Prepare HANA model &1 for data access of VirtualProvider |
| 108 | Prepare delta cache class &1 for VirtualProvider |
| 109 | Prepare source system &2 and InfoSource &1 for VirtualProvider |
| 110 | Metadefinition for trace &1 |
| 111 | RSTT trace &1 for trace area &2 |
| 112 | Writing RSTT related data failed (&1) |
| 113 | Metadefinition for trace package &1 |
| 114 | Metadefinition for trace job &1 |
| 115 | RSTT trace package &1 for trace area &2 |
| 116 | RSTT trace job &1 for trace area &2 |
| 117 | Metadefinition for test reference variant &1 |
| 118 | RSTT test reference variant &1 |
| 119 | Metadefinition for object replacement variant &1 |
| 120 | RSTT object replacement variant &1 |
| 121 | Data request &1 for advanced DataStore object &2 (request ID - &3) |
| 122 | Metadefinition for advanced DataStore object &1 |
| 123 | Prepare InfoProvider &1 of type &2 |
| 124 | Database Table &1 |
| 125 | Error while reading data (&1) |
| 126 | Error while writing data (&1) |
| 127 | Error while writing to table &1 |
| 128 | Data written to table &1 (records: &2) |
| 129 | Prepare definition for database table &1 |
| 130 | Error while checking allowed characters: &1 |
| 131 | Meta-definition for CompositeProvider &1 |
| 132 | Meta-definition for aggregation level &1 |
| 133 | Parallel master data update successful: &1 records; &2 processes |
| 134 | Parallel master data update failed: &1 recs; &2 processes failed, &3 ok |
| 135 | Sequential master data update successful: &1 records |
| 136 | Sequential master data update failed: &1 records |
| 137 | Batch job &1 released (Number: &2; GUID: &3) |
| 138 | Release of batch job &1 failed (ERROR: &2; GUID: &3) |
| 139 | Execution of transfer failed (&1) |
| 140 | Log &1 initialized |
| 141 | Object transfer started: &1/&2 (&3/&4) |
| 142 | &1 table entries added to transport request &2 |
| 143 | Error during enhancement of transport request &1 |
| 144 | Transport request &1 used for table entries is invalid |
| 145 | Full transactional data of InfoCube &1 |
| 146 | Name &1 (&2) already exists in namespace for object type &3 |
| 147 | Name &1 (&2) already exists as source object name (&3) |
| 148 | Type &1 does not support a type switch |
| 149 | Please add a valid object name to change the object type |
| 150 | Full transactional data of DataStore object (advanced) &1 |
| 151 | Meta definition for planning function &1 |
| 152 | Planning function &1 is invalid or does not exist yet |
| 153 | No header data found for InfoProvider &1 |
| 154 | Error while writing planning function &1 |
| 155 | Planning function type &1 does not exist |
| 156 | Meta definition for planning sequence &1 |
| 157 | Error while writing planning sequence &1 |
| 158 | Multiple filters found for ID &1 |
| 159 | Planning function might require manual changes |
| 160 | Characteristic relationships and central settings of &1 |
| 161 | Prepare class &2 for characteristic relationship &1 |
| 162 | Prepare class &2 for data slice &1 |
| 163 | Data slices of &1 |
| 164 | CompositeProvider &1 activated successfully |
| 165 | Activation of CompositeProvider &1 failed |
| 166 | Storage of CompositeProvider &1 failed |
| 181 | Metadefinition for CDS view &1 (type DDLS) |
| 182 | Metadefinition for ABAP Data Control Language Source &1 (type DCLS) |
| 183 | Read of meta definition failed (type &1) |
| 184 | ABAP Data Control Language Source &1 saved successfully |
| 185 | CDS view &1 saved successfully |
| 186 | CDS view &1 activated successfully |
| 187 | ABAP Data Control Language Source &1 activated successfully |
| 188 | Problems occured during extraction of table definition |
| 189 | Problems occured during saving of table definition (&1) |
| 190 | Hierarchy (&1) created successfully |
| 191 | Problems occured during activation of table definition |
| 192 | Problems occured during creation of TADIR entry |
| 193 | Table definition activated successfully |
| 194 | Metadefinition for data element &1 (type DTEL) |
| 195 | Metadefinition for domain &1 (type DOMA) |
| 200 | Call position &1 modified with system-specific settings (&2) |
| 201 | CDS view &1 activated successfully |
| 202 | Data element &1 activated successfully |
| 203 | Activation of data element &1 failed |
| 204 | Loading of data element &1 failed |
| 205 | Domain &1 activated successfully |
| 206 | Activation of domain &1 failed |
| 207 | Loading of domain &1 failed |
| 208 | Creation or update of data element &1 failed |
| 209 | Creation or update of domain &1 failed |