SAP FMFG_INVOICE_STATUS_CHECK Function Module for Check Invoice Status
FMFG_INVOICE_STATUS_CHECK is a standard fmfg invoice status check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check Invoice Status 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 invoice status check FM, simply by entering the name FMFG_INVOICE_STATUS_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: FMFG_INVOICE_STAGES
Program Name: SAPLFMFG_INVOICE_STAGES
Main Program: SAPLFMFG_INVOICE_STAGES
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FMFG_INVOICE_STATUS_CHECK 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_INVOICE_STATUS_CHECK'"Check Invoice Status.
EXPORTING
I_STATUS = "Invoice Status
EXCEPTIONS
NOT_VALID = 1
IMPORTING Parameters details for FMFG_INVOICE_STATUS_CHECK
I_STATUS - Invoice Status
Data type: FMFG_INV_STATUSOptional: No
Call by Reference: Yes
EXCEPTIONS details
NOT_VALID - Not a valid value
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FMFG_INVOICE_STATUS_CHECK 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_status | TYPE FMFG_INV_STATUS, " | |||
| lv_not_valid | TYPE FMFG_INV_STATUS. " |
|   CALL FUNCTION 'FMFG_INVOICE_STATUS_CHECK' "Check Invoice Status |
| EXPORTING | ||
| I_STATUS | = lv_i_status | |
| EXCEPTIONS | ||
| NOT_VALID = 1 | ||
| . " FMFG_INVOICE_STATUS_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM FMFG_INVOICE_STATUS_CHECK
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