SAP DSYS_OUTLINE_BROWSE Function Module for









DSYS_OUTLINE_BROWSE is a standard dsys outline browse 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 dsys outline browse FM, simply by entering the name DSYS_OUTLINE_BROWSE into the relevant SAP transaction such as SE37 or SE38.

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



Function DSYS_OUTLINE_BROWSE 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 'DSYS_OUTLINE_BROWSE'"
  EXPORTING
*  APPLICATION = 'SO70' "Table DSYDS application
   DOKLANGU =  "Language
*  FISHEYE_DOKCLASS = ' ' "Class of the module to be position
*  FISHEYE_DOKNAME = ' ' "Name of the module to be positione
   HOMETEXT =  "Text for the calling application
   OUTLINE =  "Book name
*  VIEWNAME = 'STANDARD' "
*  WINDOW_HEADER_LINE = ' ' "

 IMPORTING
   PF15 =  "Boolean, flag if PF15 is printed in the display

EXCEPTIONS
   OUTLINE_NOT_FOUND = 1
.



IMPORTING Parameters details for DSYS_OUTLINE_BROWSE

APPLICATION - Table DSYDS application

Data type: DSYDS-APPL
Default: 'SO70'
Optional: Yes
Call by Reference: No ( called with pass by value option)

DOKLANGU - Language

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

FISHEYE_DOKCLASS - Class of the module to be position

Data type: DSYSH-DOKCLASS
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

FISHEYE_DOKNAME - Name of the module to be positione

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

HOMETEXT - Text for the calling application

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

OUTLINE - Book name

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

VIEWNAME -

Data type: DSYAD-VIEWNAME
Default: 'STANDARD'
Optional: Yes
Call by Reference: No ( called with pass by value option)

WINDOW_HEADER_LINE -

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

EXPORTING Parameters details for DSYS_OUTLINE_BROWSE

PF15 - Boolean, flag if PF15 is printed in the display

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

EXCEPTIONS details

OUTLINE_NOT_FOUND - Book not found

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

Copy and paste ABAP code example for DSYS_OUTLINE_BROWSE 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_pf15  TYPE STRING, "   
lv_application  TYPE DSYDS-APPL, "   'SO70'
lv_outline_not_found  TYPE DSYDS, "   
lv_doklangu  TYPE SDSYS-SPRAS, "   
lv_fisheye_dokclass  TYPE DSYSH-DOKCLASS, "   SPACE
lv_fisheye_dokname  TYPE DSYSH, "   SPACE
lv_hometext  TYPE DSYAT-CHILD_TITL, "   
lv_outline  TYPE DSYAH-OUTLINE, "   
lv_viewname  TYPE DSYAD-VIEWNAME, "   'STANDARD'
lv_window_header_line  TYPE DSYAD. "   ' '

  CALL FUNCTION 'DSYS_OUTLINE_BROWSE'  "
    EXPORTING
         APPLICATION = lv_application
         DOKLANGU = lv_doklangu
         FISHEYE_DOKCLASS = lv_fisheye_dokclass
         FISHEYE_DOKNAME = lv_fisheye_dokname
         HOMETEXT = lv_hometext
         OUTLINE = lv_outline
         VIEWNAME = lv_viewname
         WINDOW_HEADER_LINE = lv_window_header_line
    IMPORTING
         PF15 = lv_pf15
    EXCEPTIONS
        OUTLINE_NOT_FOUND = 1
. " DSYS_OUTLINE_BROWSE




ABAP code using 7.40 inline data declarations to call FM DSYS_OUTLINE_BROWSE

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 APPL FROM DSYDS INTO @DATA(ld_application).
DATA(ld_application) = 'SO70'.
 
 
"SELECT single SPRAS FROM SDSYS INTO @DATA(ld_doklangu).
 
"SELECT single DOKCLASS FROM DSYSH INTO @DATA(ld_fisheye_dokclass).
DATA(ld_fisheye_dokclass) = ' '.
 
DATA(ld_fisheye_dokname) = ' '.
 
"SELECT single CHILD_TITL FROM DSYAT INTO @DATA(ld_hometext).
 
"SELECT single OUTLINE FROM DSYAH INTO @DATA(ld_outline).
 
"SELECT single VIEWNAME FROM DSYAD INTO @DATA(ld_viewname).
DATA(ld_viewname) = 'STANDARD'.
 
DATA(ld_window_header_line) = ' '.
 


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!