SAP OTC_TRANSACTION_READ_FROM_DB Function Module for OPEN_TRTM: Read OTC Option









OTC_TRANSACTION_READ_FROM_DB is a standard otc transaction read from db SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for OPEN_TRTM: Read OTC Option 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 otc transaction read from db FM, simply by entering the name OTC_TRANSACTION_READ_FROM_DB into the relevant SAP transaction such as SE37 or SE38.

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



Function OTC_TRANSACTION_READ_FROM_DB 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 'OTC_TRANSACTION_READ_FROM_DB'"OPEN_TRTM: Read OTC Option
  EXPORTING
   PI_BUKRS =  "Company Code
   PI_RFHA =  "Financial Transaction

 IMPORTING
   PE_FHA =  "Financial Transaction
   PE_FHAZU =  "Transaction Activity
   PE_TAB_FHAPO =  "Transaction Flows
   PE_TAB_UL_TRANSACTION =  "Financial Transaction Data Underlying
   PE_TAB_UL_ACTIVITY =  "Activity for Transaction Underlying
   PE_TAB_UL_CASHFLOW =  "Transaction Flows Underlying
   PE_TAB_UL_CONDITIONS =  "Conditions of Transaction Underlying
   PE_TAB_ADD_OPTION_DATA =  "Additional Option Data

EXCEPTIONS
   TRANSACTION_NOT_FOUND = 1    PRODUCTCATEGORY = 2
.



IMPORTING Parameters details for OTC_TRANSACTION_READ_FROM_DB

PI_BUKRS - Company Code

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

PI_RFHA - Financial Transaction

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

EXPORTING Parameters details for OTC_TRANSACTION_READ_FROM_DB

PE_FHA - Financial Transaction

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

PE_FHAZU - Transaction Activity

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

PE_TAB_FHAPO - Transaction Flows

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

PE_TAB_UL_TRANSACTION - Financial Transaction Data Underlying

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

PE_TAB_UL_ACTIVITY - Activity for Transaction Underlying

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

PE_TAB_UL_CASHFLOW - Transaction Flows Underlying

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

PE_TAB_UL_CONDITIONS - Conditions of Transaction Underlying

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

PE_TAB_ADD_OPTION_DATA - Additional Option Data

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

EXCEPTIONS details

TRANSACTION_NOT_FOUND - Geschäft nicht vorhanden

Data type:
Optional: No
Call by Reference: Yes

PRODUCTCATEGORY - keine OTC-Option

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for OTC_TRANSACTION_READ_FROM_DB 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_pe_fha  TYPE VTBFHA, "   
lv_pi_bukrs  TYPE BUKRS, "   
lv_transaction_not_found  TYPE BUKRS, "   
lv_pi_rfha  TYPE TB_RFHA, "   
lv_pe_fhazu  TYPE VTBFHAZU, "   
lv_productcategory  TYPE VTBFHAZU, "   
lv_pe_tab_fhapo  TYPE FTRTR_TAB_FHAPO, "   
lv_pe_tab_ul_transaction  TYPE FTRTR_TAB_VTIFHA, "   
lv_pe_tab_ul_activity  TYPE FTRTR_TAB_VTIFHAZU, "   
lv_pe_tab_ul_cashflow  TYPE FTRTR_TAB_VTIFHAPO, "   
lv_pe_tab_ul_conditions  TYPE FTRTR_TAB_VTIFINKO, "   
lv_pe_tab_add_option_data  TYPE FTRTR_TAB_VTIOF. "   

  CALL FUNCTION 'OTC_TRANSACTION_READ_FROM_DB'  "OPEN_TRTM: Read OTC Option
    EXPORTING
         PI_BUKRS = lv_pi_bukrs
         PI_RFHA = lv_pi_rfha
    IMPORTING
         PE_FHA = lv_pe_fha
         PE_FHAZU = lv_pe_fhazu
         PE_TAB_FHAPO = lv_pe_tab_fhapo
         PE_TAB_UL_TRANSACTION = lv_pe_tab_ul_transaction
         PE_TAB_UL_ACTIVITY = lv_pe_tab_ul_activity
         PE_TAB_UL_CASHFLOW = lv_pe_tab_ul_cashflow
         PE_TAB_UL_CONDITIONS = lv_pe_tab_ul_conditions
         PE_TAB_ADD_OPTION_DATA = lv_pe_tab_add_option_data
    EXCEPTIONS
        TRANSACTION_NOT_FOUND = 1
        PRODUCTCATEGORY = 2
. " OTC_TRANSACTION_READ_FROM_DB




ABAP code using 7.40 inline data declarations to call FM OTC_TRANSACTION_READ_FROM_DB

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!