SAP RSWR_PORTAL_CONFIG_GET Function Module for Returns Saved Runtime Data









RSWR_PORTAL_CONFIG_GET is a standard rswr portal config get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Returns Saved Runtime Data 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 rswr portal config get FM, simply by entering the name RSWR_PORTAL_CONFIG_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function RSWR_PORTAL_CONFIG_GET 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 'RSWR_PORTAL_CONFIG_GET'"Returns Saved Runtime Data
 IMPORTING
   E_USER_NAME =  "User Name
   E_DEFAULT_FONT =  "Default Font
   E_RFC_DESTINATION =  "RFC Destination
   E_SYSTEM_NAME =  "System name
   E_DEFAULT_PORTAL =  "Flag structure
   E_URL_PREFIX =  "URL Prefix
   E_USE_SAP_EXPORT_LIB =  "Use SAP Export Lib
   E_FONT_PATH =  "Font directory
   E_ADS_HTTPS =  "Use HTTPS for ADS
   E_MAX_MESSAGE_TYPE =  "Message Type

TABLES
*  I_T_STATISTIC_INFO =  "OLAP Statistics: Mass Insert of Event Data

EXCEPTIONS
   ERROR = 1
.



EXPORTING Parameters details for RSWR_PORTAL_CONFIG_GET

E_USER_NAME - User Name

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

E_DEFAULT_FONT - Default Font

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

E_RFC_DESTINATION - RFC Destination

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

E_SYSTEM_NAME - System name

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

E_DEFAULT_PORTAL - Flag structure

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

E_URL_PREFIX - URL Prefix

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

E_USE_SAP_EXPORT_LIB - Use SAP Export Lib

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

E_FONT_PATH - Font directory

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

E_ADS_HTTPS - Use HTTPS for ADS

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

E_MAX_MESSAGE_TYPE - Message Type

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

TABLES Parameters details for RSWR_PORTAL_CONFIG_GET

I_T_STATISTIC_INFO - OLAP Statistics: Mass Insert of Event Data

Data type: RSSTA_S_EVENTINPUT
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

ERROR - Error

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for RSWR_PORTAL_CONFIG_GET 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_error  TYPE STRING, "   
lv_e_user_name  TYPE STRING, "   
lt_i_t_statistic_info  TYPE STANDARD TABLE OF RSSTA_S_EVENTINPUT, "   
lv_e_default_font  TYPE STRING, "   
lv_e_rfc_destination  TYPE STRING, "   
lv_e_system_name  TYPE STRING, "   
lv_e_default_portal  TYPE RS_BOOL, "   
lv_e_url_prefix  TYPE STRING, "   
lv_e_use_sap_export_lib  TYPE RS_BOOL, "   
lv_e_font_path  TYPE STRING, "   
lv_e_ads_https  TYPE RS_BOOL, "   
lv_e_max_message_type  TYPE SYMSGTY. "   

  CALL FUNCTION 'RSWR_PORTAL_CONFIG_GET'  "Returns Saved Runtime Data
    IMPORTING
         E_USER_NAME = lv_e_user_name
         E_DEFAULT_FONT = lv_e_default_font
         E_RFC_DESTINATION = lv_e_rfc_destination
         E_SYSTEM_NAME = lv_e_system_name
         E_DEFAULT_PORTAL = lv_e_default_portal
         E_URL_PREFIX = lv_e_url_prefix
         E_USE_SAP_EXPORT_LIB = lv_e_use_sap_export_lib
         E_FONT_PATH = lv_e_font_path
         E_ADS_HTTPS = lv_e_ads_https
         E_MAX_MESSAGE_TYPE = lv_e_max_message_type
    TABLES
         I_T_STATISTIC_INFO = lt_i_t_statistic_info
    EXCEPTIONS
        ERROR = 1
. " RSWR_PORTAL_CONFIG_GET




ABAP code using 7.40 inline data declarations to call FM RSWR_PORTAL_CONFIG_GET

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



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!