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_FIN_VIEW |
| Short Description | Financial View Type |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | /RPM/FIN_VIEW_TYPE | |
| Data Type | NUMC | Character string with only digits |
| Length | 2 | |
| Decimal Places | 0 | |
| Output Length | 2 | |
| Value Table | /RPM/FIN_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 | Fin. View |
| Medium | 13 | Fin View Type |
| Long | 19 | Financial View Type |
| Heading | 20 | Financial View Type |
Documentation
Definition
A view in financial planning defines the type of values being stored for the financial planning at the financial group level.
A financial view controls the data that comes into the item/bucket/item of initiative/initiative object, as follows:
The item or the item of initiative process can be either Integration or Manual.
The bucket and the initiative process can be either Rollup or Manual.
Use
You can define multiple types of values that the system stores in financial planning to achieve a better overview of the overall planning at different object levels.
Dependencies
Example
For the financial category Revenues and the financial group Maintenance, you can assign the following types:
- Forecasted Costs
- Actual Costs
- Planned Costs
You can configure these types using financial view types.
Supplementary Documentation - /RPM/TV_FIN_VIEW0000
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 |
