SAP TPM_TRL_UPDATE_INIT_TAB Function Module for Set TRANS_FLG in TRGT_INIT_VALUES
TPM_TRL_UPDATE_INIT_TAB is a standard tpm trl update init tab SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Set TRANS_FLG in TRGT_INIT_VALUES 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 tpm trl update init tab FM, simply by entering the name TPM_TRL_UPDATE_INIT_TAB into the relevant SAP transaction such as SE37 or SE38.
Function Group: TPM_TRL_INIT_STEPS
Program Name: SAPLTPM_TRL_INIT_STEPS
Main Program: SAPLTPM_TRL_INIT_STEPS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1

Function TPM_TRL_UPDATE_INIT_TAB 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 'TPM_TRL_UPDATE_INIT_TAB'"Set TRANS_FLG in TRGT_INIT_VALUES.
EXPORTING
IM_COMPANY_CODE = "Company Code
* IM_TAB_INIT_VAL_LO = "TRL Initialization: Loans
* IM_TAB_INIT_IGT_SE = "Initialization for Intragroup Transactions
IM_VALUATION_AREA = "Valuation Area
* IM_TAB_LOANS_CONTRACT = "Darlehensverträge - obsolet
* IM_TAB_SECURITY_ID = "Range security id - obsolet
IM_MODE = "Mode
IM_PRODUCT_GROUP = "Product Group
IM_KEYDATE = "Key Date
* IM_TAB_INIT_VAL_SE = "TRL Initialization
* IM_TAB_INIT_VAL_FU = "Initialization Table for Parallel Val. Areas for Futures
IMPORTING Parameters details for TPM_TRL_UPDATE_INIT_TAB
IM_COMPANY_CODE - Company Code
Data type: BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
IM_TAB_INIT_VAL_LO - TRL Initialization: Loans
Data type: TRLY_INIT_VAL_LOOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_TAB_INIT_IGT_SE - Initialization for Intragroup Transactions
Data type: TRLY_INIT_IGT_SEOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_VALUATION_AREA - Valuation Area
Data type: TPM_VAL_AREAOptional: No
Call by Reference: No ( called with pass by value option)
IM_TAB_LOANS_CONTRACT - Darlehensverträge - obsolet
Data type: TRGR_LOANS_CONTRACTOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_TAB_SECURITY_ID - Range security id - obsolet
Data type: TRGR_SECURITY_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_MODE - Mode
Data type: TPM_MODEOptional: No
Call by Reference: No ( called with pass by value option)
IM_PRODUCT_GROUP - Product Group
Data type: TPM_PRODUCT_GROUPOptional: No
Call by Reference: No ( called with pass by value option)
IM_KEYDATE - Key Date
Data type: TPM_TRLDATEOptional: No
Call by Reference: No ( called with pass by value option)
IM_TAB_INIT_VAL_SE - TRL Initialization
Data type: TRLY_INIT_VAL_SEOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_TAB_INIT_VAL_FU - Initialization Table for Parallel Val. Areas for Futures
Data type: TRLY_INIT_VAL_FUOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for TPM_TRL_UPDATE_INIT_TAB 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_company_code | TYPE BUKRS, " | |||
| lv_im_tab_init_val_lo | TYPE TRLY_INIT_VAL_LO, " | |||
| lv_im_tab_init_igt_se | TYPE TRLY_INIT_IGT_SE, " | |||
| lv_im_valuation_area | TYPE TPM_VAL_AREA, " | |||
| lv_im_tab_loans_contract | TYPE TRGR_LOANS_CONTRACT, " | |||
| lv_im_tab_security_id | TYPE TRGR_SECURITY_ID, " | |||
| lv_im_mode | TYPE TPM_MODE, " | |||
| lv_im_product_group | TYPE TPM_PRODUCT_GROUP, " | |||
| lv_im_keydate | TYPE TPM_TRLDATE, " | |||
| lv_im_tab_init_val_se | TYPE TRLY_INIT_VAL_SE, " | |||
| lv_im_tab_init_val_fu | TYPE TRLY_INIT_VAL_FU. " |
|   CALL FUNCTION 'TPM_TRL_UPDATE_INIT_TAB' "Set TRANS_FLG in TRGT_INIT_VALUES |
| EXPORTING | ||
| IM_COMPANY_CODE | = lv_im_company_code | |
| IM_TAB_INIT_VAL_LO | = lv_im_tab_init_val_lo | |
| IM_TAB_INIT_IGT_SE | = lv_im_tab_init_igt_se | |
| IM_VALUATION_AREA | = lv_im_valuation_area | |
| IM_TAB_LOANS_CONTRACT | = lv_im_tab_loans_contract | |
| IM_TAB_SECURITY_ID | = lv_im_tab_security_id | |
| IM_MODE | = lv_im_mode | |
| IM_PRODUCT_GROUP | = lv_im_product_group | |
| IM_KEYDATE | = lv_im_keydate | |
| IM_TAB_INIT_VAL_SE | = lv_im_tab_init_val_se | |
| IM_TAB_INIT_VAL_FU | = lv_im_tab_init_val_fu | |
| . " TPM_TRL_UPDATE_INIT_TAB | ||
ABAP code using 7.40 inline data declarations to call FM TPM_TRL_UPDATE_INIT_TAB
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