SAP ABAP Message Class RSO_CTC (Message class for CTC related messages)
Basic Data
Hierarchy
☛
SAP_BW (Software Component) SAP Business Warehouse
⤷
BW (Application Component) SAP Business Information Warehouse
⤷
BW_CORE_TOOLS (Package) Tools from BW_CORE (not part of LEAN BW)
⤷
⤷
Attributes
| Message class | RSO_CTC | |
| Short Description | Message class for CTC related messages | |
| Changed On | 20140121 | |
| Last Changed At | 101803 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | Could not activate technical content | Space: object requires documentation | ||
| 2 | Technical content activation still running | The short text describes the object sufficiently | ||
| 3 | Technical content activated | The short text describes the object sufficiently | ||
| 4 | DataSources of source system &1 replicated | The short text describes the object sufficiently | ||
| 5 | DataSources of source system &1 not replicated | Space: object requires documentation | ||
| 6 | Could not check for technical content activation | Space: object requires documentation | ||
| 7 | Could not activate & | The short text describes the object sufficiently | ||
| 8 | Check for Admin Cockpit installation | Space: object requires documentation | ||
| 9 | Check for DataSource replication | Space: object requires documentation | ||
| 10 | Check for J2EE Engine availability | Space: object requires documentation | ||
| 11 | Check for activation of personalization content | Space: object requires documentation | ||
| 12 | Check for status of technical content | Space: object requires documentation | ||
| 13 | RFC destination in table RSODADMIN_INT is empty | Space: object requires documentation | ||
| 14 | RFC destination entered is invalid | The short text describes the object sufficiently | ||
| 15 | TREX server is down | The short text describes the object sufficiently | ||
| 16 | TREX server is up | The short text describes the object sufficiently | ||
| 17 | Initial indexing not started yet | The short text describes the object sufficiently | ||
| 18 | Initial indexing in progress | The short text describes the object sufficiently | ||
| 19 | Initial indexing completed | The short text describes the object sufficiently | ||
| 20 | The short text describes the object sufficiently | |||
| 21 | Check for TREX status and indexing. | Space: object requires documentation | ||
| 22 | Check for collection of content objects | The short text describes the object sufficiently | ||
| 23 | Check for activation of all the objects for role | The short text describes the object sufficiently | ||
| 24 | Check for replication of DataSource | The short text describes the object sufficiently | ||
| 25 | Check for connection of the virtual provider | The short text describes the object sufficiently | ||
| 26 | Could not complete operation, since logical system not found | The short text describes the object sufficiently | ||
| 27 | J2EE Engine set up successfully | The short text describes the object sufficiently | ||
| 28 | Could not contact IGS | Space: object requires documentation | ||
| 29 | IGS set up successfully | The short text describes the object sufficiently | ||
| 30 | Error modifying table &1 | The short text describes the object sufficiently | ||
| 31 | Check for Internet Graphic Service | Space: object requires documentation | ||
| 32 | Virtual providers of Admin Cockpit connected to source system &1 | The short text describes the object sufficiently | ||
| 33 | Logical system &1 found | The short text describes the object sufficiently | ||
| 34 | Could not find logical system &1 | The short text describes the object sufficiently | ||
| 35 | Client is not a BW client. Set client: &1 | The short text describes the object sufficiently | ||
| 36 | No entry named "BW" found in column "customizid" in table RSADMINA | The short text describes the object sufficiently | ||
| 37 | Client not available in table T000 | The short text describes the object sufficiently | ||
| 38 | Problem accessing ICF services 'Check SICF' 'SICF:TRA' | The short text describes the object sufficiently | ||
| 39 | ICF service &1 active | The short text describes the object sufficiently | ||
| 40 | ICF service &1 not active | Space: object requires documentation | ||
| 41 | Database table RSADMINA has entry with customizid = BW | The short text describes the object sufficiently | ||
| 42 | Debug user is correct | The short text describes the object sufficiently | ||
| 43 | Debug user should be empty | The short text describes the object sufficiently | ||
| 44 | Connection to TREX RFC destination is not available | The short text describes the object sufficiently | ||
| 45 | Connection to TREX RFC destination is available | The short text describes the object sufficiently | ||
| 46 | Standard transport system is in test mode (off) | The short text describes the object sufficiently | ||
| 47 | Standard transport system is not in test mode | Space: object requires documentation | ||
| 48 | No ALEREMOTE user found | The short text describes the object sufficiently | ||
| 49 | Client is incorrect. | The short text describes the object sufficiently | ||
| 50 | Check for BW system client ID | Space: object requires documentation | ||
| 51 | Check for ICF services | Space: object requires documentation | ||
| 52 | No entry found for logical system | Space: object requires documentation | ||
| 53 | User &1 exists for client | The short text describes the object sufficiently | ||
| 54 | User ALEREMOTE is not locked | The short text describes the object sufficiently | ||
| 55 | User ALEREMOTE is locked | The short text describes the object sufficiently | ||
| 56 | User ALEREMOTE does not exist for client &1 | The short text describes the object sufficiently | ||
| 57 | User ALEREMOTE has profile S_BI-WHM_RFC | The short text describes the object sufficiently | ||
| 58 | User ALEREMOTE does not have profile S_BI-WHM_RFC | Space: object requires documentation | ||
| 59 | Add profile in SU01- SU01:TRA | The short text describes the object sufficiently | ||
| 60 | User ALEREMOTE has profile S_BI-WX_RFC | The short text describes the object sufficiently | ||
| 61 | User ALEREMOTE does not have profile S_BI-WX_RFC | Space: object requires documentation | ||
| 62 | User ALEREMOTE has role SAP_RO_BCTRA | The short text describes the object sufficiently | ||
| 63 | User ALEREMOTE does not have role SAP_RO_BCTRA | Space: object requires documentation | ||
| 64 | Add role in SU01 - SU01:TRA | The short text describes the object sufficiently | ||
| 65 | Check for table setting | Space: object requires documentation | ||
| 66 | Check for user information | Space: object requires documentation | ||
| 67 | Logical system details exist | The short text describes the object sufficiently | ||
| 68 | Client is correct | The short text describes the object sufficiently | ||
| 69 | Database table RSADMINS has no entry with customizid = BW | The short text describes the object sufficiently | ||
| 70 | Database table RSADMINS has entry with customizid = BW | The short text describes the object sufficiently | ||
| 71 | Check for standard BI jobs | Space: object requires documentation | ||
| 72 | Job &1 is not running | Space: object requires documentation | ||
| 73 | Job &1 is running correctly | The short text describes the object sufficiently | ||
| 74 | Job &1 is running more than once | Space: object requires documentation | ||
| 75 | Role &1 - &2 &3 --> &4 | Space: object requires documentation | ||
| 76 | Error retrieving BW client | The short text describes the object sufficiently | ||
| 77 | Check for generation of role and user synchronization | Space: object requires documentation | ||
| 78 | Error assigning logon user as &1 to Myself RFC destination | The short text describes the object sufficiently | ||
| 79 | DTP not available for Datasource &1 Source System &2 | The short text describes the object sufficiently | ||
| 80 | Process chain &1 cannot be copied | The short text describes the object sufficiently | ||
| 81 | Required Input fields are not filled | The short text describes the object sufficiently | ||
| 82 | Object &1 of Type &2 is not assigned to Request/Package | The short text describes the object sufficiently | ||
| 83 | Object &1 of Type &2 is not active | The short text describes the object sufficiently | ||
| 84 | BW Objects listed in "Details" could not be assigned to Transport Request | The short text describes the object sufficiently | ||
| 85 | Object &1 is not available in Active Version | The short text describes the object sufficiently | ||
| 86 | The short text describes the object sufficiently | |||
| 87 | BW Objects listed in "Details" are not available in 'A' version | The short text describes the object sufficiently | ||
| 88 | Error in creation of ALV List | The short text describes the object sufficiently | ||
| 89 | BW System &1 is being disconnected from Source System &2 | The short text describes the object sufficiently | ||
| 90 | BW System &1 is successfully disconnected from Source System &2 | The short text describes the object sufficiently | ||
| 91 | User &1 has insufficient authorizations to perform BW system refresh | Space: object requires documentation | ||
| 92 | The short text describes the object sufficiently | |||
| 93 | BIA Indexes are not present. This step is not required. | The short text describes the object sufficiently | ||
| 94 | Error during clean up of BIA Index information. Refer log for details. | The short text describes the object sufficiently | ||
| 95 | BIA Index information is successfully cleaned up. | The short text describes the object sufficiently | ||
| 96 | Missing authorizations. Authorization Object: S_TREX_ADM , Activity: 02 | The short text describes the object sufficiently | ||
| 97 | Host name of BI Enqueue server is successfully adjusted in TA RSPLSE | The short text describes the object sufficiently | ||
| 98 | Correct host was successfully updated to BW RFC Destinations | The short text describes the object sufficiently | ||
| 99 | Generation flag is successfully reset for DSO activation programs | The short text describes the object sufficiently | ||
| 100 | No BW Source Systems connected. Step is not required. | The short text describes the object sufficiently | ||
| 101 | Connection to Source System &1 successfully restored | The short text describes the object sufficiently | ||
| 102 | Source system connection &1 will be deleted in BW | The short text describes the object sufficiently | ||
| 103 | Source system connection &1 successully deleted in BW | The short text describes the object sufficiently | ||
| 104 | Source System connection &1 will be restored | The short text describes the object sufficiently | ||
| 105 | Source System &1 will be retained, no need to delete connection | The short text describes the object sufficiently | ||
| 106 | Source system &2 will be remotely disconnected from BW &1 | The short text describes the object sufficiently | ||
| 107 | Source system &2 successfully disconnected from BW &1 | The short text describes the object sufficiently | ||
| 108 | Check not possible before BDLS-Task was executed | The short text describes the object sufficiently | ||
| 109 | Step is not required as this is a Non-BW system | The short text describes the object sufficiently | ||
| 110 | Structure &1 is not active; activate DataSource &2 at some time | The short text describes the object sufficiently | ||
| 111 | Activation failure of structure &1 of DataSource &2 | The short text describes the object sufficiently | ||
| 112 | Target structure &1 of DS &2 already exists with different fields | The short text describes the object sufficiently | ||
| 113 | Transfer Structure &1 does not exist | The short text describes the object sufficiently | ||
| 114 | Error when updating delta queues in source system &1 from BW | The short text describes the object sufficiently | ||
| 115 | Delta queues in source system &1 successfully updated from BW | The short text describes the object sufficiently | ||
| 116 | Source system &1 is still connected to receiver system &2 | Space: object requires documentation | ||
| 117 | Source system &1 will be remotely re-connected to BW | The short text describes the object sufficiently | ||
| 118 | Source system &1 is still connected to BW system &2 | Space: object requires documentation | ||
| 119 | BDLS task has wrong mapping for system &1; it must be a BW source system | Space: object requires documentation | ||
| 120 | &1 mapped in UI of BDLS task is not a valid BW source system | The short text describes the object sufficiently | ||
| 121 | BDLS UI contains mappings to logical system &1. Remove this mapping. | Space: object requires documentation | ||
| 122 | Corrections of note &1 is missing in system &2 | Space: object requires documentation | ||
| 123 | Corrections of note &1 is missing in &2 system; implement this note | The short text describes the object sufficiently | ||
| 124 | You have to perform this task manually for &1 according to note &2 | Space: object requires documentation | ||
| 125 | Error retrieving logical system name of this BW system | The short text describes the object sufficiently | ||
| 126 | Enter new logical system name for clone of this BW system | The short text describes the object sufficiently | ||
| 127 | Request &1 not completed successfully. Monitor this request (Tx RSRQ) | The short text describes the object sufficiently | ||
| 128 | Delta Queues successfully cloned for the selected source systems | The short text describes the object sufficiently | ||
| 129 | Request delta for &1 (&2) before synchronization of delta queues | The short text describes the object sufficiently | ||
| 130 | Check not possible before delta queues have been cloned | The short text describes the object sufficiently | ||
| 131 | Automatically reset last attempt to clone delta queues in &1 for &2 | The short text describes the object sufficiently | ||
| 132 | Previous logical system name &1 does not equal current name &2 | The short text describes the object sufficiently | ||
| 133 | Updating ALE ports successfully done | The short text describes the object sufficiently | ||
| 134 | Error updating ALE port of Source System &1 | The short text describes the object sufficiently | ||
| 135 | Successfully activated ALE partner of Source System &1 | The short text describes the object sufficiently | ||
| 136 | Predecessor task &1 not found in the tasklist | The short text describes the object sufficiently | ||
| 137 | No entry in BDLS task found for logsys &1 | The short text describes the object sufficiently | ||
| 138 | No RFC destination found for source system (logsys) &1 | The short text describes the object sufficiently | ||
| 139 | This task is not compatible with task &1 | The short text describes the object sufficiently | ||
| 140 | No BW client found: task (&1) can only be executed in a BW system | The short text describes the object sufficiently | ||
| 141 | RFC Destination &1 has errors | The short text describes the object sufficiently | ||
| 142 | Function module &1 missing in BW source system &2 | The short text describes the object sufficiently | ||
| 143 | Preparation successful | The short text describes the object sufficiently | ||
| 144 | Source system &2: Delta Queue contains much data (&1 blocks) | The short text describes the object sufficiently | ||
| 145 | &1&2&3&4 | The short text describes the object sufficiently | ||
| 146 | DataSource &2(&3): Delta Queue contains much data (&1 blocks) | The short text describes the object sufficiently | ||
| 147 | Activating Transfer Rule &1 &2... | The short text describes the object sufficiently | ||
| 148 | Activating DataSource &1 &2... | The short text describes the object sufficiently | ||
| 149 | No action required as the RFC destination is already updated | The short text describes the object sufficiently | ||
| 150 | RDA daemons and process chains could not be stopped | The short text describes the object sufficiently | ||
| 151 | RDA daemons and process chains stopped successfully | The short text describes the object sufficiently | ||
| 152 | RDA daemon could not close open delta requests | Space: object requires documentation | ||
| 153 | The function &1 must be called within the BW client | The short text describes the object sufficiently | ||
| 154 | No destination into BW client found (table RSADMINA, field TPBWMANDTRFC) | The short text describes the object sufficiently | ||
| 155 | RDA daemons and process chains have been started successfully | The short text describes the object sufficiently | ||
| 156 | RDA daemons and process chains could not be re-started | The short text describes the object sufficiently | ||
| 157 | RDA daemons and process chains re-started successfully | The short text describes the object sufficiently | ||
| 158 | &1 Process Chains have been re-scheduled | The short text describes the object sufficiently | ||
| 159 | &1 RDA Daemons have been re-started | The short text describes the object sufficiently | ||
| 160 | &1 Process Chain Start Processes have been de-scheduled | The short text describes the object sufficiently | ||
| 161 | &1 RDA Infopackages have been suspended | The short text describes the object sufficiently | ||
| 162 | &1 Process Chains are still active | The short text describes the object sufficiently | ||
| 163 | &1 RDA InfoPackages are still active | The short text describes the object sufficiently | ||
| 164 | &1 RDA requests are still open | The short text describes the object sufficiently | ||
| 165 | Background job &1 &2 could not be started | The short text describes the object sufficiently | ||
| 166 | Background job &1 &2 not found | The short text describes the object sufficiently | ||
| 167 | Joblog of background job &1 &2 not found | The short text describes the object sufficiently | ||
| 168 | Check activation status of DataSource &1(&2) | The short text describes the object sufficiently | ||
| 169 | Check activation status of Transfer Rules, 3.x DataSource &1(&2) | The short text describes the object sufficiently | ||
| 170 | No source systems have been selected | The short text describes the object sufficiently | ||
| 171 | Logsys &1 not considered | The short text describes the object sufficiently | ||
| 172 | BWA not present | The short text describes the object sufficiently | ||
| 173 | Delta for DataSource &1 (&2) will have to be re-initialized in &3 | Space: object requires documentation | ||
| 174 | &1 RDA daemons could not be re-scheduled (see BW transaction RSRDA) | The short text describes the object sufficiently |
History
| Last changed on/by | 20140121 | SAP | |
| SAP Release Created in | 711 |