SAP G_FIELD_READ Function Module for Read Attributes and Descriptions of a Table Field









G_FIELD_READ is a standard g field read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read Attributes and Descriptions of a Table Field 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 g field read FM, simply by entering the name G_FIELD_READ 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_FIELD_READ 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_FIELD_READ'"Read Attributes and Descriptions of a Table Field
  EXPORTING
   TABLE =  "Name of the table
   FIELDNAME =  "Name of the field
*  TEXT_FLAG = ' ' "Flag whether text should be read
*  LANGU = SY-LANGU "Language of the texts (default is SYLANGU)
*  NO_GLX_OBJ_PROCESSING = ' ' "
*  ADD_FLAG = ' ' "Flag for reading the table T804A
*  SHOW_ALIAS = ' ' "Use alias from T804C
*  UTABLE = ' ' "Flag for reading the user tables (T883/T883S)

 IMPORTING
   FIELD_ATTR =  "Attributes of the field (structure like DFIES)
   ORIGINAL_NAME =  "Original name if alias in T804C

EXCEPTIONS
   NOT_FOUND = 1
.



IMPORTING Parameters details for G_FIELD_READ

TABLE - Name of the table

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

FIELDNAME - Name of the field

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

TEXT_FLAG - Flag whether text should be read

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

LANGU - Language of the texts (default is SYLANGU)

Data type: SYLANGU
Default: SY-LANGU
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)

ADD_FLAG - Flag for reading the table T804A

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

SHOW_ALIAS - Use alias from T804C

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

UTABLE - Flag for reading the user tables (T883/T883S)

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

EXPORTING Parameters details for G_FIELD_READ

FIELD_ATTR - Attributes of the field (structure like DFIES)

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

ORIGINAL_NAME - Original name if alias in T804C

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

EXCEPTIONS details

NOT_FOUND - Field does not exist

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

Copy and paste ABAP code example for G_FIELD_READ 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_not_found  TYPE STRING, "   
lv_field_attr  TYPE DFIES, "   
lv_fieldname  TYPE FIELDNAME, "   
lv_original_name  TYPE FIELDNAME, "   
lv_text_flag  TYPE FIELDNAME, "   ' '
lv_langu  TYPE SYLANGU, "   SY-LANGU
lv_no_glx_obj_processing  TYPE SYLANGU, "   ' '
lv_add_flag  TYPE SYLANGU, "   ' '
lv_show_alias  TYPE SYLANGU, "   ' '
lv_utable  TYPE SYLANGU. "   ' '

  CALL FUNCTION 'G_FIELD_READ'  "Read Attributes and Descriptions of a Table Field
    EXPORTING
         TABLE = lv_table
         FIELDNAME = lv_fieldname
         TEXT_FLAG = lv_text_flag
         LANGU = lv_langu
         NO_GLX_OBJ_PROCESSING = lv_no_glx_obj_processing
         ADD_FLAG = lv_add_flag
         SHOW_ALIAS = lv_show_alias
         UTABLE = lv_utable
    IMPORTING
         FIELD_ATTR = lv_field_attr
         ORIGINAL_NAME = lv_original_name
    EXCEPTIONS
        NOT_FOUND = 1
. " G_FIELD_READ




ABAP code using 7.40 inline data declarations to call FM G_FIELD_READ

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_no_glx_obj_processing) = ' '.
 
DATA(ld_add_flag) = ' '.
 
DATA(ld_show_alias) = ' '.
 
DATA(ld_utable) = ' '.
 


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!