SAP FMFG_MM_REQ_CHANGE Function Module for Update Enjoy purchase requisition

Search SAP Function Modules

FMFG_MM_REQ_CHANGE is a standard fmfg mm req change SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Update Enjoy purchase requisition 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 fmfg mm req change FM, simply by entering the name FMFG_MM_REQ_CHANGE into the relevant SAP transaction such as SE37 or SE38.

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

Function FMFG_MM_REQ_CHANGE 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 'FMFG_MM_REQ_CHANGE'"Update Enjoy purchase requisition
  EXPORTING
   IM_BANFN =  "Purchase requisition number
*  IM_TESTRUN =  "Test run - no database update
*  IM_RELEASE_PARK =  "Post parked requisition

TABLES
*  RETURN =  "Return parameter
   IM_MEREQ_ITEM =  "OO Purchase Requisition: Item Status
   IM_MEREQ_ITEMX =  "00 Purchase Requisition: Change Bar for Item
*  IM_ACCT =  "OO Purchase Requisition: Account Assignment Status
*  IM_ACCTX =  "00 Purchase Requisition: Change Bar for Account Assignment

.

IMPORTING Parameters details for FMFG_MM_REQ_CHANGE

IM_BANFN - Purchase requisition number

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

IM_TESTRUN - Test run - no database update

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

IM_RELEASE_PARK - Post parked requisition

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

TABLES Parameters details for FMFG_MM_REQ_CHANGE

RETURN - Return parameter

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

IM_MEREQ_ITEM - OO Purchase Requisition: Item Status

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

IM_MEREQ_ITEMX - 00 Purchase Requisition: Change Bar for Item

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

IM_ACCT - OO Purchase Requisition: Account Assignment Status

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

IM_ACCTX - 00 Purchase Requisition: Change Bar for Account Assignment

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

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

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