SAP FVD_SEPA_OL_DD_CHECK_DATE Function Module for Check used payment date against mandate









FVD_SEPA_OL_DD_CHECK_DATE is a standard fvd sepa ol dd check 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 used payment date against mandate 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 date FM, simply by entering the name FVD_SEPA_OL_DD_CHECK_DATE 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_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_SEPA_OL_DD_CHECK_DATE'"Check used payment date against mandate
EXPORTING
I_PARTNER = "Business Partner Number
I_BANK_ID = "Partner Bank Type
I_MNDID = "Unique Reference to Mandate per Payment Recipient
I_WRK_VDARL = "Loans
* I_WRK_VDBOHEAD = "Business Operation: Header
I_WRK_VDBOBEPP = "Business Operation: Entered and Activated Flow Data
I_DATE = "Current Date of Application Server
I_ZLSCH = "Payment Method

IMPORTING
E_UZAWE = "Payment Method Supplement
E_CHECK_DATE = "Payment Date

EXCEPTIONS
ERROR = 1 WARNING = 2
.



IMPORTING Parameters details for FVD_SEPA_OL_DD_CHECK_DATE

I_PARTNER - Business Partner Number

Data type: BU_PARTNER
Optional: No
Call by Reference: Yes

I_BANK_ID - Partner Bank Type

Data type: BVTYP
Optional: No
Call by Reference: Yes

I_MNDID - Unique Reference to Mandate per Payment Recipient

Data type: SEPA_MNDID
Optional: No
Call by Reference: Yes

I_WRK_VDARL - Loans

Data type: VDARL
Optional: No
Call by Reference: Yes

I_WRK_VDBOHEAD - Business Operation: Header

Data type: VDBOHEAD
Optional: Yes
Call by Reference: Yes

I_WRK_VDBOBEPP - Business Operation: Entered and Activated Flow Data

Data type: VDBOBEPP
Optional: No
Call by Reference: Yes

I_DATE - Current Date of Application Server

Data type: SYDATUM
Optional: No
Call by Reference: Yes

I_ZLSCH - Payment Method

Data type: DZLSCH
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for FVD_SEPA_OL_DD_CHECK_DATE

E_UZAWE - Payment Method Supplement

Data type: VDBEPP-UZAWE
Optional: No
Call by Reference: Yes

E_CHECK_DATE - Payment Date

Data type: VDBEPP-DDISPO
Optional: No
Call by Reference: Yes

EXCEPTIONS details

ERROR -

Data type:
Optional: No
Call by Reference: Yes

WARNING -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FVD_SEPA_OL_DD_CHECK_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_error  TYPE STRING, "   
lv_e_uzawe  TYPE VDBEPP-UZAWE, "   
lv_i_partner  TYPE BU_PARTNER, "   
lv_warning  TYPE BU_PARTNER, "   
lv_i_bank_id  TYPE BVTYP, "   
lv_e_check_date  TYPE VDBEPP-DDISPO, "   
lv_i_mndid  TYPE SEPA_MNDID, "   
lv_i_wrk_vdarl  TYPE VDARL, "   
lv_i_wrk_vdbohead  TYPE VDBOHEAD, "   
lv_i_wrk_vdbobepp  TYPE VDBOBEPP, "   
lv_i_date  TYPE SYDATUM, "   
lv_i_zlsch  TYPE DZLSCH. "   

  CALL FUNCTION 'FVD_SEPA_OL_DD_CHECK_DATE'  "Check used payment date against mandate
    EXPORTING
         I_PARTNER = lv_i_partner
         I_BANK_ID = lv_i_bank_id
         I_MNDID = lv_i_mndid
         I_WRK_VDARL = lv_i_wrk_vdarl
         I_WRK_VDBOHEAD = lv_i_wrk_vdbohead
         I_WRK_VDBOBEPP = lv_i_wrk_vdbobepp
         I_DATE = lv_i_date
         I_ZLSCH = lv_i_zlsch
    IMPORTING
         E_UZAWE = lv_e_uzawe
         E_CHECK_DATE = lv_e_check_date
    EXCEPTIONS
        ERROR = 1
        WARNING = 2
. " FVD_SEPA_OL_DD_CHECK_DATE




ABAP code using 7.40 inline data declarations to call FM FVD_SEPA_OL_DD_CHECK_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 UZAWE FROM VDBEPP INTO @DATA(ld_e_uzawe).
 
 
 
 
"SELECT single DDISPO FROM VDBEPP INTO @DATA(ld_e_check_date).
 
 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!