ILM_STOR_MBC - ILM Store: MBC Message Class
The following messages are stored in message class ILM_STOR_MBC: ILM Store: MBC Message Class.
It is part of development package S_ILM_STOR_MBC_CORE in software component BC-ILM-STO. This development package consists of objects that can be grouped under "ILM Store: MBC Core Functionalities".
It is part of development package S_ILM_STOR_MBC_CORE in software component BC-ILM-STO. This development package consists of objects that can be grouped under "ILM Store: MBC Core Functionalities".
Message Nr ▲ | Message Text |
|---|---|
| 000 | &1 &2 &3 &4 |
| 001 | Request Key: '&1' |
| 002 | Reference Key: '&1' |
| 007 | Process with reference_key('&1') reached maximum steps |
| 008 | FINISH-type Notification already exist for MBC process |
| 010 | ***--- General CX_ILM_STOR_MBC_RUNTIME messages ---*** |
| 011 | Unexpected exception '&1' when calling '&2' |
| 012 | Parameter '&1' is initial in method '&2' |
| 013 | Class instance '&1' not created in method '&2' |
| 014 | Deletion of record with req.key: '&1' failed. |
| 018 | Not authorized to execute targets on MBC Client side |
| 022 | Asynchronous communication not supported. Reason: '&1' |
| 026 | No record found in table '&1' for values '&2' in method '&3' |
| 027 | Updating queue with unknown notification state: '&1' |
| 028 | Wrong state order request. Current state: '&1', requested state: '&2' |
| 031 | Record already exists in table '&1' for key values '&2' |
| 032 | Message Back Communication is not allowed |
| 033 | Payload type error |
| 034 | Unable to create and add notification to queue |
| 035 | Notification version not found in initial MBC HTTP request |
| 039 | HTTP Client send request failed for request key '&1' |
| 040 | MBC process contains notification in 'ABORTED' state |
| 041 | HTTP Client receive request failed for request key '&1' |
| 046 | Cannot instantiate HTTP client for connection '&1'. Reason: '&2' |
| 047 | Queue lock failed for table '&1' |
| 050 | MBC process does not contain START-type notification in state 'PROCESED' |
| 051 | MBC 'START' Type multiple times in queue for URI_ID '&1' |
| 053 | No data in queue for URI_ID '&1', Current type '&2' |
| 054 | Wrong MBC Type provided '&1' |
| 055 | Target execution failed on notification with req.key &1 |
| 056 | Queue on '&1' side contains failed records |
| 058 | MBC context has been not initialized yet |
| 059 | MBC queue processing job could not be scheduled (reason: &1) |
| 060 | MBC queue processing job could not be copied (reason: &1) |
| 061 | MBC queue processing job scheduling could not be completed(reason: &1) |
| 062 | Casting failure. You tried to cast '&1' to intiger |
| 063 | Client context already exist. Can not set store context. |
| 064 | Store context already exist. Can not set client context. |
| 066 | Wrong MBC Type Order provided '&1' |
| 067 | Serialization of XML failed with following reason: '&1' |
| 068 | Deserialization of XML failed with following reason: '&1' |
| 073 | No response behavior defined for given HTML response parameters |
| 074 | No response behavior registred in CL_ILM_STOR_MBC_STATE. |
| 075 | Response for Asynchronous communication with parameters: &1 not found |
| 076 | Response for Synchronous communication with parameters: &1 not found |
| 078 | Bad HTTP Request. Reason: '&1' |
| 080 | You can only specify one of the optional parameters in method '&1' |
| 081 | Context is set to Client side, but Server side is required |
| 082 | Context is set to Server side, but Client side is required |
| 083 | Instance of class '&1' was not initialized |
| 085 | Object creation for Interface: '&1' with parameter '&2' failed |
| 087 | Target type for mbc_type: &1 and class_key: &2 Not found |
| 088 | No payload found for mbc_type: &1 and class_key: &2 |
| 090 | Record with request_key: &1 not in CLIENT QUEUE |
| 091 | Authorization have failed: &1 |
| 092 | Second Deletion phase(verification) failed for URI_ID: &1 |
| 093 | MBC process contain ABORT-type notification |
| 094 | Synchronous Notification with request_key '&1' failed. |
| 095 | Execution of target &1 failed. Reason "&2". |
| 100 | ***--- General RILM_STOR_MBC_PROCESSOR_MAIN messages ---*** |
| 101 | Starting MBC Asynchronous Queue Processing |
| 102 | Processing queue contains records in "FAILED" state |
| 103 | Unexpected exception occured |
| 104 | MBC Asynchronous Processor finished successfuly |
| 105 | MBC Asynchronous Process was aborted by ILM Store |
| 138 | ***--- General CX_ILM_STOR_MBC_EXCEPTION messages ---*** |
| 139 | MBC turned off in customizing for origin &1 |
| 140 | MBC not functioning. See logs for more information |
| 141 | Archive key information not found for MBC reference key &1 |
| 176 | ****-------- CL_ILM_STOR_MBC_FACADE ------**** |
| 177 | Initiating Message Back Communication [START] |
| 178 | Initiating Message Back Communication [STEP] |
| 179 | Initiating Message Back Communication [FINISH] |
| 180 | Initiating Message Back Communication [ABORT] |
| 181 | Archiving Key, Path or File not set in ILM Store Context. |
| 200 | ***--- General CX_ILM_STOR_MBC_CUST_RUNTIME messages ---*** |
| 201 | Failed to get customizing namespace: &1 for origin: &2 |
| 400 | ***--- General CX_ILM_STOR_MBC_CL_CUST_RUNTIM messages ---*** |
| 401 | MBC customizing failed on client side |
| 426 | ***--- General MBC messages For HTTPHANDLER ---*** |
| 427 | Synchronous processing started. |
| 428 | Asynchronous processing started. |
| 429 | Deletion of notifications failed.Ref.Key:'&1' |
| 431 | Bad request. Not supported method &1 was send for GET request method. |
| 432 | Bad request. Wrong info sent about synchronous/asynchronous processing. |
| 433 | Bad request. '&1' parameter is missing in request. |
| 436 | MBC authentication have failed. |
| 437 | MBC authorization have failed. |
| 439 | Record with req. key &1 not found |
| 447 | CF failed to instatiate object for IF: &1 with param: &2 |
| 449 | Record with req.id: &1 not found in TILM_STOR_MBCCQ. |
| 450 | Scheduling BG job for MBC failed |
| 458 | HTTP Request from host: '&1' received. |
| 460 | Session timeout occured |
| 461 | Communication error occurred during send |
| 462 | Communication error occurred during receive |
| 463 | Error when processing page |
| 464 | Session terminated with error &1 &2 and reason &3 |
| 465 | Notification type &1 with req.key &2 accepted |
| 466 | Notification type Start with req.key &1 processed |
| 467 | Execution of notification type &1 with req.key &2 scheduled |
| 468 | Testing mode. Processing of Req.key &1 in new task |
| 469 | BG job with name &1 already scheduled |
| 470 | BG job with name &1 successfully scheduled |
| 500 | ***--- General MBC messages for ADK and SRS ---*** |
| 501 | Archive key '&1' was memorized for asynchronous proc. of MBC request '&2' |
| 502 | ADK DELETE post-processing of ARKEY '&1' ended with RC '&2' |
| 503 | Switch to ADK PUT post-processing for MBC request '&1' and ARKEY '&2' |
| 504 | Switch back from ADK PUT post-proc. for MBC request '&1' and ARKEY '&2' |
| 505 | Switch to ADK DELETE post-proc. for MBC request '&1' and ARKEY '&2' |
| 506 | Switch back from ADK DELETE post-proc. for request '&1' and ARKEY '&2' |
| 507 | Deletion is processing in background with MBC. |
| 508 | Switch to ADK post-processing for aborted MBC request &1 |
| 509 | Switch back from ADK post-processing for aborted MBC request &1 |
| 510 | ADK PUT post-processing of ARKEY '&1' ended with RC '&2' |
| 511 | Calling 'ARCHIVE_ASYNC_STORE_FINISH' FM for ref.key &1 |
| 530 | ***--- General MBC messages ---*** |
| 531 | Deletion of records from MBC table TILM_STOR_MBC_Q failed. |
| 532 | MBC table TILM_STOR_MBC_Q successfully cleared. |
| 533 | Second phase of deletion from destr. list &1 has finished. |
| 534 | Second phase of deletion from destr. list &1 was initiated by MBC |
| 535 | Deletion of archive file with key &1. |
| 539 | MBC table TILM_STOR_MBCCQ successfully cleared. |
| 540 | Deletion of records from MBC table TILM_STOR_MBCCQ failed. |
| 541 | Execution of target '&1' started |
| 542 | Execution of target '&1' completed |
| 543 | Execution of Notification with req.key &1 started |