SAP GLE_ECS_DB_EDIT_FIELD Function Module for

Search SAP Function Modules

GLE_ECS_DB_EDIT_FIELD is a standard gle ecs db edit field 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 db edit field FM, simply by entering the name GLE_ECS_DB_EDIT_FIELD into the relevant SAP transaction such as SE37 or SE38.

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

Function GLE_ECS_DB_EDIT_FIELD 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_DB_EDIT_FIELD'"
  EXPORTING
*  I_SEVERITY_LEVEL =  "

 IMPORTING
   E_TAB_EDIT_FIELDS =  "

EXCEPTIONS
   NOT_FOUND = 1 

.

IMPORTING Parameters details for GLE_ECS_DB_EDIT_FIELD

I_SEVERITY_LEVEL -

Data type: GLE_DTE_ECS_ITEM_SEVER_LEVEL
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for GLE_ECS_DB_EDIT_FIELD

E_TAB_EDIT_FIELDS -

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

EXCEPTIONS details

NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

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

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