SAP TERM_SET_ENQUEUE_GLOS Function Module for NOTRANSL: Sperre setzen für Pflege in Terminologiedatenbank
TERM_SET_ENQUEUE_GLOS is a standard term set enqueue glos SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Sperre setzen für Pflege in Terminologiedatenbank 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 term set enqueue glos FM, simply by entering the name TERM_SET_ENQUEUE_GLOS into the relevant SAP transaction such as SE37 or SE38.
Function Group: STERM_ATTR
Program Name: SAPLSTERM_ATTR
Main Program: SAPLSTERM_ATTR
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TERM_SET_ENQUEUE_GLOS 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 'TERM_SET_ENQUEUE_GLOS'"NOTRANSL: Sperre setzen für Pflege in Terminologiedatenbank.
EXCEPTIONS
NO_AUTHORIZATION = 1 USER_CANCELLED = 2
EXCEPTIONS details
NO_AUTHORIZATION -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
USER_CANCELLED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for TERM_SET_ENQUEUE_GLOS 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_no_authorization | TYPE STRING, " | |||
| lv_user_cancelled | TYPE STRING. " |
|   CALL FUNCTION 'TERM_SET_ENQUEUE_GLOS' "NOTRANSL: Sperre setzen für Pflege in Terminologiedatenbank |
| EXCEPTIONS | ||
| NO_AUTHORIZATION = 1 | ||
| USER_CANCELLED = 2 | ||
| . " TERM_SET_ENQUEUE_GLOS | ||
ABAP code using 7.40 inline data declarations to call FM TERM_SET_ENQUEUE_GLOS
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