SAP ICF_EXECUTE_RECORDER_REQUEST Function Module for









ICF_EXECUTE_RECORDER_REQUEST is a standard icf execute recorder request SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 icf execute recorder request FM, simply by entering the name ICF_EXECUTE_RECORDER_REQUEST into the relevant SAP transaction such as SE37 or SE38.

Function Group: SICFRECORDER
Program Name: SAPLSICFRECORDER
Main Program: SAPLSICFRECORDER
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function ICF_EXECUTE_RECORDER_REQUEST 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 'ICF_EXECUTE_RECORDER_REQUEST'"
  EXPORTING
*  MESSAGE_ID =  "
*  DOWNLOAD_MESSAGE_LIST =  "Export ICF Recorder Entries
*  CHECK_SIGNATURE = 'X' "
*  ACTION = 4 "
*  LOGON_USERNAME =  "SAP System, User Logon Name
*  LOGON_PASSWORD =  "Logon ID
*  LOGON_LANGUAGE =  "SAP R/3 System, Current Language
*  FILENAME =  "
*  PROTOCOL_ACTION = ' ' "

 IMPORTING
   REQUEST_ENTITY =  "
   RESPONSE_ENTITY =  "
   ERROR_CODE =  "
   ERROR_MESSAGE =  "
   PROTOCOLED_ACTIONS =  "List of Logged Actions for ICFRECORDER Entry
   PROTOCOLED_LOGON =  "Logon Information for Internet Communication Framework
   PROTOCOLED_FIELDS =  "
   UPLOAD_MESSAGE_LIST =  "Imported ICF Recorder Entries

CHANGING
*  ICFRECORDER_ENTRY =  "Store ICF Documents (Related to Recorder Layer)

EXCEPTIONS
   ICF_NO_MESSAGE_FOUND = 1    ICF_EXECUTION_DENIED = 10    ICF_MESSAGE_LOCKED = 11    ICF_NO_REQUEST_MESSAGE = 12    ICF_SIGNATURE_MISMATCH = 13    ICF_RUNTIME_ERROR_OCCURED = 14    ICF_EXECUTION_FAILED = 2    ICF_PLUGIN_NOT_ACTIVE = 3    ICF_REMOTE_EXECUTION_FAILED = 4    ICF_NO_AUTHORITY = 5    ICF_UNKNOWN_ACTION = 6    ICF_FILE_TRANSFER_FAILED = 7    ICF_MEMORY_TRANSFER_FAILD = 8    ICF_MISSING_INFORMATION = 9
.



IMPORTING Parameters details for ICF_EXECUTE_RECORDER_REQUEST

MESSAGE_ID -

Data type: SYSUUID_C
Optional: Yes
Call by Reference: Yes

DOWNLOAD_MESSAGE_LIST - Export ICF Recorder Entries

Data type: ICFRECODER_DOWNLOAD
Optional: Yes
Call by Reference: Yes

CHECK_SIGNATURE -

Data type: C
Default: 'X'
Optional: Yes
Call by Reference: Yes

ACTION -

Data type: I
Default: 4
Optional: Yes
Call by Reference: Yes

LOGON_USERNAME - SAP System, User Logon Name

Data type: SYUNAME
Optional: Yes
Call by Reference: Yes

LOGON_PASSWORD - Logon ID

Data type: CHAR8
Optional: Yes
Call by Reference: No ( called with pass by value option)

LOGON_LANGUAGE - SAP R/3 System, Current Language

Data type: SYLANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)

FILENAME -

Data type: STRING
Optional: Yes
Call by Reference: Yes

PROTOCOL_ACTION -

Data type: CHAR1
Default: ' '
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for ICF_EXECUTE_RECORDER_REQUEST

REQUEST_ENTITY -

Data type: IF_HTTP_REQUEST
Optional: No
Call by Reference: Yes

RESPONSE_ENTITY -

Data type: IF_HTTP_RESPONSE
Optional: No
Call by Reference: Yes

ERROR_CODE -

Data type: SYSUBRC
Optional: No
Call by Reference: No ( called with pass by value option)

ERROR_MESSAGE -

Data type: STRING
Optional: No
Call by Reference: No ( called with pass by value option)

PROTOCOLED_ACTIONS - List of Logged Actions for ICFRECORDER Entry

Data type: ICFRECODER_ACTIONS
Optional: No
Call by Reference: Yes

PROTOCOLED_LOGON - Logon Information for Internet Communication Framework

Data type: ICFRECODER_LOGON
Optional: No
Call by Reference: Yes

PROTOCOLED_FIELDS -

Data type: IHTTP_RECORDER_FIELDS
Optional: No
Call by Reference: Yes

UPLOAD_MESSAGE_LIST - Imported ICF Recorder Entries

Data type: ICFRECODER_UPLOAD
Optional: No
Call by Reference: Yes

CHANGING Parameters details for ICF_EXECUTE_RECORDER_REQUEST

ICFRECORDER_ENTRY - Store ICF Documents (Related to Recorder Layer)

Data type: ICFRECORDER
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

ICF_NO_MESSAGE_FOUND -

Data type:
Optional: No
Call by Reference: Yes

ICF_EXECUTION_DENIED -

Data type:
Optional: No
Call by Reference: Yes

ICF_MESSAGE_LOCKED -

Data type:
Optional: No
Call by Reference: Yes

ICF_NO_REQUEST_MESSAGE -

Data type:
Optional: No
Call by Reference: Yes

ICF_SIGNATURE_MISMATCH -

Data type:
Optional: No
Call by Reference: Yes

ICF_RUNTIME_ERROR_OCCURED -

Data type:
Optional: No
Call by Reference: Yes

ICF_EXECUTION_FAILED -

Data type:
Optional: No
Call by Reference: Yes

ICF_PLUGIN_NOT_ACTIVE -

Data type:
Optional: No
Call by Reference: Yes

ICF_REMOTE_EXECUTION_FAILED -

Data type:
Optional: No
Call by Reference: Yes

ICF_NO_AUTHORITY - You are not authorized to carry out this action

Data type:
Optional: No
Call by Reference: Yes

ICF_UNKNOWN_ACTION -

Data type:
Optional: No
Call by Reference: Yes

ICF_FILE_TRANSFER_FAILED -

Data type:
Optional: No
Call by Reference: Yes

ICF_MEMORY_TRANSFER_FAILD -

Data type:
Optional: No
Call by Reference: Yes

ICF_MISSING_INFORMATION - Missing Information

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ICF_EXECUTE_RECORDER_REQUEST 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_message_id  TYPE SYSUUID_C, "   
lv_request_entity  TYPE IF_HTTP_REQUEST, "   
lv_icfrecorder_entry  TYPE ICFRECORDER, "   
lv_icf_no_message_found  TYPE ICFRECORDER, "   
lv_icf_execution_denied  TYPE ICFRECORDER, "   
lv_icf_message_locked  TYPE ICFRECORDER, "   
lv_icf_no_request_message  TYPE ICFRECORDER, "   
lv_icf_signature_mismatch  TYPE ICFRECORDER, "   
lv_icf_runtime_error_occured  TYPE ICFRECORDER, "   
lv_response_entity  TYPE IF_HTTP_RESPONSE, "   
lv_icf_execution_failed  TYPE IF_HTTP_RESPONSE, "   
lv_download_message_list  TYPE ICFRECODER_DOWNLOAD, "   
lv_error_code  TYPE SYSUBRC, "   
lv_check_signature  TYPE C, "   'X'
lv_icf_plugin_not_active  TYPE C, "   
lv_action  TYPE I, "   4
lv_error_message  TYPE STRING, "   
lv_icf_remote_execution_failed  TYPE STRING, "   
lv_logon_username  TYPE SYUNAME, "   
lv_icf_no_authority  TYPE SYUNAME, "   
lv_protocoled_actions  TYPE ICFRECODER_ACTIONS, "   
lv_logon_password  TYPE CHAR8, "   
lv_protocoled_logon  TYPE ICFRECODER_LOGON, "   
lv_icf_unknown_action  TYPE ICFRECODER_LOGON, "   
lv_logon_language  TYPE SYLANGU, "   
lv_protocoled_fields  TYPE IHTTP_RECORDER_FIELDS, "   
lv_icf_file_transfer_failed  TYPE IHTTP_RECORDER_FIELDS, "   
lv_filename  TYPE STRING, "   
lv_upload_message_list  TYPE ICFRECODER_UPLOAD, "   
lv_icf_memory_transfer_faild  TYPE ICFRECODER_UPLOAD, "   
lv_protocol_action  TYPE CHAR1, "   ' '
lv_icf_missing_information  TYPE CHAR1. "   

  CALL FUNCTION 'ICF_EXECUTE_RECORDER_REQUEST'  "
    EXPORTING
         MESSAGE_ID = lv_message_id
         DOWNLOAD_MESSAGE_LIST = lv_download_message_list
         CHECK_SIGNATURE = lv_check_signature
         ACTION = lv_action
         LOGON_USERNAME = lv_logon_username
         LOGON_PASSWORD = lv_logon_password
         LOGON_LANGUAGE = lv_logon_language
         FILENAME = lv_filename
         PROTOCOL_ACTION = lv_protocol_action
    IMPORTING
         REQUEST_ENTITY = lv_request_entity
         RESPONSE_ENTITY = lv_response_entity
         ERROR_CODE = lv_error_code
         ERROR_MESSAGE = lv_error_message
         PROTOCOLED_ACTIONS = lv_protocoled_actions
         PROTOCOLED_LOGON = lv_protocoled_logon
         PROTOCOLED_FIELDS = lv_protocoled_fields
         UPLOAD_MESSAGE_LIST = lv_upload_message_list
    CHANGING
         ICFRECORDER_ENTRY = lv_icfrecorder_entry
    EXCEPTIONS
        ICF_NO_MESSAGE_FOUND = 1
        ICF_EXECUTION_DENIED = 10
        ICF_MESSAGE_LOCKED = 11
        ICF_NO_REQUEST_MESSAGE = 12
        ICF_SIGNATURE_MISMATCH = 13
        ICF_RUNTIME_ERROR_OCCURED = 14
        ICF_EXECUTION_FAILED = 2
        ICF_PLUGIN_NOT_ACTIVE = 3
        ICF_REMOTE_EXECUTION_FAILED = 4
        ICF_NO_AUTHORITY = 5
        ICF_UNKNOWN_ACTION = 6
        ICF_FILE_TRANSFER_FAILED = 7
        ICF_MEMORY_TRANSFER_FAILD = 8
        ICF_MISSING_INFORMATION = 9
. " ICF_EXECUTE_RECORDER_REQUEST




ABAP code using 7.40 inline data declarations to call FM ICF_EXECUTE_RECORDER_REQUEST

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_check_signature) = 'X'.
 
 
DATA(ld_action) = 4.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
DATA(ld_protocol_action) = ' '.
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!