Hierarchy
CPRXRPM (Software Component) SAP Portfolio and Project Management 6.0⤷
PPM-PFM (Application Component) Portfolio Management⤷
/RPM/CONFIGURATION (Package) xRPM Configuration
Basic Data
| Data Element | /RPM/TV_CAP_VIEW |
| Short Description | Capacity View Type |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | /RPM/CAP_VIEW_TYPE | |
| Data Type | NUMC | Character string with only digits |
| Length | 2 | |
| Decimal Places | 0 | |
| Output Length | 2 | |
| Value Table | /RPM/CAP_VIEW |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Cap. view |
| Medium | 18 | Cap. View Type |
| Long | 18 | Capacity View Type |
| Heading | 18 | Capacity View Type |
Documentation
Definition
A view in capacity planning defines the type of values that are stored for the capacity planning at capacity group level.
A capacity view controls the data coming into the item, bucket, item of initiative, or initiative object. The data can be either integration or a manual entry for an item. It can also be manual or a rollup for the item of initiative.
Use
You can define multiple types of values that the system stores in capacity planning to achieve a better overview of the overall planning at different object levels.
Dependencies
Example
For the capacity category Developer and the capacity group ABAP, you can assign the following types of required capacity that are maintained for the ABAP developer:
- Planned
- Forecasted
- Actuals
You can configure these types using capacity view types.
Supplementary Documentation - /RPM/TV_CAP_VIEW0001
Use
This is a view available for a portfolio item but not for an item within an initiative.
If and when an item within an initiative becomes a portfolio item (standalone item) by being moved from under an initiative, it is possible that a particular view of this item within an initiative is not available in the portfolio item. In this case the amounts maintained in this view are lost during this conversion. If you maintain the Source/Target of Data for the item within an initiative, the amounts are carried over from the original item within an initiative view to the view maintained as Source/Target of Data thus preventing any data loss.
The Source/Target of Data works the other way round as well, that is, when portfolio items become items within an initiative by being moved under an initiative. If you maintain the Source/Target of Data for the item within an initiative, then the amounts from this Source/Target of Data view are carried over to the corresponding item within an initiative view on which this Source/Target of Data is maintained.
Dependencies
Example
History
| Last changed by/on | SAP | 20141109 |
| SAP Release Created in | 400 |
