SAP FTR_TRES_DEALDATA_READ Function Module for read TRES data from database









FTR_TRES_DEALDATA_READ is a standard ftr tres dealdata read 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 TRES data from database 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 tres dealdata read FM, simply by entering the name FTR_TRES_DEALDATA_READ into the relevant SAP transaction such as SE37 or SE38.

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



Function FTR_TRES_DEALDATA_READ 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_TRES_DEALDATA_READ'"read TRES data from database
  EXPORTING
   IV_COMPANYCODE =  "Company Code
   IV_DEALNUMBER =  "Financial Transaction
*  IV_ACTIVITYNUMBER =  "Transaction activity

 IMPORTING
   ES_DEAL =  "Transaction
   ES_ACTIVITY =  "Activity
   ES_ACTIVITY_PRECEDING =  "Preceding Activity
   ET_FLOWS =  "Flows
   ET_FLOWS_PRECEDING =  "Flows of Preceding Activity
   ET_CONDITIONS =  "Conditions
   ET_CONDITIONS_PRECEDING =  "Conditions of Preceding Activity
   ET_DIVIDEND =  "Dividend Data

EXCEPTIONS
   DEAL_NOT_FOUND = 1    ACTIVITY_NOT_FOUND = 2
.



IMPORTING Parameters details for FTR_TRES_DEALDATA_READ

IV_COMPANYCODE - Company Code

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

IV_DEALNUMBER - Financial Transaction

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

IV_ACTIVITYNUMBER - Transaction activity

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

EXPORTING Parameters details for FTR_TRES_DEALDATA_READ

ES_DEAL - Transaction

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

ES_ACTIVITY - Activity

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

ES_ACTIVITY_PRECEDING - Preceding Activity

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

ET_FLOWS - Flows

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

ET_FLOWS_PRECEDING - Flows of Preceding Activity

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

ET_CONDITIONS - Conditions

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

ET_CONDITIONS_PRECEDING - Conditions of Preceding Activity

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

ET_DIVIDEND - Dividend Data

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

EXCEPTIONS details

DEAL_NOT_FOUND - Deal does not exist

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

ACTIVITY_NOT_FOUND - Operation does not exist

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

Copy and paste ABAP code example for FTR_TRES_DEALDATA_READ 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_es_deal  TYPE TRDE_STR_FHA, "   
lv_deal_not_found  TYPE TRDE_STR_FHA, "   
lv_iv_companycode  TYPE BUKRS, "   
lv_es_activity  TYPE TRDE_STR_FHAZU, "   
lv_iv_dealnumber  TYPE TB_RFHA, "   
lv_activity_not_found  TYPE TB_RFHA, "   
lv_iv_activitynumber  TYPE TB_RFHAZU, "   
lv_es_activity_preceding  TYPE TRDE_STR_FHAZU, "   
lv_et_flows  TYPE TRDE_TAB_FHAPO, "   
lv_et_flows_preceding  TYPE TRDE_TAB_FHAPO, "   
lv_et_conditions  TYPE TRDE_TAB_FINKO, "   
lv_et_conditions_preceding  TYPE TRDE_TAB_FINKO, "   
lv_et_dividend  TYPE FTRY_VTBDIVIDEND. "   

  CALL FUNCTION 'FTR_TRES_DEALDATA_READ'  "read TRES data from database
    EXPORTING
         IV_COMPANYCODE = lv_iv_companycode
         IV_DEALNUMBER = lv_iv_dealnumber
         IV_ACTIVITYNUMBER = lv_iv_activitynumber
    IMPORTING
         ES_DEAL = lv_es_deal
         ES_ACTIVITY = lv_es_activity
         ES_ACTIVITY_PRECEDING = lv_es_activity_preceding
         ET_FLOWS = lv_et_flows
         ET_FLOWS_PRECEDING = lv_et_flows_preceding
         ET_CONDITIONS = lv_et_conditions
         ET_CONDITIONS_PRECEDING = lv_et_conditions_preceding
         ET_DIVIDEND = lv_et_dividend
    EXCEPTIONS
        DEAL_NOT_FOUND = 1
        ACTIVITY_NOT_FOUND = 2
. " FTR_TRES_DEALDATA_READ




ABAP code using 7.40 inline data declarations to call FM FTR_TRES_DEALDATA_READ

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!