SAP FM_LGD_FEB_2_DG31 Function Module for









FM_LGD_FEB_2_DG31 is a standard fm lgd feb 2 dg31 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 fm lgd feb 2 dg31 FM, simply by entering the name FM_LGD_FEB_2_DG31 into the relevant SAP transaction such as SE37 or SE38.

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



Function FM_LGD_FEB_2_DG31 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 'FM_LGD_FEB_2_DG31'"
EXPORTING
I_AUGLV = "
I_FEBEP = "
I_FEBKO = "
I_TCODE = "

IMPORTING
E_MSGID = "
E_MSGNO = "
E_MSGTY = "
E_MSGV1 = "
E_MSGV2 = "
E_MSGV3 = "
E_MSGV4 = "
E_SUBRC = "

TABLES
T_FEBCL = "
T_FEBRE = "
T_FTCLEAR = "
T_FTPOST = "
.



IMPORTING Parameters details for FM_LGD_FEB_2_DG31

I_AUGLV -

Data type: T041A-AUGLV
Optional: No
Call by Reference: Yes

I_FEBEP -

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

I_FEBKO -

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

I_TCODE -

Data type: SY-TCODE
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for FM_LGD_FEB_2_DG31

E_MSGID -

Data type: SY-MSGID
Optional: No
Call by Reference: Yes

E_MSGNO -

Data type: SY-MSGNO
Optional: No
Call by Reference: Yes

E_MSGTY -

Data type: SY-MSGTY
Optional: No
Call by Reference: Yes

E_MSGV1 -

Data type: SY-MSGV1
Optional: No
Call by Reference: Yes

E_MSGV2 -

Data type: SY-MSGV2
Optional: No
Call by Reference: Yes

E_MSGV3 -

Data type: SY-MSGV3
Optional: No
Call by Reference: Yes

E_MSGV4 -

Data type: SY-MSGV4
Optional: No
Call by Reference: Yes

E_SUBRC -

Data type: SY-SUBRC
Optional: No
Call by Reference: Yes

TABLES Parameters details for FM_LGD_FEB_2_DG31

T_FEBCL -

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

T_FEBRE -

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

T_FTCLEAR -

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

T_FTPOST -

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

Copy and paste ABAP code example for FM_LGD_FEB_2_DG31 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_msgid  TYPE SY-MSGID, "   
lv_i_auglv  TYPE T041A-AUGLV, "   
lt_t_febcl  TYPE STANDARD TABLE OF FEBCL, "   
lv_e_msgno  TYPE SY-MSGNO, "   
lv_i_febep  TYPE FEBEP, "   
lt_t_febre  TYPE STANDARD TABLE OF FEBRE, "   
lv_e_msgty  TYPE SY-MSGTY, "   
lv_i_febko  TYPE FEBKO, "   
lt_t_ftclear  TYPE STANDARD TABLE OF FTCLEAR, "   
lv_e_msgv1  TYPE SY-MSGV1, "   
lv_i_tcode  TYPE SY-TCODE, "   
lt_t_ftpost  TYPE STANDARD TABLE OF FTPOST, "   
lv_e_msgv2  TYPE SY-MSGV2, "   
lv_e_msgv3  TYPE SY-MSGV3, "   
lv_e_msgv4  TYPE SY-MSGV4, "   
lv_e_subrc  TYPE SY-SUBRC. "   

  CALL FUNCTION 'FM_LGD_FEB_2_DG31'  "
    EXPORTING
         I_AUGLV = lv_i_auglv
         I_FEBEP = lv_i_febep
         I_FEBKO = lv_i_febko
         I_TCODE = lv_i_tcode
    IMPORTING
         E_MSGID = lv_e_msgid
         E_MSGNO = lv_e_msgno
         E_MSGTY = lv_e_msgty
         E_MSGV1 = lv_e_msgv1
         E_MSGV2 = lv_e_msgv2
         E_MSGV3 = lv_e_msgv3
         E_MSGV4 = lv_e_msgv4
         E_SUBRC = lv_e_subrc
    TABLES
         T_FEBCL = lt_t_febcl
         T_FEBRE = lt_t_febre
         T_FTCLEAR = lt_t_ftclear
         T_FTPOST = lt_t_ftpost
. " FM_LGD_FEB_2_DG31




ABAP code using 7.40 inline data declarations to call FM FM_LGD_FEB_2_DG31

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.

"SELECT single MSGID FROM SY INTO @DATA(ld_e_msgid).
 
"SELECT single AUGLV FROM T041A INTO @DATA(ld_i_auglv).
 
 
"SELECT single MSGNO FROM SY INTO @DATA(ld_e_msgno).
 
 
 
"SELECT single MSGTY FROM SY INTO @DATA(ld_e_msgty).
 
 
 
"SELECT single MSGV1 FROM SY INTO @DATA(ld_e_msgv1).
 
"SELECT single TCODE FROM SY INTO @DATA(ld_i_tcode).
 
 
"SELECT single MSGV2 FROM SY INTO @DATA(ld_e_msgv2).
 
"SELECT single MSGV3 FROM SY INTO @DATA(ld_e_msgv3).
 
"SELECT single MSGV4 FROM SY INTO @DATA(ld_e_msgv4).
 
"SELECT single SUBRC FROM SY INTO @DATA(ld_e_subrc).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!