SAP VERSION_GET Function Module for









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

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



Function VERSION_GET 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 'VERSION_GET'"
EXPORTING
I_VERSO = "Version
* I_ROW_COL_VERSO = "

IMPORTING
E_VERSO = "Version
E_CANC = "
.



IMPORTING Parameters details for VERSION_GET

I_VERSO - Version

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

I_ROW_COL_VERSO -

Data type: RKB1X-VERSO
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for VERSION_GET

E_VERSO - Version

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

E_CANC -

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

Copy and paste ABAP code example for VERSION_GET 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_e_verso  TYPE RKB1X-VERSO, "   
lv_i_verso  TYPE RKB1X-VERSO, "   
lv_e_canc  TYPE C, "   
lv_i_row_col_verso  TYPE RKB1X-VERSO. "   

  CALL FUNCTION 'VERSION_GET'  "
    EXPORTING
         I_VERSO = lv_i_verso
         I_ROW_COL_VERSO = lv_i_row_col_verso
    IMPORTING
         E_VERSO = lv_e_verso
         E_CANC = lv_e_canc
. " VERSION_GET




ABAP code using 7.40 inline data declarations to call FM VERSION_GET

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 VERSO FROM RKB1X INTO @DATA(ld_e_verso).
 
"SELECT single VERSO FROM RKB1X INTO @DATA(ld_i_verso).
 
 
"SELECT single VERSO FROM RKB1X INTO @DATA(ld_i_row_col_verso).
 


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!