UPWB_SET_RUNTIME SAP Function module - Setting of runtime environment for components

UPWB_SET_RUNTIME is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name UPWB_SET_RUNTIME into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: UPWB_COMPONENT
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM UPWB_SET_RUNTIME - UPWB SET RUNTIME

CALL FUNCTION 'UPWB_SET_RUNTIME' "Setting of runtime environment for components
* EXPORTING
*   event_id =                  " string
*   navigation =                " if_bsp_navigation  Business Server Page (BSP) Navigation
*   page =                      " if_bsp_page   Business Server Page (BSP) Page
*   request =                   " if_http_request  HTTP Framework (iHTTP) HTTP Request
*   response =                  " if_http_response  HTTP Framework (iHTTP) HTTP Response
*   runtime =                   " if_bsp_runtime  Business Server Page (BSP) Runtime
*   version =                   " upwb_y_html_version  HTML Version
    .  "  UPWB_SET_RUNTIME

ABAP code example for Function Module UPWB_SET_RUNTIME

The ABAP code below is a full code listing to execute function module UPWB_SET_RUNTIME including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA(ld_event_id) = 'Check type of data required'.

DATA(ld_navigation) = 'Check type of data required'.

DATA(ld_page) = 'Check type of data required'.

DATA(ld_request) = 'Check type of data required'.

DATA(ld_response) = 'Check type of data required'.

DATA(ld_runtime) = 'Check type of data required'.

DATA(ld_version) = 'Check type of data required'.
.

CALL FUNCTION 'UPWB_SET_RUNTIME'
* EXPORTING
*   event_id =                   ld_event_id
*   navigation =                 ld_navigation
*   page =                       ld_page
*   request =                    ld_request
*   response =                   ld_response
*   runtime =                    ld_runtime
*   version =                    ld_version
    .  "  UPWB_SET_RUNTIME

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_event_id
 
 TYPE STRING ,
ld_navigation
 
 TYPE IF_BSP_NAVIGATION ,
ld_page
 
 TYPE IF_BSP_PAGE ,
ld_request
 
 TYPE IF_HTTP_REQUEST ,
ld_response
 
 TYPE IF_HTTP_RESPONSE ,
ld_runtime
 
 TYPE IF_BSP_RUNTIME ,
ld_version
 
 TYPE UPWB_Y_HTML_VERSION .


ld_event_id = 'Check type of data required'.
ld_navigation = 'Check type of data required'.
ld_page = 'Check type of data required'.
ld_request = 'Check type of data required'.
ld_response = 'Check type of data required'.
ld_runtime = 'Check type of data required'.
ld_version = 'Check type of data required'.