SAP UPC_DISP_F4 Function Module for F4 for planning objects









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

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



Function UPC_DISP_F4 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 'UPC_DISP_F4'"F4 for planning objects
  EXPORTING
*  I_NODE_TYPE =  "Node Type
*  I_AREA =  "Planning Area
*  I_PLEVEL =  "Planning Level
*  I_METHOD =  "Planning Method
*  I_DISPLAY =  "Display mode
*  I_NO_PREDEFINED_METHODS =  "Without predefined methods
*  I_PROFILE =  "Planning Profile

 IMPORTING
   E_AREA =  "Planning Area
   E_PLEVEL =  "Planning Level
   E_PACKAGE =  "Planning Package
   E_METHOD =  "Planning Function
   E_PARAM =  "Parameter group
.



IMPORTING Parameters details for UPC_DISP_F4

I_NODE_TYPE - Node Type

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

I_AREA - Planning Area

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

I_PLEVEL - Planning Level

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

I_METHOD - Planning Method

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

I_DISPLAY - Display mode

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

I_NO_PREDEFINED_METHODS - Without predefined methods

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

I_PROFILE - Planning Profile

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

EXPORTING Parameters details for UPC_DISP_F4

E_AREA - Planning Area

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

E_PLEVEL - Planning Level

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

E_PACKAGE - Planning Package

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

E_METHOD - Planning Function

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

E_PARAM - Parameter group

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

Copy and paste ABAP code example for UPC_DISP_F4 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_area  TYPE UPC_Y_AREA, "   
lv_i_node_type  TYPE UPC_Y_NODE_TYPE, "   
lv_i_area  TYPE UPC_Y_AREA, "   
lv_e_plevel  TYPE UPC_Y_PLEVEL, "   
lv_i_plevel  TYPE UPC_Y_PLEVEL, "   
lv_e_package  TYPE UPC_Y_PACKAGE, "   
lv_e_method  TYPE UPC_Y_METHOD, "   
lv_i_method  TYPE UPC_Y_METHOD, "   
lv_e_param  TYPE UPC_Y_PARAM, "   
lv_i_display  TYPE CHAR1, "   
lv_i_no_predefined_methods  TYPE CHAR1, "   
lv_i_profile  TYPE UPC_Y_PROFILE. "   

  CALL FUNCTION 'UPC_DISP_F4'  "F4 for planning objects
    EXPORTING
         I_NODE_TYPE = lv_i_node_type
         I_AREA = lv_i_area
         I_PLEVEL = lv_i_plevel
         I_METHOD = lv_i_method
         I_DISPLAY = lv_i_display
         I_NO_PREDEFINED_METHODS = lv_i_no_predefined_methods
         I_PROFILE = lv_i_profile
    IMPORTING
         E_AREA = lv_e_area
         E_PLEVEL = lv_e_plevel
         E_PACKAGE = lv_e_package
         E_METHOD = lv_e_method
         E_PARAM = lv_e_param
. " UPC_DISP_F4




ABAP code using 7.40 inline data declarations to call FM UPC_DISP_F4

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!