SAP UPC_PACKAGE_CHECK_NEW Function Module for Check package when a new one is creating
UPC_PACKAGE_CHECK_NEW is a standard upc package check new SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check package when a new one is creating 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 package check new FM, simply by entering the name UPC_PACKAGE_CHECK_NEW into the relevant SAP transaction such as SE37 or SE38.
Function Group: UPC_PACKAGE
Program Name: SAPLUPC_PACKAGE
Main Program: SAPLUPC_PACKAGE
Appliation area: R
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function UPC_PACKAGE_CHECK_NEW 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_PACKAGE_CHECK_NEW'"Check package when a new one is creating.
EXPORTING
* I_AREA = "Planning Area
* I_PLEVEL = "Planning Level
* I_PACKAGE = "Planning Package
* I_TO_AREA = "New planning area
* I_TO_PLEVEL = "New planning level
I_NEW_TECH_NAME = "Item text in trees
I_NEW_DESCRIPTION = "Item text in trees
EXCEPTIONS
ERROR_CHECK = 1
IMPORTING Parameters details for UPC_PACKAGE_CHECK_NEW
I_AREA - Planning Area
Data type: UPC_Y_AREAOptional: Yes
Call by Reference: No ( called with pass by value option)
I_PLEVEL - Planning Level
Data type: UPC_Y_PLEVELOptional: Yes
Call by Reference: No ( called with pass by value option)
I_PACKAGE - Planning Package
Data type: UPC_Y_PACKAGEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_TO_AREA - New planning area
Data type: UPC_Y_AREAOptional: Yes
Call by Reference: No ( called with pass by value option)
I_TO_PLEVEL - New planning level
Data type: UPC_Y_PLEVELOptional: Yes
Call by Reference: No ( called with pass by value option)
I_NEW_TECH_NAME - Item text in trees
Data type: UPC_Y_ITEMTEXTOptional: No
Call by Reference: No ( called with pass by value option)
I_NEW_DESCRIPTION - Item text in trees
Data type: UPC_Y_ITEMTEXTOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERROR_CHECK - Error in check
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for UPC_PACKAGE_CHECK_NEW 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_Y_AREA, " | |||
| lv_error_check | TYPE UPC_Y_AREA, " | |||
| lv_i_plevel | TYPE UPC_Y_PLEVEL, " | |||
| lv_i_package | TYPE UPC_Y_PACKAGE, " | |||
| lv_i_to_area | TYPE UPC_Y_AREA, " | |||
| lv_i_to_plevel | TYPE UPC_Y_PLEVEL, " | |||
| lv_i_new_tech_name | TYPE UPC_Y_ITEMTEXT, " | |||
| lv_i_new_description | TYPE UPC_Y_ITEMTEXT. " |
|   CALL FUNCTION 'UPC_PACKAGE_CHECK_NEW' "Check package when a new one is creating |
| EXPORTING | ||
| I_AREA | = lv_i_area | |
| I_PLEVEL | = lv_i_plevel | |
| I_PACKAGE | = lv_i_package | |
| I_TO_AREA | = lv_i_to_area | |
| I_TO_PLEVEL | = lv_i_to_plevel | |
| I_NEW_TECH_NAME | = lv_i_new_tech_name | |
| I_NEW_DESCRIPTION | = lv_i_new_description | |
| EXCEPTIONS | ||
| ERROR_CHECK = 1 | ||
| . " UPC_PACKAGE_CHECK_NEW | ||
ABAP code using 7.40 inline data declarations to call FM UPC_PACKAGE_CHECK_NEW
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