My Oracle Support Banner

Allocation Processes Against Wrong Fiscal Year in Cases Where Fiscal Start Month is Not January (Doc ID 2672050.1)

Last updated on MAY 20, 2020

Applies to:

Oracle Financial Services Profitability Management - Version 8.0.0 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
Oracle Financial Services Profitability Management (PFT)

Symptoms

For PFT 8.0.x, in an environment where you use a Fiscal Start Month that is not January, Allocations run against the Management Ledger table are not selecting the correct Fiscal Year value.

For example, you updated the FSI_FSICAL_YEAR_INFO table to start in October and your Fiscal Year is as follows:

OCT 18 = FY19 Fiscal Month 01
NOV 18 = FY19 Fiscal Month 02
DEC 18 = FY19 Fiscal Month 03
JAN 19 = FY19 Fiscal Month 04
FEB 19 = FY19 Fiscal Month 05
MAR 19 = FY19 Fiscal Month 06
APR 19 = FY19 Fiscal Month 07
MAY 19 = FY19 Fiscal Month 08
JUN 19 = FY19 Fiscal Month 09
JUL 19 = FY19 Fiscal Month 10
AUG 19 = FY19 Fiscal Month 11
SEP 19 = FY19 Fiscal Month 12

In Management Ledger, you have FISCAL_YEAR set to 2019 for all of the rows in the Fiscal Year, even for rows with an AS_OF_DATE value in 2018.
(ex. AS_OF_DATE = 10/31/2018, FISCAL_MONTH = 10, FISCAL_YEAR = 2019)

However, when you run an Allocation using the As of Date that does not match your Fiscal Year, the Allocation SQL uses FISCAL_YEAR equal to the Year contains in the As of Date.
(ex. AS_OF_DATE = 10/31/2018, FISCAL_YEAR = 2018)

As a result, no rows are  processed when the FISCAL_YEAR does not match the year in the As of Date.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.