SAP LSO_GET_DESCRIPTION Function Module for









LSO_GET_DESCRIPTION is a standard lso get description 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 lso get description FM, simply by entering the name LSO_GET_DESCRIPTION into the relevant SAP transaction such as SE37 or SE38.

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



Function LSO_GET_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 'LSO_GET_DESCRIPTION'"
EXPORTING
IV_PLVAR = "Plan Version
IV_OTYPE = "Object Type
IV_OBJID = "Object ID
IV_BEGDA = "Start Date
IV_ENDDA = "End Date
* IV_LANGU = SY-LANGU "System, Current Language
* IV_MERGE_EVTYP_DESCR = ' ' "
* IV_SUBTY_SORT = ' ' "

TABLES
ET_DESCRIPTION = "1002 subtype of business event type

EXCEPTIONS
TEXT_NOT_FOUND = 1
.



IMPORTING Parameters details for LSO_GET_DESCRIPTION

IV_PLVAR - Plan Version

Data type: PLOG-PLVAR
Optional: No
Call by Reference: Yes

IV_OTYPE - Object Type

Data type: PLOG-OTYPE
Optional: No
Call by Reference: Yes

IV_OBJID - Object ID

Data type: PLOG-OBJID
Optional: No
Call by Reference: Yes

IV_BEGDA - Start Date

Data type: PLOG-BEGDA
Optional: No
Call by Reference: Yes

IV_ENDDA - End Date

Data type: PLOG-ENDDA
Optional: No
Call by Reference: Yes

IV_LANGU - System, Current Language

Data type: SY-LANGU
Default: SY-LANGU
Optional: Yes
Call by Reference: Yes

IV_MERGE_EVTYP_DESCR -

Data type: FLAG_X
Default: SPACE
Optional: Yes
Call by Reference: Yes

IV_SUBTY_SORT -

Data type: FLAG_X
Default: SPACE
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for LSO_GET_DESCRIPTION

ET_DESCRIPTION - 1002 subtype of business event type

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

EXCEPTIONS details

TEXT_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for LSO_GET_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_iv_plvar  TYPE PLOG-PLVAR, "   
lt_et_description  TYPE STANDARD TABLE OF HRV1002, "   
lv_text_not_found  TYPE HRV1002, "   
lv_iv_otype  TYPE PLOG-OTYPE, "   
lv_iv_objid  TYPE PLOG-OBJID, "   
lv_iv_begda  TYPE PLOG-BEGDA, "   
lv_iv_endda  TYPE PLOG-ENDDA, "   
lv_iv_langu  TYPE SY-LANGU, "   SY-LANGU
lv_iv_merge_evtyp_descr  TYPE FLAG_X, "   SPACE
lv_iv_subty_sort  TYPE FLAG_X. "   SPACE

  CALL FUNCTION 'LSO_GET_DESCRIPTION'  "
    EXPORTING
         IV_PLVAR = lv_iv_plvar
         IV_OTYPE = lv_iv_otype
         IV_OBJID = lv_iv_objid
         IV_BEGDA = lv_iv_begda
         IV_ENDDA = lv_iv_endda
         IV_LANGU = lv_iv_langu
         IV_MERGE_EVTYP_DESCR = lv_iv_merge_evtyp_descr
         IV_SUBTY_SORT = lv_iv_subty_sort
    TABLES
         ET_DESCRIPTION = lt_et_description
    EXCEPTIONS
        TEXT_NOT_FOUND = 1
. " LSO_GET_DESCRIPTION




ABAP code using 7.40 inline data declarations to call FM LSO_GET_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 PLVAR FROM PLOG INTO @DATA(ld_iv_plvar).
 
 
 
"SELECT single OTYPE FROM PLOG INTO @DATA(ld_iv_otype).
 
"SELECT single OBJID FROM PLOG INTO @DATA(ld_iv_objid).
 
"SELECT single BEGDA FROM PLOG INTO @DATA(ld_iv_begda).
 
"SELECT single ENDDA FROM PLOG INTO @DATA(ld_iv_endda).
 
"SELECT single LANGU FROM SY INTO @DATA(ld_iv_langu).
DATA(ld_iv_langu) = SY-LANGU.
 
DATA(ld_iv_merge_evtyp_descr) = ' '.
 
DATA(ld_iv_subty_sort) = ' '.
 


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!