SAP THMEX_GET_PLANNER Function Module for Hedge Management: Get All Exposures Assigned to Hedge









THMEX_GET_PLANNER is a standard thmex get planner 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: Get All Exposures Assigned to Hedge 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 thmex get planner FM, simply by entering the name THMEX_GET_PLANNER into the relevant SAP transaction such as SE37 or SE38.

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



Function THMEX_GET_PLANNER 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 'THMEX_GET_PLANNER'"Hedge Management: Get All Exposures Assigned to Hedge
EXPORTING
I_COMPANYCODE = "Company code
I_PLANNERID = "Hedge Management: Hedge Planner ID
* I_P_PERSISTENCY_MANAGER = "Treasury Position Management: Persistence Service

IMPORTING
E_PLANNER = "Hedge Management: Hedge Planner

EXCEPTIONS
NO_ENTRY_SELECTED = 1
.



IMPORTING Parameters details for THMEX_GET_PLANNER

I_COMPANYCODE - Company code

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

I_PLANNERID - Hedge Management: Hedge Planner ID

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

I_P_PERSISTENCY_MANAGER - Treasury Position Management: Persistence Service

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

EXPORTING Parameters details for THMEX_GET_PLANNER

E_PLANNER - Hedge Management: Hedge Planner

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

EXCEPTIONS details

NO_ENTRY_SELECTED - No Entry Selected

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for THMEX_GET_PLANNER 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_e_planner  TYPE THMEXT_PLANNER, "   
lv_i_companycode  TYPE BUKRS, "   
lv_no_entry_selected  TYPE BUKRS, "   
lv_i_plannerid  TYPE THM_PLANNERID, "   
lv_i_p_persistency_manager  TYPE CL_PERSISTENCY_MANAGER_TRG. "   

  CALL FUNCTION 'THMEX_GET_PLANNER'  "Hedge Management: Get All Exposures Assigned to Hedge
    EXPORTING
         I_COMPANYCODE = lv_i_companycode
         I_PLANNERID = lv_i_plannerid
         I_P_PERSISTENCY_MANAGER = lv_i_p_persistency_manager
    IMPORTING
         E_PLANNER = lv_e_planner
    EXCEPTIONS
        NO_ENTRY_SELECTED = 1
. " THMEX_GET_PLANNER




ABAP code using 7.40 inline data declarations to call FM THMEX_GET_PLANNER

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!