SAP THMEX_CHECK_PLANNER Function Module for Hegde Management: Check Hedge Plan Fields
THMEX_CHECK_PLANNER is a standard thmex check 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 Hegde Management: Check Hedge Plan Fields 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 check planner FM, simply by entering the name THMEX_CHECK_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_CHECK_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_CHECK_PLANNER'"Hegde Management: Check Hedge Plan Fields.
EXPORTING
I_PLANNER = "Hedge Management: Hedge Planner
* I_CHECK_MODE = TPMCO_CHAR_C "'C' = Create; 'E' = Edit; 'X' = Delete
* I_MESSAGE_TYPE = TPMCO_CHAR_E "Messages, message type
* I_P_PERSISTENCY_MANAGER = "Persistence Manager
* I_BAPI = ' ' "Aufruf erfolgt durch BAPI-Funktionsbaustein
EXCEPTIONS
PLANNER_CHECK_FAILED = 1
IMPORTING Parameters details for THMEX_CHECK_PLANNER
I_PLANNER - Hedge Management: Hedge Planner
Data type: THMEXT_PLANNEROptional: No
Call by Reference: Yes
I_CHECK_MODE - 'C' = Create; 'E' = Edit; 'X' = Delete
Data type: CDefault: TPMCO_CHAR_C
Optional: Yes
Call by Reference: Yes
I_MESSAGE_TYPE - Messages, message type
Data type: SYMSGTYDefault: TPMCO_CHAR_E
Optional: Yes
Call by Reference: Yes
I_P_PERSISTENCY_MANAGER - Persistence Manager
Data type: CL_PERSISTENCY_MANAGER_TRGOptional: Yes
Call by Reference: Yes
I_BAPI - Aufruf erfolgt durch BAPI-Funktionsbaustein
Data type: XFELDDefault: SPACE
Optional: Yes
Call by Reference: Yes
EXCEPTIONS details
PLANNER_CHECK_FAILED - There is an error in the planner structure see message
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for THMEX_CHECK_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_i_planner | TYPE THMEXT_PLANNER, " | |||
| lv_planner_check_failed | TYPE THMEXT_PLANNER, " | |||
| lv_i_check_mode | TYPE C, " TPMCO_CHAR_C | |||
| lv_i_message_type | TYPE SYMSGTY, " TPMCO_CHAR_E | |||
| lv_i_p_persistency_manager | TYPE CL_PERSISTENCY_MANAGER_TRG, " | |||
| lv_i_bapi | TYPE XFELD. " SPACE |
|   CALL FUNCTION 'THMEX_CHECK_PLANNER' "Hegde Management: Check Hedge Plan Fields |
| EXPORTING | ||
| I_PLANNER | = lv_i_planner | |
| I_CHECK_MODE | = lv_i_check_mode | |
| I_MESSAGE_TYPE | = lv_i_message_type | |
| I_P_PERSISTENCY_MANAGER | = lv_i_p_persistency_manager | |
| I_BAPI | = lv_i_bapi | |
| EXCEPTIONS | ||
| PLANNER_CHECK_FAILED = 1 | ||
| . " THMEX_CHECK_PLANNER | ||
ABAP code using 7.40 inline data declarations to call FM THMEX_CHECK_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.| DATA(ld_i_check_mode) | = TPMCO_CHAR_C. | |||
| DATA(ld_i_message_type) | = TPMCO_CHAR_E. | |||
| DATA(ld_i_bapi) | = ' '. | |||
Search for further information about these or an SAP related objects