Introduction to the Script and Associated Configuration Files

You run the kGenFiscalPeriods.sh script to add sets of periods for a range of years you specify. The periods can cover dates in the past, in the future, or both.

Note: For your convenience, PPM version 9.50 provides a set of fiscal periods in the system default language for the years 1998–2018. Each fiscal year begins on January 1.

Note: The periods used in time sheets in Time Management are independent of the configuration of periods described in this document.

Before running the script, you can optionally modify the following configuration files the script uses as it generates periods:

  • periods.conf configuration file, which specifies the following for Gregorian calendars:

    • Start month of fiscal years (for all supported languages). For information about changing the start month of fiscal years, see Shifting the Starting Month of Fiscal Years.

    • Start day of each week (for all supported languages), which is used in the Analyze Cumulative Cost Metrics page and portlet in Financial Management. For information about changing the start day of each week, see Changing the Start Day of Weeks.

      Caution: If you need to change the start day of the week from its default (Sunday) for a new installation of PPM, you must change it before generating any periods and you must retain the new setting thereafter. See Changing the Start Day of Weeks.

  • For each language installed in PPM, a separate language configuration file named periods_<language>.conf. For example:

    • periods_en.conf is the language configuration file for English.

    • periods_de.conf is the language configuration file for German.

    • periods_ko.conf is the language configuration file for Korean.

    In each language configuration file, you can optionally change the following:

    • Default long and short names of the months that appear in that language in PPM. For more information, see Changing Names of Months.

    • Default long and short formats of the periods—years, quarters, months, and weeks—that appear in that language in PPM. For more information, see Changing Formats of Periods.

  • For standard or non-standard retail calendars only, a .csv file in which you specify the date ranges for all the periods. For more information, see Generating Periods for Retail Calendars.

In addition, so that users see period names in PPM in the language they select when they log in, you use the script to establish ongoing generation of periods for some or all languages that are installed in PPM (other than the system default language). First, you change the language configuration files for the new languages for which you want to generate periods. Then you run the script with an argument that specifies the new languages, which generates periods for them that span the same time range as the existing periods for other languages. Thereafter, specifying a range of years when you run the script generates new periods for that range in all the languages that now have periods established. For information about enabling the display of periods in new languages, see Generating Periods in Additional Languages.

Before generating new periods, configure the periods.conf and periods_<language>.conf files as needed (see the following sections). If you do not need to modify any of these files, go to Generating Periods.

For more information about using multiple languages in a single installation of PPM, see the Multilingual User Interface Guide.