SAP FTR_OTC_SET_DATA_TO_MEMORY Function Module for Transfer Option Data to Memory









FTR_OTC_SET_DATA_TO_MEMORY is a standard ftr otc set data to 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 Transfer Option Data to 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 set data to memory FM, simply by entering the name FTR_OTC_SET_DATA_TO_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_SET_DATA_TO_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_SET_DATA_TO_MEMORY'"Transfer Option Data to Memory
  EXPORTING
*  I_FLG_AUSUEB =  "'A' for Exercise, 'V' for Expiration
*  I_UL_RFHA =  "Transaction Number of UL when Physically Exercised
*  I_OREF_AVG_TABLE =  "Rate Management
*  I_OREF_AVG_TABLES =  "Class for Managing Several Schedules

TABLES
*  I_VTIOF =  "Additional Option Data
*  I_VTIFHA =  "Underlying Transaction
*  I_VTIFHAZU =  "Underlying Transaction Status Table
*  I_VTIFHAPO =  "Underlying Transaction Flows
*  I_VTIFINKO =  "Underlying Transaction Conditions
*  I_AVG_SCHEDULE =  "Table Type for ftr_avg_schedule
*  I_VTIOFZU =  "Assign Option/Future to Underlyings
.



IMPORTING Parameters details for FTR_OTC_SET_DATA_TO_MEMORY

I_FLG_AUSUEB - 'A' for Exercise, 'V' for Expiration

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

I_UL_RFHA - Transaction Number of UL when Physically Exercised

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

I_OREF_AVG_TABLE - Rate Management

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

I_OREF_AVG_TABLES - Class for Managing Several Schedules

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

TABLES Parameters details for FTR_OTC_SET_DATA_TO_MEMORY

I_VTIOF - Additional Option Data

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

I_VTIFHA - Underlying Transaction

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

I_VTIFHAZU - Underlying Transaction Status Table

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

I_VTIFHAPO - Underlying Transaction Flows

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

I_VTIFINKO - Underlying Transaction Conditions

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

I_AVG_SCHEDULE - Table Type for ftr_avg_schedule

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

I_VTIOFZU - Assign Option/Future to Underlyings

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

Copy and paste ABAP code example for FTR_OTC_SET_DATA_TO_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:
lt_i_vtiof  TYPE STANDARD TABLE OF VTIOF, "   
lv_i_flg_ausueb  TYPE CHAR01, "   
lt_i_vtifha  TYPE STANDARD TABLE OF VTIFHA, "   
lv_i_ul_rfha  TYPE TB_RFHA, "   
lt_i_vtifhazu  TYPE STANDARD TABLE OF VTIFHAZU, "   
lv_i_oref_avg_table  TYPE CL_FTR_AVG, "   
lt_i_vtifhapo  TYPE STANDARD TABLE OF VTIFHAPO, "   
lv_i_oref_avg_tables  TYPE CL_FTR_AVG_TABLES, "   
lt_i_vtifinko  TYPE STANDARD TABLE OF VTIFINKO, "   
lt_i_avg_schedule  TYPE STANDARD TABLE OF FTR_TAB_AVG_SCHEDULE, "   
lt_i_vtiofzu  TYPE STANDARD TABLE OF VTIOFZU. "   

  CALL FUNCTION 'FTR_OTC_SET_DATA_TO_MEMORY'  "Transfer Option Data to Memory
    EXPORTING
         I_FLG_AUSUEB = lv_i_flg_ausueb
         I_UL_RFHA = lv_i_ul_rfha
         I_OREF_AVG_TABLE = lv_i_oref_avg_table
         I_OREF_AVG_TABLES = lv_i_oref_avg_tables
    TABLES
         I_VTIOF = lt_i_vtiof
         I_VTIFHA = lt_i_vtifha
         I_VTIFHAZU = lt_i_vtifhazu
         I_VTIFHAPO = lt_i_vtifhapo
         I_VTIFINKO = lt_i_vtifinko
         I_AVG_SCHEDULE = lt_i_avg_schedule
         I_VTIOFZU = lt_i_vtiofzu
. " FTR_OTC_SET_DATA_TO_MEMORY




ABAP code using 7.40 inline data declarations to call FM FTR_OTC_SET_DATA_TO_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!