SAP ICL_GV_BDT_GET Function Module for ICL: Get Global parameters for BDT determined in ISSTA

Search SAP Function Modules

ICL_GV_BDT_GET is a standard icl gv bdt get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for ICL: Get Global parameters for BDT determined in ISSTA 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 icl gv bdt get FM, simply by entering the name ICL_GV_BDT_GET into the relevant SAP transaction such as SE37 or SE38.

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

Function ICL_GV_BDT_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 'ICL_GV_BDT_GET'"ICL: Get Global parameters for BDT determined in ISSTA
 IMPORTING
   E_AKTYP =  "
   E_ACTION =  "
   E_XSAVE =  "
   E_XINIT =  "
   E_XUPDTASK =  "
   E_XDINP =  "
   E_XTEST =  "
   E_NODATA =  "
   E_IMP_HANDLE =  "IMP: General Counter

TABLES
*  T_RLTYP =  "
*  T_FLDVL =  "

.

EXPORTING Parameters details for ICL_GV_BDT_GET

E_AKTYP -

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

E_ACTION -

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

E_XSAVE -

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

E_XINIT -

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

E_XUPDTASK -

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

E_XDINP -

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

E_XTEST -

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

E_NODATA -

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

E_IMP_HANDLE - IMP: General Counter

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

TABLES Parameters details for ICL_GV_BDT_GET

T_RLTYP -

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

T_FLDVL -

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

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