SAP UPC_TRACE_PLANSTRUCTURE_GET Function Module for Read Plan Structure









UPC_TRACE_PLANSTRUCTURE_GET is a standard upc trace planstructure get 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 Plan Structure 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 trace planstructure get FM, simply by entering the name UPC_TRACE_PLANSTRUCTURE_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function UPC_TRACE_PLANSTRUCTURE_GET 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_TRACE_PLANSTRUCTURE_GET'"Read Plan Structure
  EXPORTING
*  I_AREA =  "Planning Area
*  I_READ_LAYOUT = ' ' "Read Layouts
*  I_READ_VARIABLE = ' ' "Read Variables
*  I_PLEVEL =  "Planning Level
*  I_PROFILE =  "Planning Profile
*  I_USE_DEFAULT =  "User's Default Profile
*  I_READ_PLEVEL = ' ' "Read Planning Levels
*  I_READ_PACKAGE = ' ' "Read Planning Packages
*  I_READ_FUNCTION = ' ' "Read Planning Functions
*  I_READ_PARAM = ' ' "Read Parameter Groups
*  I_READ_SEQUENCE = ' ' "Read Planning Sequences
.



IMPORTING Parameters details for UPC_TRACE_PLANSTRUCTURE_GET

I_AREA - Planning Area

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

I_READ_LAYOUT - Read Layouts

Data type: BOOLE-BOOLE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_READ_VARIABLE - Read Variables

Data type: BOOLE-BOOLE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_PLEVEL - Planning Level

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

I_PROFILE - Planning Profile

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

I_USE_DEFAULT - User's Default Profile

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

I_READ_PLEVEL - Read Planning Levels

Data type: BOOLE-BOOLE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_READ_PACKAGE - Read Planning Packages

Data type: BOOLE-BOOLE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_READ_FUNCTION - Read Planning Functions

Data type: BOOLE-BOOLE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_READ_PARAM - Read Parameter Groups

Data type: BOOLE-BOOLE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_READ_SEQUENCE - Read Planning Sequences

Data type: BOOLE-BOOLE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for UPC_TRACE_PLANSTRUCTURE_GET 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_AREA-AREA, "   
lv_i_read_layout  TYPE BOOLE-BOOLE, "   SPACE
lv_i_read_variable  TYPE BOOLE-BOOLE, "   SPACE
lv_i_plevel  TYPE UPC_PLEVEL-PLEVEL, "   
lv_i_profile  TYPE UPC_PROFILE-PROFILE, "   
lv_i_use_default  TYPE BOOLE-BOOLE, "   
lv_i_read_plevel  TYPE BOOLE-BOOLE, "   SPACE
lv_i_read_package  TYPE BOOLE-BOOLE, "   SPACE
lv_i_read_function  TYPE BOOLE-BOOLE, "   SPACE
lv_i_read_param  TYPE BOOLE-BOOLE, "   SPACE
lv_i_read_sequence  TYPE BOOLE-BOOLE. "   SPACE

  CALL FUNCTION 'UPC_TRACE_PLANSTRUCTURE_GET'  "Read Plan Structure
    EXPORTING
         I_AREA = lv_i_area
         I_READ_LAYOUT = lv_i_read_layout
         I_READ_VARIABLE = lv_i_read_variable
         I_PLEVEL = lv_i_plevel
         I_PROFILE = lv_i_profile
         I_USE_DEFAULT = lv_i_use_default
         I_READ_PLEVEL = lv_i_read_plevel
         I_READ_PACKAGE = lv_i_read_package
         I_READ_FUNCTION = lv_i_read_function
         I_READ_PARAM = lv_i_read_param
         I_READ_SEQUENCE = lv_i_read_sequence
. " UPC_TRACE_PLANSTRUCTURE_GET




ABAP code using 7.40 inline data declarations to call FM UPC_TRACE_PLANSTRUCTURE_GET

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 AREA FROM UPC_AREA INTO @DATA(ld_i_area).
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_read_layout).
DATA(ld_i_read_layout) = ' '.
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_read_variable).
DATA(ld_i_read_variable) = ' '.
 
"SELECT single PLEVEL FROM UPC_PLEVEL INTO @DATA(ld_i_plevel).
 
"SELECT single PROFILE FROM UPC_PROFILE INTO @DATA(ld_i_profile).
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_use_default).
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_read_plevel).
DATA(ld_i_read_plevel) = ' '.
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_read_package).
DATA(ld_i_read_package) = ' '.
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_read_function).
DATA(ld_i_read_function) = ' '.
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_read_param).
DATA(ld_i_read_param) = ' '.
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_read_sequence).
DATA(ld_i_read_sequence) = ' '.
 


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!