SAP CV115_DOCVERSION_CHECK Function Module for NOTRANSL: DVS: Setze Default für Dokumentversion









CV115_DOCVERSION_CHECK is a standard cv115 docversion check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: DVS: Setze Default für Dokumentversion 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 cv115 docversion check FM, simply by entering the name CV115_DOCVERSION_CHECK into the relevant SAP transaction such as SE37 or SE38.

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



Function CV115_DOCVERSION_CHECK 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 'CV115_DOCVERSION_CHECK'"NOTRANSL: DVS: Setze Default für Dokumentversion
EXPORTING
* PF_TRANSACTION = "
* PF_CHECK_ONLY = "
* PS_TDWA = "

IMPORTING
PFX_CREATE_NEW = "Create New Version
PFX_DOKVR_LAST = "
PFX_DOKVR_NEW = "

CHANGING
PSX_DRAW = "

EXCEPTIONS
ERROR = 1
.



IMPORTING Parameters details for CV115_DOCVERSION_CHECK

PF_TRANSACTION -

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

PF_CHECK_ONLY -

Data type: C
Optional: Yes
Call by Reference: Yes

PS_TDWA -

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

EXPORTING Parameters details for CV115_DOCVERSION_CHECK

PFX_CREATE_NEW - Create New Version

Data type: C
Optional: No
Call by Reference: Yes

PFX_DOKVR_LAST -

Data type: DRAW-DOKVR
Optional: No
Call by Reference: Yes

PFX_DOKVR_NEW -

Data type: DRAW-DOKVR
Optional: No
Call by Reference: Yes

CHANGING Parameters details for CV115_DOCVERSION_CHECK

PSX_DRAW -

Data type: DRAW
Optional: No
Call by Reference: Yes

EXCEPTIONS details

ERROR - Errors

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

Copy and paste ABAP code example for CV115_DOCVERSION_CHECK 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_error  TYPE STRING, "   
lv_psx_draw  TYPE DRAW, "   
lv_pfx_create_new  TYPE C, "   
lv_pf_transaction  TYPE SY-TCODE, "   
lv_pf_check_only  TYPE C, "   
lv_pfx_dokvr_last  TYPE DRAW-DOKVR, "   
lv_ps_tdwa  TYPE TDWA, "   
lv_pfx_dokvr_new  TYPE DRAW-DOKVR. "   

  CALL FUNCTION 'CV115_DOCVERSION_CHECK'  "NOTRANSL: DVS: Setze Default für Dokumentversion
    EXPORTING
         PF_TRANSACTION = lv_pf_transaction
         PF_CHECK_ONLY = lv_pf_check_only
         PS_TDWA = lv_ps_tdwa
    IMPORTING
         PFX_CREATE_NEW = lv_pfx_create_new
         PFX_DOKVR_LAST = lv_pfx_dokvr_last
         PFX_DOKVR_NEW = lv_pfx_dokvr_new
    CHANGING
         PSX_DRAW = lv_psx_draw
    EXCEPTIONS
        ERROR = 1
. " CV115_DOCVERSION_CHECK




ABAP code using 7.40 inline data declarations to call FM CV115_DOCVERSION_CHECK

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 TCODE FROM SY INTO @DATA(ld_pf_transaction).
 
 
"SELECT single DOKVR FROM DRAW INTO @DATA(ld_pfx_dokvr_last).
 
 
"SELECT single DOKVR FROM DRAW INTO @DATA(ld_pfx_dokvr_new).
 


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!