SAP KBPS_CHECK_VERSION Function Module for









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

Function Group: KBPS
Program Name: SAPLKBPS
Main Program: SAPLKBPS
Appliation area: K
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function KBPS_CHECK_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 'KBPS_CHECK_VERSION'"
EXPORTING
IM_APPLIK = "Application
* IM_PLANNING_INTEGRATION = ' ' "
IM_VERSION = "Hierarchy indication
IM_WRTTP = "Value Type
* IM_WRTTP2 = ' ' "
* IM_KOKRS = ' ' "Controlling Area
* IM_GJAHR = ' ' "Fiscal Year
* IM_COPY = ' ' "
* IM_NO_YEAR_CHK = ' ' "
* IM_VORGA = ' ' "Business Transaction
* IM_GEBER = ' ' "Fund
* IM_GEBER_ALL = ' ' "
* IM_LANGU = ' ' "Language
* IM_OBJECT = ' ' "
* IM_OVERWRITE = ' ' "
* IM_OVERWRITE_NO_EXCEPTION = ' ' "
* IM_UPDATE = ' ' "
* IM_NO_CO_UPDATE = ' ' "

IMPORTING
EX_VERSTXT = "
EX_OVERWRITE_DIALOG = "
EX_PLANNING_INTEGRATION = "

EXCEPTIONS
VERSION_NOT_FOUND = 1 VERSION_NO_OVERWRITE = 2 VERSION_NO_UPDATE = 3 VERSION_NOT_USEABLE = 4 VERSION_NOT_COPY = 5
.



IMPORTING Parameters details for KBPS_CHECK_VERSION

IM_APPLIK - Application

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

IM_PLANNING_INTEGRATION -

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

IM_VERSION - Hierarchy indication

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

IM_WRTTP - Value Type

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

IM_WRTTP2 -

Data type: BPIN-WRTTP
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_KOKRS - Controlling Area

Data type: BPIN-KOKRS
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_GJAHR - Fiscal Year

Data type: BPIN-GJAHR
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_COPY -

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

IM_NO_YEAR_CHK -

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

IM_VORGA - Business Transaction

Data type: BPIN-VORGA
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_GEBER - Fund

Data type: BPIN-GEBER
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_GEBER_ALL -

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

IM_LANGU - Language

Data type: SY-LANGU
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_OBJECT -

Data type: BPIN-OBJNR
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_OVERWRITE -

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

IM_OVERWRITE_NO_EXCEPTION -

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

IM_UPDATE -

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

IM_NO_CO_UPDATE -

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

EXPORTING Parameters details for KBPS_CHECK_VERSION

EX_VERSTXT -

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

EX_OVERWRITE_DIALOG -

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

EX_PLANNING_INTEGRATION -

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

EXCEPTIONS details

VERSION_NOT_FOUND - Version is not available

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

VERSION_NO_OVERWRITE - Version already exists

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

VERSION_NO_UPDATE -

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

VERSION_NOT_USEABLE -

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

VERSION_NOT_COPY -

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

Copy and paste ABAP code example for KBPS_CHECK_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_im_applik  TYPE BPIN-APPLIK, "   
lv_ex_verstxt  TYPE BPDY-TXT, "   
lv_version_not_found  TYPE BPDY, "   
lv_im_planning_integration  TYPE BPDY, "   SPACE
lv_im_version  TYPE BPIN-VERSN, "   
lv_im_wrttp  TYPE BPIN-WRTTP, "   
lv_im_wrttp2  TYPE BPIN-WRTTP, "   SPACE
lv_im_kokrs  TYPE BPIN-KOKRS, "   SPACE
lv_im_gjahr  TYPE BPIN-GJAHR, "   SPACE
lv_im_copy  TYPE BPIN, "   SPACE
lv_im_no_year_chk  TYPE BPIN, "   SPACE
lv_im_vorga  TYPE BPIN-VORGA, "   SPACE
lv_im_geber  TYPE BPIN-GEBER, "   SPACE
lv_ex_overwrite_dialog  TYPE BPIN, "   
lv_version_no_overwrite  TYPE BPIN, "   
lv_im_geber_all  TYPE BPIN, "   SPACE
lv_version_no_update  TYPE BPIN, "   
lv_ex_planning_integration  TYPE BPIN, "   
lv_im_langu  TYPE SY-LANGU, "   SPACE
lv_version_not_useable  TYPE SY, "   
lv_im_object  TYPE BPIN-OBJNR, "   SPACE
lv_version_not_copy  TYPE BPIN, "   
lv_im_overwrite  TYPE BPIN, "   SPACE
lv_im_overwrite_no_exception  TYPE BPIN, "   SPACE
lv_im_update  TYPE BPIN, "   SPACE
lv_im_no_co_update  TYPE BPIN. "   SPACE

  CALL FUNCTION 'KBPS_CHECK_VERSION'  "
    EXPORTING
         IM_APPLIK = lv_im_applik
         IM_PLANNING_INTEGRATION = lv_im_planning_integration
         IM_VERSION = lv_im_version
         IM_WRTTP = lv_im_wrttp
         IM_WRTTP2 = lv_im_wrttp2
         IM_KOKRS = lv_im_kokrs
         IM_GJAHR = lv_im_gjahr
         IM_COPY = lv_im_copy
         IM_NO_YEAR_CHK = lv_im_no_year_chk
         IM_VORGA = lv_im_vorga
         IM_GEBER = lv_im_geber
         IM_GEBER_ALL = lv_im_geber_all
         IM_LANGU = lv_im_langu
         IM_OBJECT = lv_im_object
         IM_OVERWRITE = lv_im_overwrite
         IM_OVERWRITE_NO_EXCEPTION = lv_im_overwrite_no_exception
         IM_UPDATE = lv_im_update
         IM_NO_CO_UPDATE = lv_im_no_co_update
    IMPORTING
         EX_VERSTXT = lv_ex_verstxt
         EX_OVERWRITE_DIALOG = lv_ex_overwrite_dialog
         EX_PLANNING_INTEGRATION = lv_ex_planning_integration
    EXCEPTIONS
        VERSION_NOT_FOUND = 1
        VERSION_NO_OVERWRITE = 2
        VERSION_NO_UPDATE = 3
        VERSION_NOT_USEABLE = 4
        VERSION_NOT_COPY = 5
. " KBPS_CHECK_VERSION




ABAP code using 7.40 inline data declarations to call FM KBPS_CHECK_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 APPLIK FROM BPIN INTO @DATA(ld_im_applik).
 
"SELECT single TXT FROM BPDY INTO @DATA(ld_ex_verstxt).
 
 
DATA(ld_im_planning_integration) = ' '.
 
"SELECT single VERSN FROM BPIN INTO @DATA(ld_im_version).
 
"SELECT single WRTTP FROM BPIN INTO @DATA(ld_im_wrttp).
 
"SELECT single WRTTP FROM BPIN INTO @DATA(ld_im_wrttp2).
DATA(ld_im_wrttp2) = ' '.
 
"SELECT single KOKRS FROM BPIN INTO @DATA(ld_im_kokrs).
DATA(ld_im_kokrs) = ' '.
 
"SELECT single GJAHR FROM BPIN INTO @DATA(ld_im_gjahr).
DATA(ld_im_gjahr) = ' '.
 
DATA(ld_im_copy) = ' '.
 
DATA(ld_im_no_year_chk) = ' '.
 
"SELECT single VORGA FROM BPIN INTO @DATA(ld_im_vorga).
DATA(ld_im_vorga) = ' '.
 
"SELECT single GEBER FROM BPIN INTO @DATA(ld_im_geber).
DATA(ld_im_geber) = ' '.
 
 
 
DATA(ld_im_geber_all) = ' '.
 
 
 
"SELECT single LANGU FROM SY INTO @DATA(ld_im_langu).
DATA(ld_im_langu) = ' '.
 
 
"SELECT single OBJNR FROM BPIN INTO @DATA(ld_im_object).
DATA(ld_im_object) = ' '.
 
 
DATA(ld_im_overwrite) = ' '.
 
DATA(ld_im_overwrite_no_exception) = ' '.
 
DATA(ld_im_update) = ' '.
 
DATA(ld_im_no_co_update) = ' '.
 


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!