Hi Vijaya,
The PDS data is stored in a database cluster structure which is quite difficult to navigate outside the debugger.
The easiest way to see the PDS data exactly as stored in the system via debugging is:
1) Set a breakpoint at Method GET_CLUSTER_PPE FROM, from Class /SAPAPO/CL_PDS_DB_CLUSTER_PPE, statement below:
IMPORT hirachy TO ls_ppds_data->hirarchy
hir_type TO ls_ppds_data->hirarchy_type
FROM DATABASE /sapapo/cullindx(pv)
ID iv_cluster_id.
2) Execute transaction /SAPAPO/CURTO_SIMU and display the details for a PDS. When the breakpoint is reached, you will be at callstack below:
26 METHOD GET_CLUSTER_PPE /SAPAPO/CL_PDS_DB_CLUSTER_PPE=CP
25 METHOD /SAPAPO/IF_PDS_DB~GET_CLUSTER /SAPAPO/CL_PDS_DB_PPDS========CP
24 METHOD GET_CLUSTER /SAPAPO/CL_CURTO_DB===========CP
23 METHOD CONSTRUCTOR /SAPAPO/CL_PDS_DATA_PPE=======CP
22 METHOD CONSTRUCTOR /SAPAPO/CL_PDS_BUFFER_PPDS====CP
21 METHOD GET_SINGLE_PDS /SAPAPO/CL_PDS_BUFFER_OBJ=====CP
3) Press F6 to execute the IMPORT statement. At this point, the PDS data was imported from the database into structure ls_ppds_data->hirarchy and can be navigated.
4) The Capacity Requirements, specifically, can be seen by navigating the structure until you reach point below:
LS_PPDS_DATA->HIRARCHY-ADD_APPLICTN_DATA[1]-MODES[1]-BODY-CAP_REQS
--> You can see, for example, what are the fixed and variable time-continous and bucket capacity consumptions.
Regards,
Tiago