SAP ME_COMMIT_QUOTA Function Module for NOTRANSL: Anstoß der Verbuchung der Quotensätze
ME_COMMIT_QUOTA is a standard me commit quota 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: Anstoß der Verbuchung der Quotensätze 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 commit quota FM, simply by entering the name ME_COMMIT_QUOTA into the relevant SAP transaction such as SE37 or SE38.
Function Group: MEQR
Program Name: SAPLMEQR
Main Program: SAPLMEQR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ME_COMMIT_QUOTA 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_COMMIT_QUOTA'"NOTRANSL: Anstoß der Verbuchung der Quotensätze.
EXPORTING
* FC_VORGA = "Status of Purchasing Document
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_SAPLMEQR_001 User Exit for Source Determination
IMPORTING Parameters details for ME_COMMIT_QUOTA
FC_VORGA - Status of Purchasing Document
Data type: EKKO-STATUOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ME_COMMIT_QUOTA 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_fc_vorga | TYPE EKKO-STATU. " |
|   CALL FUNCTION 'ME_COMMIT_QUOTA' "NOTRANSL: Anstoß der Verbuchung der Quotensätze |
| EXPORTING | ||
| FC_VORGA | = lv_fc_vorga | |
| . " ME_COMMIT_QUOTA | ||
ABAP code using 7.40 inline data declarations to call FM ME_COMMIT_QUOTA
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 STATU FROM EKKO INTO @DATA(ld_fc_vorga). | ||||
Search for further information about these or an SAP related objects