Work with fiscal periods
You can use the standard interface to generate fiscal periods that reflect your organization's fiscal calendar. You can also add translations of fiscal period names, shift existing fiscal periods, and import and export fiscal periods.
Generate fiscal periods
This section provides details on how to generate fiscal periods from the standard interface.
To generate fiscal periods from the standard interface:
-
Click the Administration button from the masthead.
-
From the Administration menu, select Financial Management> Generate fiscal periods.
-
In the Generate fiscal periods area, select the Generate option.
-
In the Start Year and End year fields, type the starting and ending years for the fiscal periods you want to generate.
The fiscal periods are generated, and all existing fiscal periods (for all period types) are listed on the page.
Note: If a gap exists between the latest existing fiscal period year and the starting year you specify, the fiscal periods for all of the intervening years are generated.
-
To persist the generated fiscal periods, click Commit.
-
To implement your changes, stop and then restart the servers. For details on how to stop and start servers, see Start and stop the PPM Server on a single-server system.
Shift existing fiscal periods
From the Generate fiscal periods page, you can also do the following:
-
Change the starting day of the week (START_DAY_OF_WEEK) of your organization's fiscal year.
-
Change the starting month (START_MONTH and START_MONTH_FOR_NEXT_FISCAL_YEAR) of your organization's fiscal year.
The changes you make apply to existing fiscal periods as well as to fiscal periods to be generated later, so that all fiscal periods match the fiscal year.
Note: Shifting fiscal periods changes period data in the database. It is recommended that you back up the configuration file before you perform this procedure. For information about how shifting fiscal periods affect functionality in PPM Center, see Generate fiscal periods.
To shift existing fiscal periods from the Generate fiscal periods page:
-
Open the periods.conf file in a text editor. The periods.conf file is located in the
<PPM_Home>/conf/fiscal
directory. -
To change the starting month, change the START_MONTH parameter value to the number that represents the month the fiscal year starts. For example, you would use 11 to represent November.
Note: For detailed information about how to set values for the parameters in the periods.conf file, see Generate fiscal periods.
-
To change the starting month of your organization's fiscal year, set the IS_START_MONTH_FOR_NEXT_FISCAL_YEAR parameter value to true or false, depending on the relationship between fiscal years and calendar years.
Note: The default value of false indicates that the start month does not belong to the next fiscal year.
-
To change the starting day of the week, set the START_DAY_OF_WEEK parameter to a number between 1 and 7, with 1 representing Sunday, and 7 representing Saturday.
-
Save and close the periods.conf configuration file.
-
On the Generate fiscal periods page, select the Shift option.
-
Click Submit.
The existing fiscal periods are shifted and all fiscal periods (for all period types) are listed on the page.
-
To persist the shifted fiscal periods, click Commit.
-
To implement your changes, restart the nodes.
Note: The adjusted fiscal periods apply to the display of financial data in all languages.
Import and export fiscal periods
From the Generate fiscal periods page, you can import modified period definitions to the server and export current fiscal period definitions from the server to a specific file.
To import the modified period definitions:
- On the Generate fiscal periods page, select the Import option.
-
Click Browse, and then go to and select the
<Period_Definitions_Filename>.csv
period definition file from which you want to copy fiscal period definitions. -
Click Submit.
The imported fiscal periods are listed in the right pane.
-
To persist the imported fiscal periods, click Commit.
-
To implement your changes, stop and then restart the server.
To export current fiscal period definitions to a specific file:
-
On the Generate fiscal periods page, select the Export option.
-
In the File box, type the name of the
<Period_Definitions_Filename>.csv
file to which you want to copy fiscal period definitions. -
Click Submit.
The Exported Periods tab lists the fiscal periods to be exported.
-
Click Export to File.
-
In the File Download dialog box, click Save.
-
Go to the PPM Server directory in which you want to store the file, and the save the file.
Note: On the PPM Server, the default directory for the fiscal periods definition file is
<PPM_Home>/bin/fiscal/output.
-
Check the directory you specified and verify that it now contains the file you exported.
Note: For information about how to use the kGenFiscalPeriods.sh script to export fiscal period definitions, see Generate fiscal periods.
Generate translations for fiscal periods
You can use the Generate fiscal periods page to generate translations for fiscal periods in any of the languages installed on the application. Month names and period formats are as specified in the language configuration files. After you generate the translations, users can view the fiscal periods in the session language they selected at logon. The translated periods cover the same time span as the periods covered for existing languages.
To generate translations of fiscal periods in any languages installed on the application:
-
On the Generate fiscal periods page, select the Generate translations option.
-
In the Languages list, select one or more of the languages.
Tip: Use the
Ctrl
key or theShift
key to select multiple languages. -
Click Submit. A tab listing translated periods is added for each added language.
-
To persist the added translations, click Commit.
-
To implement your changes, stop and then restart the servers.
Note: For information about how to use the kGenFiscalPeriods.sh script to create periods for languages installed on a OpenText PPM instance, see Generate fiscal periods. For information about using multiple languages on a single instance of OpenText PPM, see Multilingual User Interface.
See also: