26 Appendix E: Fiscal Year Information

Oracle Financial Services Analytical Applications (OFSAA) support both calendar year (January to December) and fiscal year configurations. If your organization operates on a fiscal year calendar, this appendix documents how to configure your fiscal year within OFSAA and how a fiscal year configuration affects processes that insert into or update the table. Note that in the context of this appendix, a fiscal year denotes a non-calendar financial year (that is, a year that does not contain 12 months and/or does not begin in January and end in December).

This appendix covers the following topics:

·       Configuring a Fiscal Year

·       How YTD Calculations Are Affected by a Fiscal Year Configuration

·       Examples of Calendar Year and Fiscal Year Configurations

·       Using the Undo Function with a Fiscal Year Configuration

Configuring a Fiscal Year

For a  setup, Fiscal year configuration data is held in FSI_FISCAL_YEAR_INFO, a special one-row, two-column table. This table is seeded with values corresponding to a standard 12-month, January to December calendar year. For a Management Ledger setup, Fiscal year configuration data is held in 'LEDGER_CCY_AND_FISCAL_YR_INFO'. If the Users fail to populate the aforesaid table but do populate the FSI_FISCAL_YEAR_INFO, this table acts as a fall back source for the Management Ledger/s.

If your organization operates on a fiscal year basis, the values in this table should be updated at the time OFSAA is installed. In the FSI-FISCAL-YEAR-INFO / LEDGER_CCY_AND_FISCAL_YR_INFO table, the values in the Fiscal-Period and Start-Month columns determine the duration and beginning month of your financial year, respectively. All application processes that insert into, update, or delete from the  table read the configuration data in FSI-FISCAL-YEAR-INFO / LEDGER_CCY_AND_FISCAL_YR_INFO to properly maintain the 12 month-to-date and the 12 year-to-date columns in .

Fiscal-Period Column

This column holds a value that represents the duration of the financial year in months. For a calendar year, this value is always 12 months. For a fiscal year, this value is typically 12 but it may have a different value. Fiscal year configurations give you the flexibility to set shorter financial periods within a 12-month period. For example, if your organization has two 6-month fiscal periods over a 12-month span, then the value in this column would be 6.

For Oracle Financial Services Analytical Applications, the default setting is a calendar year and the value in the fiscal period column is 12. If you set your fiscal period to any value other than 12, the system automatically treats this setting as a fiscal year configuration. Valid fiscal periods include 1, 2, 3, 4, 6, or 12 months. Note that fiscal period values of other than 1, 2, 3, 4, 6, or 12 months are not supported and will cause application runtime errors.

Start-Month Column

This column holds a value that represents the first month of your financial year. Calendar years, which always begin in January, have a Start Month value of 1. Start month would have a value of 3 if your fiscal year were to begin in March and a value of 7 if your fiscal year were to begin in July.

For Oracle Financial Services Analytical Applications, the default setting is a calendar year so the starting month value is 1. Note that starting month values of less than 1 or greater than 12 are not supported and will cause application runtime errors.

How YTD Calculations Are Affected by a Fiscal Year Configuration

The  table contains each of your Key Processing dimensions, several administrative columns that are also components of the table's primary key, and 24 “fact” columns (balance columns). The first 12 fact columns (MTD-01 to MTD-12) contain monthly balances; the next 12 fact columns (YTD-01 to YTD-12) contain year-to-date balances. When you are running a standard calendar year configuration, MTD_01 corresponds to January data and MTD_12 corresponds to December data. If, however, your Start-Month column was set to 9 (indicating that your fiscal year begins in September), then the MTD_01 in  would correspond to September, and MTD_12 would correspond to August.

Year-to-date calculations begin at the start date of the fiscal period rather than January of the year in which the calculations are performed. For example, if July were the start date for your organization's fiscal period, and if you were to load General Ledger data to for July, August, and September, then the YTD_03 column would contain fiscal year-to-date data for September, the 3rd month of your fiscal year. In addition to the  load process, every OFSAA process that interacts with  will reference FSI-FISCAL-YEAR-INFO/ LEDGER_CCY_AND_FISCAL_YR_INFO to properly maintain both the month columns and the YTD columns.

This is an important consideration for the following calculations:

·       Allocation rules that insert into or update the table.

·       The allocation UNDO process that performs updates or deletes from.

·       Loading data into through the OFSAA Ledger Data Loader utility (For more details, see the Ora­cle Financial Services Data Model Utilities User Guide).

·       Transfer pricing rate migration from instrument tables to the table through OFSAA Transfer Pricing.

·       Direct transfer pricing of the table through OFSAA Transfer Pricing.

Examples of Calendar Year and Fiscal Year Configurations

The following examples demonstrate different configurations in the FSI-FISCAL-YEAR-INFO / LEDGER_CCY_AND_FISCAL_YR_INFO table and show how these configurations affect application functionality involving inserts into, updates of, or deletions from the table.

Using a Calendar Year Configuration

Under the default calendar year configuration, the FSI-FISCAL-YEAR-INFO/ LEDGER_CCY_AND_FISCAL_YR_INFO table contains a Fiscal Period value of 12 and a Start Month value of 1. For the following calendar year example, calendar months for 2011 correspond to the monthly buckets as shown in the following table:

If you have set your As-of-Date to June 2011, then any OFSAA process that addresses will:

·       Set or re-set the MTD_06 column (updates and inserts)

·       Set or re-set YTD_01 to YTD_12 (updates, inserts, and deletes)

Continuing with this calendar year example, the 12 YTD buckets correspond to 2011 calendar month ranges as shown in the following table:

For details on the relationships between Month-to-Date columns and Year-to-Date columns, see Appendix A: Management Ledger.

Using a Fiscal Year Configuration with a 12-Month Duration

In this example, the FSI-FISCAL-YEAR-INFO/ LEDGER_CCY_AND_FISCAL_YR_INFO table holds the following values:

·       Start Month = 4

·       Fiscal Period = 12

Since the fiscal period in this example is 12 months long so we can refer to the fiscal period as a fiscal year. In this fiscal year example, the months for the fiscal year correspond to monthly buckets as shown in the following table:

For this fiscal year example, the first calendar month of the 2011 fiscal year is April 2011, and the last calendar month of the 2011 fiscal year is March 2012. Note that all business data for the fiscal year 2011 is stored in where every row has the same YEAR-S value of 2011. If you were to set your As-of-Date to January 31, 2012, and then execute an allocation rule that output to , the allocation engine would write its month-to-date results to the MTD-10 column with YEAR-S equal to 2011.

Continuing with this fiscal year example, the 12 YTD buckets correspond to 2011 fiscal year YTD ranges as shown in the following table:

For details on the relationships between Month-to-Date columns and Year-to-Date columns, see Appendix H: Financial Element Aggregation Methods.

Using a Fiscal Year Configuration with a 6-Month Duration

In this example, the FSI-FISCAL-YEAR-INFO/ LEDGER_CCY_AND_FISCAL_YR_INFO table holds the following values:

·       Start Month = 4

·       Fiscal Period = 6

Since in this example the Fiscal Period is 6, we are no longer dealing with a Fiscal Year, but with two fiscal periods within a 12-month time span. In this fiscal period example, there are two 6-month fiscal periods within the 12-month window beginning April 2011. Just as in the previous 12-month fiscal year example, the months for the two fiscal periods correspond to monthly buckets as shown in the following table:

Continuing with this fiscal period example, the 12 YTD buckets correspond to the two 2011 fiscal period YTD ranges (actually, fiscal period-to-date ranges) as shown in the following table:

Note that in this fiscal period example:

·       The first calendar month of the first fiscal period is April 2011

·       The last calendar month of the first fiscal period is September 2011

·       The first calendar month of the second fiscal period is October 2011

·       The last calendar month of the second fiscal period is March 2012

Also note that, as in the previous fiscal year example, all business data for this two fiscal-period example is stored in where every row has the same YEAR-S value of 2011. If you were to set your As-of-Date to January 31, 2012, and then execute an allocation rule that output to , the allocation engine would write its month-to-date results to the MTD-10 column with YEAR-S equal to 2011. These results are identical to the earlier 12-month fiscal year example. The YTD calculations, however, for the two fiscal periods are different.

When performing year-to-date calculations where the fiscal period value is 6 months, OFSAA segments the financial year into two 6-month periods. “Year-to-Date” in the context of a multi-period fiscal configuration means “fiscal period-to-date”.

Using the Undo Function with a Fiscal Year Configuration

The allocation UNDO function removes the results of allocations from the  table. The database function that operates against may be either an UPDATE or a DELETE. Generally speaking, the UNDO function operates as follows:

·       Examine each row generated by the allocation rule a specific month of which we intend to UNDO.

·       For each row, determine how many MTD columns in months other than the month currently being UNDONE contain non-zero values.

·       If the answer is zero, delete the row. If the answer is not zero, update the MTD column that is to be UNDONE with a value of zero and re-set all YTD columns in the fiscal period of the month we are UNDOING.

Examples:

The following examples assume you have run an allocation rule that posts data to  for January, February, and March. When you perform an UNDO operation on the March execution:

·       For any row in which either the January MTD column or the February MTD column contains a non-zero value.

§        The engine will update the March MTD column with a value of zero.

§        The engine will re-set (update) the YTD columns for each YTD column within the fiscal period of the month being UNDONE.

·       The engine will delete any row in which neither the January MTD column nor the February MTD column contains a non-zero value.

With a Calendar Year configuration or with a Fiscal Year configuration, the re-setting of the YTD columns will affect all 12 YTD columns. However, with a Fiscal Period configuration (a configuration in which the Fiscal Period column in FSI-FISCAL-YEAR-INFO/ LEDGER_CCY_AND_FISCAL_YR_INFO is set to 1, 2, 3, 4, or 6), the re-setting of YTD columns will only affect the YTD columns that fall within the same fiscal period as the month of the allocation that is being UNDONE.