BAPI_DOCUMENT_GETACTVERSION SAP Function module - Determine Valid Version of a Document

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

Associated Function Group: CVBAPI
Released Date: 03.06.1998
Processing type: Remote-Enabled

Pattern for FM BAPI_DOCUMENT_GETACTVERSION - BAPI DOCUMENT GETACTVERSION

CALL FUNCTION 'BAPI_DOCUMENT_GETACTVERSION' "Determine Valid Version of a Document
  EXPORTING
    documenttype =              " bapi_doc_aux-doctype  Document Type
    documentnumber =            " bapi_doc_aux-docnumber  Document Number
    documentpart =              " bapi_doc_aux-docpart  Document Part
*   documentversion =           " bapi_doc_aux-docversion  Document Version
*   date = SY-DATUM             " bapi_doc_aux-datum  Date
*   releaseonly = ''            " bapi_doc_aux-flag  Released Documents Only
  IMPORTING
    return =                    " bapiret2      BAPI Return
    actualversion =             " bapi_doc_aux-docversion  Valid Document Version
    .  "  BAPI_DOCUMENT_GETACTVERSION

ABAP code example for Function Module BAPI_DOCUMENT_GETACTVERSION

The ABAP code below is a full code listing to execute function module BAPI_DOCUMENT_GETACTVERSION 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_return  
 
 TYPE BAPIRET2
,
ld_actualversion  
 
 TYPE BAPI_DOC_AUX-DOCVERSION
.



DATA(ld_documenttype) = some text here


DATA(ld_documentnumber) = some text here


DATA(ld_documentpart) = some text here


DATA(ld_documentversion) = some text here


DATA(ld_date) = 20210129


DATA(ld_releaseonly) = some text here
.

CALL FUNCTION 'BAPI_DOCUMENT_GETACTVERSION'
  EXPORTING
    documenttype =               ld_documenttype
    documentnumber =             ld_documentnumber
    documentpart =               ld_documentpart
*   documentversion =            ld_documentversion
*   date =                       ld_date
*   releaseonly =                ld_releaseonly
  IMPORTING
    return =                     ld_return
    actualversion =              ld_actualversion
    .  "  BAPI_DOCUMENT_GETACTVERSION

IF SY-SUBRC EQ 0.
  "All OK
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_return
 
 TYPE BAPIRET2 ,
ld_documenttype
 
 TYPE BAPI_DOC_AUX-DOCTYPE ,
ld_actualversion
 
 TYPE BAPI_DOC_AUX-DOCVERSION ,
ld_documentnumber
 
 TYPE BAPI_DOC_AUX-DOCNUMBER ,
ld_documentpart
 
 TYPE BAPI_DOC_AUX-DOCPART ,
ld_documentversion
 
 TYPE BAPI_DOC_AUX-DOCVERSION ,
ld_date
 
 TYPE BAPI_DOC_AUX-DATUM ,
ld_releaseonly
 
 TYPE BAPI_DOC_AUX-FLAG .



ld_documenttype = some text here

ld_documentnumber = some text here

ld_documentpart = some text here

ld_documentversion = some text here

ld_date = 20210129

ld_releaseonly = some text here

SAP Documentation for FM BAPI_DOCUMENT_GETACTVERSION