SAP ICF_MODIFY_RECORDER_EXPIRATION Function Module for
ICF_MODIFY_RECORDER_EXPIRATION is a standard icf modify recorder expiration 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 modify recorder expiration FM, simply by entering the name ICF_MODIFY_RECORDER_EXPIRATION 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_MODIFY_RECORDER_EXPIRATION 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_MODIFY_RECORDER_EXPIRATION'".
EXPORTING
* ACTION = 4 "
CHANGING
* EXPIRATION_ENTRY = "Store ICF Documents (Related to Recorder Layer)
* EXPIRATION_DAYS = "Number of days
* EXPIRATION_TIME = "Date and Time, Current Application Server Time
* ACTION_PERMISSION = "Check Recorder Actions (Download, Upload)
* MAX_USER_ENTRIES = "
* MAX_FAILED_LOGON_ENTRIES = "
EXCEPTIONS
ICF_UNKNOWN_ACTION = 1 ICF_NO_AUTHORITY = 2 ICF_MESSAGE_LOCKED = 3 ICF_EXECUTION_DENIED = 4 ICF_NO_MESSAGE_FOUND = 5
IMPORTING Parameters details for ICF_MODIFY_RECORDER_EXPIRATION
ACTION -
Data type: IDefault: 4
Optional: No
Call by Reference: Yes
CHANGING Parameters details for ICF_MODIFY_RECORDER_EXPIRATION
EXPIRATION_ENTRY - Store ICF Documents (Related to Recorder Layer)
Data type: ICFRECORDEROptional: Yes
Call by Reference: Yes
EXPIRATION_DAYS - Number of days
Data type: IOptional: Yes
Call by Reference: Yes
EXPIRATION_TIME - Date and Time, Current Application Server Time
Data type: SYUZEITOptional: Yes
Call by Reference: Yes
ACTION_PERMISSION - Check Recorder Actions (Download, Upload)
Data type: ICFREC_PERMISSIONOptional: Yes
Call by Reference: Yes
MAX_USER_ENTRIES -
Data type: IOptional: Yes
Call by Reference: Yes
MAX_FAILED_LOGON_ENTRIES -
Data type: IOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
ICF_UNKNOWN_ACTION -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ICF_NO_AUTHORITY - You are not authorized to carry out this action
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ICF_MESSAGE_LOCKED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ICF_EXECUTION_DENIED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ICF_NO_MESSAGE_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ICF_MODIFY_RECORDER_EXPIRATION 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_action | TYPE I, " 4 | |||
| lv_expiration_entry | TYPE ICFRECORDER, " | |||
| lv_icf_unknown_action | TYPE ICFRECORDER, " | |||
| lv_expiration_days | TYPE I, " | |||
| lv_icf_no_authority | TYPE I, " | |||
| lv_expiration_time | TYPE SYUZEIT, " | |||
| lv_icf_message_locked | TYPE SYUZEIT, " | |||
| lv_action_permission | TYPE ICFREC_PERMISSION, " | |||
| lv_icf_execution_denied | TYPE ICFREC_PERMISSION, " | |||
| lv_max_user_entries | TYPE I, " | |||
| lv_icf_no_message_found | TYPE I, " | |||
| lv_max_failed_logon_entries | TYPE I. " |
|   CALL FUNCTION 'ICF_MODIFY_RECORDER_EXPIRATION' " |
| EXPORTING | ||
| ACTION | = lv_action | |
| CHANGING | ||
| EXPIRATION_ENTRY | = lv_expiration_entry | |
| EXPIRATION_DAYS | = lv_expiration_days | |
| EXPIRATION_TIME | = lv_expiration_time | |
| ACTION_PERMISSION | = lv_action_permission | |
| MAX_USER_ENTRIES | = lv_max_user_entries | |
| MAX_FAILED_LOGON_ENTRIES | = lv_max_failed_logon_entries | |
| EXCEPTIONS | ||
| ICF_UNKNOWN_ACTION = 1 | ||
| ICF_NO_AUTHORITY = 2 | ||
| ICF_MESSAGE_LOCKED = 3 | ||
| ICF_EXECUTION_DENIED = 4 | ||
| ICF_NO_MESSAGE_FOUND = 5 | ||
| . " ICF_MODIFY_RECORDER_EXPIRATION | ||
ABAP code using 7.40 inline data declarations to call FM ICF_MODIFY_RECORDER_EXPIRATION
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_action) | = 4. | |||
Search for further information about these or an SAP related objects