SAP THMEX_UPDATE_PLAN_FOR_RO Function Module for Simulate Update Hedge Plan with RO Data









THMEX_UPDATE_PLAN_FOR_RO is a standard thmex update plan for ro SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Simulate Update Hedge Plan with RO Data 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 update plan for ro FM, simply by entering the name THMEX_UPDATE_PLAN_FOR_RO into the relevant SAP transaction such as SE37 or SE38.

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



Function THMEX_UPDATE_PLAN_FOR_RO 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_UPDATE_PLAN_FOR_RO'"Simulate Update Hedge Plan with RO Data
EXPORTING
IM_BUKRS = "Company Code
IM_P_PERSISTENCY_MANAGER = "Treasury Position Management: Persistence Service
IM_P_LOG_HANDLER = "

IMPORTING
RESULT = "Ausgabe des Aktualisierungsprozesses
EX_TAB_MESS = "Application Log: Table with Messages

CHANGING
CH_TABLE = "Plan über Risikoträger aktualisieren: Bild
* CH_FLG_TESTRUN = 'X' "

EXCEPTIONS
DB_ERROR = 1 INCONSISTENT_DATA = 2
.



IMPORTING Parameters details for THMEX_UPDATE_PLAN_FOR_RO

IM_BUKRS - Company Code

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

IM_P_PERSISTENCY_MANAGER - Treasury Position Management: Persistence Service

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

IM_P_LOG_HANDLER -

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

EXPORTING Parameters details for THMEX_UPDATE_PLAN_FOR_RO

RESULT - Ausgabe des Aktualisierungsprozesses

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

EX_TAB_MESS - Application Log: Table with Messages

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

CHANGING Parameters details for THMEX_UPDATE_PLAN_FOR_RO

CH_TABLE - Plan über Risikoträger aktualisieren: Bild

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

CH_FLG_TESTRUN -

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

EXCEPTIONS details

DB_ERROR - Database update error

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

INCONSISTENT_DATA - Inconsistent Data

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for THMEX_UPDATE_PLAN_FOR_RO 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_result  TYPE GE1_UPDATE, "   
lv_ch_table  TYPE THMEXS_THM_HM_SCREEN, "   
lv_db_error  TYPE THMEXS_THM_HM_SCREEN, "   
lv_im_bukrs  TYPE BUKRS, "   
lv_ex_tab_mess  TYPE BAL_T_MSG, "   
lv_ch_flg_testrun  TYPE TPM_TESTRUN, "   'X'
lv_inconsistent_data  TYPE TPM_TESTRUN, "   
lv_im_p_persistency_manager  TYPE CL_PERSISTENCY_MANAGER_TRG, "   
lv_im_p_log_handler  TYPE CL_PROTOCOL_HANDLER_TRP. "   

  CALL FUNCTION 'THMEX_UPDATE_PLAN_FOR_RO'  "Simulate Update Hedge Plan with RO Data
    EXPORTING
         IM_BUKRS = lv_im_bukrs
         IM_P_PERSISTENCY_MANAGER = lv_im_p_persistency_manager
         IM_P_LOG_HANDLER = lv_im_p_log_handler
    IMPORTING
         RESULT = lv_result
         EX_TAB_MESS = lv_ex_tab_mess
    CHANGING
         CH_TABLE = lv_ch_table
         CH_FLG_TESTRUN = lv_ch_flg_testrun
    EXCEPTIONS
        DB_ERROR = 1
        INCONSISTENT_DATA = 2
. " THMEX_UPDATE_PLAN_FOR_RO




ABAP code using 7.40 inline data declarations to call FM THMEX_UPDATE_PLAN_FOR_RO

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_ch_flg_testrun) = '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!