Changing Names of Months

Period names are displayed many places in PPM (see Scope of Changes to Fiscal Periods), as in the table heading rows in the example in Figure 2-1. Example of period names (part of a financial summary), where the names of the quarters are Q1 2013, Q2 2013, and Q3 2013, and the names of the months are Jan 13, Feb 13, and so on.

Figure 2-1. Example of period names

To change the specific long and short names that are displayed for each of the twelve months of the year, before you run the script to add periods, you modify the periods_<language>.conf language configuration files as desired for each installed language. The script refers to these configuration files as it generates periods.

When the script is run to generate periods after you change any language configuration files, the changes are applied to all previously generated periods and to the new periods the script generates. For information about the affected functions in PPM, see Scope of Changes to Fiscal Periods.

Note: This procedure applies to non-retail calendars, where each fiscal year has twelve Gregorian calendar months and starts on the first day of the same particular month each year.

To support retail calendars, which do not have these limitations, the configuration file for each language includes long and short names for configurable periods (for English, LONG_NAME_PERIOD_1 through LONG_NAME_PERIOD_12, and SHORT_NAME_PERIOD_1 through SHORT_NAME_PERIOD_12). These period names are not to be used in this procedure. For more information about retail calendars, see Generating Periods for Retail Calendars.

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

To change the names of the months for a language:

  1. Open the periods_<language>.conf configuration file for the language in the <PPM_Home>/conf/fiscal directory. See the System Requirements and Compatibility Matrix for supported languages and the language code to use in the file name periods_<language>.conf.

    Caution: Do not delete any of the parameters in the periods_<language>.conf file or change their names. Change only their values, as needed.

  2. Copy and paste the set of names to be changed, then comment out the original set by typing # at the beginning of each line.

  3. Change the names of each month as desired.

    For example, using the English configuration file periods_en.conf, if you want long names for months to be in all capital letters rather than the default mixed case, and you want short names to have a period at the end, change the copied lines for each month to the following:

    LONG_NAME_MONTH_1=JANUARY
    LONG_NAME_MONTH_2=FEBRUARY 
       .
       .
       .
    LONG_NAME_MONTH_12=DECEMBER
    SHORT_NAME_MONTH_1=Jan.
    SHORT_NAME_MONTH_2=Feb.
       .
       .
       .
    SHORT_NAME_MONTH_12=Dec.
  4. Save and close the periods_<language>.conf configuration file.

  5. We recommend that you perform step 1 through step 4 each configured language at this time, changing the month names as desired.

    However, any time after you run the script to add the periods, you can update the language configuration files and run the script with the -language argument to change existing month names for the language or languages you specify. For more information, see Generating Periods in Additional Languages.

  6. 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.