SAP SDOK_LOIO_CALL_VIEWER Function Module for

Search SAP Function Modules

SDOK_LOIO_CALL_VIEWER is a standard sdok loio call viewer 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 sdok loio call viewer FM, simply by entering the name SDOK_LOIO_CALL_VIEWER into the relevant SAP transaction such as SE37 or SE38.

Function Group: SDCL
Program Name: SAPLSDCL
Main Program: SAPLSDCL
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function SDOK_LOIO_CALL_VIEWER 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 'SDOK_LOIO_CALL_VIEWER'"
  EXPORTING
   OBJECT_ID =  "BOR Key for the Object
*  X_TESTMODE =  "
*  BROWSER_TYPE =  "
*  BROWSER_CONTEXTSTRING =  "

 IMPORTING
   URL =  "

TABLES
   CONTEXT =  "Context description

EXCEPTIONS
   BAD_CLASS = 1    NOT_ALLOWED = 2    NOT_AUTHORIZED = 3    FRONTEND_NOT_SUPPORTED = 4    FRONTEND_ERROR = 5    PROG_NOT_FOUND = 6    NO_BATCH = 7    UNSPECIFIED_ERROR = 8 

.

IMPORTING Parameters details for SDOK_LOIO_CALL_VIEWER

OBJECT_ID - BOR Key for the Object

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

X_TESTMODE -

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

BROWSER_TYPE -

Data type: TOLE-APP
Optional: Yes
Call by Reference: No ( called with pass by value option)

BROWSER_CONTEXTSTRING -

Data type: SDOK_IFACE-CONTEXTSTR
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for SDOK_LOIO_CALL_VIEWER

URL -

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

TABLES Parameters details for SDOK_LOIO_CALL_VIEWER

CONTEXT - Context description

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

EXCEPTIONS details

BAD_CLASS -

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

NOT_ALLOWED - Object Cannot Be Deleted

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

NOT_AUTHORIZED - No Authorization

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

FRONTEND_NOT_SUPPORTED - Frontend Not Supported

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

FRONTEND_ERROR - Error occurred in SAPGUI

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

PROG_NOT_FOUND - Program not found or not in executable form

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

NO_BATCH - Front-End Function Cannot Be Executed in Backgrnd

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

UNSPECIFIED_ERROR - Unspecified Exception

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

Copy and paste ABAP code example for SDOK_LOIO_CALL_VIEWER 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.

ABAP code using 7.40 inline data declarations to call FM SDOK_LOIO_CALL_VIEWER

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