SAP Function Modules

FVD_ADDFLOW_OL_GET_FLOWS SAP Function module - Additional Flows: Get Flows







FVD_ADDFLOW_OL_GET_FLOWS is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name FVD_ADDFLOW_OL_GET_FLOWS into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: FVD_ADDFLOW_OL
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM FVD_ADDFLOW_OL_GET_FLOWS - FVD ADDFLOW OL GET FLOWS





CALL FUNCTION 'FVD_ADDFLOW_OL_GET_FLOWS' "Additional Flows: Get Flows
* EXPORTING
*   i_all_flows = CON_FALSE     " boolean       All flows
*   i_without_deleted = CON_TRUE  " boolean     Ohne gelöschte Bewegungen
*   i_without_init_lines = CON_TRUE  " boolean  Ohne initiale Bewegungen
*   i_no_checked_err = CON_TRUE  " boolean      Keine Bewegungen mit Fehlern
  IMPORTING
    e_tab_addflow =             " trty_rbobepp  Table Category for RBOBEPP (Standard)
    e_tab_bobepp =              " trty_vdbobepp  Table Type for Table VDBOBEPP
    .  "  FVD_ADDFLOW_OL_GET_FLOWS

ABAP code example for Function Module FVD_ADDFLOW_OL_GET_FLOWS





The ABAP code below is a full code listing to execute function module FVD_ADDFLOW_OL_GET_FLOWS including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_e_tab_addflow  TYPE TRTY_RBOBEPP ,
ld_e_tab_bobepp  TYPE TRTY_VDBOBEPP .

DATA(ld_i_all_flows) = 'Check type of data required'.
DATA(ld_i_without_deleted) = 'Check type of data required'.
DATA(ld_i_without_init_lines) = 'Check type of data required'.
DATA(ld_i_no_checked_err) = 'Check type of data required'. . CALL FUNCTION 'FVD_ADDFLOW_OL_GET_FLOWS' * EXPORTING * i_all_flows = ld_i_all_flows * i_without_deleted = ld_i_without_deleted * i_without_init_lines = ld_i_without_init_lines * i_no_checked_err = ld_i_no_checked_err IMPORTING e_tab_addflow = ld_e_tab_addflow e_tab_bobepp = ld_e_tab_bobepp . " FVD_ADDFLOW_OL_GET_FLOWS
IF SY-SUBRC EQ 0. "All OK ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:
ld_e_tab_addflow  TYPE TRTY_RBOBEPP ,
ld_i_all_flows  TYPE BOOLEAN ,
ld_e_tab_bobepp  TYPE TRTY_VDBOBEPP ,
ld_i_without_deleted  TYPE BOOLEAN ,
ld_i_without_init_lines  TYPE BOOLEAN ,
ld_i_no_checked_err  TYPE BOOLEAN .

ld_i_all_flows = 'Check type of data required'.
ld_i_without_deleted = 'Check type of data required'.
ld_i_without_init_lines = 'Check type of data required'.
ld_i_no_checked_err = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name FVD_ADDFLOW_OL_GET_FLOWS or its description.