SAP DOCUMENT_WAS_RELEASED Function Module for Finds whether document has been released









DOCUMENT_WAS_RELEASED is a standard document was released SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Finds whether document has been released 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 document was released FM, simply by entering the name DOCUMENT_WAS_RELEASED into the relevant SAP transaction such as SE37 or SE38.

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



Function DOCUMENT_WAS_RELEASED 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 'DOCUMENT_WAS_RELEASED'"Finds whether document has been released
EXPORTING
DOKAR = "Document Type
DOKNR = "Document number
DOKVR = "Document Version
DOKTEIL = "Document Part

IMPORTING
RELEASED_STATUS = "Document Log File
REVISION_USAGE = "
DOCUMENT_ACTUAL_RELEASED = "Document Management Flag
MARKED_FOR_DELETE = "Document Management Flag

EXCEPTIONS
DOCUMENT_NOT_RELEASED = 1
.



IMPORTING Parameters details for DOCUMENT_WAS_RELEASED

DOKAR - Document Type

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

DOKNR - Document number

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

DOKVR - Document Version

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

DOKTEIL - Document Part

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

EXPORTING Parameters details for DOCUMENT_WAS_RELEASED

RELEASED_STATUS - Document Log File

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

REVISION_USAGE -

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

DOCUMENT_ACTUAL_RELEASED - Document Management Flag

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

MARKED_FOR_DELETE - Document Management Flag

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

EXCEPTIONS details

DOCUMENT_NOT_RELEASED -

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

Copy and paste ABAP code example for DOCUMENT_WAS_RELEASED 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_dokar  TYPE DRAW-DOKAR, "   
lv_released_status  TYPE DRAP, "   
lv_document_not_released  TYPE DRAP, "   
lv_doknr  TYPE DRAW-DOKNR, "   
lv_revision_usage  TYPE DRAW, "   
lv_dokvr  TYPE DRAW-DOKVR, "   
lv_document_actual_released  TYPE MCDOK-MARAF, "   
lv_dokteil  TYPE DRAW-DOKTL, "   
lv_marked_for_delete  TYPE MCDOK-MARAF. "   

  CALL FUNCTION 'DOCUMENT_WAS_RELEASED'  "Finds whether document has been released
    EXPORTING
         DOKAR = lv_dokar
         DOKNR = lv_doknr
         DOKVR = lv_dokvr
         DOKTEIL = lv_dokteil
    IMPORTING
         RELEASED_STATUS = lv_released_status
         REVISION_USAGE = lv_revision_usage
         DOCUMENT_ACTUAL_RELEASED = lv_document_actual_released
         MARKED_FOR_DELETE = lv_marked_for_delete
    EXCEPTIONS
        DOCUMENT_NOT_RELEASED = 1
. " DOCUMENT_WAS_RELEASED




ABAP code using 7.40 inline data declarations to call FM DOCUMENT_WAS_RELEASED

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 DOKAR FROM DRAW INTO @DATA(ld_dokar).
 
 
 
"SELECT single DOKNR FROM DRAW INTO @DATA(ld_doknr).
 
 
"SELECT single DOKVR FROM DRAW INTO @DATA(ld_dokvr).
 
"SELECT single MARAF FROM MCDOK INTO @DATA(ld_document_actual_released).
 
"SELECT single DOKTL FROM DRAW INTO @DATA(ld_dokteil).
 
"SELECT single MARAF FROM MCDOK INTO @DATA(ld_marked_for_delete).
 


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!