SAP FVER_READ_FLOW Function Module for Read Flows for a Right









FVER_READ_FLOW is a standard fver read flow 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 Flows for a Right 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 fver read flow FM, simply by entering the name FVER_READ_FLOW into the relevant SAP transaction such as SE37 or SE38.

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



Function FVER_READ_FLOW 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 'FVER_READ_FLOW'"Read Flows for a Right
  EXPORTING
   I_STR_MARKET_DATA =  "Current Market Data
*  I_TAB_REVAL_ER =  "Positions
*  I_TAB_QUANTITY =  "Table of Positions for Executable Rights
   I_REFERENCENUMBER =  "identifiziert die Rechtemenge
*  I_EXERCISETYPE =  "Exercise Type
*  I_SETTLEMENT =  "Clearing
*  I_STARTDATE =  "Period from
*  I_ENDDATE =  "Term To
   I_RANLUNDERLYING =  "ID number of underlying for executable right

 IMPORTING
   E_TAB_VWBWER =  "Tabelle der Bewegungen(vor 46C)
   E_TAB_FLOW =  "Tabelle der Bewegungen(ab CFM1.0)
   E_TAB_MESG =  "Messages Table

EXCEPTIONS
   RIGHTS_NOT_FOUND = 1    FLOW_GENERATION_ERROR = 2
.



IMPORTING Parameters details for FVER_READ_FLOW

I_STR_MARKET_DATA - Current Market Data

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

I_TAB_REVAL_ER - Positions

Data type: TERYREVAL
Optional: Yes
Call by Reference: Yes

I_TAB_QUANTITY - Table of Positions for Executable Rights

Data type: TERY_QUANTITY
Optional: Yes
Call by Reference: Yes

I_REFERENCENUMBER - identifiziert die Rechtemenge

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

I_EXERCISETYPE - Exercise Type

Data type: SOPTTYP
Optional: Yes
Call by Reference: Yes

I_SETTLEMENT - Clearing

Data type: SVERROPT
Optional: Yes
Call by Reference: Yes

I_STARTDATE - Period from

Data type: DLAVO
Optional: Yes
Call by Reference: Yes

I_ENDDATE - Term To

Data type: DLABI
Optional: Yes
Call by Reference: Yes

I_RANLUNDERLYING - ID number of underlying for executable right

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

EXPORTING Parameters details for FVER_READ_FLOW

E_TAB_VWBWER - Tabelle der Bewegungen(vor 46C)

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

E_TAB_FLOW - Tabelle der Bewegungen(ab CFM1.0)

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

E_TAB_MESG - Messages Table

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

EXCEPTIONS details

RIGHTS_NOT_FOUND - keine Rechte vorhanden

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

FLOW_GENERATION_ERROR - Fehler bei den Bewegungen entstanden

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

Copy and paste ABAP code example for FVER_READ_FLOW 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_e_tab_vwbwer  TYPE TERYVWBWER, "   
lv_rights_not_found  TYPE TERYVWBWER, "   
lv_i_str_market_data  TYPE TERSMARKET_DATA, "   
lv_e_tab_flow  TYPE TERY_FLOW, "   
lv_i_tab_reval_er  TYPE TERYREVAL, "   
lv_flow_generation_error  TYPE TERYREVAL, "   
lv_e_tab_mesg  TYPE TERYMESG, "   
lv_i_tab_quantity  TYPE TERY_QUANTITY, "   
lv_i_referencenumber  TYPE TER_REFERENCENUMBER, "   
lv_i_exercisetype  TYPE SOPTTYP, "   
lv_i_settlement  TYPE SVERROPT, "   
lv_i_startdate  TYPE DLAVO, "   
lv_i_enddate  TYPE DLABI, "   
lv_i_ranlunderlying  TYPE TER_RANLUNDER. "   

  CALL FUNCTION 'FVER_READ_FLOW'  "Read Flows for a Right
    EXPORTING
         I_STR_MARKET_DATA = lv_i_str_market_data
         I_TAB_REVAL_ER = lv_i_tab_reval_er
         I_TAB_QUANTITY = lv_i_tab_quantity
         I_REFERENCENUMBER = lv_i_referencenumber
         I_EXERCISETYPE = lv_i_exercisetype
         I_SETTLEMENT = lv_i_settlement
         I_STARTDATE = lv_i_startdate
         I_ENDDATE = lv_i_enddate
         I_RANLUNDERLYING = lv_i_ranlunderlying
    IMPORTING
         E_TAB_VWBWER = lv_e_tab_vwbwer
         E_TAB_FLOW = lv_e_tab_flow
         E_TAB_MESG = lv_e_tab_mesg
    EXCEPTIONS
        RIGHTS_NOT_FOUND = 1
        FLOW_GENERATION_ERROR = 2
. " FVER_READ_FLOW




ABAP code using 7.40 inline data declarations to call FM FVER_READ_FLOW

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!