SAP Function Modules

BICS_PROV_GET_VERSION SAP Function module - Get Back-End Version







BICS_PROV_GET_VERSION 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 BICS_PROV_GET_VERSION into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: RSBOLAP_BICS_PROVIDER
Released Date: Not Released
Processing type: Remote-Enabled
remote enabled module settings


Pattern for FM BICS_PROV_GET_VERSION - BICS PROV GET VERSION





CALL FUNCTION 'BICS_PROV_GET_VERSION' "Get Back-End Version
* EXPORTING
*   i_java_version =            " int4          Java Version
  IMPORTING
    e_release =                 " int4          Natural Number
    e_support_package =         " int4          Natural Number
    e_version =                 " int4          Natural Number
    e_java_version_supported =   " rs_bool      Is Java Version Supported?
    e_max_message_type =        " symsgty       Messages, Message Type
* TABLES
*   i_t_statistic_info =        " rssta_s_eventinput  OLAP Statistics: Mass Insert of Event Data
  EXCEPTIONS
    UNSUPPORTED_JAVA_VERSION = 1  "             This Java Version Is Not Supported
    .  "  BICS_PROV_GET_VERSION

ABAP code example for Function Module BICS_PROV_GET_VERSION





The ABAP code below is a full code listing to execute function module BICS_PROV_GET_VERSION 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_e_release  TYPE INT4 ,
ld_e_support_package  TYPE INT4 ,
ld_e_version  TYPE INT4 ,
ld_e_java_version_supported  TYPE RS_BOOL ,
ld_e_max_message_type  TYPE SYMSGTY ,
it_i_t_statistic_info  TYPE STANDARD TABLE OF RSSTA_S_EVENTINPUT,"TABLES PARAM
wa_i_t_statistic_info  LIKE LINE OF it_i_t_statistic_info .

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

"populate fields of struture and append to itab
append wa_i_t_statistic_info to it_i_t_statistic_info. . CALL FUNCTION 'BICS_PROV_GET_VERSION' * EXPORTING * i_java_version = ld_i_java_version IMPORTING e_release = ld_e_release e_support_package = ld_e_support_package e_version = ld_e_version e_java_version_supported = ld_e_java_version_supported e_max_message_type = ld_e_max_message_type * TABLES * i_t_statistic_info = it_i_t_statistic_info EXCEPTIONS UNSUPPORTED_JAVA_VERSION = 1 . " BICS_PROV_GET_VERSION
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here 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_e_release  TYPE INT4 ,
ld_i_java_version  TYPE INT4 ,
it_i_t_statistic_info  TYPE STANDARD TABLE OF RSSTA_S_EVENTINPUT ,
wa_i_t_statistic_info  LIKE LINE OF it_i_t_statistic_info,
ld_e_support_package  TYPE INT4 ,
ld_e_version  TYPE INT4 ,
ld_e_java_version_supported  TYPE RS_BOOL ,
ld_e_max_message_type  TYPE SYMSGTY .

ld_i_java_version = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_i_t_statistic_info to it_i_t_statistic_info.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name BICS_PROV_GET_VERSION or its description.