SAP MIG_FLARE_DATA Function Module for Migration of flare data









MIG_FLARE_DATA is a standard mig flare data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Migration of flare data 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 flare data FM, simply by entering the name MIG_FLARE_DATA 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_FLARE_DATA 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_FLARE_DATA'"Migration of flare data
  EXPORTING
   IT_PRA_FLARE_DATA =  "Table type to hold measurement point information
   IT_PRA_FLARE_DATED =  "Table Type to hold the measurment point dated information
   IV_IS_TRAIL =  "Flag
   IT_REGION =  "Table type for UOM-->PRA Region Map Table
   IT_MIG_DEFAULT =  "Table Type for Migration Default
   IT_ENT_MAP =  "Table Type for DN Entity Mapping
   IT_PRA_OBJ_MAP =  "table type of pra object Map

 IMPORTING
   ET_MESSAGES =  "Table with BAPI Return Information
.



IMPORTING Parameters details for MIG_FLARE_DATA

IT_PRA_FLARE_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_FLARE_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)

IV_IS_TRAIL - Flag

Data type: FLAG
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)

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_ENT_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_PRA_OBJ_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)

EXPORTING Parameters details for MIG_FLARE_DATA

ET_MESSAGES - Table with BAPI Return Information

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

Copy and paste ABAP code example for MIG_FLARE_DATA 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_et_messages  TYPE BAPIRETTAB, "   
lv_it_pra_flare_data  TYPE UPOTT_MIG_MEASUREMENT_POINT, "   
lv_it_pra_flare_dated  TYPE UPOTT_MIG_MEASUREMENT_POINT_DT, "   
lv_iv_is_trail  TYPE FLAG, "   
lv_it_region  TYPE UPOTT_MIG_REGION_MAP, "   
lv_it_mig_default  TYPE UPOTT_MIG_DEFAULT, "   
lv_it_ent_map  TYPE UPOTT_MIG_EMAP_MD, "   
lv_it_pra_obj_map  TYPE UPOTT_MIG_OBJECT_MAP. "   

  CALL FUNCTION 'MIG_FLARE_DATA'  "Migration of flare data
    EXPORTING
         IT_PRA_FLARE_DATA = lv_it_pra_flare_data
         IT_PRA_FLARE_DATED = lv_it_pra_flare_dated
         IV_IS_TRAIL = lv_iv_is_trail
         IT_REGION = lv_it_region
         IT_MIG_DEFAULT = lv_it_mig_default
         IT_ENT_MAP = lv_it_ent_map
         IT_PRA_OBJ_MAP = lv_it_pra_obj_map
    IMPORTING
         ET_MESSAGES = lv_et_messages
. " MIG_FLARE_DATA




ABAP code using 7.40 inline data declarations to call FM MIG_FLARE_DATA

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!