SAP TERM_GET_COMPONENTS Function Module for NOTRANSL: Holen Von Komponentenschlüssel, Kürzel und Langtext









TERM_GET_COMPONENTS is a standard term get components 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: Holen Von Komponentenschlüssel, Kürzel und Langtext 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 get components FM, simply by entering the name TERM_GET_COMPONENTS 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_GET_COMPONENTS 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_GET_COMPONENTS'"NOTRANSL: Holen Von Komponentenschlüssel, Kürzel und Langtext
EXPORTING
* LANGU = SY-LANGU "ABAP System Field: Language Key of Text Environment
* SYSTEM_ID = SY-SYSID "ABAP System Field: Name of SAP System

IMPORTING
APPLICATION = "

EXCEPTIONS
NO_ENTRY_FOUND = 1
.



IMPORTING Parameters details for TERM_GET_COMPONENTS

LANGU - ABAP System Field: Language Key of Text Environment

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

SYSTEM_ID - ABAP System Field: Name of SAP System

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

EXPORTING Parameters details for TERM_GET_COMPONENTS

APPLICATION -

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

EXCEPTIONS details

NO_ENTRY_FOUND -

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

Copy and paste ABAP code example for TERM_GET_COMPONENTS 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_langu  TYPE SY-LANGU, "   SY-LANGU
lv_application  TYPE TERMS_TAB_APPLICATIONS, "   
lv_no_entry_found  TYPE TERMS_TAB_APPLICATIONS, "   
lv_system_id  TYPE SY-SYSID. "   SY-SYSID

  CALL FUNCTION 'TERM_GET_COMPONENTS'  "NOTRANSL: Holen Von Komponentenschlüssel, Kürzel und Langtext
    EXPORTING
         LANGU = lv_langu
         SYSTEM_ID = lv_system_id
    IMPORTING
         APPLICATION = lv_application
    EXCEPTIONS
        NO_ENTRY_FOUND = 1
. " TERM_GET_COMPONENTS




ABAP code using 7.40 inline data declarations to call FM TERM_GET_COMPONENTS

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 LANGU FROM SY INTO @DATA(ld_langu).
DATA(ld_langu) = SY-LANGU.
 
 
 
"SELECT single SYSID FROM SY INTO @DATA(ld_system_id).
DATA(ld_system_id) = SY-SYSID.
 


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!