SAP UPP_PLAN_INIT Function Module for Planning: Initialization of the detail application









UPP_PLAN_INIT is a standard upp plan init SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Planning: Initialization of the detail application 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 upp plan init FM, simply by entering the name UPP_PLAN_INIT into the relevant SAP transaction such as SE37 or SE38.

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



Function UPP_PLAN_INIT 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 'UPP_PLAN_INIT'"Planning: Initialization of the detail application
EXPORTING
I_FCODE = "Function Code
I_AREA = "Planning Area
I_PLEVEL = "Planning level
I_PACKAGE = "
I_METHOD = "Planning Method
I_PARAM = "parametrization
* I_DO_NOT_FREE_PREV_INST = "Single-Character Flag
* I_FB_GET_OK_CODE = "FM, to read framework ok code

IMPORTING
E_REPID = "master program of the screens
E_DYNNR = "dynpro number of the screen
ET_MESG = "Message Table
E_PP_HNDL = "Planningprocessor: Handle for context

EXCEPTIONS
ERROR_INIT = 1
.



IMPORTING Parameters details for UPP_PLAN_INIT

I_FCODE - Function Code

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

I_AREA - Planning Area

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

I_PLEVEL - Planning level

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

I_PACKAGE -

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

I_METHOD - Planning Method

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

I_PARAM - parametrization

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

I_DO_NOT_FREE_PREV_INST - Single-Character Flag

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

I_FB_GET_OK_CODE - FM, to read framework ok code

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

EXPORTING Parameters details for UPP_PLAN_INIT

E_REPID - master program of the screens

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

E_DYNNR - dynpro number of the screen

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

ET_MESG - Message Table

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

E_PP_HNDL - Planningprocessor: Handle for context

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

EXCEPTIONS details

ERROR_INIT - Init error

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for UPP_PLAN_INIT 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_e_repid  TYPE SY-REPID, "   
lv_i_fcode  TYPE SY-UCOMM, "   
lv_error_init  TYPE SY, "   
lv_i_area  TYPE UPC_Y_AREA, "   
lv_e_dynnr  TYPE SY-DYNNR, "   
lv_et_mesg  TYPE UPC_YT_MESG, "   
lv_i_plevel  TYPE UPC_Y_PLEVEL, "   
lv_e_pp_hndl  TYPE UPP_Y_PP_HNDL, "   
lv_i_package  TYPE UPC_Y_PACKAGE, "   
lv_i_method  TYPE UPC_Y_METHOD, "   
lv_i_param  TYPE UPC_Y_PARAM, "   
lv_i_do_not_free_prev_inst  TYPE CHAR1, "   
lv_i_fb_get_ok_code  TYPE RS38L_FNAM. "   

  CALL FUNCTION 'UPP_PLAN_INIT'  "Planning: Initialization of the detail application
    EXPORTING
         I_FCODE = lv_i_fcode
         I_AREA = lv_i_area
         I_PLEVEL = lv_i_plevel
         I_PACKAGE = lv_i_package
         I_METHOD = lv_i_method
         I_PARAM = lv_i_param
         I_DO_NOT_FREE_PREV_INST = lv_i_do_not_free_prev_inst
         I_FB_GET_OK_CODE = lv_i_fb_get_ok_code
    IMPORTING
         E_REPID = lv_e_repid
         E_DYNNR = lv_e_dynnr
         ET_MESG = lv_et_mesg
         E_PP_HNDL = lv_e_pp_hndl
    EXCEPTIONS
        ERROR_INIT = 1
. " UPP_PLAN_INIT




ABAP code using 7.40 inline data declarations to call FM UPP_PLAN_INIT

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 REPID FROM SY INTO @DATA(ld_e_repid).
 
"SELECT single UCOMM FROM SY INTO @DATA(ld_i_fcode).
 
 
 
"SELECT single DYNNR FROM SY INTO @DATA(ld_e_dynnr).
 
 
 
 
 
 
 
 
 


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!