SAP G_FIELDTAB_GET Function Module for









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

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



Function G_FIELDTAB_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 'G_FIELDTAB_GET'"
  EXPORTING
   TABLE =  "
*  TEXT_FLAG = ' ' "
*  LANGU = SY-LANGU "
*  FTYPE = 'K' "
*  LENGTH24 = ' ' "
*  ADD_FLAG = ' ' "
*  NO_GLX_OBJ_PROCESSING = ' ' "
*  OBJECTTABLE = ' ' "
*  OBJECTTABLE2 = ' ' "

 IMPORTING
   OTABLE =  "

TABLES
   T_FIELDTAB =  "

EXCEPTIONS
   NOT_FOUND = 1
.



IMPORTING Parameters details for G_FIELDTAB_GET

TABLE -

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

TEXT_FLAG -

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

LANGU -

Data type: SYLANGU
Default: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)

FTYPE -

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

LENGTH24 -

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

ADD_FLAG -

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

NO_GLX_OBJ_PROCESSING -

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

OBJECTTABLE -

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

OBJECTTABLE2 -

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

EXPORTING Parameters details for G_FIELDTAB_GET

OTABLE -

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

TABLES Parameters details for G_FIELDTAB_GET

T_FIELDTAB -

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

EXCEPTIONS details

NOT_FOUND -

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

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

DATA:
lv_table  TYPE STRING, "   
lv_otable  TYPE STRING, "   
lv_not_found  TYPE STRING, "   
lt_t_fieldtab  TYPE STANDARD TABLE OF DFIES, "   
lv_text_flag  TYPE DFIES, "   ' '
lv_langu  TYPE SYLANGU, "   SY-LANGU
lv_ftype  TYPE SYLANGU, "   'K'
lv_length24  TYPE SYLANGU, "   ' '
lv_add_flag  TYPE SYLANGU, "   ' '
lv_no_glx_obj_processing  TYPE SYLANGU, "   ' '
lv_objecttable  TYPE SYLANGU, "   ' '
lv_objecttable2  TYPE SYLANGU. "   ' '

  CALL FUNCTION 'G_FIELDTAB_GET'  "
    EXPORTING
         TABLE = lv_table
         TEXT_FLAG = lv_text_flag
         LANGU = lv_langu
         FTYPE = lv_ftype
         LENGTH24 = lv_length24
         ADD_FLAG = lv_add_flag
         NO_GLX_OBJ_PROCESSING = lv_no_glx_obj_processing
         OBJECTTABLE = lv_objecttable
         OBJECTTABLE2 = lv_objecttable2
    IMPORTING
         OTABLE = lv_otable
    TABLES
         T_FIELDTAB = lt_t_fieldtab
    EXCEPTIONS
        NOT_FOUND = 1
. " G_FIELDTAB_GET




ABAP code using 7.40 inline data declarations to call FM G_FIELDTAB_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.

 
 
 
 
DATA(ld_text_flag) = ' '.
 
DATA(ld_langu) = SY-LANGU.
 
DATA(ld_ftype) = 'K'.
 
DATA(ld_length24) = ' '.
 
DATA(ld_add_flag) = ' '.
 
DATA(ld_no_glx_obj_processing) = ' '.
 
DATA(ld_objecttable) = ' '.
 
DATA(ld_objecttable2) = ' '.
 


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!