SAP FTR_OTC_GET_DATA_FROM_MEMORY Function Module for Get Option Data from Memory









FTR_OTC_GET_DATA_FROM_MEMORY is a standard ftr otc get data from memory SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get Option Data from Memory 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 ftr otc get data from memory FM, simply by entering the name FTR_OTC_GET_DATA_FROM_MEMORY into the relevant SAP transaction such as SE37 or SE38.

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



Function FTR_OTC_GET_DATA_FROM_MEMORY 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 'FTR_OTC_GET_DATA_FROM_MEMORY'"Get Option Data from Memory
  EXPORTING
   I_TRANSACTION_OTC =  "Financial Transaction

 IMPORTING
   E_FLG_AUSUEB =  "A = Exercise, V = Expiration
   E_UL_RFHA =  "Financial Transaction UL - Phys. Exer.
   E_OREF_AVG_TABLE =  "Rate Management
   E_OREF_AVG_TABLES =  "Class for Managing Several Schedules

TABLES
*  E_TAB_UL_FHA =  "Underlying Transaction
*  E_TAB_UL_FHAZU =  "Underlying Transaction Status Table
*  E_TAB_UL_FHAPO =  "Underlying Transaction Flows
*  E_TAB_UL_FINKO =  "Underlying Transaction Conditions
*  E_TAB_VTIOF =  "Additional Option Data
*  E_AVG_SCHEDULE =  "Table Type for ftr_avg_schedule
*  E_TAB_VTIOFZU =  "Allocation of Option/Future to Underlying

EXCEPTIONS
   UNDERLYING_NOT_FOUND = 1
.



IMPORTING Parameters details for FTR_OTC_GET_DATA_FROM_MEMORY

I_TRANSACTION_OTC - Financial Transaction

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

EXPORTING Parameters details for FTR_OTC_GET_DATA_FROM_MEMORY

E_FLG_AUSUEB - A = Exercise, V = Expiration

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

E_UL_RFHA - Financial Transaction UL - Phys. Exer.

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

E_OREF_AVG_TABLE - Rate Management

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

E_OREF_AVG_TABLES - Class for Managing Several Schedules

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

TABLES Parameters details for FTR_OTC_GET_DATA_FROM_MEMORY

E_TAB_UL_FHA - Underlying Transaction

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

E_TAB_UL_FHAZU - Underlying Transaction Status Table

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

E_TAB_UL_FHAPO - Underlying Transaction Flows

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

E_TAB_UL_FINKO - Underlying Transaction Conditions

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

E_TAB_VTIOF - Additional Option Data

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

E_AVG_SCHEDULE - Table Type for ftr_avg_schedule

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

E_TAB_VTIOFZU - Allocation of Option/Future to Underlying

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

EXCEPTIONS details

UNDERLYING_NOT_FOUND - The underlying was not found

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FTR_OTC_GET_DATA_FROM_MEMORY 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_flg_ausueb  TYPE CHAR1, "   
lt_e_tab_ul_fha  TYPE STANDARD TABLE OF VTIFHA, "   
lv_i_transaction_otc  TYPE VTBFHA, "   
lv_underlying_not_found  TYPE VTBFHA, "   
lv_e_ul_rfha  TYPE TB_RFHA, "   
lt_e_tab_ul_fhazu  TYPE STANDARD TABLE OF VTIFHAZU, "   
lt_e_tab_ul_fhapo  TYPE STANDARD TABLE OF VTIFHAPO, "   
lv_e_oref_avg_table  TYPE CL_FTR_AVG, "   
lt_e_tab_ul_finko  TYPE STANDARD TABLE OF VTIFINKO, "   
lv_e_oref_avg_tables  TYPE CL_FTR_AVG_TABLES, "   
lt_e_tab_vtiof  TYPE STANDARD TABLE OF VTIOF, "   
lt_e_avg_schedule  TYPE STANDARD TABLE OF FTR_TAB_AVG_SCHEDULE, "   
lt_e_tab_vtiofzu  TYPE STANDARD TABLE OF VTIOFZU. "   

  CALL FUNCTION 'FTR_OTC_GET_DATA_FROM_MEMORY'  "Get Option Data from Memory
    EXPORTING
         I_TRANSACTION_OTC = lv_i_transaction_otc
    IMPORTING
         E_FLG_AUSUEB = lv_e_flg_ausueb
         E_UL_RFHA = lv_e_ul_rfha
         E_OREF_AVG_TABLE = lv_e_oref_avg_table
         E_OREF_AVG_TABLES = lv_e_oref_avg_tables
    TABLES
         E_TAB_UL_FHA = lt_e_tab_ul_fha
         E_TAB_UL_FHAZU = lt_e_tab_ul_fhazu
         E_TAB_UL_FHAPO = lt_e_tab_ul_fhapo
         E_TAB_UL_FINKO = lt_e_tab_ul_finko
         E_TAB_VTIOF = lt_e_tab_vtiof
         E_AVG_SCHEDULE = lt_e_avg_schedule
         E_TAB_VTIOFZU = lt_e_tab_vtiofzu
    EXCEPTIONS
        UNDERLYING_NOT_FOUND = 1
. " FTR_OTC_GET_DATA_FROM_MEMORY




ABAP code using 7.40 inline data declarations to call FM FTR_OTC_GET_DATA_FROM_MEMORY

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!