SRT_ADMIN - Administration Messages for SOAP Runtime
The following messages are stored in message class SRT_ADMIN: Administration Messages for SOAP Runtime.
It is part of development package SOAP_CONFIG in software component BC-ESI-WS-ABA-CFG. This development package consists of objects that can be grouped under "SOAP Configuration Framework".
It is part of development package SOAP_CONFIG in software component BC-ESI-WS-ABA-CFG. This development package consists of objects that can be grouped under "SOAP Configuration Framework".
Message Nr ▲ | Message Text |
|---|---|
| 000 | & & & & |
| 001 | WSRM event handler is active |
| 002 | WSRM event handler is not active |
| 003 | Task watcher is active |
| 004 | Task watcher is not active |
| 005 | Job & for SOAP runtime monitoring is active |
| 006 | Job & for SOAP runtime monitoring is not active |
| 007 | Job & for SOAP runtime management is active |
| 008 | Job & for SOAP runtime management is not active |
| 009 | Service RFC destination & is operational |
| 010 | Service RFC destination is not defined in central configuration |
| 011 | Connection for service RFC destination & tested successfully |
| 012 | Connection test for service RFC destination & unsuccessful |
| 013 | Service RFC destination & does not exist (SM59) |
| 014 | Type of RFC service destination & is not "3" |
| 015 | Authorization &1 is missing for service user &2 on destination &3 |
| 016 | Service user does not exist or does not have type S |
| 017 | & & & & |
| 018 | & |
| 019 | Authorizations of service user & are sufficient |
| 020 | Could not check authorizations of service user |
| 021 | Data collector for monitoring is activated |
| 022 | Data collector for monitoring is not activated |
| 023 | Client in RFC destination & is & and not & |
| 024 | Could not configure destination & |
| 025 | Destination & entered in central configuration |
| 026 | Registration of consumer queue &: Program & does not exist |
| 027 | Registration of provider queue &: Program & does not exist |
| 028 | Registration of consumer queue &: Queue name is not valid |
| 029 | Registration of provider queue &: Queue name is not valid |
| 030 | Registration of consumer queue &: Queue name is already registered |
| 031 | Registration of provider queue &: Queue name is already registered |
| 032 | Unknown error in queue registration |
| 033 | Consumer queue & registered successfully |
| 034 | Provider queue & registered successfully |
| 035 | Destination & is not valid for background qRFC |
| 036 | Outbound destination is operational for qRFC & |
| 037 | Outbound destination is not defined in central configuration |
| 038 | Connection test successful for outbound destination & |
| 039 | Connection test failed for outbound destination & |
| 040 | Outbound destination & does not exist (SM59) |
| 041 | Type of outbound destination & is not "3" |
| 042 | Authorization &1 is missing for service user &2 on destination &3 |
| 043 | Client setting not correct in destination & |
| 044 | bgRFC registration successful |
| 045 | bgRFC registration failed |
| 046 | Could not read service destination |
| 047 | Could not read outbound destination |
| 048 | Could not register C queue |
| 049 | Could not register P queue |
| 050 | Could not create service destination |
| 051 | Could not create outbound destination |
| 052 | Could not create service user & |
| 053 | Destination & is not suitable for classic RFC |
| 054 | Could not register S queue |
| 055 | No administration authorization |
| 056 | Error when reading global properties in SOAP Runtime |
| 057 | Automatic configuration of SOAP Runtime already complete |
| 058 | Could not register service destination & in SMQS |
| 059 | Could not register queue in bgRFC |
| 060 | Inbound bgRFC destination is not entered in technical configuration |
| 061 | Authorization check for user failed in destination & |
| 062 | Inbound destination changed from &1 to &2 |
| 063 | Cannot use inbound destination in bgRFC & |
| 064 | Could not register prefixes in bgRFC: & |
| 065 | Destination & does not have a valid qRFC version |
| 066 | Service destination & is operational |
| 067 | User & does not exist in system |
| 068 | Service destination in client & is not operational |
| 069 | Calling method & & with task id: & ( user: & ) |
| 070 | Connection to destination & failed: & |
| 071 | User at service destination has unsufficient RFC authority:& |
| 072 | Task for client &1 ,no service destination for client found |
| 073 | No authorization for &1: &2 |
| 074 | IDP database tables generated |
| 075 | Error generating IDP database tables: &1 |
| 076 | Setup of IDP successful |
| 077 | Setup of IDP failed |
| 088 | Class & called with method if_task_service_callback~on_failure |
| 089 | Task watcher task ID:&1 |
| 090 | Error when processing CALLBACK mechanism by task watcher |
| 091 | Authorization for object & missing |
| 092 | Service destination for client & is not registered |
| 093 | No authorization to check and change RFC Destination of Type "3" |
| 094 | UniCode settings of service destination & could not be read |
| 095 | UniCode settings of service destination & are correct |
| 096 | UniCode settings of service destination & failed |
| 097 | UniCode settings of service destination & corrected |
| 098 | UniCode settings of service destination & are NOT correct |
| 099 | No Inconsistency found |
| 100 | Starting checks for client (&): |
| 101 | End of checks for client (&) |
| 102 | Checking cross-system settings |
| 103 | Ending check of cross-system settings |
| 104 | Checking client-specific settings |
| 105 | Ending check of client-specific settings |
| 106 | Client-specific connection checks (destinations) |
| 107 | End of client-specific connection tests (destinations) |
| 109 | Status: Supervisor destination bgRFC |
| 110 | Status: Service destination in client & |
| 111 | Status: bgRFC destination |
| 112 | Status: WSRM Event Handler |
| 113 | Status: Task Watcher |
| 114 | Status: Job for Runtime Management |
| 115 | Status: Job for Runtime Monitoring |
| 116 | bgRFC destination & is not operational |
| 117 | bgRFC destination is operational |
| 118 | Destination & is operational |
| 119 | Destination & is not the destination configured in bgRFC: & |
| 120 | bgRFC supervisor destination is not registered |
| 121 | bgRFC supervisor destination is registered in client:& |
| 122 | All ICF nodes for SOAP Runtime are active |
| 123 | Not all ICF nodes for SOAP Runtime are active |
| 124 | Checking service user |
| 126 | Checking service destination |
| 127 | Checking bgrfc inbound destination |
| 128 | All icf nodes are active |
| 129 | Client: & Could not check icf nodes |
| 130 | HealthCheck returned at least one problem |
| 131 | Checking service destination |
| 132 | Checking icf nodes |
| 133 | HealthCheck returned no problem |
| 134 | Could not check icf nodes |
| 135 | Not all icf nodes are active! |
| 139 | Error text from runlevel framework:& |
| 140 | No specific error text found in exception from runlevel framework |
| 142 | Checking IDP settings |
| 143 | Checking bgrfc inbound destination |
| 144 | Client: & Technical setup processed |
| 145 | Client: & Service user created: & |
| 146 | Client: & Service destination created/confirmed: & |
| 147 | Inbound destination &2 for client &1 saved |
| 148 | Client: & Role & assigned to service user: & |
| 149 | Client: & Service destination not usable: & |
| 150 | Client: & Service Destination deleted: & |
| 151 | Client: & Could not delete service destination: & |
| 152 | Client: & No configuration exists |
| 153 | Client: & Service user deleted: & |
| 154 | Client: & Could not delete service user: & |
| 155 | Client: & Configuration of service destination reset |
| 156 | Client: & & |
| 157 | Client: & Registration of inbound destination changed |
| 158 | Client: & Registration of service destination changed |
| 162 | Client: & Inbound destination not usable:& |
| 163 | Client: & Run Report SRT_ADMIN_CHECK for problem analysis |
| 164 | Client: & bgRFC Supervisordestination & not usable |
| 165 | Checking bgRFC Supervisor destination |
| 166 | Client: & Task Watcher started |
| 167 | Client: & WSRM Event Handler started |
| 168 | Client: & Service user: & is not usable |
| 170 | Client: & Invalid message identifier found: & |
| 171 | Client: & & |
| 172 | Checking client & |
| 173 | Checking bgrfc configuration and runtime |
| 175 | Check Class & for inbound destination & confirmed. |
| 176 | Could not setup up inbound destination |
| 177 | Exception handling in periodic background (task watcher) |
| 199 | Could not read destination &1: &2 |
| 200 | Could not stop WSRM event handler |
| 201 | Could not read destination settings |
| 202 | Format problem when reading destination &1 |
| 203 | No authorization to read destination &1 |
| 204 | Unknown problem for read settings of destination &1 |
| 205 | Destination client setting is &1 instead of &2 |
| 206 | Destination &1 has no user setting |
| 207 | Destination &1 has wrong version |
| 208 | Unicodeflag on destination &1 is different than on client |
| 209 | No user specified in settings of destination &1 |
| 210 | Connection test with destination &1 failed: &2 |
| 211 | Authority check for destination &1 failed: &2 |
| 212 | Authorization missing for user &1 and object &2 |
| 213 | Could not check authority. Destination &1 is not available |
| 214 | User '&1' does not exist |
| 215 | User &1 is not of type "System" or "Service" |
| 216 | Role check failed: role &1 is missing for service user &2 |
| 217 | Could not delete user &1 |
| 218 | Could not delete destination &1 |
| 219 | Destination &1 deleted |
| 220 | Configuration of service destination &1 removed |
| 221 | Could not remove service destination &1 from configuration |
| 222 | Service user &1 already exists |
| 223 | Creation of Service user &1 failed |
| 224 | Role assignment for service user &1 failed |
| 225 | Deletion of Service user &1 failed |
| 226 | Service destination &1 created |
| 227 | Service destination &1 saved |
| 228 | Service destination &1 not saved |
| 229 | Service destination &1 and service user can only be created together |
| 230 | Password changed |
| 231 | Change of password failed |
| 232 | Service user &1 already exists |
| 233 | Service destination &1 already exists |
| 234 | Role &1 added to user &2 |
| 235 | Creation of service user &1 failed: &1 |
| 236 | No service destination defined. Further destination checks not possible |
| 237 | Role check successful: role &1 assigned to service user &2 |
| 238 | Role check failed for service user &1 and role &2: &3 |
| 239 | Reset of bgRFC inbound destination successful |
| 240 | Reset of bgRFC inbound destination failed |
| 241 | You can reset tthe bgRFC inbound destination only in client &1 |
| 242 | Connection test with destination &1 successful |
| 243 | Check settings of destination &1 successful |
| 244 | Role check for service user skipped: user &1 has not authorization |
| 245 | Destination &1 is operational |
| 246 | Destination &1 is not operational |
| 247 | Service user &1 deleted |
| 248 | Role &1 updated |
| 249 | Reset of service destination successful |
| 250 | Reset of service destination failed |
| 251 | Setup of service destination successful |
| 252 | Setup of service destination failed |
| 253 | Creation of bgRFC inbound destination &1 failed: &2 |
| 254 | Setup of bgRFC inbound destination successful |
| 255 | Setup of bgRFC inbound destination failed |
| 256 | Reset of bgRFC inbound destination successful |
| 257 | Reset of bgRFC inbound destination failed |
| 258 | You can reset the task watcher only in client &1 |
| 259 | Reset of Task watcher successful |
| 260 | Reset of Task watcher failed |
| 261 | Setup of Task watcher successful |
| 262 | Setup of Task watcher failed |
| 263 | BgRFC inbound destination can only be set up in client &1 |
| 264 | Task watcher can only be set up in client &1 |
| 265 | Task watcher is starting |
| 266 | Task watcher is stopping |
| 267 | Delay Logon User (WS Security) is operational |
| 268 | Setup of Delay Logon User (WS Security) successful |
| 269 | Setup of Delay Logon User (WS Security) failed |
| 270 | Delay Logon User (WS Security) is not operational |
| 271 | WSRM Event Handler can only be set up in client &1 |
| 272 | Reset of WSRM Event Handler successful |
| 273 | Reset of WSRM Event Handler failed |
| 274 | You can reset the WSRM Event Handler only in client &1 |
| 275 | WSRM Event could not be stopped |
| 276 | WSRM Event could not be started |
| 277 | WSRM Event Handler can only be set up in client &1 |
| 278 | Setup of WSRM Event Handler successful |
| 279 | Setup of WSRM Event Handler failed |
| 280 | WSRM Event handler is active |
| 281 | WSRM Event handler is not active |
| 282 | BGRFC Supervisor is active |
| 283 | BGRFC Supervisor is not active |
| 284 | Setup of ICF nodes successful |
| 285 | Setup of ICF nodes failed |
| 286 | Inbound destination in configuration cannot be deleted |
| 287 | User &1 created |
| 288 | WSRM Event Handler is not needed anymore in this release. |
| 289 | WSRM Event Handler is running even it is needed for this release. |
| 290 | WSRM Event Handler is not running (not needed for this release) |
| 291 | There is no Service RFC destination |
| 292 | Inbound destination not defined |
| 301 | Standard Check class &1 is not maintained at bgRFC destination &2 |
| 302 | Standard Check cklass & is not active |
| 303 | Not all Web service prefixes assigned to bgRRC inbound destination & |
| 304 | WS prefixes assigned to inbound destination & and instead of & |
| 305 | bgRFC inbound destination & is operational |
| 306 | bgRFC inbound destination & is not operational |
| 307 | bgRFC is operational |
| 308 | bgRFC is not operational |
| 309 | Idempotency is operational |
| 310 | Idempotency is not operational. For setup use transaction WSIDPADMIN. |
| 311 | AUTOABAP is deactivated. Profile paramter 'disp/autoabaptime' is 0 |
| 501 | Password change failed for service destination &1 |
| 502 | Password changed for service destination &1 |
| 503 | Profile for role SAP_BC_WEBSERVICE_SERVICE_USER generated and activated |