SAP MMHR_BUYER_PROCESS Function Module for NOTRANSL: Anzeigen/Ändern/Anlegen Einkäufer
MMHR_BUYER_PROCESS is a standard mmhr buyer process 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: Anzeigen/Ändern/Anlegen Einkäufer 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 mmhr buyer process FM, simply by entering the name MMHR_BUYER_PROCESS into the relevant SAP transaction such as SE37 or SE38.
Function Group: WY09
Program Name: SAPLWY09
Main Program: SAPLWY09
Appliation area: W
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MMHR_BUYER_PROCESS 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 'MMHR_BUYER_PROCESS'"NOTRANSL: Anzeigen/Ändern/Anlegen Einkäufer.
EXPORTING
* PI_PERNR = "Personnel number
PI_TCODE = "Transaction
IMPORTING Parameters details for MMHR_BUYER_PROCESS
PI_PERNR - Personnel number
Data type: WYT3-PERNROptional: Yes
Call by Reference: No ( called with pass by value option)
PI_TCODE - Transaction
Data type: T020-TCODEOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MMHR_BUYER_PROCESS 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_pi_pernr | TYPE WYT3-PERNR, " | |||
| lv_pi_tcode | TYPE T020-TCODE. " |
|   CALL FUNCTION 'MMHR_BUYER_PROCESS' "NOTRANSL: Anzeigen/Ändern/Anlegen Einkäufer |
| EXPORTING | ||
| PI_PERNR | = lv_pi_pernr | |
| PI_TCODE | = lv_pi_tcode | |
| . " MMHR_BUYER_PROCESS | ||
ABAP code using 7.40 inline data declarations to call FM MMHR_BUYER_PROCESS
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 PERNR FROM WYT3 INTO @DATA(ld_pi_pernr). | ||||
| "SELECT single TCODE FROM T020 INTO @DATA(ld_pi_tcode). | ||||
Search for further information about these or an SAP related objects