SAP Function Modules

THMEX_LOAD_PLAN_FROM_DB_MULTI SAP Function module - Read Data for Several Hedge Plans in One Company Code







THMEX_LOAD_PLAN_FROM_DB_MULTI is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name THMEX_LOAD_PLAN_FROM_DB_MULTI into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: THMEX_HM_VIA_RO
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM THMEX_LOAD_PLAN_FROM_DB_MULTI - THMEX LOAD PLAN FROM DB MULTI





CALL FUNCTION 'THMEX_LOAD_PLAN_FROM_DB_MULTI' "Read Data for Several Hedge Plans in One Company Code
  EXPORTING
    im_bukrs =                  " bukrs         Range Table for Company Code
    im_rng_plannerid =          " thar_plannerid  Ranges Structure for the Hedge Plan
  IMPORTING
    ex_tab_planner =            " thah_planner  Table Type for THMEXT_PLANNER
    ex_tab_trans =              " thaexy_trans  Table Type for THMEXT_TRANS
    ex_tab_trans_fx =           " thaexy_trans_fx  Table Type for THMEXT_TRANS_FX
    ex_tab_trans_fx_obs =       " thaexy_trans_fx  Table Type for THMEXT_TRANS_FX
    ex_tab_trans_ir =           " thaexy_trans_ir  Table Type for THMEXT_TRANS_IR
    ex_tab_trans_ir_obs =       " thaexy_trans_ir  Table Type for THMEXT_TRANS_IR
    ex_tab_expos =              " thaexy_expos  Table Type for THMEXT_EXPOS
    ex_tab_expos_fx =           " thaexy_expos_fx  Table Type for THMEXT_EXPOS_FX
    ex_tab_expos_ir =           " thaexy_expos_ir  Table Type for THMEXT_EXPOS_IR
    ex_tab_exp_hdg =            " thaexy_exp_hdg  Table Type for THAEXT_EXP_HDG
    ex_tab_hedge =              " thay_hedge_item  Table Type for THMT_HEDGE_ITEM
    ex_tab_hedgerel =           " vts_tab_hrt   FTR: Table for Transferring HRs to Transact. Mgmt
    ex_tab_hr_obs =             " vts_tab_hrt   FTR: Table for Transferring HRs to Transact. Mgmt
    ex_tab_hr_strat =           " thahry_hr_strat  Table Type for THMHRT_HR_STRAT
    ex_tab_hr_val =             " thahry_hr_val  Table Type for THMHRT_HR_VAL
    ex_tab_messages =           " bal_t_msg     Application Log: Table with Messages
  EXCEPTIONS
    INTERNAL_ERROR = 1          "               Internal Error
    .  "  THMEX_LOAD_PLAN_FROM_DB_MULTI

ABAP code example for Function Module THMEX_LOAD_PLAN_FROM_DB_MULTI





The ABAP code below is a full code listing to execute function module THMEX_LOAD_PLAN_FROM_DB_MULTI including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_ex_tab_planner  TYPE THAH_PLANNER ,
ld_ex_tab_trans  TYPE THAEXY_TRANS ,
ld_ex_tab_trans_fx  TYPE THAEXY_TRANS_FX ,
ld_ex_tab_trans_fx_obs  TYPE THAEXY_TRANS_FX ,
ld_ex_tab_trans_ir  TYPE THAEXY_TRANS_IR ,
ld_ex_tab_trans_ir_obs  TYPE THAEXY_TRANS_IR ,
ld_ex_tab_expos  TYPE THAEXY_EXPOS ,
ld_ex_tab_expos_fx  TYPE THAEXY_EXPOS_FX ,
ld_ex_tab_expos_ir  TYPE THAEXY_EXPOS_IR ,
ld_ex_tab_exp_hdg  TYPE THAEXY_EXP_HDG ,
ld_ex_tab_hedge  TYPE THAY_HEDGE_ITEM ,
ld_ex_tab_hedgerel  TYPE VTS_TAB_HRT ,
ld_ex_tab_hr_obs  TYPE VTS_TAB_HRT ,
ld_ex_tab_hr_strat  TYPE THAHRY_HR_STRAT ,
ld_ex_tab_hr_val  TYPE THAHRY_HR_VAL ,
ld_ex_tab_messages  TYPE BAL_T_MSG .

DATA(ld_im_bukrs) = 'Check type of data required'.
DATA(ld_im_rng_plannerid) = 'Check type of data required'. . CALL FUNCTION 'THMEX_LOAD_PLAN_FROM_DB_MULTI' EXPORTING im_bukrs = ld_im_bukrs im_rng_plannerid = ld_im_rng_plannerid IMPORTING ex_tab_planner = ld_ex_tab_planner ex_tab_trans = ld_ex_tab_trans ex_tab_trans_fx = ld_ex_tab_trans_fx ex_tab_trans_fx_obs = ld_ex_tab_trans_fx_obs ex_tab_trans_ir = ld_ex_tab_trans_ir ex_tab_trans_ir_obs = ld_ex_tab_trans_ir_obs ex_tab_expos = ld_ex_tab_expos ex_tab_expos_fx = ld_ex_tab_expos_fx ex_tab_expos_ir = ld_ex_tab_expos_ir ex_tab_exp_hdg = ld_ex_tab_exp_hdg ex_tab_hedge = ld_ex_tab_hedge ex_tab_hedgerel = ld_ex_tab_hedgerel ex_tab_hr_obs = ld_ex_tab_hr_obs ex_tab_hr_strat = ld_ex_tab_hr_strat ex_tab_hr_val = ld_ex_tab_hr_val ex_tab_messages = ld_ex_tab_messages EXCEPTIONS INTERNAL_ERROR = 1 . " THMEX_LOAD_PLAN_FROM_DB_MULTI
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:
ld_ex_tab_planner  TYPE THAH_PLANNER ,
ld_im_bukrs  TYPE BUKRS ,
ld_ex_tab_trans  TYPE THAEXY_TRANS ,
ld_im_rng_plannerid  TYPE THAR_PLANNERID ,
ld_ex_tab_trans_fx  TYPE THAEXY_TRANS_FX ,
ld_ex_tab_trans_fx_obs  TYPE THAEXY_TRANS_FX ,
ld_ex_tab_trans_ir  TYPE THAEXY_TRANS_IR ,
ld_ex_tab_trans_ir_obs  TYPE THAEXY_TRANS_IR ,
ld_ex_tab_expos  TYPE THAEXY_EXPOS ,
ld_ex_tab_expos_fx  TYPE THAEXY_EXPOS_FX ,
ld_ex_tab_expos_ir  TYPE THAEXY_EXPOS_IR ,
ld_ex_tab_exp_hdg  TYPE THAEXY_EXP_HDG ,
ld_ex_tab_hedge  TYPE THAY_HEDGE_ITEM ,
ld_ex_tab_hedgerel  TYPE VTS_TAB_HRT ,
ld_ex_tab_hr_obs  TYPE VTS_TAB_HRT ,
ld_ex_tab_hr_strat  TYPE THAHRY_HR_STRAT ,
ld_ex_tab_hr_val  TYPE THAHRY_HR_VAL ,
ld_ex_tab_messages  TYPE BAL_T_MSG .

ld_im_bukrs = 'Check type of data required'.
ld_im_rng_plannerid = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name THMEX_LOAD_PLAN_FROM_DB_MULTI or its description.