SAP GET_COMPONENT_DESCRIPTION Function Module for NOTRANSL: Holen des des Kurz- und Langtextes zu einem Komponentenschlüssel
GET_COMPONENT_DESCRIPTION is a standard get component description 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 des des Kurz- und Langtextes zu einem Komponentenschlüssel 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 get component description FM, simply by entering the name GET_COMPONENT_DESCRIPTION into the relevant SAP transaction such as SE37 or SE38.
Function Group: SGLA
Program Name: SAPLSGLA
Main Program: SAPLSGLA
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function GET_COMPONENT_DESCRIPTION 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 'GET_COMPONENT_DESCRIPTION'"NOTRANSL: Holen des des Kurz- und Langtextes zu einem Komponentenschlüssel.
EXPORTING
* LANGU = SY-LANGU "ABAP System Field: Language Key of Text Environment
* COMPONENT = "Application Component
* COMP_DESCRIPTION = "Application component ID
IMPORTING
FCTR_ID = "Application Component
PS_POSID = "Application component ID
NAME = "Short text
EXCEPTIONS
KEY_NOT_FOUND = 1
IMPORTING Parameters details for GET_COMPONENT_DESCRIPTION
LANGU - ABAP System Field: Language Key of Text Environment
Data type: SY-LANGUDefault: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)
COMPONENT - Application Component
Data type: DF14L-FCTR_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
COMP_DESCRIPTION - Application component ID
Data type: DF14L-PS_POSIDOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for GET_COMPONENT_DESCRIPTION
FCTR_ID - Application Component
Data type: DF14L-FCTR_IDOptional: No
Call by Reference: No ( called with pass by value option)
PS_POSID - Application component ID
Data type: DF14L-PS_POSIDOptional: No
Call by Reference: No ( called with pass by value option)
NAME - Short text
Data type: DF14T-NAMEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
KEY_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for GET_COMPONENT_DESCRIPTION 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_fctr_id | TYPE DF14L-FCTR_ID, " | |||
| lv_key_not_found | TYPE DF14L, " | |||
| lv_ps_posid | TYPE DF14L-PS_POSID, " | |||
| lv_component | TYPE DF14L-FCTR_ID, " | |||
| lv_name | TYPE DF14T-NAME, " | |||
| lv_comp_description | TYPE DF14L-PS_POSID. " |
|   CALL FUNCTION 'GET_COMPONENT_DESCRIPTION' "NOTRANSL: Holen des des Kurz- und Langtextes zu einem Komponentenschlüssel |
| EXPORTING | ||
| LANGU | = lv_langu | |
| COMPONENT | = lv_component | |
| COMP_DESCRIPTION | = lv_comp_description | |
| IMPORTING | ||
| FCTR_ID | = lv_fctr_id | |
| PS_POSID | = lv_ps_posid | |
| NAME | = lv_name | |
| EXCEPTIONS | ||
| KEY_NOT_FOUND = 1 | ||
| . " GET_COMPONENT_DESCRIPTION | ||
ABAP code using 7.40 inline data declarations to call FM GET_COMPONENT_DESCRIPTION
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 FCTR_ID FROM DF14L INTO @DATA(ld_fctr_id). | ||||
| "SELECT single PS_POSID FROM DF14L INTO @DATA(ld_ps_posid). | ||||
| "SELECT single FCTR_ID FROM DF14L INTO @DATA(ld_component). | ||||
| "SELECT single NAME FROM DF14T INTO @DATA(ld_name). | ||||
| "SELECT single PS_POSID FROM DF14L INTO @DATA(ld_comp_description). | ||||
Search for further information about these or an SAP related objects