SAP MIG_MP_COMPRESSOR Function Module for UPO Compressor Migration FM For Parallel Processing









MIG_MP_COMPRESSOR is a standard mig mp compressor SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for UPO Compressor Migration FM For Parallel Processing 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 mig mp compressor FM, simply by entering the name MIG_MP_COMPRESSOR into the relevant SAP transaction such as SE37 or SE38.

Function Group: UPO_MIG_PARALLEL
Program Name: SAPLUPO_MIG_PARALLEL
Main Program: SAPLUPO_MIG_PARALLEL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function MIG_MP_COMPRESSOR 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 'MIG_MP_COMPRESSOR'"UPO Compressor Migration FM For Parallel Processing
  EXPORTING
*  IV_TRIAL =  "describe the type of migration run type
   IT_PRA_COMP_DATA =  "table type to hold measurement point information
   IT_PRA_COMP_DATED =  "Table Type to hold the measurment point dated information
   IT_ENTITY_MAP =  "Table Type for DN Entity Mapping
   IT_MIG_DEFAULT =  "Table Type for Migration Default
   IT_PRA_OBJECT_MAP =  "table type of pra object Map
   IT_REGION =  "Table type for UOM-->PRA Region Map Table

 IMPORTING
   EV_FAILED =  "General Flag
   ET_MESSAGES =  "Message Table (enhanced)
.



IMPORTING Parameters details for MIG_MP_COMPRESSOR

IV_TRIAL - describe the type of migration run type

Data type: UPO_MIG_RUN_TYPE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IT_PRA_COMP_DATA - table type to hold measurement point information

Data type: UPOTT_MIG_MEASUREMENT_POINT
Optional: No
Call by Reference: No ( called with pass by value option)

IT_PRA_COMP_DATED - Table Type to hold the measurment point dated information

Data type: UPOTT_MIG_MEASUREMENT_POINT_DT
Optional: No
Call by Reference: No ( called with pass by value option)

IT_ENTITY_MAP - Table Type for DN Entity Mapping

Data type: UPOTT_MIG_EMAP_MD
Optional: No
Call by Reference: No ( called with pass by value option)

IT_MIG_DEFAULT - Table Type for Migration Default

Data type: UPOTT_MIG_DEFAULT
Optional: No
Call by Reference: No ( called with pass by value option)

IT_PRA_OBJECT_MAP - table type of pra object Map

Data type: UPOTT_MIG_OBJECT_MAP
Optional: No
Call by Reference: No ( called with pass by value option)

IT_REGION - Table type for UOM-->PRA Region Map Table

Data type: UPOTT_MIG_REGION_MAP
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for MIG_MP_COMPRESSOR

EV_FAILED - General Flag

Data type: FLAG
Optional: No
Call by Reference: No ( called with pass by value option)

ET_MESSAGES - Message Table (enhanced)

Data type: BAPIRETTAB
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for MIG_MP_COMPRESSOR 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_iv_trial  TYPE UPO_MIG_RUN_TYPE, "   
lv_ev_failed  TYPE FLAG, "   
lv_et_messages  TYPE BAPIRETTAB, "   
lv_it_pra_comp_data  TYPE UPOTT_MIG_MEASUREMENT_POINT, "   
lv_it_pra_comp_dated  TYPE UPOTT_MIG_MEASUREMENT_POINT_DT, "   
lv_it_entity_map  TYPE UPOTT_MIG_EMAP_MD, "   
lv_it_mig_default  TYPE UPOTT_MIG_DEFAULT, "   
lv_it_pra_object_map  TYPE UPOTT_MIG_OBJECT_MAP, "   
lv_it_region  TYPE UPOTT_MIG_REGION_MAP. "   

  CALL FUNCTION 'MIG_MP_COMPRESSOR'  "UPO Compressor Migration FM For Parallel Processing
    EXPORTING
         IV_TRIAL = lv_iv_trial
         IT_PRA_COMP_DATA = lv_it_pra_comp_data
         IT_PRA_COMP_DATED = lv_it_pra_comp_dated
         IT_ENTITY_MAP = lv_it_entity_map
         IT_MIG_DEFAULT = lv_it_mig_default
         IT_PRA_OBJECT_MAP = lv_it_pra_object_map
         IT_REGION = lv_it_region
    IMPORTING
         EV_FAILED = lv_ev_failed
         ET_MESSAGES = lv_et_messages
. " MIG_MP_COMPRESSOR




ABAP code using 7.40 inline data declarations to call FM MIG_MP_COMPRESSOR

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!