SAP UPC_FW_START Function Module for Start of the planning framework

Search SAP Function Modules

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

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

Function UPC_FW_START 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_FW_START'"Start of the planning framework
  EXPORTING
*  I_PROFILE =  "Initial planning profile
*  I_FW_CALL =  "Call from FW
*  I_NODE_TYPE =  "Node Type
*  I_AREA =  "Planning Area
*  I_PLEVEL =  "Planning Level
*  I_PACKAGE =  "Planning Package
*  I_METHOD =  "Planning Function
*  I_PARAM =  "Parameter group
*  I_FCODE =  "Initial fcode for INIT module
*  I_HIDE_TREES =  "Show or hide navigation

 IMPORTING
   E_TR_DATA_CHANGED =  "Flag if transactional data have been changed

TABLES
*  ET_MESG =  "Messages

EXCEPTIONS
   OBJECT_NOT_EXISTING = 1    PROFILE_NOT_EXISTING = 2    ERROR_INIT = 3 

.

IMPORTING Parameters details for UPC_FW_START

I_PROFILE - Initial planning profile

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

I_FW_CALL - Call from FW

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

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_PACKAGE - Planning Package

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

I_METHOD - Planning Function

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

I_PARAM - Parameter group

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

I_FCODE - Initial fcode for INIT module

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

I_HIDE_TREES - Show or hide navigation

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

EXPORTING Parameters details for UPC_FW_START

E_TR_DATA_CHANGED - Flag if transactional data have been changed

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

TABLES Parameters details for UPC_FW_START

ET_MESG - Messages

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

EXCEPTIONS details

OBJECT_NOT_EXISTING - Planning object does not exist

Data type:
Optional: No
Call by Reference: Yes

PROFILE_NOT_EXISTING - Profile does not exist

Data type:
Optional: No
Call by Reference: Yes

ERROR_INIT - Error in init module

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for UPC_FW_START 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.

ABAP code using 7.40 inline data declarations to call FM UPC_FW_START

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