SAP ABAP Message Class RSAPI_CTC (Messages to be shown for BW SAPI configurations)
Basic Data
Hierarchy
☛
PI_BASIS (Software Component) Basis Plug-In
⤷ BC-BW (Application Component) BW Service API
⤷ RSAPI_CTC (Package) CTC objects for BW SAPI systems
⤷ BC-BW (Application Component) BW Service API
⤷ RSAPI_CTC (Package) CTC objects for BW SAPI systems
Attributes
Message class | RSAPI_CTC | |
Short Description | Messages to be shown for BW SAPI configurations | |
Changed On | 20131127 | |
Last Changed At | 163550 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | &1 is a BW system. Perform BW System Copy Configurations | The short text describes the object sufficiently | |
2 | 001 | System &1 is connected to BW systems. Connection will be disconnected | The short text describes the object sufficiently | |
3 | 002 | Error in creation of ALV List | The short text describes the object sufficiently | |
4 | 003 | Disconnecting BW system &1 from BW source system &2... | The short text describes the object sufficiently | |
5 | 004 | BW system &1 successfully disconnected from BW source system &2 | The short text describes the object sufficiently | |
6 | 005 | DataSources in 'Details' restored for BW system &1 | The short text describes the object sufficiently | |
7 | 006 | DataSources in "Details" could not be restored for BW system &1 | The short text describes the object sufficiently | |
8 | 007 | Select the required systems and press execute (F8) | The short text describes the object sufficiently | |
9 | 008 | Action cancelled by user | The short text describes the object sufficiently | |
10 | 009 | System is not a BW system or a source system | The short text describes the object sufficiently | |
11 | 010 | Error when updating delta queue for BW system &1 | The short text describes the object sufficiently | |
12 | 011 | Error when updating ALE port of BW system &1 in BW source system &2 | The short text describes the object sufficiently | |
13 | 012 | Error when activating ALE partner of BW system &1 in BW source system &2 | The short text describes the object sufficiently | |
14 | 013 | ALE/IDOC details updated | The short text describes the object sufficiently | |
15 | 014 | Delta queue restored for BW system &1 | The short text describes the object sufficiently | |
16 | 015 | Invalid RFC destination &1 to local source client &2. Check connection. | The short text describes the object sufficiently | |
17 | 016 | Maintain RFC destination for local source client &1 | The short text describes the object sufficiently | |
18 | 017 | No BW systems are connected. This step will not be executed. | The short text describes the object sufficiently | |
19 | 018 | Connections to OSS is not maintained. Cannot get latest version of notes | The short text describes the object sufficiently | |
20 | 019 | Include task "Select System Connections to be Retained After Copy" | The short text describes the object sufficiently | |
21 | 020 | Some of the required notes are not yet implemented. See details | The short text describes the object sufficiently | |
22 | 021 | All the required notes are implemented | The short text describes the object sufficiently | |
23 | 022 | RFC destination is not maintained for local Source Client &1 | The short text describes the object sufficiently | |
24 | 023 | BW system &1 will also be copied. No need to disconnect from &2. | The short text describes the object sufficiently | |
25 | 024 | Note 1523687 has to be implemented in the system | The short text describes the object sufficiently | |
26 | 025 | BDLS task has wrong mapping for system &1; it has to be a BW system | Space: object requires documentation | |
27 | 026 | Mappings for logical system &1 not maintained in BDLS task | Space: object requires documentation | |
28 | 027 | Enable 'Release Jobs' for task 'Conversion of Logical System Names' | The short text describes the object sufficiently | |
29 | 028 | BW system &1 is not correctly connected to BW source system &2 | Space: object requires documentation | |
30 | 029 | System &1 is not a BW system | The short text describes the object sufficiently | |
31 | 030 | BW source system &1 has to be maintained in BDLS task | Space: object requires documentation | |
32 | 031 | No authorizations to execute this task | The short text describes the object sufficiently | |
33 | 032 | Connections to system &1 correct | The short text describes the object sufficiently | |
34 | 033 | Corrections in SAP Note &1 missing in system &2. Implement this Note. | The short text describes the object sufficiently | |
35 | 034 | RFC destination to local BW client not maintained | Space: object requires documentation | |
36 | 035 | Connections to Systems are present. Select in UI to retain Connections | The short text describes the object sufficiently | |
37 | 036 | Connections to System &1 failed. Repair the connection | The short text describes the object sufficiently | |
38 | 037 | System copy automation does not support BW only system copy | Space: object requires documentation | |
39 | 038 | BW systems are not connected to this system. No need for RFC destination | The short text describes the object sufficiently | |
40 | 039 | Error when calling documentation | The short text describes the object sufficiently | |
41 | 040 | Failed to check BW-Source connection as RFC Destination &1 is incorrect | The short text describes the object sufficiently | |
42 | 041 | Will system &1 be refreshed by copying from another system? | The short text describes the object sufficiently | |
43 | 042 | Authorization check failed for user of RFC destination &1 | The short text describes the object sufficiently | |
44 | 043 | Determine the copy scenario | The short text describes the object sufficiently | |
45 | 044 | Select relevant copy scenario to transfer system names to BDLS task | Space: object requires documentation | |
46 | 045 | Copy scenario is already selected as 'Refresh'. | The short text describes the object sufficiently | |
47 | 046 | Copy scenario is already selected as 'New Installation'. | The short text describes the object sufficiently | |
48 | 047 | Copy scenario was not selected by user. It is not possible to select now. | The short text describes the object sufficiently | |
49 | 048 | IDOC &1 used to connect system &2 is not assigned to any package | Space: object requires documentation | |
50 | 049 | Connection check impossible due to missing destination to local BW client | Space: object requires documentation | |
51 | 050 | Maintain target client for RFC destination &1 | The short text describes the object sufficiently | |
52 | 051 | Corrections in SAP Note &1 missing in system &2 | Space: object requires documentation | |
53 | 052 | Ensure Secure Store is correctly configured by executing relevant tasks | Space: object requires documentation | |
54 | 053 | BW system &1 is not up to date. Connection cannot be auto-restored. | Space: object requires documentation | |
55 | 054 | BDLS UI contains mappings to logical system &1. Remove this mapping. | Space: object requires documentation | |
56 | 210 | Update of ALE ports and settings successfully done | The short text describes the object sufficiently | |
57 | 211 | Error updating ALE port of Source System &1 | The short text describes the object sufficiently | |
58 | 212 | Successfully activated ALE partner of Source System &1 | The short text describes the object sufficiently | |
59 | 213 | Predecessor task &1 not found in the tasklist | The short text describes the object sufficiently | |
60 | 214 | No entry in BDLS task found for logsys &1 | The short text describes the object sufficiently | |
61 | 215 | No RFC destination found for source system (logsys) &1 | The short text describes the object sufficiently | |
62 | 216 | Task &1 ALE import not compatible with this taks: ALE configuration | The short text describes the object sufficiently | |
63 | 217 | No destination to BW client &1 found | The short text describes the object sufficiently | |
64 | 218 | Deletion of ALE settings successfully done | The short text describes the object sufficiently | |
65 | 219 | Successfully deleted ALE settings to Source System &1 | The short text describes the object sufficiently | |
66 | 220 | No RSBASIDOC entry found (RLOGSYS=&1; SLOGSYS=&2) | The short text describes the object sufficiently | |
67 | 221 | &1 &2 &3 &4 | The short text describes the object sufficiently | |
68 | 222 | &1&2&3&4 | The short text describes the object sufficiently | |
69 | 223 | Logsys &1: RFC destination &2 has errors | The short text describes the object sufficiently | |
70 | 224 | Successfully deleted ALE settings of BW system &1 | The short text describes the object sufficiently | |
71 | 225 | Error updating description of Logical System &1 | The short text describes the object sufficiently | |
72 | 226 | Successfully deleted ALE settings to BW system &1 | Space: object requires documentation | |
73 | 227 | Connection of BW system &1 still exists in RSBASIDOC | The short text describes the object sufficiently | |
74 | 228 | Connection of Source system &1 still exists in RSBASIDOC | The short text describes the object sufficiently | |
75 | 229 | function '&1' failed | The short text describes the object sufficiently | |
76 | 230 | Destination &1 is not local (system ID: &2; host: &3) | The short text describes the object sufficiently | |
77 | 231 | New Destination &1 is working fine | The short text describes the object sufficiently | |
78 | 232 | New Destination &1 not working | The short text describes the object sufficiently | |
79 | 233 | New Destination &1 does not exist | The short text describes the object sufficiently | |
80 | 234 | New Destination &1 was assigned to source system &2 in table RSLOGSYSDEST | The short text describes the object sufficiently | |
81 | 235 | Dest. &1 will be assigned to BW system &2 after BDLS via equal naming | The short text describes the object sufficiently | |
82 | 236 | Old destination &1 successfully deleted | The short text describes the object sufficiently | |
83 | 237 | Maintain task CL_RSO_DESTINATION_RENAME first | The short text describes the object sufficiently | |
84 | 238 | Old destination &1 does not exist (anymore); deletion not neccessary | The short text describes the object sufficiently | |
85 | 239 | New Destination &1 was assigned as TPBWMANDTRFC | The short text describes the object sufficiently | |
86 | 240 | New Destination &1 was assigned as BWMANDTRFC | The short text describes the object sufficiently | |
87 | 241 | Source System &1 missing in RSLOGSYSDEST | The short text describes the object sufficiently | |
88 | 242 | New entry created in RSLOGSYSDEST for &1 with destination &2 | The short text describes the object sufficiently | |
89 | 243 | Upload the .csv file attached to note 1707321 | Space: object requires documentation | |
90 | 244 | Check for Note implementation can only be done in background | The short text describes the object sufficiently | |
91 | 245 | Error when connecting to BW RFC destination &1 | The short text describes the object sufficiently | |
92 | 246 | This task list must only be executed on Client 000 | Space: object requires documentation | |
93 | 247 | Logical system &1 must be mapped to Logical System &2 in BDLS UI | Space: object requires documentation | |
94 | 248 | No mapping is maintained for Original Logical System &1 in BDLS UI | The short text describes the object sufficiently | |
95 | 249 | Target BW system &1 must be mapped with Original BW system &2 in BDLS UI | Space: object requires documentation |
History
Last changed on/by | 20131127 | SAP | |
SAP Release Created in | 731 |