SAP BAPI_MEDDOC_SETSTATUS Function Module for IS-H*MED: Set Document Status









BAPI_MEDDOC_SETSTATUS is a standard bapi meddoc setstatus SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-H*MED: Set Document Status 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 bapi meddoc setstatus FM, simply by entering the name BAPI_MEDDOC_SETSTATUS into the relevant SAP transaction such as SE37 or SE38.

Function Group: 1400
Program Name: SAPL1400
Main Program: SAPL1400
Appliation area:
Release date: 20-Aug-2001
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_MEDDOC_SETSTATUS 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 'BAPI_MEDDOC_SETSTATUS'"IS-H*MED: Set Document Status
  EXPORTING
   DOCUMENTTYPE =  "Document Type
*  DOCUMENTDATA =  "Document Management Data - WITHOUT Multiple Mov,Service,Req
*  TESTRUN = ' ' "Checkbox: Test Run Without Database Modifications
*  CHECK_PMD_RELEASE = 'X' "Checkbox: Release: Are the Checks to Be Executed in PMD?
   DOCUMENTNUMBER =  "Document Number
   DOCUMENTPART =  "Document Part
   DOCUMENTVERSION =  "Document Version
*  SET_NEXT_STATUS = ' ' "Checkbox: Set Next Status
*  SET_RELEASE_STATUS = ' ' "Checkbox: Release Document
*  STATUSEXTERN =  "Status Abbreviation (Language-Dependent)
*  STATUSINTERN =  "Internal Document Status
*  LOGFIELD =  "Document Management Log Field

 IMPORTING
   WORST_RETURNED_MSGTY =  "Most Severe Message Type

TABLES
*  RETURN =  "Return Messages
.



IMPORTING Parameters details for BAPI_MEDDOC_SETSTATUS

DOCUMENTTYPE - Document Type

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

DOCUMENTDATA - Document Management Data - WITHOUT Multiple Mov,Service,Req

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

TESTRUN - Checkbox: Test Run Without Database Modifications

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

CHECK_PMD_RELEASE - Checkbox: Release: Are the Checks to Be Executed in PMD?

Data type: BAPINALL-XIND
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

DOCUMENTNUMBER - Document Number

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

DOCUMENTPART - Document Part

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

DOCUMENTVERSION - Document Version

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

SET_NEXT_STATUS - Checkbox: Set Next Status

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

SET_RELEASE_STATUS - Checkbox: Release Document

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

STATUSEXTERN - Status Abbreviation (Language-Dependent)

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

STATUSINTERN - Internal Document Status

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

LOGFIELD - Document Management Log Field

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

EXPORTING Parameters details for BAPI_MEDDOC_SETSTATUS

WORST_RETURNED_MSGTY - Most Severe Message Type

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

TABLES Parameters details for BAPI_MEDDOC_SETSTATUS

RETURN - Return Messages

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

Copy and paste ABAP code example for BAPI_MEDDOC_SETSTATUS 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:
lt_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_documenttype  TYPE BAPIMEDDOC_DATA-DOCUMENTTYPE, "   
lv_worst_returned_msgty  TYPE BAPINALL-WORSTRETMSG, "   
lv_documentdata  TYPE BAPIMEDDOC_DATA, "   
lv_testrun  TYPE BAPINALL-TESTRUN, "   SPACE
lv_check_pmd_release  TYPE BAPINALL-XIND, "   'X'
lv_documentnumber  TYPE BAPIMEDDOC_DATA-DOCUMENTNUMBER, "   
lv_documentpart  TYPE BAPIMEDDOC_DATA-DOCUMENTPART, "   
lv_documentversion  TYPE BAPIMEDDOC_DATA-DOCUMENTVERSION, "   
lv_set_next_status  TYPE BAPINALL-XIND, "   SPACE
lv_set_release_status  TYPE BAPINALL-XIND, "   SPACE
lv_statusextern  TYPE BAPIMEDDOC_DATAIN-STATUSEXTERN, "   
lv_statusintern  TYPE BAPIMEDDOC_DATA-STATUSINTERN, "   
lv_logfield  TYPE BAPIMEDDOC_DATA-LOGFIELD. "   

  CALL FUNCTION 'BAPI_MEDDOC_SETSTATUS'  "IS-H*MED: Set Document Status
    EXPORTING
         DOCUMENTTYPE = lv_documenttype
         DOCUMENTDATA = lv_documentdata
         TESTRUN = lv_testrun
         CHECK_PMD_RELEASE = lv_check_pmd_release
         DOCUMENTNUMBER = lv_documentnumber
         DOCUMENTPART = lv_documentpart
         DOCUMENTVERSION = lv_documentversion
         SET_NEXT_STATUS = lv_set_next_status
         SET_RELEASE_STATUS = lv_set_release_status
         STATUSEXTERN = lv_statusextern
         STATUSINTERN = lv_statusintern
         LOGFIELD = lv_logfield
    IMPORTING
         WORST_RETURNED_MSGTY = lv_worst_returned_msgty
    TABLES
         RETURN = lt_return
. " BAPI_MEDDOC_SETSTATUS




ABAP code using 7.40 inline data declarations to call FM BAPI_MEDDOC_SETSTATUS

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 DOCUMENTTYPE FROM BAPIMEDDOC_DATA INTO @DATA(ld_documenttype).
 
"SELECT single WORSTRETMSG FROM BAPINALL INTO @DATA(ld_worst_returned_msgty).
 
 
"SELECT single TESTRUN FROM BAPINALL INTO @DATA(ld_testrun).
DATA(ld_testrun) = ' '.
 
"SELECT single XIND FROM BAPINALL INTO @DATA(ld_check_pmd_release).
DATA(ld_check_pmd_release) = 'X'.
 
"SELECT single DOCUMENTNUMBER FROM BAPIMEDDOC_DATA INTO @DATA(ld_documentnumber).
 
"SELECT single DOCUMENTPART FROM BAPIMEDDOC_DATA INTO @DATA(ld_documentpart).
 
"SELECT single DOCUMENTVERSION FROM BAPIMEDDOC_DATA INTO @DATA(ld_documentversion).
 
"SELECT single XIND FROM BAPINALL INTO @DATA(ld_set_next_status).
DATA(ld_set_next_status) = ' '.
 
"SELECT single XIND FROM BAPINALL INTO @DATA(ld_set_release_status).
DATA(ld_set_release_status) = ' '.
 
"SELECT single STATUSEXTERN FROM BAPIMEDDOC_DATAIN INTO @DATA(ld_statusextern).
 
"SELECT single STATUSINTERN FROM BAPIMEDDOC_DATA INTO @DATA(ld_statusintern).
 
"SELECT single LOGFIELD FROM BAPIMEDDOC_DATA INTO @DATA(ld_logfield).
 


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!