SAP BAPI_XBP_VERSION_CHECK_INT Function Module for The Version of the External Tool is Tested Against the Supported Vers.









BAPI_XBP_VERSION_CHECK_INT is a standard bapi xbp version check int SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for The Version of the External Tool is Tested Against the Supported Vers. 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 bapi xbp version check int FM, simply by entering the name BAPI_XBP_VERSION_CHECK_INT into the relevant SAP transaction such as SE37 or SE38.

Function Group: SXBP
Program Name: SAPLSXBP
Main Program: SAPLSXBP
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function BAPI_XBP_VERSION_CHECK_INT 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 'BAPI_XBP_VERSION_CHECK_INT'"The Version of the External Tool is Tested Against the Supported Vers.
EXPORTING
* MAJOR = 00 "
* MINOR = 00 "
* PATCHLEVEL = 0000 "

IMPORTING
VERSION_VALID = "
.



IMPORTING Parameters details for BAPI_XBP_VERSION_CHECK_INT

MAJOR -

Data type: SXMIMAJMIN-MAJOR
Default: 00
Optional: Yes
Call by Reference: No ( called with pass by value option)

MINOR -

Data type: SXMIMAJMIN-MINOR
Default: 00
Optional: Yes
Call by Reference: No ( called with pass by value option)

PATCHLEVEL -

Data type: SXMIMAJMIN-PATCHLEVEL
Default: 0000
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BAPI_XBP_VERSION_CHECK_INT

VERSION_VALID -

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

Copy and paste ABAP code example for BAPI_XBP_VERSION_CHECK_INT 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_major  TYPE SXMIMAJMIN-MAJOR, "   00
lv_version_valid  TYPE C, "   
lv_minor  TYPE SXMIMAJMIN-MINOR, "   00
lv_patchlevel  TYPE SXMIMAJMIN-PATCHLEVEL. "   0000

  CALL FUNCTION 'BAPI_XBP_VERSION_CHECK_INT'  "The Version of the External Tool is Tested Against the Supported Vers.
    EXPORTING
         MAJOR = lv_major
         MINOR = lv_minor
         PATCHLEVEL = lv_patchlevel
    IMPORTING
         VERSION_VALID = lv_version_valid
. " BAPI_XBP_VERSION_CHECK_INT




ABAP code using 7.40 inline data declarations to call FM BAPI_XBP_VERSION_CHECK_INT

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 MAJOR FROM SXMIMAJMIN INTO @DATA(ld_major).
DATA(ld_major) = 00.
 
 
"SELECT single MINOR FROM SXMIMAJMIN INTO @DATA(ld_minor).
DATA(ld_minor) = 00.
 
"SELECT single PATCHLEVEL FROM SXMIMAJMIN INTO @DATA(ld_patchlevel).
DATA(ld_patchlevel) = 0000.
 


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!