SAP FMED_GET_HEADER Function Module for Get header contents from FMBH
FMED_GET_HEADER is a standard fmed get header SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get header contents from FMBH 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 fmed get header FM, simply by entering the name FMED_GET_HEADER into the relevant SAP transaction such as SE37 or SE38.
Function Group: FMED_DATABASE_ACCESS
Program Name: SAPLFMED_DATABASE_ACCESS
Main Program: SAPLFMED_DATABASE_ACCESS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FMED_GET_HEADER 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 'FMED_GET_HEADER'"Get header contents from FMBH.
EXPORTING
I_F_DOCID = "FM entry document ID
IMPORTING
E_F_FMBH = "Entry document header
EXCEPTIONS
NOT_FOUND = 1
IMPORTING Parameters details for FMED_GET_HEADER
I_F_DOCID - FM entry document ID
Data type: FMED_S_DOCIDOptional: No
Call by Reference: Yes
EXPORTING Parameters details for FMED_GET_HEADER
E_F_FMBH - Entry document header
Data type: FMBHOptional: No
Call by Reference: Yes
EXCEPTIONS details
NOT_FOUND - No record found
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FMED_GET_HEADER 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_e_f_fmbh | TYPE FMBH, " | |||
| lv_i_f_docid | TYPE FMED_S_DOCID, " | |||
| lv_not_found | TYPE FMED_S_DOCID. " |
|   CALL FUNCTION 'FMED_GET_HEADER' "Get header contents from FMBH |
| EXPORTING | ||
| I_F_DOCID | = lv_i_f_docid | |
| IMPORTING | ||
| E_F_FMBH | = lv_e_f_fmbh | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| . " FMED_GET_HEADER | ||
ABAP code using 7.40 inline data declarations to call FM FMED_GET_HEADER
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