SAP FVD_SEPA_OL_DD_CHECK_RECORD Function Module for Check planned record. Relevant or not ?
FVD_SEPA_OL_DD_CHECK_RECORD is a standard fvd sepa ol dd check record 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 planned record. Relevant or not ? 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 sepa ol dd check record FM, simply by entering the name FVD_SEPA_OL_DD_CHECK_RECORD into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVD_SEPA_OL
Program Name: SAPLFVD_SEPA_OL
Main Program: SAPLFVD_SEPA_OL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FVD_SEPA_OL_DD_CHECK_RECORD 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_SEPA_OL_DD_CHECK_RECORD'"Check planned record. Relevant or not ?.
EXPORTING
I_KEYDATE = "SEPA DD Key date
I_WRK_VDBEPP = "Flow Data - Planned Item
* I_WRK_ADDBEPP = "Additional information on VDBEPP
* I_WRK_VDARL = "Loans
* I_MINDATE = "SEPA DD Minimum Posting Date
IMPORTING
E_FLG_RELEVANT = "General Flag
E_WRK_SEPA_DD_RESULT = "Structure for SEPA Direct Debit
E_SEPA_POSTING_DATE = "Posting Date in the Document
E_CALC_DATE = "Payment Date
EXCEPTIONS
ERROR = 1 LEADTIME_NOT_UNIQUE = 2 LEADTIME_NO_RESULT = 3 LEADTIME_ERROR = 4 NO_VALID_MANDATE = 5
IMPORTING Parameters details for FVD_SEPA_OL_DD_CHECK_RECORD
I_KEYDATE - SEPA DD Key date
Data type: TB_SEPA_DD_KEYDATEOptional: No
Call by Reference: Yes
I_WRK_VDBEPP - Flow Data - Planned Item
Data type: VDBEPPOptional: No
Call by Reference: Yes
I_WRK_ADDBEPP - Additional information on VDBEPP
Data type: ADDBEPPOptional: Yes
Call by Reference: Yes
I_WRK_VDARL - Loans
Data type: VDARLOptional: Yes
Call by Reference: Yes
I_MINDATE - SEPA DD Minimum Posting Date
Data type: TB_SEPA_DD_BUDATOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for FVD_SEPA_OL_DD_CHECK_RECORD
E_FLG_RELEVANT - General Flag
Data type: FLAGOptional: No
Call by Reference: Yes
E_WRK_SEPA_DD_RESULT - Structure for SEPA Direct Debit
Data type: VDSEPA_DD_FIELDSOptional: No
Call by Reference: Yes
E_SEPA_POSTING_DATE - Posting Date in the Document
Data type: BUDATOptional: No
Call by Reference: Yes
E_CALC_DATE - Payment Date
Data type: VDBEPP-DDISPOOptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR -
Data type:Optional: No
Call by Reference: Yes
LEADTIME_NOT_UNIQUE -
Data type:Optional: No
Call by Reference: Yes
LEADTIME_NO_RESULT -
Data type:Optional: No
Call by Reference: Yes
LEADTIME_ERROR -
Data type:Optional: No
Call by Reference: Yes
NO_VALID_MANDATE -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FVD_SEPA_OL_DD_CHECK_RECORD 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_error | TYPE STRING, " | |||
| lv_i_keydate | TYPE TB_SEPA_DD_KEYDATE, " | |||
| lv_e_flg_relevant | TYPE FLAG, " | |||
| lv_i_wrk_vdbepp | TYPE VDBEPP, " | |||
| lv_leadtime_not_unique | TYPE VDBEPP, " | |||
| lv_e_wrk_sepa_dd_result | TYPE VDSEPA_DD_FIELDS, " | |||
| lv_i_wrk_addbepp | TYPE ADDBEPP, " | |||
| lv_leadtime_no_result | TYPE ADDBEPP, " | |||
| lv_e_sepa_posting_date | TYPE BUDAT, " | |||
| lv_e_calc_date | TYPE VDBEPP-DDISPO, " | |||
| lv_i_wrk_vdarl | TYPE VDARL, " | |||
| lv_leadtime_error | TYPE VDARL, " | |||
| lv_i_mindate | TYPE TB_SEPA_DD_BUDAT, " | |||
| lv_no_valid_mandate | TYPE TB_SEPA_DD_BUDAT. " |
|   CALL FUNCTION 'FVD_SEPA_OL_DD_CHECK_RECORD' "Check planned record. Relevant or not ? |
| EXPORTING | ||
| I_KEYDATE | = lv_i_keydate | |
| I_WRK_VDBEPP | = lv_i_wrk_vdbepp | |
| I_WRK_ADDBEPP | = lv_i_wrk_addbepp | |
| I_WRK_VDARL | = lv_i_wrk_vdarl | |
| I_MINDATE | = lv_i_mindate | |
| IMPORTING | ||
| E_FLG_RELEVANT | = lv_e_flg_relevant | |
| E_WRK_SEPA_DD_RESULT | = lv_e_wrk_sepa_dd_result | |
| E_SEPA_POSTING_DATE | = lv_e_sepa_posting_date | |
| E_CALC_DATE | = lv_e_calc_date | |
| EXCEPTIONS | ||
| ERROR = 1 | ||
| LEADTIME_NOT_UNIQUE = 2 | ||
| LEADTIME_NO_RESULT = 3 | ||
| LEADTIME_ERROR = 4 | ||
| NO_VALID_MANDATE = 5 | ||
| . " FVD_SEPA_OL_DD_CHECK_RECORD | ||
ABAP code using 7.40 inline data declarations to call FM FVD_SEPA_OL_DD_CHECK_RECORD
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 DDISPO FROM VDBEPP INTO @DATA(ld_e_calc_date). | ||||
Search for further information about these or an SAP related objects