SAP UPC_PACKAGE_READ Function Module for Read
UPC_PACKAGE_READ is a standard upc package read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read 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 read FM, simply by entering the name UPC_PACKAGE_READ 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_READ 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_READ'"Read.
EXPORTING
I_AREA = "Planning Area
I_PLEVEL = "Planning Level
IMPORTING
ET_CHILDREN = "Alle levels for Area
ET_MESG = "Messages
IMPORTING Parameters details for UPC_PACKAGE_READ
I_AREA - Planning Area
Data type: UPC_Y_AREAOptional: No
Call by Reference: No ( called with pass by value option)
I_PLEVEL - Planning Level
Data type: UPC_Y_PLEVELOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for UPC_PACKAGE_READ
ET_CHILDREN - Alle levels for Area
Data type: UPC_YT_CHILDRENOptional: No
Call by Reference: Yes
ET_MESG - Messages
Data type: UPC_YT_MESGOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for UPC_PACKAGE_READ 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_et_children | TYPE UPC_YT_CHILDREN, " | |||
| lv_et_mesg | TYPE UPC_YT_MESG, " | |||
| lv_i_plevel | TYPE UPC_Y_PLEVEL. " |
|   CALL FUNCTION 'UPC_PACKAGE_READ' "Read |
| EXPORTING | ||
| I_AREA | = lv_i_area | |
| I_PLEVEL | = lv_i_plevel | |
| IMPORTING | ||
| ET_CHILDREN | = lv_et_children | |
| ET_MESG | = lv_et_mesg | |
| . " UPC_PACKAGE_READ | ||
ABAP code using 7.40 inline data declarations to call FM UPC_PACKAGE_READ
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