SAP FVD_CHECK_CHANGE_AFTER_DATE Function Module for Check If Manually Changed Flows Exist After Key Date
FVD_CHECK_CHANGE_AFTER_DATE is a standard fvd check change after date 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 If Manually Changed Flows Exist After Key Date 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 fvd check change after date FM, simply by entering the name FVD_CHECK_CHANGE_AFTER_DATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVD_ALV
Program Name: SAPLFVD_ALV
Main Program: SAPLFVD_ALV
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FVD_CHECK_CHANGE_AFTER_DATE 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 'FVD_CHECK_CHANGE_AFTER_DATE'"Check If Manually Changed Flows Exist After Key Date.
EXPORTING
SI_CHECK_DATE = "Key Date
* SI_IT_VZZBEPP = "Flows
* SI_IT_VDBEPP = "
EXCEPTIONS
RESULT_TRUE = 1
IMPORTING Parameters details for FVD_CHECK_CHANGE_AFTER_DATE
SI_CHECK_DATE - Key Date
Data type: VZZBEPP-DVALUTOptional: No
Call by Reference: Yes
SI_IT_VZZBEPP - Flows
Data type: TRTY_VZZBEPPOptional: Yes
Call by Reference: Yes
SI_IT_VDBEPP -
Data type: TRTY_VDBEPPOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
RESULT_TRUE - Es existieren geƤnderte Bewegungen nach Stichtag
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FVD_CHECK_CHANGE_AFTER_DATE 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_result_true | TYPE STRING, " | |||
| lv_si_check_date | TYPE VZZBEPP-DVALUT, " | |||
| lv_si_it_vzzbepp | TYPE TRTY_VZZBEPP, " | |||
| lv_si_it_vdbepp | TYPE TRTY_VDBEPP. " |
|   CALL FUNCTION 'FVD_CHECK_CHANGE_AFTER_DATE' "Check If Manually Changed Flows Exist After Key Date |
| EXPORTING | ||
| SI_CHECK_DATE | = lv_si_check_date | |
| SI_IT_VZZBEPP | = lv_si_it_vzzbepp | |
| SI_IT_VDBEPP | = lv_si_it_vdbepp | |
| EXCEPTIONS | ||
| RESULT_TRUE = 1 | ||
| . " FVD_CHECK_CHANGE_AFTER_DATE | ||
ABAP code using 7.40 inline data declarations to call FM FVD_CHECK_CHANGE_AFTER_DATE
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 DVALUT FROM VZZBEPP INTO @DATA(ld_si_check_date). | ||||
Search for further information about these or an SAP related objects