/BDL/TASKMANAGER - Messages for SDCCN Taskmanager
The following messages are stored in message class /BDL/TASKMANAGER: Messages for SDCCN Taskmanager.
It is part of development package /BDL/TASKMANAGER in software component SV-SMG-SDD. This development package consists of objects that can be grouped under "Task Manager".
It is part of development package /BDL/TASKMANAGER in software component SV-SMG-SDD. This development package consists of objects that can be grouped under "Task Manager".
Message Nr ▲ | Message Text |
|---|---|
| 010 | Service Definitions have been deleted & |
| 011 | Deletion of Service Definitions failed & |
| 012 | Generation of Logfunc-Includes completed & |
| 013 | Generation error: & |
| 014 | Task & for Service Definition Refresh was created |
| 015 | Creation of task for Service Definition Refresh failed & |
| 017 | Creation of task failed |
| 020 | Could not read download data |
| 021 | XML file is emtpy |
| 022 | Could not read download data: download not found |
| 023 | Could not read download data: error extracting download |
| 024 | Could not read download data: errror converting result |
| 048 | SDCC background job is still active |
| 049 | SDCC background job was deactivated |
| 050 | SDCC background job could not be deactivated |
| 051 | Activation for satellite system |
| 052 | Activation for Solution Manager system |
| 053 | Customizing was already filled |
| 054 | Customizing has been filled |
| 055 | Filling customizing failed |
| 056 | RFC connection to SAP's support backbone has been created (SDCC_OSS) |
| 057 | Creation of RFC connection to SAP's support backbone failed (&1) |
| 058 | RFC connection to SAP's support backbone is already existing |
| 059 | Standard tasks are already existing |
| 060 | Tasks 'Maintenance Package' and 'Service Preparation Check' created |
| 061 | Creation of standard tasks failed |
| 062 | SDCCN background job is already active (/BDL/TASK_PROCESSOR) |
| 063 | SDCCN background job has been activated (/BDL/TASK_PROCESSOR) |
| 064 | Activation of SDCCN background job failed |
| 065 | Old transaction SDCC has been locked |
| 066 | Old transaction SDCC could not be locked |
| 067 | Old transaction SDCC was already locked |
| 068 | RFC connection 'NONE' was already registered in SDCCN |
| 069 | RFC connection 'NONE' has been registered in SDCCN |
| 070 | RFC connection 'NONE' could not be registered in SDCCN |
| 071 | RFC connection &1 is already registered in SDCCN and flagged as 'Master' |
| 072 | RFC connection &1 has been registered in SDCCN and flagged as 'Master' |
| 073 | RFC connection &1 could not be registered in SDCCN |
| 074 | Customizing is not filled |
| 075 | SDCCN background job is not active |
| 076 | No connection to SAP's support backbone registered in SDCCN |
| 077 | RFC connection &1 does not point to SAP's support backbone |
| 078 | RFC connection &1 does not work |
| 079 | RFC connection &1 is not registered in SDCCN as 'Master' |
| 080 | No RFC connection pointing to system itself is registered in SDCCN |
| 081 | Task processor cannot be started, SDCCN is not activated (see longtext) |
| 090 | Error testing HTTP connections to SAP Backbone |
| 100 | Deletion of session data cancelled |
| 101 | Only whole downloads can be deleted |
| 102 | No data found |
| 103 | Session data was deleted (& entries) |
| 104 | Not all session data could be deleted |
| 105 | SDCCN reference download, deletion not possible |
| 106 | Only complete deletion possible |
| 107 | Only whole downloads or data for logical functions can be deleted |
| 108 | Restoring of deleted session data cancelled |
| 109 | Session data could not be restored |
| 110 | Session data was restored |
| 111 | Failed to get the installation number from HTTP destination & |
| 112 | Failed to add destination & |
| 113 | Destination & has been registered successfully |
| 114 | A periodic EWA task & already exists, do nothing |
| 115 | Task & is created |
| 120 | No authority for execution (Activity &1 Authority Object &2) |
| 121 | Authority &1 is missing |
| 122 | &1 &2 &3 &4 |
| 123 | To overwrite existing setting, select force mode |
| 124 | Check successful |
| 125 | RFC destination &1 already exists |
| 126 | RFC destination &1 created |
| 127 | RFC destination &1 creation failed |
| 128 | Call to &1 failed; return code &2 |
| 200 | Set &1 not available |