ME_RELEASE_REQUISITION SAP Function module - Process Purchase Requisition

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

Associated Function Group: MESHOW
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM ME_RELEASE_REQUISITION - ME RELEASE REQUISITION

CALL FUNCTION 'ME_RELEASE_REQUISITION' "Process Purchase Requisition
  EXPORTING
    im_banfn =                  " eban-banfn    Purchase Requisition Number
*   im_bnfpo =                  " eban-bnfpo    Item Number of Purchase Requisition
*   im_frgco =                  " frgco         Release Code
*   im_wf =                     " mmpur_bool
  IMPORTING
    ex_requisitions =           " mereq_t_eban_mem  PReq Memory Table Type
    ex_updkz =                  " char1
  EXCEPTIONS
    NO_AUTHORITY = 1            "
    .  "  ME_RELEASE_REQUISITION

ABAP code example for Function Module ME_RELEASE_REQUISITION

The ABAP code below is a full code listing to execute function module ME_RELEASE_REQUISITION 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_ex_requisitions  
 
 TYPE MEREQ_T_EBAN_MEM
,
ld_ex_updkz  
 
 TYPE CHAR1
.

 

SELECT single BANFN 
  FROM EBAN 
  INTO @DATA(ld_im_banfn).

 

SELECT single BNFPO 
  FROM EBAN 
  INTO @DATA(ld_im_bnfpo).


DATA(ld_im_frgco) = 'Check type of data required'.

DATA(ld_im_wf) = 'Check type of data required'.
.

CALL FUNCTION 'ME_RELEASE_REQUISITION'
  EXPORTING
    im_banfn =                   ld_im_banfn
*   im_bnfpo =                   ld_im_bnfpo
*   im_frgco =                   ld_im_frgco
*   im_wf =                      ld_im_wf
  IMPORTING
    ex_requisitions =            ld_ex_requisitions
    ex_updkz =                   ld_ex_updkz
  EXCEPTIONS
    NO_AUTHORITY =               1
    .  "  ME_RELEASE_REQUISITION

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
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_ex_requisitions
 
 TYPE MEREQ_T_EBAN_MEM ,
ld_im_banfn
 
 TYPE EBAN-BANFN ,
ld_ex_updkz
 
 TYPE CHAR1 ,
ld_im_bnfpo
 
 TYPE EBAN-BNFPO ,
ld_im_frgco
 
 TYPE FRGCO ,
ld_im_wf
 
 TYPE MMPUR_BOOL .



SELECT single BANFN 
  FROM EBAN 
  INTO ld_im_banfn.


SELECT single BNFPO 
  FROM EBAN 
  INTO ld_im_bnfpo.

ld_im_frgco = 'Check type of data required'.
ld_im_wf = 'Check type of data required'.