SAP THMHR_DOCU_EXECUTE Function Module for Execute Documentation for Hedging Relationship
THMHR_DOCU_EXECUTE is a standard thmhr docu execute SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Execute Documentation for Hedging Relationship 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 thmhr docu execute FM, simply by entering the name THMHR_DOCU_EXECUTE into the relevant SAP transaction such as SE37 or SE38.
Function Group: THMHR_DOCU
Program Name: SAPLTHMHR_DOCU
Main Program: SAPLTHMHR_DOCU
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function THMHR_DOCU_EXECUTE 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 'THMHR_DOCU_EXECUTE'"Execute Documentation for Hedging Relationship.
EXPORTING
* IM_VERSION = "
* IM_TAB_EXP_TRAN_DCSP = "Table Type to Exposure Transaction DCS based Prices
IM_TAB_HEDGE_RELATION = "TTYP: TR-LDB Hedge: Hedging Relationship
IM_TAB_HEDGE_PLAN = "TTYP: Hedge Plan Header Information
IM_TAB_EXPOSURE = "TTYP: TR-LDB Hedge: Exposure
IM_TAB_EXP_TRANS = "TTYP: TR-LDB Hedge: Exposure Transaction
IM_TAB_EXP_HEDGE_REL = "TTYP: TR-LDB Hedge: Exposure - Hedge Relationship
IM_TAB_HEDGE_ITEM = "TTYP: TR-LDB Hedge: Hedged Item
* IM_PROTOCOL = "Treasury: Worklist Positions for the TRL Valuation
* IM_TAB_EXP_TRANS_COP = "Table Type to Exposure Transaktion Prices
EXCEPTIONS
HREL_NOT_FOUND = 1
IMPORTING Parameters details for THMHR_DOCU_EXECUTE
IM_VERSION -
Data type: COptional: Yes
Call by Reference: Yes
IM_TAB_EXP_TRAN_DCSP - Table Type to Exposure Transaction DCS based Prices
Data type: FTI_LDB_TR_HM_EXP_TRAN_DCSP_TOptional: Yes
Call by Reference: Yes
IM_TAB_HEDGE_RELATION - TTYP: TR-LDB Hedge: Hedging Relationship
Data type: FTI_LDB_TR_HM_HEDGE_REL_TOptional: No
Call by Reference: Yes
IM_TAB_HEDGE_PLAN - TTYP: Hedge Plan Header Information
Data type: FTI_LDB_TR_HM_HEGDEPLAN_TOptional: No
Call by Reference: Yes
IM_TAB_EXPOSURE - TTYP: TR-LDB Hedge: Exposure
Data type: FTI_LDB_TR_HM_EXPOSURE_TOptional: No
Call by Reference: Yes
IM_TAB_EXP_TRANS - TTYP: TR-LDB Hedge: Exposure Transaction
Data type: FTI_LDB_TR_HM_EXP_TRANS_TOptional: No
Call by Reference: Yes
IM_TAB_EXP_HEDGE_REL - TTYP: TR-LDB Hedge: Exposure - Hedge Relationship
Data type: FTI_LDB_TR_HM_EXP_HDG_REL_TOptional: No
Call by Reference: Yes
IM_TAB_HEDGE_ITEM - TTYP: TR-LDB Hedge: Hedged Item
Data type: FTI_LDB_TR_HM_HEDGE_ID_TOptional: No
Call by Reference: Yes
IM_PROTOCOL - Treasury: Worklist Positions for the TRL Valuation
Data type: CL_PROTOCOL_HANDLER_TRPOptional: Yes
Call by Reference: Yes
IM_TAB_EXP_TRANS_COP - Table Type to Exposure Transaktion Prices
Data type: FTI_LDB_TR_HM_EXP_TRANS_COP_TOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
HREL_NOT_FOUND - No Hedge Relation exist
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for THMHR_DOCU_EXECUTE 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_im_version | TYPE C, " | |||
| lv_hrel_not_found | TYPE C, " | |||
| lv_im_tab_exp_tran_dcsp | TYPE FTI_LDB_TR_HM_EXP_TRAN_DCSP_T, " | |||
| lv_im_tab_hedge_relation | TYPE FTI_LDB_TR_HM_HEDGE_REL_T, " | |||
| lv_im_tab_hedge_plan | TYPE FTI_LDB_TR_HM_HEGDEPLAN_T, " | |||
| lv_im_tab_exposure | TYPE FTI_LDB_TR_HM_EXPOSURE_T, " | |||
| lv_im_tab_exp_trans | TYPE FTI_LDB_TR_HM_EXP_TRANS_T, " | |||
| lv_im_tab_exp_hedge_rel | TYPE FTI_LDB_TR_HM_EXP_HDG_REL_T, " | |||
| lv_im_tab_hedge_item | TYPE FTI_LDB_TR_HM_HEDGE_ID_T, " | |||
| lv_im_protocol | TYPE CL_PROTOCOL_HANDLER_TRP, " | |||
| lv_im_tab_exp_trans_cop | TYPE FTI_LDB_TR_HM_EXP_TRANS_COP_T. " |
|   CALL FUNCTION 'THMHR_DOCU_EXECUTE' "Execute Documentation for Hedging Relationship |
| EXPORTING | ||
| IM_VERSION | = lv_im_version | |
| IM_TAB_EXP_TRAN_DCSP | = lv_im_tab_exp_tran_dcsp | |
| IM_TAB_HEDGE_RELATION | = lv_im_tab_hedge_relation | |
| IM_TAB_HEDGE_PLAN | = lv_im_tab_hedge_plan | |
| IM_TAB_EXPOSURE | = lv_im_tab_exposure | |
| IM_TAB_EXP_TRANS | = lv_im_tab_exp_trans | |
| IM_TAB_EXP_HEDGE_REL | = lv_im_tab_exp_hedge_rel | |
| IM_TAB_HEDGE_ITEM | = lv_im_tab_hedge_item | |
| IM_PROTOCOL | = lv_im_protocol | |
| IM_TAB_EXP_TRANS_COP | = lv_im_tab_exp_trans_cop | |
| EXCEPTIONS | ||
| HREL_NOT_FOUND = 1 | ||
| . " THMHR_DOCU_EXECUTE | ||
ABAP code using 7.40 inline data declarations to call FM THMHR_DOCU_EXECUTE
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