Fiscal Year Planning
With this function, you can define and display data in fiscal year format and therefore use the fiscal year variant for planning a fiscal year. In case planning data is being imported from the SAP ERP system by linking a portfolio item to a PS project element, the fiscal year variant used for the PS project element and the portfolio item must be same.
If you use several Controlling areas, for example if you have connected several SAP ERP systems, then you only can import into the portfolio if the fiscal year variants of the Controlling areas are equal.
You can customize the fiscal year periods and each period can have different number of days. Hence the number of days for a period is read from Customizing. You can maintain a fiscal year variant for a portfolio type in Customizing.
Note
In the front end, you can only display the fiscal year variant defined for a portfolio.
To use fiscal year planning, you have switched on the following:
in Customizing for SAP Portfolio and Project Management
under .
in Customizing for SAP Portfolio and Project Management
under .
Note
If you have not activated the fiscal year in the SAP Portfolio and Project Management system but it is activated in the SAP ERP system, the system maps the calendar year to the fiscal year.
If you would like to use a default fiscal year variant for processing, you must have set the value in Customizing for SAP Portfolio and Project Management
under .
You defined fiscal year variants in Customizing for SAP Portfolio and Project Management
under .
Note
Portfolio Management supports fiscal year variants with 12 periods. These periods can start on any day of the month.
You defined the fiscal year variant that is used, on the portfolio level in Customizing for SAP Portfolio and Project Management
under .
Note
During the import of values from underlying SAP ERP systems, an error occurs when an item is linked to an object that has a different fiscal year variant than the fiscal year variant defined in the portfolio.
For financial and capacity planning, the following period breakdown according to the fiscal year definition is supported, whereas the following rules apply:
Breakdown |
Overall Planning Period |
Displayed Columns without |
Displayed Columns with |
|---|---|---|---|
Annually |
12 periods defined for a fiscal year variant |
2007 |
2007 |
Monthly |
Period Breakdown |
Jan 2007, Feb 2007 |
P12 2006, P1 2007 |
Quarterly |
1 Quarter = 3 Periods |
Jan-Mar 2007 |
P1-3 2007 |
Biennially |
24 periods |
2007-2008 |
2007-2008 |
Bi-Monthly |
2 Periods |
Jan-Feb 2007 |
P12-P1 2007 |
Every Five Years |
5x12 Periods |
2007-2011 |
2007-2011 |
Every Four Years |
4x12 Periods |
2007-2010 |
2007-2010 |
Every Three Years |
3x12 Periods |
2007-2009 |
2007-2009 |
Semi-Annual |
6 Periods |
Jan-June 2007 |
P1-6 2007 |
Note
If you have defined a period text for a fiscal year variant then the system displays that text in the column.
If you have activated the fiscal year planning, the year-to-date values represent the values from the first periods (P1) of the current fiscal year until the current period.
If you have activated the fiscal year planning, the system uses one exchange rate per period during the import from SAP ERP. To determine the exchange rate, the system uses the first day of the period.
If you have switched on the switch , you must use the /RPM/MIGRATION_CAL_TO_FISCAL report to transfer the values from calendar year format to fiscal year format.
If you want to copy the fiscal year variants from the SAP ERP system, you can use the /RPM/FISCAL_VARIANT_COPY report.