Shifting the Starting Month of Fiscal Years

If your company's fiscal year does not start on January 1, you can run the script to change the starting month for previously generated years and for years to be generated later, so that all years match the fiscal year. Usually, this procedure will need to be performed only once, if at all. For information about the affected functions in PPM, see Scope of Changes to Fiscal Periods.

Note: If any of the fiscal months in your fiscal year do not begin on the first day of the month, use the procedure in Generating Periods for Retail Calendars to configure the months.

Note: This procedure changes period data in the database. We recommend that you back up the configuration file before modifying it.

To change the starting month for fiscal years:

  1. Open the periods.conf configuration file in the <PPM_Home>/conf/fiscal directory. (The parameters in this file apply to all languages.)

  2. Change the START_MONTH parameter to a number that represents the month the fiscal year starts, for example 11 for November.

  3. Set the IS_START_MONTH_FOR_NEXT_FISCAL_YEAR parameter to true or false according to the relationship between fiscal years and calendar years, as follows:

    If the redefined start month starts the fiscal years that are given the same numbers as the following calendar years, for example, if November is the redefined start month and November 2009 is the start of fiscal year 2010, set the IS_START_MONTH_FOR_NEXT_FISCAL_YEAR parameter to true. In this example, if periods for only year 2010 have been generated, the script does the following:

    • Shifts fiscal year 2010 to cover November 2009 through October 2010.

    • Generates a complete fiscal year 2011 from November 2010 through October 2011, retaining the previously generated months of November and December 2010 (including their monthly data, if any).

    • Shifts the quarters of fiscal year 2010 (FY2010), as follows:

      • Q1 of FY2010 becomes November 2009 through January 2010.

      • Q2 of FY2010 becomes February 2010 through April 2010.

      • Q3 of FY2010 becomes May 2010 through July 2010.

      • Q4 of FY2010 becomes August 2010 through October 2010.

    If the redefined start month starts the fiscal years that are given the same numbers as the current calendar years, for example, if March is the redefined start month and March 2010 is the start of fiscal year 2010, set the IS_START_MONTH_FOR_NEXT_FISCAL_YEAR parameter to false. In this example, if periods for only year 2010 have been generated, the script does the following:

    • Shifts fiscal year 2010 to cover March 2010 through February 2011.

    • Generates a complete fiscal year 2009 from March 2009 through February 2010, retaining the previously generated months of January and February 2010 (including their monthly data, if any).

    • Shifts the quarters of fiscal year 2010 (FY2010) as follows:

      • Q1 of FY2010 becomes March 2010 through May 2010.

      • Q2 of FY2010 becomes June 2010 through August 2010.

      • Q3 of FY2010 becomes September 2010 through November 2010.

      • Q4 of FY2010 becomes December 2010 through February 2011.

    If more than one year has been previously generated, similar changes are made to periods of all the years to ensure that each fiscal year is complete and that all previously generated periods are included in a fiscal year.

  4. Save and close the periods.conf configuration file.

  5. On the PPM Server, navigate to the directory that contains the kGenFiscalPeriods.sh script:

    cd <PPM_Home>/bin

    where <PPM_Home> represents the path where your PPM instance is installed.

  6. Run the following script:

    sh ./kGenFiscalPeriods.sh shift

    Note: Do not attempt to simultaneously generate additional periods and use the shift option in the script.

    The script saves the revised set of periods in a preview file fiscal_periods_<time stamp>.csv in the <PPM_Home>/bin/fiscal/output directory for you to verify before you commit the periods to the database.

  7. Verify that the periods listed in the preview file are appropriate.

  8. When you are satisfied with the data in the preview file, run the script again with the shift and commit options to apply your changes to the database.

    When the script is run to generate periods after you change the periods.conf configuration file, the new starting month applies to all previously generated fiscal years and to new fiscal years the script generates. (Do not use the shift option in the script when you generate periods.)

    The adjusted fiscal years and quarters apply to displays of financial data in all languages.

  9. Return to Introduction to the Script and Associated Configuration Files to determine whether you need to change configuration files further. If not, go to Generating Periods.