SAP MMPV_DATE_CHECK Function Module for
MMPV_DATE_CHECK is a standard mmpv date check 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 mmpv date check FM, simply by entering the name MMPV_DATE_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: MLCCS_MATERIAL_MASTER
Program Name: SAPLMLCCS_MATERIAL_MASTER
Main Program: SAPLMLCCS_MATERIAL_MASTER
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MMPV_DATE_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 'MMPV_DATE_CHECK'".
EXPORTING
I_NEW_LFGJA = "
I_NEW_LFMON = "
I_BUKRS = "Company Code
I_FY_VARIANT = "
EXCEPTIONS
MMPV_BLOCKED = 1 ERROR_OCCURRED = 2
IMPORTING Parameters details for MMPV_DATE_CHECK
I_NEW_LFGJA -
Data type: BDATJOptional: No
Call by Reference: Yes
I_NEW_LFMON -
Data type: MONATOptional: No
Call by Reference: Yes
I_BUKRS - Company Code
Data type: T001-BUKRSOptional: No
Call by Reference: Yes
I_FY_VARIANT -
Data type: PERIVOptional: No
Call by Reference: Yes
EXCEPTIONS details
MMPV_BLOCKED -
Data type:Optional: No
Call by Reference: Yes
ERROR_OCCURRED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for MMPV_DATE_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_new_lfgja | TYPE BDATJ, " | |||
| lv_mmpv_blocked | TYPE BDATJ, " | |||
| lv_i_new_lfmon | TYPE MONAT, " | |||
| lv_error_occurred | TYPE MONAT, " | |||
| lv_i_bukrs | TYPE T001-BUKRS, " | |||
| lv_i_fy_variant | TYPE PERIV. " |
|   CALL FUNCTION 'MMPV_DATE_CHECK' " |
| EXPORTING | ||
| I_NEW_LFGJA | = lv_i_new_lfgja | |
| I_NEW_LFMON | = lv_i_new_lfmon | |
| I_BUKRS | = lv_i_bukrs | |
| I_FY_VARIANT | = lv_i_fy_variant | |
| EXCEPTIONS | ||
| MMPV_BLOCKED = 1 | ||
| ERROR_OCCURRED = 2 | ||
| . " MMPV_DATE_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM MMPV_DATE_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.| "SELECT single BUKRS FROM T001 INTO @DATA(ld_i_bukrs). | ||||
Search for further information about these or an SAP related objects