SAP CALL_BROWSER Function Module for Call browsers with instance management
CALL_BROWSER is a standard call browser SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Call browsers with instance management 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 call browser FM, simply by entering the name CALL_BROWSER into the relevant SAP transaction such as SE37 or SE38.
Function Group: SDCB
Program Name: SAPLSDCB
Main Program: SAPLSDCB
Appliation area: S
Release date: 17-May-2001
Mode(Normal, Remote etc): Normal Function Module
Update:
Function CALL_BROWSER 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 'CALL_BROWSER'"Call browsers with instance management.
EXPORTING
* URL = ' ' "URL of Browser Call
* WINDOW_NAME = ' ' "Under ITS: Name of Browser Target Window
* NEW_WINDOW = ' ' "Under Win32: Open a New Window
* BROWSER_TYPE = "Obsolete: Do Not Use
* CONTEXTSTRING = "Obsolete: Do Not Use
EXCEPTIONS
FRONTEND_NOT_SUPPORTED = 1 FRONTEND_ERROR = 2 PROG_NOT_FOUND = 3 NO_BATCH = 4 UNSPECIFIED_ERROR = 5
IMPORTING Parameters details for CALL_BROWSER
URL - URL of Browser Call
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
WINDOW_NAME - Under ITS: Name of Browser Target Window
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
NEW_WINDOW - Under Win32: Open a New Window
Data type: SY-DATARDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
BROWSER_TYPE - Obsolete: Do Not Use
Data type: TOLE-APPOptional: Yes
Call by Reference: No ( called with pass by value option)
CONTEXTSTRING - Obsolete: Do Not Use
Data type: SDOK_IFACE-CONTEXTSTROptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
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 CALL_BROWSER 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_url | TYPE C, " SPACE | |||
lv_frontend_not_supported | TYPE C, " | |||
lv_window_name | TYPE C, " SPACE | |||
lv_frontend_error | TYPE C, " | |||
lv_new_window | TYPE SY-DATAR, " SPACE | |||
lv_prog_not_found | TYPE SY, " | |||
lv_no_batch | TYPE SY, " | |||
lv_browser_type | TYPE TOLE-APP, " | |||
lv_contextstring | TYPE SDOK_IFACE-CONTEXTSTR, " | |||
lv_unspecified_error | TYPE SDOK_IFACE. " |
  CALL FUNCTION 'CALL_BROWSER' "Call browsers with instance management |
EXPORTING | ||
URL | = lv_url | |
WINDOW_NAME | = lv_window_name | |
NEW_WINDOW | = lv_new_window | |
BROWSER_TYPE | = lv_browser_type | |
CONTEXTSTRING | = lv_contextstring | |
EXCEPTIONS | ||
FRONTEND_NOT_SUPPORTED = 1 | ||
FRONTEND_ERROR = 2 | ||
PROG_NOT_FOUND = 3 | ||
NO_BATCH = 4 | ||
UNSPECIFIED_ERROR = 5 | ||
. " CALL_BROWSER |
ABAP code using 7.40 inline data declarations to call FM CALL_BROWSER
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.DATA(ld_url) | = ' '. | |||
DATA(ld_window_name) | = ' '. | |||
"SELECT single DATAR FROM SY INTO @DATA(ld_new_window). | ||||
DATA(ld_new_window) | = ' '. | |||
"SELECT single APP FROM TOLE INTO @DATA(ld_browser_type). | ||||
"SELECT single CONTEXTSTR FROM SDOK_IFACE INTO @DATA(ld_contextstring). | ||||
Search for further information about these or an SAP related objects