SAP FMEINDECK_GET Function Module for

Search SAP Function Modules

FMEINDECK_GET is a standard fmeindeck get 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 fmeindeck get FM, simply by entering the name FMEINDECK_GET into the relevant SAP transaction such as SE37 or SE38.

Function Group: FMAM
Program Name: SAPLFMAM
Main Program: SAPLFMAM
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FMEINDECK_GET 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 'FMEINDECK_GET'"
  EXPORTING
   I_F_GLOBAL =  "
*  I_FLG_USE_DB =  "
*  I_FLG_USE_RANGES =  "
*  I_FLG_USE_BUFFER =  "

 IMPORTING
   E_T_FMEINDECK_BFR =  "
   E_T_FMAA_NO_DATA =  "
   E_T_FMAA_DATA =  "

TABLES
*  T_FMAA =  "
*  R_FINCD =  "
*  R_FICTR =  "
*  R_FIPEX =  "
*  R_FAREA =  "

EXCEPTIONS
   NO_DATA_FOUND = 1 

.

IMPORTING Parameters details for FMEINDECK_GET

I_F_GLOBAL -

Data type: FMKT_GLOBAL_INT
Optional: No
Call by Reference: Yes

I_FLG_USE_DB -

Data type: FMDY-XFELD
Optional: Yes
Call by Reference: Yes

I_FLG_USE_RANGES -

Data type: FMDY-XFELD
Optional: Yes
Call by Reference: Yes

I_FLG_USE_BUFFER -

Data type: FMDY-XFELD
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for FMEINDECK_GET

E_T_FMEINDECK_BFR -

Data type: FMKT_T_FMEINDECK_BFR
Optional: No
Call by Reference: Yes

E_T_FMAA_NO_DATA -

Data type: FMKT_T_FMAA_INT
Optional: No
Call by Reference: Yes

E_T_FMAA_DATA -

Data type: FMKT_T_FMAA_INT
Optional: No
Call by Reference: Yes

TABLES Parameters details for FMEINDECK_GET

T_FMAA -

Data type: FMKT_T_FMAA_INT
Optional: Yes
Call by Reference: No ( called with pass by value option)

R_FINCD -

Data type: RANGE_C10
Optional: Yes
Call by Reference: No ( called with pass by value option)

R_FICTR -

Data type: RANGE_C16
Optional: Yes
Call by Reference: No ( called with pass by value option)

R_FIPEX -

Data type: RANGE_C24
Optional: Yes
Call by Reference: No ( called with pass by value option)

R_FAREA -

Data type: RANGE_C16
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

NO_DATA_FOUND -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for FMEINDECK_GET 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.

ABAP code using 7.40 inline data declarations to call FM FMEINDECK_GET

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