SAP FM4C_GET_INTERNAL_DATA Function Module for Return hierarchy and object data
FM4C_GET_INTERNAL_DATA is a standard fm4c get internal data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Return hierarchy and object data 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 fm4c get internal data FM, simply by entering the name FM4C_GET_INTERNAL_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: FM4C
Program Name: SAPLFM4C
Main Program: SAPLFM4C
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FM4C_GET_INTERNAL_DATA 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 'FM4C_GET_INTERNAL_DATA'"Return hierarchy and object data.
IMPORTING
E_FMDY = "
TABLES
* T_FMFPO = "
* T_FMHIPOS = "
* T_VFMPG = "
* T_FMPPT = "
* T_FMHIPG = "
* T_FMHISV = "
* T_FMCI = "
* T_FMCIT = "
* T_FMHICI = "
* T_FMFPOT = "
* T_FMFCTR = "
* T_FMFCTRT = "
* T_FMBU = "Structure hierarchy
* T_BPCK = "
* T_BPCG = "Overall objects
* T_BPCJ = "Annual objects
* T_FMHICTR = "
EXPORTING Parameters details for FM4C_GET_INTERNAL_DATA
E_FMDY -
Data type: FMDYOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for FM4C_GET_INTERNAL_DATA
T_FMFPO -
Data type: FMFPOOptional: Yes
Call by Reference: No ( called with pass by value option)
T_FMHIPOS -
Data type: FMHIPOSOptional: Yes
Call by Reference: No ( called with pass by value option)
T_VFMPG -
Data type: VFMPGOptional: Yes
Call by Reference: No ( called with pass by value option)
T_FMPPT -
Data type: FMPPTOptional: Yes
Call by Reference: No ( called with pass by value option)
T_FMHIPG -
Data type: FMHIPGOptional: Yes
Call by Reference: No ( called with pass by value option)
T_FMHISV -
Data type: FMHISVOptional: Yes
Call by Reference: No ( called with pass by value option)
T_FMCI -
Data type: FMCIOptional: Yes
Call by Reference: Yes
T_FMCIT -
Data type: FMCITOptional: Yes
Call by Reference: Yes
T_FMHICI -
Data type: FMHICIOptional: Yes
Call by Reference: Yes
T_FMFPOT -
Data type: FMFPOTOptional: Yes
Call by Reference: No ( called with pass by value option)
T_FMFCTR -
Data type: FMFCTROptional: Yes
Call by Reference: No ( called with pass by value option)
T_FMFCTRT -
Data type: FMFCTRTOptional: Yes
Call by Reference: No ( called with pass by value option)
T_FMBU - Structure hierarchy
Data type: FMBUOptional: Yes
Call by Reference: No ( called with pass by value option)
T_BPCK -
Data type: BPCKOptional: Yes
Call by Reference: No ( called with pass by value option)
T_BPCG - Overall objects
Data type: BPCGOptional: Yes
Call by Reference: No ( called with pass by value option)
T_BPCJ - Annual objects
Data type: BPCJOptional: Yes
Call by Reference: No ( called with pass by value option)
T_FMHICTR -
Data type: FMHICTROptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FM4C_GET_INTERNAL_DATA 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_fmdy | TYPE FMDY, " | |||
| lt_t_fmfpo | TYPE STANDARD TABLE OF FMFPO, " | |||
| lt_t_fmhipos | TYPE STANDARD TABLE OF FMHIPOS, " | |||
| lt_t_vfmpg | TYPE STANDARD TABLE OF VFMPG, " | |||
| lt_t_fmppt | TYPE STANDARD TABLE OF FMPPT, " | |||
| lt_t_fmhipg | TYPE STANDARD TABLE OF FMHIPG, " | |||
| lt_t_fmhisv | TYPE STANDARD TABLE OF FMHISV, " | |||
| lt_t_fmci | TYPE STANDARD TABLE OF FMCI, " | |||
| lt_t_fmcit | TYPE STANDARD TABLE OF FMCIT, " | |||
| lt_t_fmhici | TYPE STANDARD TABLE OF FMHICI, " | |||
| lt_t_fmfpot | TYPE STANDARD TABLE OF FMFPOT, " | |||
| lt_t_fmfctr | TYPE STANDARD TABLE OF FMFCTR, " | |||
| lt_t_fmfctrt | TYPE STANDARD TABLE OF FMFCTRT, " | |||
| lt_t_fmbu | TYPE STANDARD TABLE OF FMBU, " | |||
| lt_t_bpck | TYPE STANDARD TABLE OF BPCK, " | |||
| lt_t_bpcg | TYPE STANDARD TABLE OF BPCG, " | |||
| lt_t_bpcj | TYPE STANDARD TABLE OF BPCJ, " | |||
| lt_t_fmhictr | TYPE STANDARD TABLE OF FMHICTR. " |
|   CALL FUNCTION 'FM4C_GET_INTERNAL_DATA' "Return hierarchy and object data |
| IMPORTING | ||
| E_FMDY | = lv_e_fmdy | |
| TABLES | ||
| T_FMFPO | = lt_t_fmfpo | |
| T_FMHIPOS | = lt_t_fmhipos | |
| T_VFMPG | = lt_t_vfmpg | |
| T_FMPPT | = lt_t_fmppt | |
| T_FMHIPG | = lt_t_fmhipg | |
| T_FMHISV | = lt_t_fmhisv | |
| T_FMCI | = lt_t_fmci | |
| T_FMCIT | = lt_t_fmcit | |
| T_FMHICI | = lt_t_fmhici | |
| T_FMFPOT | = lt_t_fmfpot | |
| T_FMFCTR | = lt_t_fmfctr | |
| T_FMFCTRT | = lt_t_fmfctrt | |
| T_FMBU | = lt_t_fmbu | |
| T_BPCK | = lt_t_bpck | |
| T_BPCG | = lt_t_bpcg | |
| T_BPCJ | = lt_t_bpcj | |
| T_FMHICTR | = lt_t_fmhictr | |
| . " FM4C_GET_INTERNAL_DATA | ||
ABAP code using 7.40 inline data declarations to call FM FM4C_GET_INTERNAL_DATA
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