SAP FCC_HDR_EDIT Function Module for Editing of Header Information
FCC_HDR_EDIT is a standard fcc hdr edit SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Editing of Header Information 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 fcc hdr edit FM, simply by entering the name FCC_HDR_EDIT into the relevant SAP transaction such as SE37 or SE38.
Function Group: FCC_HDR_EDIT
Program Name: SAPLFCC_HDR_EDIT
Main Program: SAPLFCC_HDR_EDIT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FCC_HDR_EDIT 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 'FCC_HDR_EDIT'"Editing of Header Information.
EXPORTING
IS_HDR = "Header Information on Status Admin for Fast Close
* IS_INSTANCE = "Instances of a Profile
* ID_MODE = 'A' "
* ID_KIND = 'T' "
* IR_CFC = "Enhancement of CFC
IMPORTING
ES_HDR = "Header Information on Status Admin for Fast Close
ES_INSTANCE = "Instances of a Profile
ES_ROLLOUT_FIELD = "Rollout fields for selecting on screen
ET_ADDI_ROLLOUT_FLD = "List of Field Names
ED_CLT_CHANGED = "Single-Character Flag
EXCEPTIONS
E_USER_CANCELED = 1
IMPORTING Parameters details for FCC_HDR_EDIT
IS_HDR - Header Information on Status Admin for Fast Close
Data type: FCC_INST_HDROptional: No
Call by Reference: Yes
IS_INSTANCE - Instances of a Profile
Data type: FCC_INSTANCEOptional: Yes
Call by Reference: Yes
ID_MODE -
Data type: CHAR1Default: 'A'
Optional: Yes
Call by Reference: Yes
ID_KIND -
Data type: CHAR1Default: 'T'
Optional: Yes
Call by Reference: Yes
IR_CFC - Enhancement of CFC
Data type: CL_FCC_CFCOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for FCC_HDR_EDIT
ES_HDR - Header Information on Status Admin for Fast Close
Data type: FCC_INST_HDROptional: No
Call by Reference: Yes
ES_INSTANCE - Instances of a Profile
Data type: FCC_INSTANCEOptional: No
Call by Reference: Yes
ES_ROLLOUT_FIELD - Rollout fields for selecting on screen
Data type: FCC_S_ROLLOUT_FLD_SELOptional: No
Call by Reference: Yes
ET_ADDI_ROLLOUT_FLD - List of Field Names
Data type: DCBTFIELDSOptional: No
Call by Reference: Yes
ED_CLT_CHANGED - Single-Character Flag
Data type: CHAR1Optional: No
Call by Reference: Yes
EXCEPTIONS details
E_USER_CANCELED - Canceled by user
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FCC_HDR_EDIT 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_es_hdr | TYPE FCC_INST_HDR, " | |||
| lv_is_hdr | TYPE FCC_INST_HDR, " | |||
| lv_e_user_canceled | TYPE FCC_INST_HDR, " | |||
| lv_es_instance | TYPE FCC_INSTANCE, " | |||
| lv_is_instance | TYPE FCC_INSTANCE, " | |||
| lv_id_mode | TYPE CHAR1, " 'A' | |||
| lv_es_rollout_field | TYPE FCC_S_ROLLOUT_FLD_SEL, " | |||
| lv_id_kind | TYPE CHAR1, " 'T' | |||
| lv_et_addi_rollout_fld | TYPE DCBTFIELDS, " | |||
| lv_ir_cfc | TYPE CL_FCC_CFC, " | |||
| lv_ed_clt_changed | TYPE CHAR1. " |
|   CALL FUNCTION 'FCC_HDR_EDIT' "Editing of Header Information |
| EXPORTING | ||
| IS_HDR | = lv_is_hdr | |
| IS_INSTANCE | = lv_is_instance | |
| ID_MODE | = lv_id_mode | |
| ID_KIND | = lv_id_kind | |
| IR_CFC | = lv_ir_cfc | |
| IMPORTING | ||
| ES_HDR | = lv_es_hdr | |
| ES_INSTANCE | = lv_es_instance | |
| ES_ROLLOUT_FIELD | = lv_es_rollout_field | |
| ET_ADDI_ROLLOUT_FLD | = lv_et_addi_rollout_fld | |
| ED_CLT_CHANGED | = lv_ed_clt_changed | |
| EXCEPTIONS | ||
| E_USER_CANCELED = 1 | ||
| . " FCC_HDR_EDIT | ||
ABAP code using 7.40 inline data declarations to call FM FCC_HDR_EDIT
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_id_mode) | = 'A'. | |||
| DATA(ld_id_kind) | = 'T'. | |||
Search for further information about these or an SAP related objects