SAP FVD_MAP_LC_BATCH_PAY_TRANSAC Function Module for Determine Processing Characteristics for Payment Run









FVD_MAP_LC_BATCH_PAY_TRANSAC is a standard fvd map lc batch pay transac SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determine Processing Characteristics for Payment Run 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 map lc batch pay transac FM, simply by entering the name FVD_MAP_LC_BATCH_PAY_TRANSAC into the relevant SAP transaction such as SE37 or SE38.

Function Group: FVD_MAP_LC_BATCH
Program Name: SAPLFVD_MAP_LC_BATCH
Main Program: SAPLFVD_MAP_LC_BATCH
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function FVD_MAP_LC_BATCH_PAY_TRANSAC 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_MAP_LC_BATCH_PAY_TRANSAC'"Determine Processing Characteristics for Payment Run
EXPORTING
* I_FLG_INVALID = ' ' "'X' = Merkmale werden nur auf ungültig gesetzt
* I_FLG_LOCK_VDARL = ' ' "'X' = VDARL wird bei der Verarbeitung zusätzlich gesperrt
* I_FLG_IN_UPDATE_TASK = 'X' "'X' = Verbuchen in Update Task
I_TAB_VDBEKI = "Table Type for Table VDBEKI
I_TAB_VDBEPI = "Table Type for Table VDBEPI

TABLES
I_TAB_VZESS = "Item data IP interface to FI-VV

EXCEPTIONS
ERROR = 1
.



IMPORTING Parameters details for FVD_MAP_LC_BATCH_PAY_TRANSAC

I_FLG_INVALID - 'X' = Merkmale werden nur auf ungültig gesetzt

Data type: FLAG
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_FLG_LOCK_VDARL - 'X' = VDARL wird bei der Verarbeitung zusätzlich gesperrt

Data type: FLAG
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_FLG_IN_UPDATE_TASK - 'X' = Verbuchen in Update Task

Data type: FLAG
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_TAB_VDBEKI - Table Type for Table VDBEKI

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

I_TAB_VDBEPI - Table Type for Table VDBEPI

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

TABLES Parameters details for FVD_MAP_LC_BATCH_PAY_TRANSAC

I_TAB_VZESS - Item data IP interface to FI-VV

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

EXCEPTIONS details

ERROR - Program error

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

Copy and paste ABAP code example for FVD_MAP_LC_BATCH_PAY_TRANSAC 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, "   
lt_i_tab_vzess  TYPE STANDARD TABLE OF VZESS, "   
lv_i_flg_invalid  TYPE FLAG, "   SPACE
lv_i_flg_lock_vdarl  TYPE FLAG, "   SPACE
lv_i_flg_in_update_task  TYPE FLAG, "   'X'
lv_i_tab_vdbeki  TYPE TRTY_VDBEKI, "   
lv_i_tab_vdbepi  TYPE TRTY_VDBEPI. "   

  CALL FUNCTION 'FVD_MAP_LC_BATCH_PAY_TRANSAC'  "Determine Processing Characteristics for Payment Run
    EXPORTING
         I_FLG_INVALID = lv_i_flg_invalid
         I_FLG_LOCK_VDARL = lv_i_flg_lock_vdarl
         I_FLG_IN_UPDATE_TASK = lv_i_flg_in_update_task
         I_TAB_VDBEKI = lv_i_tab_vdbeki
         I_TAB_VDBEPI = lv_i_tab_vdbepi
    TABLES
         I_TAB_VZESS = lt_i_tab_vzess
    EXCEPTIONS
        ERROR = 1
. " FVD_MAP_LC_BATCH_PAY_TRANSAC




ABAP code using 7.40 inline data declarations to call FM FVD_MAP_LC_BATCH_PAY_TRANSAC

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.

 
 
DATA(ld_i_flg_invalid) = ' '.
 
DATA(ld_i_flg_lock_vdarl) = ' '.
 
DATA(ld_i_flg_in_update_task) = 'X'.
 
 
 


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!