SAP FMMM_PROCESS_PURCHASE_ORDER Function Module for









FMMM_PROCESS_PURCHASE_ORDER is a standard fmmm process purchase order SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 fmmm process purchase order FM, simply by entering the name FMMM_PROCESS_PURCHASE_ORDER into the relevant SAP transaction such as SE37 or SE38.

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



Function FMMM_PROCESS_PURCHASE_ORDER 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 'FMMM_PROCESS_PURCHASE_ORDER'"
EXPORTING
I_EBELN = "
I_COMPONENT = "
* I_ENQUEUE = 'X' "
* I_APPLC_CA = ' ' "
* I_APPLC_CB = ' ' "
* I_APPLC_CO = ' ' "
* I_APPLC_FD = ' ' "

EXCEPTIONS
DOCUMENT_LOCKED = 1 DOCUMENT_NOT_FOUND = 2
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLFMMM_001 MM-Commitment Authorization Update: Query FMBUDAT Check in Popup
EXIT_SAPLFMMM_002 MM-VE-Update: Check CCN-active Change: Query on Popup

IMPORTING Parameters details for FMMM_PROCESS_PURCHASE_ORDER

I_EBELN -

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

I_COMPONENT -

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

I_ENQUEUE -

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

I_APPLC_CA -

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

I_APPLC_CB -

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

I_APPLC_CO -

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

I_APPLC_FD -

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

EXCEPTIONS details

DOCUMENT_LOCKED -

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

DOCUMENT_NOT_FOUND -

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

Copy and paste ABAP code example for FMMM_PROCESS_PURCHASE_ORDER 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_i_ebeln  TYPE EKKO-EBELN, "   
lv_document_locked  TYPE EKKO, "   
lv_i_component  TYPE TRWPR-COMPONENT, "   
lv_document_not_found  TYPE TRWPR, "   
lv_i_enqueue  TYPE TRWPR, "   'X'
lv_i_applc_ca  TYPE FMDY-XFELD, "   SPACE
lv_i_applc_cb  TYPE FMDY-XFELD, "   SPACE
lv_i_applc_co  TYPE FMDY-XFELD, "   SPACE
lv_i_applc_fd  TYPE FMDY-XFELD. "   SPACE

  CALL FUNCTION 'FMMM_PROCESS_PURCHASE_ORDER'  "
    EXPORTING
         I_EBELN = lv_i_ebeln
         I_COMPONENT = lv_i_component
         I_ENQUEUE = lv_i_enqueue
         I_APPLC_CA = lv_i_applc_ca
         I_APPLC_CB = lv_i_applc_cb
         I_APPLC_CO = lv_i_applc_co
         I_APPLC_FD = lv_i_applc_fd
    EXCEPTIONS
        DOCUMENT_LOCKED = 1
        DOCUMENT_NOT_FOUND = 2
. " FMMM_PROCESS_PURCHASE_ORDER




ABAP code using 7.40 inline data declarations to call FM FMMM_PROCESS_PURCHASE_ORDER

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 EBELN FROM EKKO INTO @DATA(ld_i_ebeln).
 
 
"SELECT single COMPONENT FROM TRWPR INTO @DATA(ld_i_component).
 
 
DATA(ld_i_enqueue) = 'X'.
 
"SELECT single XFELD FROM FMDY INTO @DATA(ld_i_applc_ca).
DATA(ld_i_applc_ca) = ' '.
 
"SELECT single XFELD FROM FMDY INTO @DATA(ld_i_applc_cb).
DATA(ld_i_applc_cb) = ' '.
 
"SELECT single XFELD FROM FMDY INTO @DATA(ld_i_applc_co).
DATA(ld_i_applc_co) = ' '.
 
"SELECT single XFELD FROM FMDY INTO @DATA(ld_i_applc_fd).
DATA(ld_i_applc_fd) = ' '.
 


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!