SAP GLOSSARY_EDIT Function Module for EDITOR-CALL for glossary definition









GLOSSARY_EDIT is a standard glossary edit SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for EDITOR-CALL for glossary definition 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 glossary edit FM, simply by entering the name GLOSSARY_EDIT into the relevant SAP transaction such as SE37 or SE38.

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



Function GLOSSARY_EDIT 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 'GLOSSARY_EDIT'"EDITOR-CALL for glossary definition
EXPORTING
BEGRIFF = "Glossary entry
DISPLAY = "
SPRACHE = "Language
.



IMPORTING Parameters details for GLOSSARY_EDIT

BEGRIFF - Glossary entry

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

DISPLAY -

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

SPRACHE - Language

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

Copy and paste ABAP code example for GLOSSARY_EDIT 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_begriff  TYPE TERM3-BEGRIFF, "   
lv_display  TYPE TERM3, "   
lv_sprache  TYPE TERM3-SPRAS. "   

  CALL FUNCTION 'GLOSSARY_EDIT'  "EDITOR-CALL for glossary definition
    EXPORTING
         BEGRIFF = lv_begriff
         DISPLAY = lv_display
         SPRACHE = lv_sprache
. " GLOSSARY_EDIT




ABAP code using 7.40 inline data declarations to call FM GLOSSARY_EDIT

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.

"SELECT single BEGRIFF FROM TERM3 INTO @DATA(ld_begriff).
 
 
"SELECT single SPRAS FROM TERM3 INTO @DATA(ld_sprache).
 


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!