SAP SIW_R3LINK_VIEW Function Module for
SIW_R3LINK_VIEW is a standard siw r3link view 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 siw r3link view FM, simply by entering the name SIW_R3LINK_VIEW into the relevant SAP transaction such as SE37 or SE38.
Function Group: SI17_V
Program Name: SAPLSI17_V
Main Program: SAPLSI17_V
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function SIW_R3LINK_VIEW 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 'SIW_R3LINK_VIEW'".
EXPORTING
* DEVCLASS = "Package
* TCODE = "Transaction Code
* PROGRAM = "Program Name
* DYNPRONR = "
* EXTENSION = "
* FRONTEND_PLATFORM = 'NONE' "
* CALL_BROWSER = 'X' "
* SINGLE_OBJECT = ' ' "Single-Character Flag
IMPORTING
ERROR_MSG = "
ACTION = "
FRONTEND_URL = "
FRONTEND_PROGRAM = "
IMPORTING Parameters details for SIW_R3LINK_VIEW
DEVCLASS - Package
Data type: IWREFERENC-DEVCLASSOptional: Yes
Call by Reference: No ( called with pass by value option)
TCODE - Transaction Code
Data type: IWREFERENC-TCODEOptional: Yes
Call by Reference: No ( called with pass by value option)
PROGRAM - Program Name
Data type: IWREFERENC-PROGRAMMOptional: Yes
Call by Reference: No ( called with pass by value option)
DYNPRONR -
Data type: IWREFERENC-DYNPRONROptional: Yes
Call by Reference: No ( called with pass by value option)
EXTENSION -
Data type: IWREFERENC-SPEC_TEXTOptional: Yes
Call by Reference: No ( called with pass by value option)
FRONTEND_PLATFORM -
Data type: SY-OPSYSDefault: 'NONE'
Optional: Yes
Call by Reference: No ( called with pass by value option)
CALL_BROWSER -
Data type: IWPARAMS-FLAGDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
SINGLE_OBJECT - Single-Character Flag
Data type: IWPARAMS-FLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SIW_R3LINK_VIEW
ERROR_MSG -
Data type: IWERRORMSGOptional: No
Call by Reference: No ( called with pass by value option)
ACTION -
Data type: SY-XCODEOptional: No
Call by Reference: No ( called with pass by value option)
FRONTEND_URL -
Data type: SDOK_IFACE-URLOptional: No
Call by Reference: No ( called with pass by value option)
FRONTEND_PROGRAM -
Data type: SDOK_IFACE-URLOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SIW_R3LINK_VIEW 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_devclass | TYPE IWREFERENC-DEVCLASS, " | |||
lv_error_msg | TYPE IWERRORMSG, " | |||
lv_tcode | TYPE IWREFERENC-TCODE, " | |||
lv_action | TYPE SY-XCODE, " | |||
lv_program | TYPE IWREFERENC-PROGRAMM, " | |||
lv_frontend_url | TYPE SDOK_IFACE-URL, " | |||
lv_dynpronr | TYPE IWREFERENC-DYNPRONR, " | |||
lv_frontend_program | TYPE SDOK_IFACE-URL, " | |||
lv_extension | TYPE IWREFERENC-SPEC_TEXT, " | |||
lv_frontend_platform | TYPE SY-OPSYS, " 'NONE' | |||
lv_call_browser | TYPE IWPARAMS-FLAG, " 'X' | |||
lv_single_object | TYPE IWPARAMS-FLAG. " SPACE |
  CALL FUNCTION 'SIW_R3LINK_VIEW' " |
EXPORTING | ||
DEVCLASS | = lv_devclass | |
TCODE | = lv_tcode | |
PROGRAM | = lv_program | |
DYNPRONR | = lv_dynpronr | |
EXTENSION | = lv_extension | |
FRONTEND_PLATFORM | = lv_frontend_platform | |
CALL_BROWSER | = lv_call_browser | |
SINGLE_OBJECT | = lv_single_object | |
IMPORTING | ||
ERROR_MSG | = lv_error_msg | |
ACTION | = lv_action | |
FRONTEND_URL | = lv_frontend_url | |
FRONTEND_PROGRAM | = lv_frontend_program | |
. " SIW_R3LINK_VIEW |
ABAP code using 7.40 inline data declarations to call FM SIW_R3LINK_VIEW
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 DEVCLASS FROM IWREFERENC INTO @DATA(ld_devclass). | ||||
"SELECT single TCODE FROM IWREFERENC INTO @DATA(ld_tcode). | ||||
"SELECT single XCODE FROM SY INTO @DATA(ld_action). | ||||
"SELECT single PROGRAMM FROM IWREFERENC INTO @DATA(ld_program). | ||||
"SELECT single URL FROM SDOK_IFACE INTO @DATA(ld_frontend_url). | ||||
"SELECT single DYNPRONR FROM IWREFERENC INTO @DATA(ld_dynpronr). | ||||
"SELECT single URL FROM SDOK_IFACE INTO @DATA(ld_frontend_program). | ||||
"SELECT single SPEC_TEXT FROM IWREFERENC INTO @DATA(ld_extension). | ||||
"SELECT single OPSYS FROM SY INTO @DATA(ld_frontend_platform). | ||||
DATA(ld_frontend_platform) | = 'NONE'. | |||
"SELECT single FLAG FROM IWPARAMS INTO @DATA(ld_call_browser). | ||||
DATA(ld_call_browser) | = 'X'. | |||
"SELECT single FLAG FROM IWPARAMS INTO @DATA(ld_single_object). | ||||
DATA(ld_single_object) | = ' '. | |||
Search for further information about these or an SAP related objects