SAP CRM_IST_MESSAGE_DELETE Function Module for Delete message from message log
CRM_IST_MESSAGE_DELETE is a standard crm ist message delete SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Delete message from message log processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for crm ist message delete FM, simply by entering the name CRM_IST_MESSAGE_DELETE into the relevant SAP transaction such as SE37 or SE38.
Function Group: CRM_IST_ORDER_TOOLS
Program Name: SAPLCRM_IST_ORDER_TOOLS
Main Program: SAPLCRM_IST_ORDER_TOOLS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function CRM_IST_MESSAGE_DELETE pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'CRM_IST_MESSAGE_DELETE'"Delete message from message log.
EXPORTING
* IV_CALLER_NAME = 'ORDERADM_I' "Name of the Calling Subobject (CRMC_OBJECTS)
* IV_REF_OBJECT = "GUID of Item / Header to Be Processed
* IV_REF_KIND = 'B' "Header = A, Item = B
IV_MSGNO_LOW = "Message Number
IV_MSGNO_HIGH = "Message Number
* IV_MSGID = 'CRM_IST_CONTRACT' "Message Class
* IT_ORDERADM_I = "Item: Database + Dynamic Part
IMPORTING
EV_MSGTY = "Messages, Message Type
ES_MSG_HANDLE = "Application Log: Message Handle
EXCEPTIONS
APPL_LOG_ERROR = 1
IMPORTING Parameters details for CRM_IST_MESSAGE_DELETE
IV_CALLER_NAME - Name of the Calling Subobject (CRMC_OBJECTS)
Data type: CRMT_OBJECT_NAMEDefault: 'ORDERADM_I'
Optional: Yes
Call by Reference: Yes
IV_REF_OBJECT - GUID of Item / Header to Be Processed
Data type: CRMT_OBJECT_GUIDOptional: Yes
Call by Reference: Yes
IV_REF_KIND - Header = A, Item = B
Data type: CRMT_OBJECT_KINDDefault: 'B'
Optional: Yes
Call by Reference: Yes
IV_MSGNO_LOW - Message Number
Data type: SYMSGNOOptional: No
Call by Reference: Yes
IV_MSGNO_HIGH - Message Number
Data type: SYMSGNOOptional: No
Call by Reference: Yes
IV_MSGID - Message Class
Data type: SYMSGIDDefault: 'CRM_IST_CONTRACT'
Optional: Yes
Call by Reference: Yes
IT_ORDERADM_I - Item: Database + Dynamic Part
Data type: CRMT_ORDERADM_I_WRKTOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for CRM_IST_MESSAGE_DELETE
EV_MSGTY - Messages, Message Type
Data type: SYMSGTYOptional: No
Call by Reference: Yes
ES_MSG_HANDLE - Application Log: Message Handle
Data type: BALMSGHNDLOptional: No
Call by Reference: Yes
EXCEPTIONS details
APPL_LOG_ERROR - The log was not found
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CRM_IST_MESSAGE_DELETE Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.DATA: | ||||
lv_ev_msgty | TYPE SYMSGTY, " | |||
lv_appl_log_error | TYPE SYMSGTY, " | |||
lv_iv_caller_name | TYPE CRMT_OBJECT_NAME, " 'ORDERADM_I' | |||
lv_es_msg_handle | TYPE BALMSGHNDL, " | |||
lv_iv_ref_object | TYPE CRMT_OBJECT_GUID, " | |||
lv_iv_ref_kind | TYPE CRMT_OBJECT_KIND, " 'B' | |||
lv_iv_msgno_low | TYPE SYMSGNO, " | |||
lv_iv_msgno_high | TYPE SYMSGNO, " | |||
lv_iv_msgid | TYPE SYMSGID, " 'CRM_IST_CONTRACT' | |||
lv_it_orderadm_i | TYPE CRMT_ORDERADM_I_WRKT. " |
  CALL FUNCTION 'CRM_IST_MESSAGE_DELETE' "Delete message from message log |
EXPORTING | ||
IV_CALLER_NAME | = lv_iv_caller_name | |
IV_REF_OBJECT | = lv_iv_ref_object | |
IV_REF_KIND | = lv_iv_ref_kind | |
IV_MSGNO_LOW | = lv_iv_msgno_low | |
IV_MSGNO_HIGH | = lv_iv_msgno_high | |
IV_MSGID | = lv_iv_msgid | |
IT_ORDERADM_I | = lv_it_orderadm_i | |
IMPORTING | ||
EV_MSGTY | = lv_ev_msgty | |
ES_MSG_HANDLE | = lv_es_msg_handle | |
EXCEPTIONS | ||
APPL_LOG_ERROR = 1 | ||
. " CRM_IST_MESSAGE_DELETE |
ABAP code using 7.40 inline data declarations to call FM CRM_IST_MESSAGE_DELETE
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.DATA(ld_iv_caller_name) | = 'ORDERADM_I'. | |||
DATA(ld_iv_ref_kind) | = 'B'. | |||
DATA(ld_iv_msgid) | = 'CRM_IST_CONTRACT'. | |||
Search for further information about these or an SAP related objects