SAP ME_PROCESS_REQUISITIONS Function Module for NOTRANSL: Bestellanforderungen umsetzen

Search SAP Function Modules

ME_PROCESS_REQUISITIONS is a standard me process requisitions 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: Bestellanforderungen umsetzen 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 me process requisitions FM, simply by entering the name ME_PROCESS_REQUISITIONS into the relevant SAP transaction such as SE37 or SE38.

Function Group: MESHOW
Program Name: SAPLMESHOW
Main Program: SAPLMESHOW
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function ME_PROCESS_REQUISITIONS 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 'ME_PROCESS_REQUISITIONS'"NOTRANSL: Bestellanforderungen umsetzen
  EXPORTING
   I_EKKO =  "Transfer Parameters
*  I_AUTO = ' ' "Control Parameters
*  I_ENQUEUE = ' ' "
   I_REQUISITIONS =  "Table Type EBAN
*  I_REQUISITION_ACCOUNTINGS =  "Table Type EBKN

 IMPORTING
   E_REQUISITIONS =  "PReq Memory Table Type
   E_UPDKZ =  "

EXCEPTIONS
   NO_AUTHORITY = 1    INVALID_CALL = 2 

.

IMPORTING Parameters details for ME_PROCESS_REQUISITIONS

I_EKKO - Transfer Parameters

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

I_AUTO - Control Parameters

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

I_ENQUEUE -

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

I_REQUISITIONS - Table Type EBAN

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

I_REQUISITION_ACCOUNTINGS - Table Type EBKN

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

EXPORTING Parameters details for ME_PROCESS_REQUISITIONS

E_REQUISITIONS - PReq Memory Table Type

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

E_UPDKZ -

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

EXCEPTIONS details

NO_AUTHORITY -

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

INVALID_CALL -

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

Copy and paste ABAP code example for ME_PROCESS_REQUISITIONS 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.

ABAP code using 7.40 inline data declarations to call FM ME_PROCESS_REQUISITIONS

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.

Search for further information about these or an SAP related objects