SAP TPM_TRDT_POST Function Module for Legacy Data Transfer: Update Legacy Data Tables
TPM_TRDT_POST is a standard tpm trdt post SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Legacy Data Transfer: Update Legacy Data Tables 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 trdt post FM, simply by entering the name TPM_TRDT_POST into the relevant SAP transaction such as SE37 or SE38.
Function Group: TPM_TRDT_APPL
Program Name: SAPLTPM_TRDT_APPL
Main Program: SAPLTPM_TRDT_APPL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1
Function TPM_TRDT_POST 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_TRDT_POST'"Legacy Data Transfer: Update Legacy Data Tables.
EXPORTING
* IM_TAB_POS_SEC_UPD = "Legacy Data Transfer Securities - Subledger Positions
* IM_TAB_DATA_SEC_UPD = "Legacy Data Transfer Securities (VA-Independent)
* IM_TAB_VADATA_SEC_UPD = "Legacy Data Transfer Securities (per Valuation Area)
* IM_TAB_VADATA_OTC_UPD = "Legacy Data Transfer Money Market/Forex/OTC Der. (per VArea)
* IM_TAB_VADATA_FUT_UPD = "Legacy Data Transfer Listed Options/Futures (per ValArea)
* IM_TAB_IGTDATA_SEC_UPD = "IGT Legacy Data Transfer for Securities (for Each Val.Area)
* IM_TAB_VAD_SECSUB_UPD = "Table Type: Legacy Data Transfer, Securities in Hedging Rel.
* IM_TAB_VAD_FUTSUB_UPD = "Table Type: Legacy Data Transfer, Futures in Hedging Rel.
* IM_TAB_VAD_OTCSUB_UPD = "Table Type: Legacy Data Transfer, OTC in Hedging Rel.
IMPORTING Parameters details for TPM_TRDT_POST
IM_TAB_POS_SEC_UPD - Legacy Data Transfer Securities - Subledger Positions
Data type: TRDTY_POS_SECOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_TAB_DATA_SEC_UPD - Legacy Data Transfer Securities (VA-Independent)
Data type: TRDTY_DATA_SECOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_TAB_VADATA_SEC_UPD - Legacy Data Transfer Securities (per Valuation Area)
Data type: TRDTY_VADATA_SECOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_TAB_VADATA_OTC_UPD - Legacy Data Transfer Money Market/Forex/OTC Der. (per VArea)
Data type: TRDTY_VADATA_OTCOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_TAB_VADATA_FUT_UPD - Legacy Data Transfer Listed Options/Futures (per ValArea)
Data type: TRDTY_VADATA_FUTOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_TAB_IGTDATA_SEC_UPD - IGT Legacy Data Transfer for Securities (for Each Val.Area)
Data type: TRDTY_IGTDATA_SEOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_TAB_VAD_SECSUB_UPD - Table Type: Legacy Data Transfer, Securities in Hedging Rel.
Data type: TRDTY_VAD_SECSUBOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_TAB_VAD_FUTSUB_UPD - Table Type: Legacy Data Transfer, Futures in Hedging Rel.
Data type: TRDTY_VAD_FUTSUBOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_TAB_VAD_OTCSUB_UPD - Table Type: Legacy Data Transfer, OTC in Hedging Rel.
Data type: TRDTY_VAD_OTCSUBOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for TPM_TRDT_POST 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_tab_pos_sec_upd | TYPE TRDTY_POS_SEC, " | |||
| lv_im_tab_data_sec_upd | TYPE TRDTY_DATA_SEC, " | |||
| lv_im_tab_vadata_sec_upd | TYPE TRDTY_VADATA_SEC, " | |||
| lv_im_tab_vadata_otc_upd | TYPE TRDTY_VADATA_OTC, " | |||
| lv_im_tab_vadata_fut_upd | TYPE TRDTY_VADATA_FUT, " | |||
| lv_im_tab_igtdata_sec_upd | TYPE TRDTY_IGTDATA_SE, " | |||
| lv_im_tab_vad_secsub_upd | TYPE TRDTY_VAD_SECSUB, " | |||
| lv_im_tab_vad_futsub_upd | TYPE TRDTY_VAD_FUTSUB, " | |||
| lv_im_tab_vad_otcsub_upd | TYPE TRDTY_VAD_OTCSUB. " |
| CALL FUNCTION 'TPM_TRDT_POST' "Legacy Data Transfer: Update Legacy Data Tables |
| EXPORTING | ||
| IM_TAB_POS_SEC_UPD | = lv_im_tab_pos_sec_upd | |
| IM_TAB_DATA_SEC_UPD | = lv_im_tab_data_sec_upd | |
| IM_TAB_VADATA_SEC_UPD | = lv_im_tab_vadata_sec_upd | |
| IM_TAB_VADATA_OTC_UPD | = lv_im_tab_vadata_otc_upd | |
| IM_TAB_VADATA_FUT_UPD | = lv_im_tab_vadata_fut_upd | |
| IM_TAB_IGTDATA_SEC_UPD | = lv_im_tab_igtdata_sec_upd | |
| IM_TAB_VAD_SECSUB_UPD | = lv_im_tab_vad_secsub_upd | |
| IM_TAB_VAD_FUTSUB_UPD | = lv_im_tab_vad_futsub_upd | |
| IM_TAB_VAD_OTCSUB_UPD | = lv_im_tab_vad_otcsub_upd | |
| . " TPM_TRDT_POST | ||
ABAP code using 7.40 inline data declarations to call FM TPM_TRDT_POST
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