SAP TPM_MIG_PROCESS_PACKAGE001_PAR Function Module for Asynchronous Call to Process a Package
TPM_MIG_PROCESS_PACKAGE001_PAR is a standard tpm mig process package001 par SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Asynchronous Call to Process a Package 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 mig process package001 par FM, simply by entering the name TPM_MIG_PROCESS_PACKAGE001_PAR into the relevant SAP transaction such as SE37 or SE38.
Function Group: TPM_TRG_MIGRATION_ERP20
Program Name: SAPLTPM_TRG_MIGRATION_ERP20
Main Program: SAPLTPM_TRG_MIGRATION_ERP20
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function TPM_MIG_PROCESS_PACKAGE001_PAR 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_MIG_PROCESS_PACKAGE001_PAR'"Asynchronous Call to Process a Package.
EXPORTING
IM_MODE = "1 Echt; 2 Test; 3 Storno; 4 Storno Test
IM_INIT_DATE = "Key Date for Initialization of Parallel Valuation Areas
IM_PRODUCT_GROUP = "Product Group
IM_PACKAGE = "Paket von IDs für Distributor-Geschäftsvorfälle
IM_TCODE = "ABAP Program, Current Transaction Code
IM_COMPANY_CODE = "Company Code
IMPORTING
EX_ERROR = "Error
EX_TAB_MESSAGE = "Table with Messages
EX_PACKAGE_ID = "Nummer des abgearbeiteten Paketes
IMPORTING Parameters details for TPM_MIG_PROCESS_PACKAGE001_PAR
IM_MODE - 1 Echt; 2 Test; 3 Storno; 4 Storno Test
Data type: CHAR1Optional: No
Call by Reference: No ( called with pass by value option)
IM_INIT_DATE - Key Date for Initialization of Parallel Valuation Areas
Data type: TPM_INIT_DATEOptional: 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_PACKAGE - Paket von IDs für Distributor-Geschäftsvorfälle
Data type: TRDS_BUSTRANSID_PACKAGEOptional: No
Call by Reference: No ( called with pass by value option)
IM_TCODE - ABAP Program, Current Transaction Code
Data type: SYTCODEOptional: No
Call by Reference: No ( called with pass by value option)
IM_COMPANY_CODE - Company Code
Data type: BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for TPM_MIG_PROCESS_PACKAGE001_PAR
EX_ERROR - Error
Data type: CHAR1Optional: No
Call by Reference: No ( called with pass by value option)
EX_TAB_MESSAGE - Table with Messages
Data type: BAL_T_MSGOptional: No
Call by Reference: No ( called with pass by value option)
EX_PACKAGE_ID - Nummer des abgearbeiteten Paketes
Data type: INT4Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for TPM_MIG_PROCESS_PACKAGE001_PAR 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 CHAR1, " | |||
| lv_ex_error | TYPE CHAR1, " | |||
| lv_im_init_date | TYPE TPM_INIT_DATE, " | |||
| lv_ex_tab_message | TYPE BAL_T_MSG, " | |||
| lv_ex_package_id | TYPE INT4, " | |||
| lv_im_product_group | TYPE TPM_PRODUCT_GROUP, " | |||
| lv_im_package | TYPE TRDS_BUSTRANSID_PACKAGE, " | |||
| lv_im_tcode | TYPE SYTCODE, " | |||
| lv_im_company_code | TYPE BUKRS. " |
|   CALL FUNCTION 'TPM_MIG_PROCESS_PACKAGE001_PAR' "Asynchronous Call to Process a Package |
| EXPORTING | ||
| IM_MODE | = lv_im_mode | |
| IM_INIT_DATE | = lv_im_init_date | |
| IM_PRODUCT_GROUP | = lv_im_product_group | |
| IM_PACKAGE | = lv_im_package | |
| IM_TCODE | = lv_im_tcode | |
| IM_COMPANY_CODE | = lv_im_company_code | |
| IMPORTING | ||
| EX_ERROR | = lv_ex_error | |
| EX_TAB_MESSAGE | = lv_ex_tab_message | |
| EX_PACKAGE_ID | = lv_ex_package_id | |
| . " TPM_MIG_PROCESS_PACKAGE001_PAR | ||
ABAP code using 7.40 inline data declarations to call FM TPM_MIG_PROCESS_PACKAGE001_PAR
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