SAP BWSAPI_GET_VERSION Function Module for









BWSAPI_GET_VERSION is a standard bwsapi get version 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 bwsapi get version FM, simply by entering the name BWSAPI_GET_VERSION into the relevant SAP transaction such as SE37 or SE38.

Function Group: RSBW
Program Name: SAPLRSBW
Main Program: SAPLRSBW
Appliation area: B
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function BWSAPI_GET_VERSION 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 'BWSAPI_GET_VERSION'"
IMPORTING
COMPONENT = "
RELEASE = "
VERSION = "

EXCEPTIONS
NO_VERSION = 1
.



EXPORTING Parameters details for BWSAPI_GET_VERSION

COMPONENT -

Data type: RSSAPIVERS-COMPONENT
Optional: No
Call by Reference: No ( called with pass by value option)

RELEASE -

Data type: RSSAPIVERS-RELEASE
Optional: No
Call by Reference: No ( called with pass by value option)

VERSION -

Data type: RSSAPIVERS-VERSION
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

NO_VERSION -

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

Copy and paste ABAP code example for BWSAPI_GET_VERSION 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_component  TYPE RSSAPIVERS-COMPONENT, "   
lv_no_version  TYPE RSSAPIVERS, "   
lv_release  TYPE RSSAPIVERS-RELEASE, "   
lv_version  TYPE RSSAPIVERS-VERSION. "   

  CALL FUNCTION 'BWSAPI_GET_VERSION'  "
    IMPORTING
         COMPONENT = lv_component
         RELEASE = lv_release
         VERSION = lv_version
    EXCEPTIONS
        NO_VERSION = 1
. " BWSAPI_GET_VERSION




ABAP code using 7.40 inline data declarations to call FM BWSAPI_GET_VERSION

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 COMPONENT FROM RSSAPIVERS INTO @DATA(ld_component).
 
 
"SELECT single RELEASE FROM RSSAPIVERS INTO @DATA(ld_release).
 
"SELECT single VERSION FROM RSSAPIVERS INTO @DATA(ld_version).
 


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!