SAP UPARU_UI_EXECUTE_SEQUENCE Function Module for Execute a planning sequence









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

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



Function UPARU_UI_EXECUTE_SEQUENCE 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 'UPARU_UI_EXECUTE_SEQUENCE'"Execute a planning sequence
EXPORTING
I_AREA = "Planning Area
I_PLEVEL = "Planning level
I_PPACKAGE = "Planning Package
I_SEQUENCE = "Planning Sequence

IMPORTING
E_SUBRC = "Return Value, Return Value After ABAP Statements

TABLES
ETK_RETURN = "MAP-SEM: Error returned messages
.



IMPORTING Parameters details for UPARU_UI_EXECUTE_SEQUENCE

I_AREA - Planning Area

Data type: UPC_AREA-AREA
Optional: No
Call by Reference: No ( called with pass by value option)

I_PLEVEL - Planning level

Data type: UPC_PLEVEL-PLEVEL
Optional: No
Call by Reference: No ( called with pass by value option)

I_PPACKAGE - Planning Package

Data type: UPC_PACKAGE-PPACKAGE
Optional: No
Call by Reference: No ( called with pass by value option)

I_SEQUENCE - Planning Sequence

Data type: UPF_BUNDLE-BUNDLE
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for UPARU_UI_EXECUTE_SEQUENCE

E_SUBRC - Return Value, Return Value After ABAP Statements

Data type: SY-SUBRC
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for UPARU_UI_EXECUTE_SEQUENCE

ETK_RETURN - MAP-SEM: Error returned messages

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

Copy and paste ABAP code example for UPARU_UI_EXECUTE_SEQUENCE 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_i_area  TYPE UPC_AREA-AREA, "   
lv_e_subrc  TYPE SY-SUBRC, "   
lt_etk_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_i_plevel  TYPE UPC_PLEVEL-PLEVEL, "   
lv_i_ppackage  TYPE UPC_PACKAGE-PPACKAGE, "   
lv_i_sequence  TYPE UPF_BUNDLE-BUNDLE. "   

  CALL FUNCTION 'UPARU_UI_EXECUTE_SEQUENCE'  "Execute a planning sequence
    EXPORTING
         I_AREA = lv_i_area
         I_PLEVEL = lv_i_plevel
         I_PPACKAGE = lv_i_ppackage
         I_SEQUENCE = lv_i_sequence
    IMPORTING
         E_SUBRC = lv_e_subrc
    TABLES
         ETK_RETURN = lt_etk_return
. " UPARU_UI_EXECUTE_SEQUENCE




ABAP code using 7.40 inline data declarations to call FM UPARU_UI_EXECUTE_SEQUENCE

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.

"SELECT single AREA FROM UPC_AREA INTO @DATA(ld_i_area).
 
"SELECT single SUBRC FROM SY INTO @DATA(ld_e_subrc).
 
 
"SELECT single PLEVEL FROM UPC_PLEVEL INTO @DATA(ld_i_plevel).
 
"SELECT single PPACKAGE FROM UPC_PACKAGE INTO @DATA(ld_i_ppackage).
 
"SELECT single BUNDLE FROM UPF_BUNDLE INTO @DATA(ld_i_sequence).
 


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!