SAP MEDI_REQ_RELEASE Function Module for NOTRANSL: Update aus Freigabe









MEDI_REQ_RELEASE is a standard medi req release 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: Update aus Freigabe 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 medi req release FM, simply by entering the name MEDI_REQ_RELEASE into the relevant SAP transaction such as SE37 or SE38.

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



Function MEDI_REQ_RELEASE 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 'MEDI_REQ_RELEASE'"NOTRANSL: Update aus Freigabe
EXPORTING
IM_EBAN = "Purchase Requisition
IM_EBAN_OLD = "
IM_ACTIVITY = "Activity Category in the Transaction
* IM_DCM = "DCM Purchasing Version Management
* IM_DCM_ADAPTER = "Links Business Object to DCM
* IM_PERSISTENT = MMPUR_YES "
* IM_NO_OVERALL_RELEASE = MMPUR_NO "
* IM_OV_REJECTED = MMPUR_NO "

IMPORTING
EX_DCM = "DCM Purchasing Version Management
EX_BANPR = "Requisition Processing State
EX_RLWRT = "Total value at time of release

EXCEPTIONS
DCM_ERROR = 1
.



IMPORTING Parameters details for MEDI_REQ_RELEASE

IM_EBAN - Purchase Requisition

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

IM_EBAN_OLD -

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

IM_ACTIVITY - Activity Category in the Transaction

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

IM_DCM - DCM Purchasing Version Management

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

IM_DCM_ADAPTER - Links Business Object to DCM

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

IM_PERSISTENT -

Data type: MMPUR_BOOL
Default: MMPUR_YES
Optional: Yes
Call by Reference: Yes

IM_NO_OVERALL_RELEASE -

Data type: MMPUR_BOOL
Default: MMPUR_NO
Optional: Yes
Call by Reference: Yes

IM_OV_REJECTED -

Data type: MMPUR_BOOL
Default: MMPUR_NO
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for MEDI_REQ_RELEASE

EX_DCM - DCM Purchasing Version Management

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

EX_BANPR - Requisition Processing State

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

EX_RLWRT - Total value at time of release

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

EXCEPTIONS details

DCM_ERROR -

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

Copy and paste ABAP code example for MEDI_REQ_RELEASE 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_ex_dcm  TYPE IF_REVISION_MANAGER_DCM, "   
lv_im_eban  TYPE EBAN, "   
lv_dcm_error  TYPE EBAN, "   
lv_ex_banpr  TYPE BANPR, "   
lv_im_eban_old  TYPE EBAN, "   
lv_ex_rlwrt  TYPE RLWRT, "   
lv_im_activity  TYPE AKTYP, "   
lv_im_dcm  TYPE IF_REVISION_MANAGER_DCM, "   
lv_im_dcm_adapter  TYPE IF_DCM_ADAPTER, "   
lv_im_persistent  TYPE MMPUR_BOOL, "   MMPUR_YES
lv_im_no_overall_release  TYPE MMPUR_BOOL, "   MMPUR_NO
lv_im_ov_rejected  TYPE MMPUR_BOOL. "   MMPUR_NO

  CALL FUNCTION 'MEDI_REQ_RELEASE'  "NOTRANSL: Update aus Freigabe
    EXPORTING
         IM_EBAN = lv_im_eban
         IM_EBAN_OLD = lv_im_eban_old
         IM_ACTIVITY = lv_im_activity
         IM_DCM = lv_im_dcm
         IM_DCM_ADAPTER = lv_im_dcm_adapter
         IM_PERSISTENT = lv_im_persistent
         IM_NO_OVERALL_RELEASE = lv_im_no_overall_release
         IM_OV_REJECTED = lv_im_ov_rejected
    IMPORTING
         EX_DCM = lv_ex_dcm
         EX_BANPR = lv_ex_banpr
         EX_RLWRT = lv_ex_rlwrt
    EXCEPTIONS
        DCM_ERROR = 1
. " MEDI_REQ_RELEASE




ABAP code using 7.40 inline data declarations to call FM MEDI_REQ_RELEASE

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.

 
 
 
 
 
 
 
 
 
DATA(ld_im_persistent) = MMPUR_YES.
 
DATA(ld_im_no_overall_release) = MMPUR_NO.
 
DATA(ld_im_ov_rejected) = MMPUR_NO.
 


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!