Message Number list used by SAP ABAP Class CL_RSO_OBJECT_COLLECTOR (BW Repository: Object Collector)
SAP ABAP Class CL_RSO_OBJECT_COLLECTOR (BW Repository: Object Collector) is using
# | Object Type | Object Name | Object Description | Note |
---|---|---|---|---|
1 | Message Number | RSO - 312 | Cannot install Business Content. Objects are missing | |
2 | Message Number | RSO - 304 | Object '&1' (type '&2') locked by request &3 | |
3 | Message Number | RSO - 305 | Objects that are locked by other transport requests | |
4 | Message Number | RSO - 306 | Transport requests that first have to be released | |
5 | Message Number | RSO - 307 | Transport request &1 of user &2 (request &3 of &4) | |
6 | Message Number | RSO - 308 | No authorization for transporting role &1 (see long text) | |
7 | Message Number | RSO - 309 | Cannot transport local object &1 | |
8 | Message Number | RSO - 311 | Transport not possible. Required objects are missing | |
9 | Message Number | RSO - 311 | Transport not possible. Required objects are missing | |
10 | Message Number | RSO - 311 | Transport not possible. Required objects are missing | |
11 | Message Number | RSO - 252 | Object '&1' (&2) of type '&3' is not available in version '&4' | |
12 | Message Number | RSO - 313 | Installation of: &1 (&2) | |
13 | Message Number | RSO - 314 | Installation (simulation mode) of: &1 (&2) | |
14 | Message Number | RSO - 315 | Transferring the &3 objects from type &1 took &2 seconds | |
15 | Message Number | RSO - 320 | Internal error &1 when reading the object catalog entry (TADIR) | |
16 | Message Number | RSO - 320 | Internal error &1 when reading the object catalog entry (TADIR) | |
17 | Message Number | RSO - 321 | Source systems are not transported | |
18 | Message Number | RSO - 323 | Exception '&3' in progrmm '&4' when passing type '&1' &2 | |
19 | Message Number | RSO - 370 | &1 &2 was modified and is not copied from the content | |
20 | Message Number | RSO - 303 | Order &1 of the block is invalid (object '&2', '&3') | |
21 | Message Number | RSO - 209 | Further objects will be sought only &1 level deeper | |
22 | Message Number | RSO - 259 | Object '&1' of type '&2' already exists in tree | |
23 | Message Number | RSO - 260 | Activation of Content with type &1 (FB &2) is not yet available | |
24 | Message Number | RSO - 261 | Object '&1' of type '&2' already exists in network | |
25 | Message Number | RSO - 262 | Root object '&1' (type '&2') of an association is not yet available | |
26 | Message Number | RSO - 271 | Target object '&1' (type '&2') of an association is not available | |
27 | Message Number | RSO - 274 | Object '&1::&2' refers to the invalid object '&3::&4' | |
28 | Message Number | RSO - 275 | The object '&1::&2' cannot be activated (see long text) | |
29 | Message Number | RSO - 296 | Object &1 (&2) could not be collected for object &3 (&4) | |
30 | Message Number | RSO - 299 | Technical name '&1' for object of type &2 '&3' is invalid | |
31 | Message Number | RSO - 300 | Error in checking the long-term block for '&1', type '&2' | |
32 | Message Number | RSO - 300 | Error in checking the long-term block for '&1', type '&2' | |
33 | Message Number | RSO - 301 | System name missing when checking the long-term block for '&1', '&2' | |
34 | Message Number | RSO - 301 | System name missing when checking the long-term block for '&1', '&2' | |
35 | Message Number | RSO - 302 | System type missing when checking the long-term block for '&1', '&2' | |
36 | Message Number | RSO - 302 | System type missing when checking the long-term block for '&1', '&2' | |
37 | Message Number | RSO - 303 | Order &1 of the block is invalid (object '&2', '&3') | |
38 | Message Number | RS_GENERAL - 001 | Error while importing the data from the memory (ID &1) |