SAP EXIT_SAPLFVDA_001 Function Module for User Exit IS-IS Disbursement with PAI
EXIT_SAPLFVDA_001 is a standard exit saplfvda 001 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for User Exit IS-IS Disbursement with PAI 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 exit saplfvda 001 FM, simply by entering the name EXIT_SAPLFVDA_001 into the relevant SAP transaction such as SE37 or SE38.
Function Group: XFVD
Program Name: SAPLXFVD
Main Program:
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EXIT_SAPLFVDA_001 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 'EXIT_SAPLFVDA_001'"User Exit IS-IS Disbursement with PAI.
EXPORTING
I_OKCODE_400 = "OK Code from Screen 400
I_OKCODE_430 = "OK Code from Screen 430
I_RMF67 = "Current Screen Value Table RMF67
I_VDARL = "Current VDARL
IMPORTING
CHANGE_FLAG = "Change Flag
E_SBEWART = "Changed Flow Type
TABLES
COPY_AZHBEPP = "
COPY_VDBEPP = "Copy of VDBEPP
Related Function Modules
Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.DISBURSEMENT_SIMULATE Simulates a Loan Disbursement
FVD_DISB_LOG_CHECK Check additional log
FVD_DISB_LOG_STORE Store additional log
FVD_NOTEPAY_CALL_SCREEN Call Screen
LOAN_PAYMENT Loan disbursement
IMPORTING Parameters details for EXIT_SAPLFVDA_001
I_OKCODE_400 - OK Code from Screen 400
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
I_OKCODE_430 - OK Code from Screen 430
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
I_RMF67 - Current Screen Value Table RMF67
Data type: RMF67Optional: No
Call by Reference: No ( called with pass by value option)
I_VDARL - Current VDARL
Data type: VDARLOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for EXIT_SAPLFVDA_001
CHANGE_FLAG - Change Flag
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
E_SBEWART - Changed Flow Type
Data type: VZZBEPP-SBEWARTOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for EXIT_SAPLFVDA_001
COPY_AZHBEPP -
Data type: VZZBEPPOptional: No
Call by Reference: No ( called with pass by value option)
COPY_VDBEPP - Copy of VDBEPP
Data type: VDBEPPOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EXIT_SAPLFVDA_001 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_change_flag | TYPE STRING, " | |||
| lt_copy_azhbepp | TYPE STANDARD TABLE OF VZZBEPP, " | |||
| lv_i_okcode_400 | TYPE VZZBEPP, " | |||
| lv_e_sbewart | TYPE VZZBEPP-SBEWART, " | |||
| lt_copy_vdbepp | TYPE STANDARD TABLE OF VDBEPP, " | |||
| lv_i_okcode_430 | TYPE VDBEPP, " | |||
| lv_i_rmf67 | TYPE RMF67, " | |||
| lv_i_vdarl | TYPE VDARL. " |
|   CALL FUNCTION 'EXIT_SAPLFVDA_001' "User Exit IS-IS Disbursement with PAI |
| EXPORTING | ||
| I_OKCODE_400 | = lv_i_okcode_400 | |
| I_OKCODE_430 | = lv_i_okcode_430 | |
| I_RMF67 | = lv_i_rmf67 | |
| I_VDARL | = lv_i_vdarl | |
| IMPORTING | ||
| CHANGE_FLAG | = lv_change_flag | |
| E_SBEWART | = lv_e_sbewart | |
| TABLES | ||
| COPY_AZHBEPP | = lt_copy_azhbepp | |
| COPY_VDBEPP | = lt_copy_vdbepp | |
| . " EXIT_SAPLFVDA_001 | ||
ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLFVDA_001
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 SBEWART FROM VZZBEPP INTO @DATA(ld_e_sbewart). | ||||
Search for further information about these or an SAP related objects