SAP RSWAD_URL_GET Function Module for Get the URL for Templates, Queries, Reports (3.5 and 7.0)









RSWAD_URL_GET is a standard rswad url 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 Get the URL for Templates, Queries, Reports (3.5 and 7.0) 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 rswad url get FM, simply by entering the name RSWAD_URL_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function RSWAD_URL_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 'RSWAD_URL_GET'"Get the URL for Templates, Queries, Reports (3.5 and 7.0)
  EXPORTING
   I_ACTION =  "Requested Action
*  I_OBJTYPE =  "Object Type (Template, Query, ...)
*  I_TECHNAME =  "Technical Name of the Object
*  I_ADDITIONAL_QUERY_STRING =  "Additional query string
*  I_SERVICE_35 =  "Service (only 3.5)
*  I_SUFFIX_35 =  "Suffix (only 3.5)

 IMPORTING
   E_URL =  "Requested URL
   E_SUBRC =  "Return Value of ABAP Statements
   E_MAX_MESSAGE_TYPE =  "Maximum Message Type

TABLES
*  E_T_MESSAGE =  "Message Texts
*  I_T_STATISTIC_INFO =  "OLAP Statistik: Massen Insert von Event Daten
.



IMPORTING Parameters details for RSWAD_URL_GET

I_ACTION - Requested Action

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

I_OBJTYPE - Object Type (Template, Query, ...)

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

I_TECHNAME - Technical Name of the Object

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

I_ADDITIONAL_QUERY_STRING - Additional query string

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

I_SERVICE_35 - Service (only 3.5)

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

I_SUFFIX_35 - Suffix (only 3.5)

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

EXPORTING Parameters details for RSWAD_URL_GET

E_URL - Requested URL

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

E_SUBRC - Return Value of ABAP Statements

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

E_MAX_MESSAGE_TYPE - Maximum Message Type

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

TABLES Parameters details for RSWAD_URL_GET

E_T_MESSAGE - Message Texts

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

I_T_STATISTIC_INFO - OLAP Statistik: Massen Insert von Event Daten

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

Copy and paste ABAP code example for RSWAD_URL_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_e_url  TYPE STRING, "   
lv_i_action  TYPE RSZWOBJID, "   
lt_e_t_message  TYPE STANDARD TABLE OF BICS_PROV_T_MESSAGE, "   
lv_e_subrc  TYPE SYSUBRC, "   
lv_i_objtype  TYPE RSZWOBJID, "   
lt_i_t_statistic_info  TYPE STANDARD TABLE OF RSSTA_S_EVENTINPUT, "   
lv_i_techname  TYPE RSZWOBJID, "   
lv_e_max_message_type  TYPE SYMSGTY, "   
lv_i_additional_query_string  TYPE STRING, "   
lv_i_service_35  TYPE RSZWOBJID, "   
lv_i_suffix_35  TYPE RSZWOBJID. "   

  CALL FUNCTION 'RSWAD_URL_GET'  "Get the URL for Templates, Queries, Reports (3.5 and 7.0)
    EXPORTING
         I_ACTION = lv_i_action
         I_OBJTYPE = lv_i_objtype
         I_TECHNAME = lv_i_techname
         I_ADDITIONAL_QUERY_STRING = lv_i_additional_query_string
         I_SERVICE_35 = lv_i_service_35
         I_SUFFIX_35 = lv_i_suffix_35
    IMPORTING
         E_URL = lv_e_url
         E_SUBRC = lv_e_subrc
         E_MAX_MESSAGE_TYPE = lv_e_max_message_type
    TABLES
         E_T_MESSAGE = lt_e_t_message
         I_T_STATISTIC_INFO = lt_i_t_statistic_info
. " RSWAD_URL_GET




ABAP code using 7.40 inline data declarations to call FM RSWAD_URL_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!