SAP FVD_INV_ACC_OBJ_GET_FLOWS Function Module for Read Flow Data of Contract from DB









FVD_INV_ACC_OBJ_GET_FLOWS is a standard fvd inv acc obj get flows SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read Flow Data of Contract from DB 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 inv acc obj get flows FM, simply by entering the name FVD_INV_ACC_OBJ_GET_FLOWS into the relevant SAP transaction such as SE37 or SE38.

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



Function FVD_INV_ACC_OBJ_GET_FLOWS 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_INV_ACC_OBJ_GET_FLOWS'"Read Flow Data of Contract from DB
  EXPORTING
   I_STR_VDARL =  "Darlehens Stammdaten
*  I_FLG_NO_STORNO = 'X' "No Reversed Flows
*  I_FLG_PLANNED_RECORDS = 'X' "Nur Plansätze zum Vertrag lesen
*  I_FLG_POSTED_RECORDS = 'X' "Plan- und Istsätze zum Vertrag lesen

 IMPORTING
   E_TAB_VDBEPP =  "Alle Plansätze eines Vertrags
   E_TAB_VZZBEPP =  "Alle Plan- und Istsätze eines Vertrags

EXCEPTIONS
   INPUT_NOT_FILLED = 1    NOT_FOUND = 2    FAILED = 3
.



IMPORTING Parameters details for FVD_INV_ACC_OBJ_GET_FLOWS

I_STR_VDARL - Darlehens Stammdaten

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

I_FLG_NO_STORNO - No Reversed Flows

Data type: FLAG
Default: 'X'
Optional: Yes
Call by Reference: Yes

I_FLG_PLANNED_RECORDS - Nur Plansätze zum Vertrag lesen

Data type: FLAG
Default: 'X'
Optional: Yes
Call by Reference: Yes

I_FLG_POSTED_RECORDS - Plan- und Istsätze zum Vertrag lesen

Data type: FLAG
Default: 'X'
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for FVD_INV_ACC_OBJ_GET_FLOWS

E_TAB_VDBEPP - Alle Plansätze eines Vertrags

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

E_TAB_VZZBEPP - Alle Plan- und Istsätze eines Vertrags

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

EXCEPTIONS details

INPUT_NOT_FILLED - Import Parameters Blank

Data type:
Optional: No
Call by Reference: Yes

NOT_FOUND - Keine Bewegungen zum Vertrag gefunden

Data type:
Optional: No
Call by Reference: Yes

FAILED - Lesen der Bewegungsdaten fehlgeschlagen

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FVD_INV_ACC_OBJ_GET_FLOWS 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_str_vdarl  TYPE VDARL, "   
lv_e_tab_vdbepp  TYPE TRTY_VDBEPP, "   
lv_input_not_filled  TYPE TRTY_VDBEPP, "   
lv_not_found  TYPE TRTY_VDBEPP, "   
lv_e_tab_vzzbepp  TYPE TRTY_VZZBEPP, "   
lv_i_flg_no_storno  TYPE FLAG, "   'X'
lv_failed  TYPE FLAG, "   
lv_i_flg_planned_records  TYPE FLAG, "   'X'
lv_i_flg_posted_records  TYPE FLAG. "   'X'

  CALL FUNCTION 'FVD_INV_ACC_OBJ_GET_FLOWS'  "Read Flow Data of Contract from DB
    EXPORTING
         I_STR_VDARL = lv_i_str_vdarl
         I_FLG_NO_STORNO = lv_i_flg_no_storno
         I_FLG_PLANNED_RECORDS = lv_i_flg_planned_records
         I_FLG_POSTED_RECORDS = lv_i_flg_posted_records
    IMPORTING
         E_TAB_VDBEPP = lv_e_tab_vdbepp
         E_TAB_VZZBEPP = lv_e_tab_vzzbepp
    EXCEPTIONS
        INPUT_NOT_FILLED = 1
        NOT_FOUND = 2
        FAILED = 3
. " FVD_INV_ACC_OBJ_GET_FLOWS




ABAP code using 7.40 inline data declarations to call FM FVD_INV_ACC_OBJ_GET_FLOWS

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_no_storno) = 'X'.
 
 
DATA(ld_i_flg_planned_records) = 'X'.
 
DATA(ld_i_flg_posted_records) = '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!