SAP MIG_MODEL_PPN Function Module for Migrate Model PPN









MIG_MODEL_PPN is a standard mig model ppn SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Migrate Model PPN 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 model ppn FM, simply by entering the name MIG_MODEL_PPN 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_MODEL_PPN 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_MODEL_PPN'"Migrate Model PPN
  EXPORTING
   IV_IS_TRIAL =  "General Flag
   IT_SEPERATOR =  "Well and Well Completion Separator in WC ID
   IT_DN_DET =  "table type for the DN run details
   IT_PPADJ_RC_TXT =  "Table type for Prior Period Adjustment Reason Code Text
   IT_PPN_SET =  "Table Type for PPN Set
   IT_MIG_PPN =  "Table type for PPN event
   IT_MPTYP_MAP =  "PRA MP Type to UOM Network Obj Type Mapping
   IT_MP_DET =  "table type to hold measurement point information
   IT_MODEL_EVENT =  "Table Type for PPN Event
   IT_EVENT_DET =  "PRA PPN Event Detail

 IMPORTING
   ET_MESSAGES =  "Table with BAPI Return Information
.



IMPORTING Parameters details for MIG_MODEL_PPN

IV_IS_TRIAL - General Flag

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

IT_SEPERATOR - Well and Well Completion Separator in WC ID

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

IT_DN_DET - table type for the DN run details

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

IT_PPADJ_RC_TXT - Table type for Prior Period Adjustment Reason Code Text

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

IT_PPN_SET - Table Type for PPN Set

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

IT_MIG_PPN - Table type for PPN event

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

IT_MPTYP_MAP - PRA MP Type to UOM Network Obj Type Mapping

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

IT_MP_DET - 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_MODEL_EVENT - Table Type for PPN Event

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

IT_EVENT_DET - PRA PPN Event Detail

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

EXPORTING Parameters details for MIG_MODEL_PPN

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_MODEL_PPN 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_iv_is_trial  TYPE FLAG, "   
lv_it_seperator  TYPE UPOTT_MIG_WC_SEP, "   
lv_it_dn_det  TYPE UPOTT_MIG_DN_RUN_DET, "   
lv_it_ppadj_rc_txt  TYPE UPOTT_MIG_PP_ADJ_RC_TEXT, "   
lv_it_ppn_set  TYPE UPOTT_MIG_PPN_SET, "   
lv_it_mig_ppn  TYPE UPOTT_MIG_PPN, "   
lv_it_mptyp_map  TYPE UPOTT_MIG_MPTYP, "   
lv_it_mp_det  TYPE UPOTT_MIG_MEASUREMENT_POINT, "   
lv_it_model_event  TYPE UPOTT_MIG_EVENT_TYPE, "   
lv_it_event_det  TYPE UPOTT_MIG_PRA_PPN_EVENT. "   

  CALL FUNCTION 'MIG_MODEL_PPN'  "Migrate Model PPN
    EXPORTING
         IV_IS_TRIAL = lv_iv_is_trial
         IT_SEPERATOR = lv_it_seperator
         IT_DN_DET = lv_it_dn_det
         IT_PPADJ_RC_TXT = lv_it_ppadj_rc_txt
         IT_PPN_SET = lv_it_ppn_set
         IT_MIG_PPN = lv_it_mig_ppn
         IT_MPTYP_MAP = lv_it_mptyp_map
         IT_MP_DET = lv_it_mp_det
         IT_MODEL_EVENT = lv_it_model_event
         IT_EVENT_DET = lv_it_event_det
    IMPORTING
         ET_MESSAGES = lv_et_messages
. " MIG_MODEL_PPN




ABAP code using 7.40 inline data declarations to call FM MIG_MODEL_PPN

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!