RSAPI_CTC - Messages to be shown for BW SAPI configurations
The following messages are stored in message class RSAPI_CTC: Messages to be shown for BW SAPI configurations.
It is part of development package RSAPI_CTC in software component BC-BW. This development package consists of objects that can be grouped under "CTC objects for BW SAPI systems".
It is part of development package RSAPI_CTC in software component BC-BW. This development package consists of objects that can be grouped under "CTC objects for BW SAPI systems".
Message Nr ▲ | Message Text |
---|---|
000 | &1 is a BW system. Perform BW System Copy Configurations |
001 | System &1 is connected to BW systems. Connection will be disconnected |
002 | Error in creation of ALV List |
003 | Disconnecting BW system &1 from BW source system &2... |
004 | BW system &1 successfully disconnected from BW source system &2 |
005 | DataSources in 'Details' restored for BW system &1 |
006 | DataSources in "Details" could not be restored for BW system &1 |
007 | Select the required systems and press execute (F8) |
008 | Action cancelled by user |
009 | System is not a BW system or a source system |
010 | Error when updating delta queue for BW system &1 |
011 | Error when updating ALE port of BW system &1 in BW source system &2 |
012 | Error when activating ALE partner of BW system &1 in BW source system &2 |
013 | ALE/IDOC details updated |
014 | Delta queue restored for BW system &1 |
015 | Invalid RFC destination &1 to local source client &2. Check connection. |
016 | Maintain RFC destination for local source client &1 |
017 | No BW systems are connected. This step will not be executed. |
018 | Connections to OSS is not maintained. Cannot get latest version of notes |
019 | Include task "Select System Connections to be Retained After Copy" |
020 | Some of the required notes are not yet implemented. See details |
021 | All the required notes are implemented |
022 | RFC destination is not maintained for local Source Client &1 |
023 | BW system &1 will also be copied. No need to disconnect from &2. |
024 | Note 1523687 has to be implemented in the system |
025 | BDLS task has wrong mapping for system &1; it has to be a BW system |
026 | Mappings for logical system &1 not maintained in BDLS task |
027 | Enable 'Release Jobs' for task 'Conversion of Logical System Names' |
028 | BW system &1 is not correctly connected to BW source system &2 |
029 | System &1 is not a BW system |
030 | BW source system &1 has to be maintained in BDLS task |
031 | No authorizations to execute this task |
032 | Connections to system &1 correct |
033 | Corrections in SAP Note &1 missing in system &2. Implement this Note. |
034 | RFC destination to local BW client not maintained |
035 | Connections to Systems are present. Select in UI to retain Connections |
036 | Connections to System &1 failed. Repair the connection |
037 | System copy automation does not support BW only system copy |
038 | BW systems are not connected to this system. No need for RFC destination. |
039 | Error when calling documentation |
040 | Failed to check BW-Source connection as RFC Destination &1 is incorrect |
041 | Will system &1 be refreshed by copying from another system? |
042 | Authorization check failed for user of RFC destination &1 |
043 | Determine the copy scenario |
044 | Select relevant copy scenario to transfer system names to BDLS task |
045 | Copy scenario is already selected as 'Refresh'. |
046 | Copy scenario is already selected as 'New Installation'. |
047 | Copy scenario was not selected by user. It is not possible to select now. |
048 | IDOC &1 used to connect system &2 is not assigned to any package |
049 | Connection check impossible due to missing destination to local BW client |
050 | Maintain target client for RFC destination &1 |
051 | Corrections in SAP Note &1 missing in system &2 |
052 | Ensure Secure Store is correctly configured by executing relevant tasks |
053 | BW system &1 is not up to date. Connection cannot be auto-restored. |
054 | BDLS UI contains mappings to logical system &1. Remove this mapping. |
055 | ODP-Connection to &1 not deleted, since connection retained |
210 | Update of ALE ports and settings successfully done |
211 | Error updating ALE port of Source System &1 |
212 | Successfully activated ALE partner of Source System &1 |
213 | Predecessor task &1 not found in the tasklist |
214 | No entry in BDLS task found for logsys &1 |
215 | No RFC destination found for source system (logsys) &1 |
216 | Task &1 ALE import not compatible with this taks: ALE configuration |
217 | No destination to BW client &1 found |
218 | Deletion of ALE settings successfully done |
219 | Successfully deleted ALE settings to Source System &1 |
220 | No RSBASIDOC entry found (RLOGSYS=&1; SLOGSYS=&2) |
221 | &1 &2 &3 &4 |
222 | &1&2&3&4 |
223 | Logsys &1: RFC destination &2 has errors |
224 | Successfully deleted ALE settings of BW system &1 |
225 | Error updating description of Logical System &1 |
226 | Successfully deleted ALE settings to BW system &1 |
227 | Connection of BW system &1 still exists in RSBASIDOC |
228 | Connection of Source system &1 still exists in RSBASIDOC |
229 | function '&1' failed |
230 | Destination &1 is not local (system ID: &2; host: &3) |
231 | New Destination &1 is working fine |
232 | New Destination &1 not working |
233 | New Destination &1 does not exist |
234 | New Destination &1 was assigned to source system &2 in table RSLOGSYSDEST |
235 | Dest. &1 will be assigned to BW system &2 after BDLS via equal naming |
236 | Old destination &1 successfully deleted |
237 | Maintain task CL_RSO_DESTINATION_RENAME first |
238 | Old destination &1 does not exist (anymore); deletion not neccessary |
239 | New Destination &1 was assigned as TPBWMANDTRFC |
240 | New Destination &1 was assigned as BWMANDTRFC |
241 | Source System &1 missing in RSLOGSYSDEST |
242 | New entry created in RSLOGSYSDEST for &1 with destination &2 |
243 | Upload the .csv file attached to note 1707321 |
244 | Check for Note implementation can only be done in background |
245 | Error when connecting to BW RFC destination &1 |
246 | This task list must only be executed on Client 000 |
247 | Logical system &1 must be mapped to Logical System &2 in BDLS UI |
248 | No mapping is maintained for Original Logical System &1 in BDLS UI |
249 | Target BW system &1 must be mapped with Original BW system &2 in BDLS UI |