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