SAP GLE_ECS_AL_GET_FIELDNAMES Function Module for









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

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



Function GLE_ECS_AL_GET_FIELDNAMES 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 'GLE_ECS_AL_GET_FIELDNAMES'"
EXPORTING
I_COMP_ERROR = "

IMPORTING
E_TAB_FIELD_SEL = "

EXCEPTIONS
NO_COMP_ERROR = 1
.



IMPORTING Parameters details for GLE_ECS_AL_GET_FIELDNAMES

I_COMP_ERROR -

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

EXPORTING Parameters details for GLE_ECS_AL_GET_FIELDNAMES

E_TAB_FIELD_SEL -

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

EXCEPTIONS details

NO_COMP_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for GLE_ECS_AL_GET_FIELDNAMES 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_i_comp_error  TYPE GLE_DTE_ECS_ERROR_COMPOUND, "   
lv_no_comp_error  TYPE GLE_DTE_ECS_ERROR_COMPOUND, "   
lv_e_tab_field_sel  TYPE GLE_ECS_TAB_FIELD_SELECTION. "   

  CALL FUNCTION 'GLE_ECS_AL_GET_FIELDNAMES'  "
    EXPORTING
         I_COMP_ERROR = lv_i_comp_error
    IMPORTING
         E_TAB_FIELD_SEL = lv_e_tab_field_sel
    EXCEPTIONS
        NO_COMP_ERROR = 1
. " GLE_ECS_AL_GET_FIELDNAMES




ABAP code using 7.40 inline data declarations to call FM GLE_ECS_AL_GET_FIELDNAMES

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



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!