SAP MPE_RTG_UI_CREATE_VERSION Function Module for Create routing version









MPE_RTG_UI_CREATE_VERSION is a standard mpe rtg ui create version SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create routing version 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 mpe rtg ui create version FM, simply by entering the name MPE_RTG_UI_CREATE_VERSION into the relevant SAP transaction such as SE37 or SE38.

Function Group: MPE_RTG_UI
Program Name: SAPLMPE_RTG_UI
Main Program: SAPLMPE_RTG_UI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function MPE_RTG_UI_CREATE_VERSION 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 'MPE_RTG_UI_CREATE_VERSION'"Create routing version
  EXPORTING
   IV_PLNTY =  "Task List Type
*  IS_RTGV_CR =  "Change Record Structure
*  IV_NO_MAINTENANCE =  "
*  IV_FOLDER_ID =  "Folder UUID
*  IV_REFERENCE_TEMPLATE_CATEGORY =  "Template Category
   IV_PLNNR =  "Key for Task List Group
   IV_PLNAL =  "Group Counter
   IV_VERSN =  "Routing Version
*  IV_SOURCE_PLNTY =  "Task List Type
*  IV_SOURCE_PLNNR =  "Key for Task List Group
*  IV_SOURCE_PLNAL =  "Group Counter
*  IV_SOURCE_VERSN =  "Routing Version
*  IV_AUFNR =  "Order Number

 IMPORTING
   ET_MESSAGE =  "Message
.



IMPORTING Parameters details for MPE_RTG_UI_CREATE_VERSION

IV_PLNTY - Task List Type

Data type: PLNTY
Optional: No
Call by Reference: Yes

IS_RTGV_CR - Change Record Structure

Data type: MPES_RTGV_CR
Optional: Yes
Call by Reference: Yes

IV_NO_MAINTENANCE -

Data type: ABAP_BOOL
Optional: Yes
Call by Reference: Yes

IV_FOLDER_ID - Folder UUID

Data type: MPE_RTG_FOLDER_UUID
Optional: Yes
Call by Reference: Yes

IV_REFERENCE_TEMPLATE_CATEGORY - Template Category

Data type: MPE_RTG_REF_TEMPLATE_CATEGORY
Optional: Yes
Call by Reference: Yes

IV_PLNNR - Key for Task List Group

Data type: PLNNR
Optional: No
Call by Reference: Yes

IV_PLNAL - Group Counter

Data type: PLNAL
Optional: No
Call by Reference: Yes

IV_VERSN - Routing Version

Data type: PLNVERSN
Optional: No
Call by Reference: Yes

IV_SOURCE_PLNTY - Task List Type

Data type: PLNTY
Optional: Yes
Call by Reference: Yes

IV_SOURCE_PLNNR - Key for Task List Group

Data type: PLNNR
Optional: Yes
Call by Reference: Yes

IV_SOURCE_PLNAL - Group Counter

Data type: PLNAL
Optional: Yes
Call by Reference: Yes

IV_SOURCE_VERSN - Routing Version

Data type: PLNVERSN
Optional: Yes
Call by Reference: Yes

IV_AUFNR - Order Number

Data type: CP_AUFNR
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for MPE_RTG_UI_CREATE_VERSION

ET_MESSAGE - Message

Data type: MPET_RTGV_MESSAGE
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for MPE_RTG_UI_CREATE_VERSION 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_plnty  TYPE PLNTY, "   
lv_et_message  TYPE MPET_RTGV_MESSAGE, "   
lv_is_rtgv_cr  TYPE MPES_RTGV_CR, "   
lv_iv_no_maintenance  TYPE ABAP_BOOL, "   
lv_iv_folder_id  TYPE MPE_RTG_FOLDER_UUID, "   
lv_iv_reference_template_category  TYPE MPE_RTG_REF_TEMPLATE_CATEGORY, "   
lv_iv_plnnr  TYPE PLNNR, "   
lv_iv_plnal  TYPE PLNAL, "   
lv_iv_versn  TYPE PLNVERSN, "   
lv_iv_source_plnty  TYPE PLNTY, "   
lv_iv_source_plnnr  TYPE PLNNR, "   
lv_iv_source_plnal  TYPE PLNAL, "   
lv_iv_source_versn  TYPE PLNVERSN, "   
lv_iv_aufnr  TYPE CP_AUFNR. "   

  CALL FUNCTION 'MPE_RTG_UI_CREATE_VERSION'  "Create routing version
    EXPORTING
         IV_PLNTY = lv_iv_plnty
         IS_RTGV_CR = lv_is_rtgv_cr
         IV_NO_MAINTENANCE = lv_iv_no_maintenance
         IV_FOLDER_ID = lv_iv_folder_id
         IV_REFERENCE_TEMPLATE_CATEGORY = lv_iv_reference_template_category
         IV_PLNNR = lv_iv_plnnr
         IV_PLNAL = lv_iv_plnal
         IV_VERSN = lv_iv_versn
         IV_SOURCE_PLNTY = lv_iv_source_plnty
         IV_SOURCE_PLNNR = lv_iv_source_plnnr
         IV_SOURCE_PLNAL = lv_iv_source_plnal
         IV_SOURCE_VERSN = lv_iv_source_versn
         IV_AUFNR = lv_iv_aufnr
    IMPORTING
         ET_MESSAGE = lv_et_message
. " MPE_RTG_UI_CREATE_VERSION




ABAP code using 7.40 inline data declarations to call FM MPE_RTG_UI_CREATE_VERSION

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!