SAP ABAP Message Class RSO (BW Repository)
Basic Data
Hierarchy
☛
SAP_BW (Software Component) SAP Business Warehouse
⤷
BW-WHM-MTD (Application Component) Metadata (Repository)
⤷
RSO (Package) BW Repository: Infastructure and Core GUI Components
⤷
⤷
Attributes
| Message class | RSO | |
| Short Description | BW Repository | |
| Changed On | 20140121 | |
| Last Changed At | 101802 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | -------------- Message for matching A/D version InfoObjects ------------- | Space: object requires documentation | ||
| 2 | InfoObject &1: active and revised version are different | Space: object requires documentation | ||
| 3 | InfoObject &1: &2 was changed inappropriately (from '&3' to '&4') | Space: object requires documentation | ||
| 4 | InfoObject &1: SAP version is protected - you cannot change object | Space: object requires documentation | ||
| 5 | InfoObject &1: '&2' will not be changed from '&3' to '&4' | Space: object requires documentation | ||
| 6 | InfoObject &1: '&2' is changed from '&3' to '&4' | Space: object requires documentation | ||
| 7 | In the Content system, the function "Transfer Content" is not allowed | Space: object requires documentation | ||
| 8 | InfoObject &1: InfoObject &2 is included again in the compounding | Space: object requires documentation | ||
| 9 | InfoObject &1: InfoObject &2 is included again as attribute | Space: object requires documentation | ||
| 10 | InfoObject &1: InfoObject &2 is included again as navigation attribute | Space: object requires documentation | ||
| 11 | Attribute &1: &2 will not be changed from &3 to &4 | Space: object requires documentation | ||
| 12 | Attribute &1: &2 is changed from &3 to &4 | Space: object requires documentation | ||
| 13 | The versions (&2 and &3) of InfoObject &1 agree | Space: object requires documentation | ||
| 14 | Manual match of InfoObject &1 | Space: object requires documentation | ||
| 15 | InfoObject &1 matched with Content version | Space: object requires documentation | ||
| 16 | InfoObject &1 copied from Content version | Space: object requires documentation | ||
| 17 | Error when matching InfoObject &1 with Content version | Space: object requires documentation | ||
| 18 | InfoObject &1 used and activated (from modified version) | Space: object requires documentation | ||
| 19 | InfoObject &1: InfoObject &2 is included as an ext. hierarchy charstic. | Space: object requires documentation | ||
| 20 | Action canceled | The short text describes the object sufficiently | ||
| 21 | No hits found with this search term | The short text describes the object sufficiently | ||
| 22 | ------ Messages for comparing A/D version of InfoObjectCatalog ------ | Space: object requires documentation | ||
| 23 | Still have available texts on InfoObjectCatalog &1 in language &2 | Space: object requires documentation | ||
| 24 | InfoObject &1 entered in InfoObjectCatalog &2 | Space: object requires documentation | ||
| 25 | The versions of InfoObjCat &1 concurs in all properties | Space: object requires documentation | ||
| 26 | ---------- Messages for interface Repository ----------------------- | Space: object requires documentation | ||
| 27 | No objects are loaded in the Repository (main memory) | Space: object requires documentation | ||
| 28 | Maintenance of object '&1' of type '&2' is not yet available | Space: object requires documentation | ||
| 29 | Node &1 is not available in tree | Space: object requires documentation | ||
| 30 | No document found for object &2 of type &1 | Space: object requires documentation | ||
| 31 | No documents available for type &1 of object &2 | Space: object requires documentation | ||
| 32 | No corresponding entries were found in tree | Space: object requires documentation | ||
| 33 | The comparison of versions &2/&3 is 'not available' for type '&1' | Space: object requires documentation | ||
| 34 | You are not authorized to change documents for object &2 (&1) | Space: object requires documentation | ||
| 35 | Further objects will be sought only &1 level deeper | The short text describes the object sufficiently | ||
| 36 | InfoArea &2 of InfoCube &1 does not exist | Space: object requires documentation | ||
| 37 | Choose one or more source systems | Space: object requires documentation | ||
| 38 | Could not open file on the application server: &1 | Space: object requires documentation | ||
| 39 | File &1 was written successfully to the application server | Space: object requires documentation | ||
| 40 | Search index is not available. Start structure via 'Extras' menu | Space: object requires documentation | ||
| 41 | ======================================================================== | Space: object requires documentation | ||
| 42 | ------------ Messages for Controls ----------------------------------- | Space: object requires documentation | ||
| 43 | Error &1 occurred in display control | Space: object requires documentation | ||
| 44 | ------------ BW Repository Messages ---------------------------------- | Space: object requires documentation | ||
| 45 | Object type '&1' of object '&2' is not yet supported | Space: object requires documentation | ||
| 46 | Object '&1' (&2) of type '&3' is not available in version '&4' | Space: object requires documentation | ||
| 47 | Object type (TLOGO) is missing | Space: object requires documentation | ||
| 48 | Name of object of type '&1' is missing | Space: object requires documentation | ||
| 49 | Where-used list for object &1 (&2) not yet implemented | Space: object requires documentation | ||
| 50 | Function module &1 is not active | Space: object requires documentation | ||
| 51 | Object type (TLOGO) of object '&1' is missing | Space: object requires documentation | ||
| 52 | Name of object of type '&1' is missing | Space: object requires documentation | ||
| 53 | Object '&1' of type '&2' already exists in tree | Space: object requires documentation | ||
| 54 | Activation of Content with type &1 (FB &2) is not yet available | Space: object requires documentation | ||
| 55 | Object '&1' of type '&2' already exists in network | Space: object requires documentation | ||
| 56 | Root object '&1' (type '&2') of an association is not yet available | Space: object requires documentation | ||
| 57 | Input help for objects of type '&1' (&2) is not yet available | Space: object requires documentation | ||
| 58 | No objects of type '&1' (&2) are available in version &3 | Space: object requires documentation | ||
| 59 | Could not export file '&1' (error &2) | Space: object requires documentation | ||
| 60 | The file '&1' could not be opened during export | Space: object requires documentation | ||
| 61 | File '&1' could not be written during export | Space: object requires documentation | ||
| 62 | Error occurred in frontend (GUI) when exporting file '&1' | Space: object requires documentation | ||
| 63 | There is no data to export | Space: object requires documentation | ||
| 64 | Approx. &1 MByte of data will be transported | Space: object requires documentation | ||
| 65 | Target object '&1' (type '&2') of an association is not available | Space: object requires documentation | ||
| 66 | No relevant data was found | Space: object requires documentation | ||
| 67 | The higher-level application component &1 is missing from &2 | Space: object requires documentation | ||
| 68 | Object '&1::&2' refers to the invalid object '&3::&4' | Space: object requires documentation | ||
| 69 | The object '&1::&2' cannot be activated (see long text) | The short text describes the object sufficiently | ||
| 70 | Job &1 (&2) could not be started (&3) | Space: object requires documentation | ||
| 71 | Job &1 (&2) was started successfully | Space: object requires documentation | ||
| 72 | Installation could not be started as job &1 (&2) | Space: object requires documentation | ||
| 73 | Installation was successfully started as job &1 (&2) | Space: object requires documentation | ||
| 74 | Job &1 in group &2 could not be scheduled (error &3) | Space: object requires documentation | ||
| 75 | Program &3 could not be scheduled in job &1, no. &2 (&4) | Space: object requires documentation | ||
| 76 | No reversal can be determined for association &1 | Space: object requires documentation | ||
| 77 | The collecting process was successfullly started as job &1 (&2) | Space: object requires documentation | ||
| 78 | Could not start the collecting process as job &1 (&2) | Space: object requires documentation | ||
| 79 | InfoPackage &1 does not exist. Data was not loaded. | Space: object requires documentation | ||
| 80 | InfoPackage &1 is locked. Data was not loaded. | Space: object requires documentation | ||
| 81 | The loading process for InfoPackage &1 is already running | Space: object requires documentation | ||
| 82 | The loading process for InfoPackage &1 is already scheduled | Space: object requires documentation | ||
| 83 | The data files could not be written (&1) | Space: object requires documentation | ||
| 84 | Could not create source system '&1' (&2): Cause &3 | Space: object requires documentation | ||
| 85 | Object &1 (&2) could not be collected for object &3 (&4) | Space: object requires documentation | ||
| 86 | Transfer of &1(&2) necessary, due to &3(&4) | Space: object requires documentation | ||
| 87 | Transport of &1(&2) necessary, due to &3(&4) | Space: object requires documentation | ||
| 88 | Technical name '&1' for object of type &2 '&3' is invalid | Space: object requires documentation | ||
| 89 | Error in checking the long-term block for '&1', type '&2' | Space: object requires documentation | ||
| 90 | System name missing when checking the long-term block for '&1', '&2' | Space: object requires documentation | ||
| 91 | System type missing when checking the long-term block for '&1', '&2' | Space: object requires documentation | ||
| 92 | Order &1 of the block is invalid (object '&2', '&3') | Space: object requires documentation | ||
| 93 | Object '&1' (type '&2') locked by request &3 | Space: object requires documentation | ||
| 94 | Objects that are locked by other transport requests | Space: object requires documentation | ||
| 95 | Transport requests that first have to be released | Space: object requires documentation | ||
| 96 | Transport request &1 of user &2 (request &3 of &4) | Space: object requires documentation | ||
| 97 | No authorization for transporting role &1 (see long text) | Space: object requires documentation | ||
| 98 | Cannot transport local object &1 | The short text describes the object sufficiently | ||
| 99 | Transport of activity groups was canceled | Space: object requires documentation | ||
| 100 | Transport not possible. Required objects are missing | Space: object requires documentation | ||
| 101 | Cannot install Business Content. Objects are missing | Space: object requires documentation | ||
| 102 | Installation of: &1 (&2) | Space: object requires documentation | ||
| 103 | Installation (simulation mode) of: &1 (&2) | Space: object requires documentation | ||
| 104 | Transferring the &3 objects from type &1 took &2 seconds | Space: object requires documentation | ||
| 105 | Transferring the documents for objects of type &1 | Space: object requires documentation | ||
| 106 | Transferring the documents for type &1 took &2 seconds | Space: object requires documentation | ||
| 107 | Post-processing of Objects after activation | Space: object requires documentation | ||
| 108 | The post-processing lasts &1 seconds | Space: object requires documentation | ||
| 109 | Internal error &1 when reading the object catalog entry (TADIR) | Space: object requires documentation | ||
| 110 | Source systems are not transported | Space: object requires documentation | ||
| 111 | Error &3 when changing object catalog entry for object &1 (&2) | Space: object requires documentation | ||
| 112 | Exception '&3' in progrmm '&4' when passing type '&1' &2 | The short text describes the object sufficiently | ||
| 113 | Documentation for object &1 could not be read from &2 (&3) | Space: object requires documentation | ||
| 114 | Document &1 must be in HTML format and not '&2' | Space: object requires documentation | ||
| 115 | Activation of content package number &1 | The short text describes the object sufficiently | ||
| 116 | Searching for dependent objects for &1 objects | The short text describes the object sufficiently | ||
| 117 | &1 objects were collected (including the incoming objects) | The short text describes the object sufficiently | ||
| 118 | Content is activated for &1 objects | The short text describes the object sufficiently | ||
| 119 | No content is activated because "Collect Only" was selected | The short text describes the object sufficiently | ||
| 120 | Reading objects from the DB | The short text describes the object sufficiently | ||
| 121 | Could not find package of &1 &2 (version &3); object is ignored | The short text describes the object sufficiently | ||
| 122 | Special messages for BYD (method &1) | The short text describes the object sufficiently | ||
| 123 | Activation not executed due to special messages for BYD | The short text describes the object sufficiently | ||
| 124 | Exporting BW Repository Metadata into system &1 | Space: object requires documentation | ||
| 125 | Importing BW Repository Metadata from system &1 | Space: object requires documentation | ||
| 126 | Reading Metadata from system &1 ... | Space: object requires documentation | ||
| 127 | Write Metadata to system &1... | Space: object requires documentation | ||
| 128 | Metadata of &1 objects was read in system &2 | Space: object requires documentation | ||
| 129 | The export of Metadata in system &1 was finished | Space: object requires documentation | ||
| 130 | The import of Metadata in system &1 was finished | Space: object requires documentation | ||
| 131 | The RFC destination for logical system &1 does not exist | Space: object requires documentation | ||
| 132 | No RFC connection to system &1: &2&3&4 | Space: object requires documentation | ||
| 133 | No other BW systems (data marts) are connected to this one | Space: object requires documentation | ||
| 134 | &1 &2 was modified and is not copied from the content | Space: object requires documentation | ||
| 135 | --------------- Messages for CTC Content Activation ----------------- | The short text describes the object sufficiently | ||
| 136 | Not all the required content objects for &1 &2 were available | Space: object requires documentation | ||
| 137 | Process chain not activated; no monitoring data supplied | Space: object requires documentation | ||
| 138 | Collection of Required Content Objects | The short text describes the object sufficiently | ||
| 139 | Activation of Required Content Objects | The short text describes the object sufficiently | ||
| 140 | Reactivation of Required Process Chains | Space: object requires documentation | ||
| 141 | Connect source system with VirtualProvider | The short text describes the object sufficiently | ||
| 142 | --------------- Messages for generic functions ------------------ | Space: object requires documentation | ||
| 143 | &1 &2 is already active | Space: object requires documentation | ||
| 144 | &1 &2 is already saved | Space: object requires documentation | ||
| 145 | &1 &2 activated | Space: object requires documentation | ||
| 146 | Error when activating &1 &2 | Space: object requires documentation | ||
| 147 | Object &1 &2 is not transferred (component &3 is not active) | Space: object requires documentation | ||
| 148 | Error when deleting InfoSets, or InfoSet queries | Space: object requires documentation | ||
| 149 | Object &1 &2 was set to 'inactive' | Space: object requires documentation | ||
| 150 | Object &1 &2: Business Content component &3 is not active | Space: object requires documentation | ||
| 151 | &1 &2 was reset to the active version | Space: object requires documentation | ||
| 152 | Error when resetting &1 &2 to the active version | Space: object requires documentation | ||
| 153 | The documentation of &1 &2 is currently locked by user &3 | Space: object requires documentation | ||
| 154 | '&1' '&2' is not active - Texts in the M version have not been translated | Space: object requires documentation | ||
| 155 | Object &1 &2 has been deleted | Space: object requires documentation | ||
| 156 | Error when deleting object &1 &2 | Space: object requires documentation | ||
| 157 | Using &1 &2: | Space: object requires documentation | ||
| 158 | Object &1 &2 used in object &3 &4 (not deleted) | Space: object requires documentation | ||
| 159 | Usage check object type &1 | Space: object requires documentation | ||
| 160 | Still used in &1 &2 (&3) | Space: object requires documentation | ||
| 161 | Object &1 &2 not found | Space: object requires documentation | ||
| 162 | &1 &2 cannot be deleted because of references | Space: object requires documentation | ||
| 163 | Object &1 &2 is required by &3 (&4) | Space: object requires documentation | ||
| 164 | DDIC Object &1 &2 has not been activated | Space: object requires documentation | ||
| 165 | DDIC Object &1 &2 has not been deleted | Space: object requires documentation | ||
| 166 | Object &1 &2 is not available in version &3 | Space: object requires documentation | ||
| 167 | Object &1 &2: Installation of the Content Version | Space: object requires documentation | ||
| 168 | Object &1 &2: will also be transferred (&3 / &4) | Space: object requires documentation | ||
| 169 | Object &1 &2: must be activated (&3 / &4) | Space: object requires documentation | ||
| 170 | Object &1 &2: Merge with the Content Version | Space: object requires documentation | ||
| 171 | The Tlogo type &1 needs no treatment after translation | Space: object requires documentation | ||
| 172 | Impact analysis of &1 &2 | Space: object requires documentation | ||
| 173 | Object &1 &2: Error installing the Content version | Space: object requires documentation | ||
| 174 | Target name for object &1 &2 in &3 was not found | Space: object requires documentation | ||
| 175 | Object &1 &2 is already deleted | The short text describes the object sufficiently | ||
| 176 | Function not possible for TLOGO type &1 with these parameters | Space: object requires documentation | ||
| 177 | Error during creation of DDIC sources of &1 &2 | The short text describes the object sufficiently | ||
| 178 | Object &1 &2 can only be displayed and cannot be edited | The short text describes the object sufficiently | ||
| 179 | Object &1 &2 (version &3) deleted from database | The short text describes the object sufficiently | ||
| 180 | Error while deleting object &1 &2 (version &3) from database | The short text describes the object sufficiently | ||
| 181 | Could not determine pseudo D version of object &1 &2 | The short text describes the object sufficiently | ||
| 182 | Source system-dependent object &1 &2 inconsistent (instance not avail.) | The short text describes the object sufficiently | ||
| 183 | Object &1 &2 belongs to technical Content; changes will be overwritten | Space: object requires documentation | ||
| 184 | &1 &2 Successfully Scheduled/Executed | The short text describes the object sufficiently | ||
| 185 | Error when Scheduling / Executing &1 &2 | The short text describes the object sufficiently | ||
| 186 | Execute authorization check | The short text describes the object sufficiently | ||
| 187 | Object &1 &2 cannot be deleted; you do not have authorization | The short text describes the object sufficiently | ||
| 188 | Object &1 &2 has no TADIR entry | The short text describes the object sufficiently | ||
| 189 | Error while editing after saving the DDIC sources of &1 &2 | The short text describes the object sufficiently | ||
| 190 | Cannot schedule or execute &1 &2 because not active | The short text describes the object sufficiently | ||
| 191 | Object catalog entry &1 of last imported object is used | Space: object requires documentation | ||
| 192 | Package &1 is transferred from catalog entry of imported object | Space: object requires documentation | ||
| 193 | Object is local and is not transported when changed | Space: object requires documentation | ||
| 194 | ----------------------- Content admin messages | Space: object requires documentation | ||
| 195 | Business Content component &1 does not exist (obsolete) | Space: object requires documentation | ||
| 196 | Business Content component changed from &1 to &2 (obsolete) | The short text describes the object sufficiently | ||
| 197 | You do not have administration authorization for the Content system | The short text describes the object sufficiently | ||
| 198 | The system was set as a "Content system" | The short text describes the object sufficiently | ||
| 199 | The system was set as a normal ("non Content") system | The short text describes the object sufficiently | ||
| 200 | Namespace &1 cannot be used for roles | The short text describes the object sufficiently | ||
| 201 | Customer namespace &1 is a prefix of customer namespace &2 | The short text describes the object sufficiently | ||
| 202 | Customer namespace &1 is used more than once | The short text describes the object sufficiently | ||
| 203 | D version of role &1 renamed as &2, as per table RSOTLOGONSPDEL | The short text describes the object sufficiently | ||
| 204 | ------------------------Messages Appends / Enhancements-------------- | The short text describes the object sufficiently | ||
| 205 | Enhancement with name &1 already exists - change name | The short text describes the object sufficiently | ||
| 206 | A general error with append &1 occurred | The short text describes the object sufficiently | ||
| 207 | append &1 does not exist (version &2) | The short text describes the object sufficiently | ||
| 208 | Name of append &1 is invalid | The short text describes the object sufficiently | ||
| 209 | Enhancement &1 is not a BW enhancement | Space: object requires documentation | ||
| 210 | Appends still exist for main object - cannot delete | The short text describes the object sufficiently | ||
| 211 | Append &1 of main object &2 not saved | The short text describes the object sufficiently | ||
| 212 | Append &1 deleted | The short text describes the object sufficiently | ||
| 213 | Cannot create - append &1 is not active | Space: object requires documentation | ||
| 214 | Only objects with the same switch may be included | Space: object requires documentation | ||
| 215 | Append &1 has no objects, cannot save | The short text describes the object sufficiently | ||
| 216 | Internal error: Append inconsistent - &1 &2 &3 &4 | The short text describes the object sufficiently | ||
| 217 | Only one append can exist for each switch | Space: object requires documentation | ||
| 218 | Append &1 and append &2 are in the same switch (&3) | The short text describes the object sufficiently | ||
| 219 | Append must be assigned to a switch (development class: &1) | Space: object requires documentation | ||
| 220 | Error while determining package of append | The short text describes the object sufficiently | ||
| 221 | Append &1 of main object &2 saved | The short text describes the object sufficiently | ||
| 222 | Append &1 is locked (can only be displayed) | The short text describes the object sufficiently | ||
| 223 | Error (&1) while activating (deleting) append &2; see long text | Space: object requires documentation | ||
| 224 | Error while deleting append &1 | The short text describes the object sufficiently | ||
| 225 | Error while saving append &1 (&2) | The short text describes the object sufficiently | ||
| 226 | Append &1 is locked | The short text describes the object sufficiently | ||
| 227 | Unable to activate append &1 | The short text describes the object sufficiently | ||
| 228 | Append &1 of main object &2 was activated | The short text describes the object sufficiently | ||
| 229 | Switch &3 for object &1(&2) is inactive | Space: object requires documentation | ||
| 230 | Switch for object &1 is inactive | The short text describes the object sufficiently | ||
| 231 | Append cannot be assigned to main object | The short text describes the object sufficiently | ||
| 232 | Check of append &1 in version &2 | The short text describes the object sufficiently | ||
| 233 | Object &1 may not be assigned to append &2 | The short text describes the object sufficiently | ||
| 234 | Object &1 may not be assigned to main object &2 | The short text describes the object sufficiently | ||
| 235 | Appends are not supported for object type &1 | The short text describes the object sufficiently | ||
| 236 | Switches are not supported for object type &1 | The short text describes the object sufficiently | ||
| 237 | Append &1 is displayed | The short text describes the object sufficiently | ||
| 238 | Append &1 is processed | The short text describes the object sufficiently | ||
| 239 | No main object found for append &1 (is ignored) | The short text describes the object sufficiently | ||
| 240 | Creation of appends not allowed for content activation user | The short text describes the object sufficiently | ||
| 241 | ----- Messages for Matching A/D Version InfoCubes / MultiProvider ------- | Space: object requires documentation | ||
| 242 | InfoProvider &1: The active version is different to the modified version | Space: object requires documentation | ||
| 243 | Keep existing texts for InfoProvider &1 in language &2 | Space: object requires documentation | ||
| 244 | InfoObject &1 transferred from the 'M' version of InfoProvider &2 | Space: object requires documentation | ||
| 245 | InfoObject &1 was assigned to dimension &2 | Space: object requires documentation | ||
| 246 | Dimension &1 was added | Space: object requires documentation | ||
| 247 | Still have available texts for dimension &1 in language &2 | Space: object requires documentation | ||
| 248 | InfoProvider &1, relevant to MultiProvider &2, has been added | Space: object requires documentation | ||
| 249 | Assignment of InfoObject &1 has changed in Provider &2 from &3 to &4 | Space: object requires documentation | ||
| 250 | In Provider &2, the assignment of InfoObject &1 to &3 has been added | Space: object requires documentation | ||
| 251 | Versions of InfoProvider &1 have the same properties | Space: object requires documentation | ||
| 252 | InfoObject &1 was added during version comparison | Space: object requires documentation | ||
| 253 | Dimension &1 was added during version comparison | Space: object requires documentation | ||
| 254 | InfoObject &1 has been added to dimension &2 | Space: object requires documentation | ||
| 255 | Navigation attribute &1 was added during version comparison | Space: object requires documentation | ||
| 256 | InfoProvider &1 was added during version comparison | Space: object requires documentation | ||
| 257 | Key figure &1 was added to hierarchy node &2 | The short text describes the object sufficiently | ||
| 258 | Hierarchy was added (comparison with existing hierarchy) | The short text describes the object sufficiently | ||
| 259 | Available texts for InfoProvider &1, language &2, InfoObject &3 are kept | Space: object requires documentation | ||
| 260 | ---------------------- Checks Before Export ---------------------------- | The short text describes the object sufficiently | ||
| 261 | Cannot perform check for &1 &2: Error &3 &4 | The short text describes the object sufficiently | ||
| 262 | Error reading request &1 | The short text describes the object sufficiently | ||
| 263 | Error while converting from D or shadow object &1 &2 to A version. | Space: object requires documentation | ||
| 264 | Reading request &1 | The short text describes the object sufficiently | ||
| 265 | Checking objects of request &1 | The short text describes the object sufficiently | ||
| 266 | Transportable object &1 &2 needs local object &3 &4 | Space: object requires documentation | ||
| 267 | Object &1 &2 needs object &3 &4; latter is not in a request | Space: object requires documentation | ||
| 268 | &1 needs &2; latter is in request &3 (release request) | The short text describes the object sufficiently | ||
| 269 | Inconsistent objects: | The short text describes the object sufficiently | ||
| 270 | Local dependent objects: | The short text describes the object sufficiently | ||
| 271 | Dependent objects that are not in a transport: | The short text describes the object sufficiently | ||
| 272 | Dependent objects that need to be released: | The short text describes the object sufficiently | ||
| 273 | Object &1 &2 needs object &3 &4; the latter does not exist | The short text describes the object sufficiently | ||
| 274 | Dependent objects that do not exist: | The short text describes the object sufficiently | ||
| 275 | Request is consistent | The short text describes the object sufficiently | ||
| 276 | Inactive Objects: | The short text describes the object sufficiently | ||
| 277 | Object &1 &2: Active version differs from modified version | The short text describes the object sufficiently | ||
| 278 | Deletions: | The short text describes the object sufficiently | ||
| 279 | Object &1 &2 does not exist. Will also be deleted in target system | The short text describes the object sufficiently | ||
| 280 | Shadow object &1 &2 is inconsistent | The short text describes the object sufficiently | ||
| 281 | Active version of &1 &2 does not exist - dependent objects unknown | The short text describes the object sufficiently | ||
| 282 | Object &1 &2 is generated and cannot be transported | The short text describes the object sufficiently | ||
| 283 | Request &1 inconsistent. Not released | Space: object requires documentation | ||
| 284 | Object &1 &2 on exception list. Dependents not checked | The short text describes the object sufficiently | ||
| 285 | Request &1 on exception list. Not checked | The short text describes the object sufficiently | ||
| 286 | Release check switched off. Request &1 not checked | The short text describes the object sufficiently | ||
| 287 | ------------------BOBJ Transport/Checks---------------------------- | The short text describes the object sufficiently | ||
| 288 | Object '&1' (&2) of type '&3' is local and must be transported | The short text describes the object sufficiently | ||
| 289 | Found &1 as package for new objects (using user parameter DVC) | The short text describes the object sufficiently | ||
| 290 | &1 is package for n objects (using packages of dependent objects) | The short text describes the object sufficiently | ||
| 291 | Could not determine a package for new objects. See long text | Space: object requires documentation | ||
| 292 | Transport request &1 from user &2 | The short text describes the object sufficiently | ||
| 293 | Transport object &1 (type &2) in BW system manually | The short text describes the object sufficiently | ||
| 294 | ----------------- Generic Copy Tool ------------------------------------ | Space: object requires documentation | ||
| 295 | Object type &1 does not support copying - Remove | Space: object requires documentation | ||
| 296 | The number of copies for object &1 &2 is different from the others | Space: object requires documentation | ||
| 297 | There are no copies for object &1 &2 | Space: object requires documentation | ||
| 298 | Object &1 &2 exists already in version &3 (will be skipped) | Space: object requires documentation | ||
| 299 | Object &1 &2 has been copied successfully to &3 | Space: object requires documentation | ||
| 300 | Error when checking the copy rules for type &1 | Space: object requires documentation | ||
| 301 | Object &1 &2 The new name is not specified | Space: object requires documentation | ||
| 302 | Target name &2 is assigned more than once for Object type &1 | Space: object requires documentation | ||
| 303 | Wild card character '*' only allowed at end of name &1 | Space: object requires documentation | ||
| 304 | Wild card character '+' not allowed in name &1 | Space: object requires documentation | ||
| 305 | Name &1 must contain wild card character '*' | Space: object requires documentation | ||
| 306 | Object &1 &2 already in conversion table (cannot appear twice) | Space: object requires documentation | ||
| 307 | &1 entries added to copy table | Space: object requires documentation | ||
| 308 | ----------------------Parallel AIMs------------------------------------ | The short text describes the object sufficiently | ||
| 309 | * Parallel after import handling for object type &1 (&2 packages) | The short text describes the object sufficiently | ||
| 310 | * Processing package &1 in background job &2; Start time &3; Objects &4 | The short text describes the object sufficiently | ||
| 311 | * Processing of package &1 in main process; start time &2; objects &3 | The short text describes the object sufficiently | ||
| 312 | * Start of after import background process &1 (Number: &2) | The short text describes the object sufficiently | ||
| 313 | * End of after import background process &1 (number: &2; runtime: &3) | The short text describes the object sufficiently | ||
| 314 | * Start of AIM function module &1 for object type &2 | The short text describes the object sufficiently | ||
| 315 | * After-import method &1; Package no. &2 (Status: &3) | The short text describes the object sufficiently | ||
| 316 | End of after import methode &1 (&2) - runtime: &3 | The short text describes the object sufficiently | ||
| 317 | Termination in background job &1 while processing package &2 | Space: object requires documentation | ||
| 318 | * Object &1 contained in package &2 | The short text describes the object sufficiently | ||
| 319 | Invalid objects: 'After Import' terminated (see long text) | Space: object requires documentation | ||
| 320 | Skipped pseudo D version for object type &1 (see Note 1649901) | The short text describes the object sufficiently | ||
| 321 | Import All request &1: Post-processing object list after interruption | Space: object requires documentation | ||
| 322 | Import object &1 &2 incorr. processed with this request with obj ID &3 | The short text describes the object sufficiently | ||
| 323 | Object &1 &2 processed with errors on this request | The short text describes the object sufficiently | ||
| 324 | Object &1 &2 imported with errors on subsequent request &3 | Space: object requires documentation | ||
| 325 | Object &1 &2 processed with errors on request &3 | The short text describes the object sufficiently | ||
| 326 | Error with request &1. Import All log refers to request &2. | Space: object requires documentation | ||
| 327 | Import object &1 &2 incorr. processed with request &3 with obj ID &4 | The short text describes the object sufficiently | ||
| 328 | Request &1 (time stamp: &2), not relevant for BW after import | The short text describes the object sufficiently | ||
| 329 | Request &1 (time stamp: &2), erroneous objects follow: | The short text describes the object sufficiently | ||
| 330 | Request &2 aborted. Follow-up request &1 inherits RC = 12. | The short text describes the object sufficiently | ||
| 331 | After-import request &2 RC = 12. Request &1 not processed completely. | Space: object requires documentation | ||
| 332 | Erroneous object &1 &2 skipped by exception handling | The short text describes the object sufficiently | ||
| 333 | ---- Function Group RSVERS / REORGS / generic Messages ------ | Space: object requires documentation | ||
| 334 | Logical transport object &1 not found in table RSTLOGOPROP | Space: object requires documentation | ||
| 335 | Object &1 &2 copied (or deleted) from A version to D (&3) | Space: object requires documentation | ||
| 336 | Object &1 &2 copied in shadow object &3 &4 | Space: object requires documentation | ||
| 337 | Object &1 &2: D version deleted | Space: object requires documentation | ||
| 338 | Object &1 &2 &3 cannot be converted in D Version | Space: object requires documentation | ||
| 339 | TADIR entry written for object &1 &2 | Space: object requires documentation | ||
| 340 | Object &1 &2 written to request/task &3 | Space: object requires documentation | ||
| 341 | Object &1 &2 deleted from request/task &3 | Space: object requires documentation | ||
| 342 | Object &1 &2 is locked in request &3 | Space: object requires documentation | ||
| 343 | Specify a transportable package. ('&1') not possible | Space: object requires documentation | ||
| 344 | Error in development class, object &1 &2 not saved to the request | Space: object requires documentation | ||
| 345 | Object &1 &2 could not be saved to an request | Space: object requires documentation | ||
| 346 | Error in saving the documents of &1 &2 to a request (&3) | Space: object requires documentation | ||
| 347 | TADIR entry for object &1 &2 changed | Space: object requires documentation | ||
| 348 | Error in changing TADIR entry for object &1 &2 | Space: object requires documentation | ||
| 349 | TADIR entry for object &1 &2 deleted | Space: object requires documentation | ||
| 350 | Error while deleting TADIR entry for object &1 &2 | Space: object requires documentation | ||
| 351 | Release request &1 | Space: object requires documentation | ||
| 352 | Enter a transport request in the next popup | Space: object requires documentation | ||
| 353 | Package &1 is not possible - transport target is not '&2' | Space: object requires documentation | ||
| 354 | Local TADIR entry for object &1 &2 created | Space: object requires documentation | ||
| 355 | Error in creating the local TADIR entry for object &1 &2 | Space: object requires documentation | ||
| 356 | Enter a customer development class (&1 belongs to SAP) | Space: object requires documentation | ||
| 357 | Object &1 &2 could not be saved to order &3 | Space: object requires documentation | ||
| 358 | Object &1 &2 is not connected to the CTO in the Content system | Space: object requires documentation | ||
| 359 | Error while deleting the BDS documents from object &1 &2 | Space: object requires documentation | ||
| 360 | BEx transport request '&1' is not available or not suitable | Space: object requires documentation | ||
| 361 | No new BEX transport request necessary, as request &1 still exists | Space: object requires documentation | ||
| 362 | No documents have been maintained yet for &1 &2 | Space: object requires documentation | ||
| 363 | The documentation display was started in a separate window | Space: object requires documentation | ||
| 364 | Processing of the documents has been started in a separate window | Space: object requires documentation | ||
| 365 | R3 Link for object &1 &2 has been deleted | Space: object requires documentation | ||
| 366 | Application &1 is not assigned to a document type (table TOADD) | Space: object requires documentation | ||
| 367 | Documentation from &1 &2 deleted | Space: object requires documentation | ||
| 368 | Documentation from &1 &2 saved in the BDS | Space: object requires documentation | ||
| 369 | The documentation can only be displayed | Space: object requires documentation | ||
| 370 | Package &1 is already in use | Space: object requires documentation | ||
| 371 | R3 Link for object &1 &2 created | Space: object requires documentation | ||
| 372 | Write to transport requests terminated by the user | Space: object requires documentation | ||
| 373 | Error while writing objects to a transport request | Space: object requires documentation | ||
| 374 | Saving &1 &2 | Space: object requires documentation | ||
| 375 | &1 &2 saved | Space: object requires documentation | ||
| 376 | Error while saving &1 &2 | Space: object requires documentation | ||
| 377 | No connection found for document &1 | Space: object requires documentation | ||
| 378 | Several documents found for document &1 | Space: object requires documentation | ||
| 379 | Document &1 &2 (&3) converted | Space: object requires documentation | ||
| 380 | Object &1 &2 is not being processed | Space: object requires documentation | ||
| 381 | Standard transport activated (see long text) | Space: object requires documentation | ||
| 382 | Standard transport deactivated (see long text) | Space: object requires documentation | ||
| 383 | Object &1 &2 cannot be processed in the Content system | Space: object requires documentation | ||
| 384 | Upgrade is running (phase &1) - you are not able to change objects | Space: object requires documentation | ||
| 385 | You can only display BW objects in this system | Space: object requires documentation | ||
| 386 | System can be changed; settings not necessary | Space: object requires documentation | ||
| 387 | Start after-import methods for texts | Space: object requires documentation | ||
| 388 | Object &1 &2 was delivered as Content to this system | Space: object requires documentation | ||
| 389 | BEx request &1 already released and removed | Space: object requires documentation | ||
| 390 | Error &2 during after import handling of objects with type(s) &1 | Space: object requires documentation | ||
| 391 | &1 &2: Dependant objects are not subject to recording in requests | Space: object requires documentation | ||
| 392 | Error occurred when saving dependent object &4 of &1 &2 to a request (&3) | Space: object requires documentation | ||
| 393 | BW systems with MDMP configuration are not supported | Space: object requires documentation | ||
| 394 | Upgrade running (phase &1) - you can only make limited changes to objects | Space: object requires documentation | ||
| 395 | Object &1 &2 cannot be edited during the upgrade (phase &3) | The short text describes the object sufficiently | ||
| 396 | All edited objects (target &1) already locked on request &2 | The short text describes the object sufficiently | ||
| 397 | The edited objects with target &1 are locked on the following requests: | Space: object requires documentation | ||
| 398 | System is set to not changeable; objects cannot be changed | Space: object requires documentation | ||
| 399 | Objects are consistent | The short text describes the object sufficiently | ||
| 400 | Starting automatic activation of BI Content | The short text describes the object sufficiently | ||
| 401 | Deleting objects of type &1 | The short text describes the object sufficiently | ||
| 402 | Starting after import method &1 for object type(s) &2 in delete mode | The short text describes the object sufficiently | ||
| 403 | Starting after import method &1 for object type(s) &2 in Content mode | The short text describes the object sufficiently | ||
| 404 | Short dump &1 &2 occurred during After Import handling in area &3 | Space: object requires documentation | ||
| 405 | Deletion of &1 TLOGO objects | The short text describes the object sufficiently | ||
| 406 | Content status entry for object &1 &2 (version &3) generated | The short text describes the object sufficiently | ||
| 407 | Content status entry for object &1 &2 (version &3) deleted | The short text describes the object sufficiently | ||
| 408 | Error &1 &2 (&3) in TP command &4 | The short text describes the object sufficiently | ||
| 409 | Could not determine the BW client | Space: object requires documentation | ||
| 410 | Could not determine the RFC destination in the BW client | The short text describes the object sufficiently | ||
| 411 | Object &1 &2 to be deleted could not be written to transport request | Space: object requires documentation | ||
| 412 | No request specified for transport destination &1 | The short text describes the object sufficiently | ||
| 413 | Call of BAdI implementation for BW after import handling | Space: object requires documentation | ||
| 414 | Error calling BAdI implementation "BW After Import Handling" | The short text describes the object sufficiently | ||
| 415 | After import handling of order &1 has been performed for order &2 | Space: object requires documentation | ||
| 416 | After import order &1: The following orders are also processed common: | Space: object requires documentation | ||
| 417 | Error while reading objects from request &1 (-> individual import) | The short text describes the object sufficiently | ||
| 418 | Request &1 (time stamp: &2) | The short text describes the object sufficiently | ||
| 419 | Object &1 &2 is generated and cannot be transported | Space: object requires documentation | ||
| 420 | BW BYD upgrade: Request &1 rebuilds the BW buffer (MAINFL=&2) | The short text describes the object sufficiently | ||
| 421 | BW BYD upgrade: Handling of request &1 and dependents completed | The short text describes the object sufficiently | ||
| 422 | Error - not related to request &1. Log displayed for subsequent request | Space: object requires documentation | ||
| 423 | Error with objects of request &1. See log for request &2 | Space: object requires documentation | ||
| 424 | Error with request &1. Import All log will follow | Space: object requires documentation | ||
| 425 | No error with object of request &1. See log for request &2 | The short text describes the object sufficiently | ||
| 426 | No errors with request &1. Log displayed for subsequent request | The short text describes the object sufficiently | ||
| 427 | Not an error (last request &1). Full log will follow (see request &2) | The short text describes the object sufficiently | ||
| 428 | Request &1: Simulated call of after import handling | The short text describes the object sufficiently | ||
| 429 | Request &1 marked as incorrect due to type &2 (may possibly be correct) | Space: object requires documentation | ||
| 430 | Processing of request &1 is also recorded in the log | The short text describes the object sufficiently | ||
| 431 | Summary of objects with errors from request &1 | The short text describes the object sufficiently |
History
| Last changed on/by | 20140121 | SAP | |
| SAP Release Created in | 730 |