SAP FB_ICRC_HDB_CUST_EDIT_MODE_SET Function Module for Set Edit Mode
FB_ICRC_HDB_CUST_EDIT_MODE_SET is a standard fb icrc hdb cust edit mode set SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Set Edit Mode 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 fb icrc hdb cust edit mode set FM, simply by entering the name FB_ICRC_HDB_CUST_EDIT_MODE_SET into the relevant SAP transaction such as SE37 or SE38.
Function Group: FB_ICRC_VIEWS
Program Name: SAPLFB_ICRC_VIEWS
Main Program: SAPLFB_ICRC_VIEWS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FB_ICRC_HDB_CUST_EDIT_MODE_SET 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 'FB_ICRC_HDB_CUST_EDIT_MODE_SET'"Set Edit Mode.
EXPORTING
ID_APPLICATION = "Application
ID_SUBAPPLICATION = "Sub-Application
ID_EDIT_MODE = "'X' = Change, ' ' = Display
IMPORTING Parameters details for FB_ICRC_HDB_CUST_EDIT_MODE_SET
ID_APPLICATION - Application
Data type: HDB_APPLICATIONOptional: No
Call by Reference: Yes
ID_SUBAPPLICATION - Sub-Application
Data type: HDB_SUBAPPLICATIONOptional: No
Call by Reference: Yes
ID_EDIT_MODE - 'X' = Change, SPACE = Display
Data type: BOOLE_DOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FB_ICRC_HDB_CUST_EDIT_MODE_SET 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_id_application | TYPE HDB_APPLICATION, " | |||
| lv_id_subapplication | TYPE HDB_SUBAPPLICATION, " | |||
| lv_id_edit_mode | TYPE BOOLE_D. " |
|   CALL FUNCTION 'FB_ICRC_HDB_CUST_EDIT_MODE_SET' "Set Edit Mode |
| EXPORTING | ||
| ID_APPLICATION | = lv_id_application | |
| ID_SUBAPPLICATION | = lv_id_subapplication | |
| ID_EDIT_MODE | = lv_id_edit_mode | |
| . " FB_ICRC_HDB_CUST_EDIT_MODE_SET | ||
ABAP code using 7.40 inline data declarations to call FM FB_ICRC_HDB_CUST_EDIT_MODE_SET
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.Search for further information about these or an SAP related objects