SAP FVD_AUTODRAFT_PROCESS Function Module for Create Auto Debit Collection









FVD_AUTODRAFT_PROCESS is a standard fvd autodraft process SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create Auto Debit Collection 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 autodraft process FM, simply by entering the name FVD_AUTODRAFT_PROCESS into the relevant SAP transaction such as SE37 or SE38.

Function Group: FVD_AUTODRAFT_PROCESS
Program Name: SAPLFVD_AUTODRAFT_PROCESS
Main Program: SAPLFVD_AUTODRAFT_PROCESS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function FVD_AUTODRAFT_PROCESS 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_AUTODRAFT_PROCESS'"Create Auto Debit Collection
  EXPORTING
   I_AUTODRAFT_DATE =  "Auto Debit Creation Date
   I_TAB_VDAD_KEYS =  "Table Type for Control Key
   I_OBJECT_LOG =  "Application Log: Object Name (Application Code)
   I_EXT_LOG_NO =  "Application Log: External Identification
   I_SIMULATION =  "Checkbox
   I_RESULT_WRITE =  "Checkbox
   I_TASK_NO =  "Eight-digit numeric value

 IMPORTING
   E_TAB_VDAD_RESULT =  "Result Table for Auto Debit Collection
   E_TAB_VDAD_HIST =  "Table Type Auto Debits History Table
.



IMPORTING Parameters details for FVD_AUTODRAFT_PROCESS

I_AUTODRAFT_DATE - Auto Debit Creation Date

Data type: TB_AD_DATE
Optional: No
Call by Reference: No ( called with pass by value option)

I_TAB_VDAD_KEYS - Table Type for Control Key

Data type: TRTY_VDAD_CONTROL_KEY
Optional: No
Call by Reference: No ( called with pass by value option)

I_OBJECT_LOG - Application Log: Object Name (Application Code)

Data type: BALOBJ_D
Optional: No
Call by Reference: No ( called with pass by value option)

I_EXT_LOG_NO - Application Log: External Identification

Data type: BALNREXT
Optional: No
Call by Reference: No ( called with pass by value option)

I_SIMULATION - Checkbox

Data type: XFELD
Optional: No
Call by Reference: No ( called with pass by value option)

I_RESULT_WRITE - Checkbox

Data type: XFELD
Optional: No
Call by Reference: No ( called with pass by value option)

I_TASK_NO - Eight-digit numeric value

Data type: NUM8
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for FVD_AUTODRAFT_PROCESS

E_TAB_VDAD_RESULT - Result Table for Auto Debit Collection

Data type: TRTY_VDAD_RESULT
Optional: No
Call by Reference: No ( called with pass by value option)

E_TAB_VDAD_HIST - Table Type Auto Debits History Table

Data type: TRTY_VDAD_HIST
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for FVD_AUTODRAFT_PROCESS 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_i_autodraft_date  TYPE TB_AD_DATE, "   
lv_e_tab_vdad_result  TYPE TRTY_VDAD_RESULT, "   
lv_e_tab_vdad_hist  TYPE TRTY_VDAD_HIST, "   
lv_i_tab_vdad_keys  TYPE TRTY_VDAD_CONTROL_KEY, "   
lv_i_object_log  TYPE BALOBJ_D, "   
lv_i_ext_log_no  TYPE BALNREXT, "   
lv_i_simulation  TYPE XFELD, "   
lv_i_result_write  TYPE XFELD, "   
lv_i_task_no  TYPE NUM8. "   

  CALL FUNCTION 'FVD_AUTODRAFT_PROCESS'  "Create Auto Debit Collection
    EXPORTING
         I_AUTODRAFT_DATE = lv_i_autodraft_date
         I_TAB_VDAD_KEYS = lv_i_tab_vdad_keys
         I_OBJECT_LOG = lv_i_object_log
         I_EXT_LOG_NO = lv_i_ext_log_no
         I_SIMULATION = lv_i_simulation
         I_RESULT_WRITE = lv_i_result_write
         I_TASK_NO = lv_i_task_no
    IMPORTING
         E_TAB_VDAD_RESULT = lv_e_tab_vdad_result
         E_TAB_VDAD_HIST = lv_e_tab_vdad_hist
. " FVD_AUTODRAFT_PROCESS




ABAP code using 7.40 inline data declarations to call FM FVD_AUTODRAFT_PROCESS

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



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!