SAP TPM_TRG_MIGRATE_PATTERN Function Module for Copy Template: Company Code-Independent Migration Step
TPM_TRG_MIGRATE_PATTERN is a standard tpm trg migrate pattern SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Copy Template: Company Code-Independent Migration Step 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 trg migrate pattern FM, simply by entering the name TPM_TRG_MIGRATE_PATTERN into the relevant SAP transaction such as SE37 or SE38.
Function Group: TPM_TRG_MIGRATION
Program Name: SAPLTPM_TRG_MIGRATION
Main Program: SAPLTPM_TRG_MIGRATION
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TPM_TRG_MIGRATE_PATTERN 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_TRG_MIGRATE_PATTERN'"Copy Template: Company Code-Independent Migration Step.
EXPORTING
IM_MODE = "1 Echt; 2 Test; 3 Storno; 4 Storno Test
IM_PROTOCOL_HANDLER = "Protocol Manager
* IM_REVERSAL_REASON = "Reason for Reversal
* IM_MIGR_CAT = "Migration Type
* IM_REFRESH = "refresh der globalen Daten
* IM_MIGR_CUST = "Customizing for Converting to Enterprise 2.0
* IM_PACKAGE_FAILED = "Prozessierung fehlgeschlagener Pakete
IMPORTING
EX_CANCEL = "Cancel
CHANGING
CH_EXECUTION_RATE = "Execution Rate of Migration Step
IMPORTING Parameters details for TPM_TRG_MIGRATE_PATTERN
IM_MODE - 1 Echt; 2 Test; 3 Storno; 4 Storno Test
Data type: COptional: No
Call by Reference: Yes
IM_PROTOCOL_HANDLER - Protocol Manager
Data type: CL_PROTOCOL_HANDLER_TRPOptional: No
Call by Reference: Yes
IM_REVERSAL_REASON - Reason for Reversal
Data type: SSTOGRDOptional: Yes
Call by Reference: Yes
IM_MIGR_CAT - Migration Type
Data type: TPM_MIGRATION_CATOptional: Yes
Call by Reference: Yes
IM_REFRESH - refresh der globalen Daten
Data type: CHAR1Optional: Yes
Call by Reference: Yes
IM_MIGR_CUST - Customizing for Converting to Enterprise 2.0
Data type: TRGC_MIGR1Optional: Yes
Call by Reference: Yes
IM_PACKAGE_FAILED - Prozessierung fehlgeschlagener Pakete
Data type: CHAR1Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for TPM_TRG_MIGRATE_PATTERN
EX_CANCEL - Cancel
Data type: CHAR1Optional: No
Call by Reference: Yes
CHANGING Parameters details for TPM_TRG_MIGRATE_PATTERN
CH_EXECUTION_RATE - Execution Rate of Migration Step
Data type: TPM_MIGRATION_EXECUTION_RATEOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for TPM_TRG_MIGRATE_PATTERN 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_mode | TYPE C, " | |||
| lv_ex_cancel | TYPE CHAR1, " | |||
| lv_ch_execution_rate | TYPE TPM_MIGRATION_EXECUTION_RATE, " | |||
| lv_im_protocol_handler | TYPE CL_PROTOCOL_HANDLER_TRP, " | |||
| lv_im_reversal_reason | TYPE SSTOGRD, " | |||
| lv_im_migr_cat | TYPE TPM_MIGRATION_CAT, " | |||
| lv_im_refresh | TYPE CHAR1, " | |||
| lv_im_migr_cust | TYPE TRGC_MIGR1, " | |||
| lv_im_package_failed | TYPE CHAR1. " |
|   CALL FUNCTION 'TPM_TRG_MIGRATE_PATTERN' "Copy Template: Company Code-Independent Migration Step |
| EXPORTING | ||
| IM_MODE | = lv_im_mode | |
| IM_PROTOCOL_HANDLER | = lv_im_protocol_handler | |
| IM_REVERSAL_REASON | = lv_im_reversal_reason | |
| IM_MIGR_CAT | = lv_im_migr_cat | |
| IM_REFRESH | = lv_im_refresh | |
| IM_MIGR_CUST | = lv_im_migr_cust | |
| IM_PACKAGE_FAILED | = lv_im_package_failed | |
| IMPORTING | ||
| EX_CANCEL | = lv_ex_cancel | |
| CHANGING | ||
| CH_EXECUTION_RATE | = lv_ch_execution_rate | |
| . " TPM_TRG_MIGRATE_PATTERN | ||
ABAP code using 7.40 inline data declarations to call FM TPM_TRG_MIGRATE_PATTERN
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