SAP FTI_LDB_GET_HM_DATA_GENERAL Function Module for Hedge Management - Generic Data Access









FTI_LDB_GET_HM_DATA_GENERAL is a standard fti ldb get hm data general SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Hedge Management - Generic Data Access 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 fti ldb get hm data general FM, simply by entering the name FTI_LDB_GET_HM_DATA_GENERAL into the relevant SAP transaction such as SE37 or SE38.

Function Group: FTI_LDB_RAPI
Program Name: SAPLFTI_LDB_RAPI
Main Program: SAPLFTI_LDB_RAPI
Appliation area:
Release date: 13-Mar-2007
Mode(Normal, Remote etc): Normal Function Module
Update:



Function FTI_LDB_GET_HM_DATA_GENERAL 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 'FTI_LDB_GET_HM_DATA_GENERAL'"Hedge Management - Generic Data Access
  EXPORTING
*  I_BUKRS =  "Company Code
*  I_HDGPLNID =  "Hedge Plan ID
*  I_EXPID =  "Exposure ID
*  I_VLAREA =  "Valuation Area
*  I_RFHA =  "Hedging Instrument
*  I_HDGID =  "Identification Number of Hedge Item
*  I_RSKCAT =  "Risk Category
*  I_FLG_VERS = 'X' "Indicate Last Version

 IMPORTING
   E_TAB_HEDGEPLAN =  "Hedge Plan Header Information
   E_TAB_NSH_HEDGE_ID =  "Non-Single Hedge: Hedged Item
   E_TAB_NSH_HEDGE_REL =  "Non-Single Hedge: Hedging Relationship
   E_TAB_NSH_EFF_VAL =  "Non-Single Hedge: Effectiveness Results
   E_TAB_ERRORS =  "Table Type for Error Handling
   E_TAB_EXPOSURE =  "Exposure
   E_TAB_EXP_TRANS =  "Exposure Transaction
   E_TAB_HEDGE_ID =  "Hedged Item
   E_TAB_HEDGE_RELATION =  "Hedging Relationship
   E_TAB_EXP_HEDGE_REL =  "Relationship: Exposure - Hedged Item
   E_TAB_EFF_VAL =  "Effectiveness Results
   E_TAB_NSH_EXP =  "Non-Single Hedge: Exposure
   E_TAB_NSH_EXP_TRANS =  "Non-Single Hedge: Exposure Transaction
.



IMPORTING Parameters details for FTI_LDB_GET_HM_DATA_GENERAL

I_BUKRS - Company Code

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

I_HDGPLNID - Hedge Plan ID

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

I_EXPID - Exposure ID

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

I_VLAREA - Valuation Area

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

I_RFHA - Hedging Instrument

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

I_HDGID - Identification Number of Hedge Item

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

I_RSKCAT - Risk Category

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

I_FLG_VERS - Indicate Last Version

Data type: C
Default: 'X'
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for FTI_LDB_GET_HM_DATA_GENERAL

E_TAB_HEDGEPLAN - Hedge Plan Header Information

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

E_TAB_NSH_HEDGE_ID - Non-Single Hedge: Hedged Item

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

E_TAB_NSH_HEDGE_REL - Non-Single Hedge: Hedging Relationship

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

E_TAB_NSH_EFF_VAL - Non-Single Hedge: Effectiveness Results

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

E_TAB_ERRORS - Table Type for Error Handling

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

E_TAB_EXPOSURE - Exposure

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

E_TAB_EXP_TRANS - Exposure Transaction

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

E_TAB_HEDGE_ID - Hedged Item

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

E_TAB_HEDGE_RELATION - Hedging Relationship

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

E_TAB_EXP_HEDGE_REL - Relationship: Exposure - Hedged Item

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

E_TAB_EFF_VAL - Effectiveness Results

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

E_TAB_NSH_EXP - Non-Single Hedge: Exposure

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

E_TAB_NSH_EXP_TRANS - Non-Single Hedge: Exposure Transaction

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

Copy and paste ABAP code example for FTI_LDB_GET_HM_DATA_GENERAL 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_i_bukrs  TYPE TRGR_COMPANY_CODE, "   
lv_e_tab_hedgeplan  TYPE FTI_LDB_TR_HM_HEGDEPLAN_T, "   
lv_e_tab_nsh_hedge_id  TYPE FTI_LDB_TR_HM_NSH_HEDGE_ID_T, "   
lv_e_tab_nsh_hedge_rel  TYPE FTI_LDB_TR_HM_NSH_HEDGE_REL_T, "   
lv_e_tab_nsh_eff_val  TYPE FTI_LDB_TR_HM_NSH_EFF_VAL_T, "   
lv_e_tab_errors  TYPE BAPIERR_T, "   
lv_i_hdgplnid  TYPE THAR_PLANNERID, "   
lv_e_tab_exposure  TYPE FTI_LDB_TR_HM_EXPOSURE_T, "   
lv_i_expid  TYPE THAR_EXPOSUREID, "   
lv_e_tab_exp_trans  TYPE FTI_LDB_TR_HM_EXP_TRANS_T, "   
lv_i_vlarea  TYPE TRGR_VALUATION_AREA, "   
lv_e_tab_hedge_id  TYPE FTI_LDB_TR_HM_HEDGE_ID_T, "   
lv_i_rfha  TYPE TRGR_DEAL_NUMBER, "   
lv_e_tab_hedge_relation  TYPE FTI_LDB_TR_HM_HEDGE_REL_T, "   
lv_i_hdgid  TYPE THAR_HEDGE_ID, "   
lv_e_tab_exp_hedge_rel  TYPE FTI_LDB_TR_HM_EXP_HDG_REL_T, "   
lv_i_rskcat  TYPE THAR_RISKCAT, "   
lv_e_tab_eff_val  TYPE FTI_LDB_TR_HM_EFF_VAL_T, "   
lv_i_flg_vers  TYPE C, "   'X'
lv_e_tab_nsh_exp  TYPE FTI_LDB_TR_HM_NSH_EXP_T, "   
lv_e_tab_nsh_exp_trans  TYPE FTI_LDB_TR_HM_NSH_EXP_TR_T. "   

  CALL FUNCTION 'FTI_LDB_GET_HM_DATA_GENERAL'  "Hedge Management - Generic Data Access
    EXPORTING
         I_BUKRS = lv_i_bukrs
         I_HDGPLNID = lv_i_hdgplnid
         I_EXPID = lv_i_expid
         I_VLAREA = lv_i_vlarea
         I_RFHA = lv_i_rfha
         I_HDGID = lv_i_hdgid
         I_RSKCAT = lv_i_rskcat
         I_FLG_VERS = lv_i_flg_vers
    IMPORTING
         E_TAB_HEDGEPLAN = lv_e_tab_hedgeplan
         E_TAB_NSH_HEDGE_ID = lv_e_tab_nsh_hedge_id
         E_TAB_NSH_HEDGE_REL = lv_e_tab_nsh_hedge_rel
         E_TAB_NSH_EFF_VAL = lv_e_tab_nsh_eff_val
         E_TAB_ERRORS = lv_e_tab_errors
         E_TAB_EXPOSURE = lv_e_tab_exposure
         E_TAB_EXP_TRANS = lv_e_tab_exp_trans
         E_TAB_HEDGE_ID = lv_e_tab_hedge_id
         E_TAB_HEDGE_RELATION = lv_e_tab_hedge_relation
         E_TAB_EXP_HEDGE_REL = lv_e_tab_exp_hedge_rel
         E_TAB_EFF_VAL = lv_e_tab_eff_val
         E_TAB_NSH_EXP = lv_e_tab_nsh_exp
         E_TAB_NSH_EXP_TRANS = lv_e_tab_nsh_exp_trans
. " FTI_LDB_GET_HM_DATA_GENERAL




ABAP code using 7.40 inline data declarations to call FM FTI_LDB_GET_HM_DATA_GENERAL

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.

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
DATA(ld_i_flg_vers) = 'X'.
 
 
 


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!