SAP FVD_SEPA_OL_GET_EDD_CUST Function Module for Lesen SEPA Customizing for the Payment Method
FVD_SEPA_OL_GET_EDD_CUST is a standard fvd sepa ol get edd cust SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Lesen SEPA Customizing for the Payment Method 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 get edd cust FM, simply by entering the name FVD_SEPA_OL_GET_EDD_CUST 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_GET_EDD_CUST 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_GET_EDD_CUST'"Lesen SEPA Customizing for the Payment Method.
EXPORTING
I_BUKRS = "Company Code
I_ZLSCH = "Payment Method
IMPORTING
E_XSEPA = "Single-Character Flag
IMPORTING Parameters details for FVD_SEPA_OL_GET_EDD_CUST
I_BUKRS - Company Code
Data type: BUKRSOptional: No
Call by Reference: Yes
I_ZLSCH - Payment Method
Data type: DZLSCHOptional: No
Call by Reference: Yes
EXPORTING Parameters details for FVD_SEPA_OL_GET_EDD_CUST
E_XSEPA - Single-Character Flag
Data type: XSEPAOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FVD_SEPA_OL_GET_EDD_CUST 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_e_xsepa | TYPE XSEPA, " | |||
lv_i_bukrs | TYPE BUKRS, " | |||
lv_i_zlsch | TYPE DZLSCH. " |
  CALL FUNCTION 'FVD_SEPA_OL_GET_EDD_CUST' "Lesen SEPA Customizing for the Payment Method |
EXPORTING | ||
I_BUKRS | = lv_i_bukrs | |
I_ZLSCH | = lv_i_zlsch | |
IMPORTING | ||
E_XSEPA | = lv_e_xsepa | |
. " FVD_SEPA_OL_GET_EDD_CUST |
ABAP code using 7.40 inline data declarations to call FM FVD_SEPA_OL_GET_EDD_CUST
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