Essbase Data Not Cleared Before Rerunning BSP Cash Flow Process (Doc ID 1614283.1)

Last updated on APRIL 06, 2016

Applies to:

Oracle Financial Services Balance Sheet Planning - Version 6.1 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)

Symptoms

On Oracle Financial Services Balance Sheet Planning (BSP) 6.1, when running the cash flow process, it appears that Essbase data is not properly cleared.

ACTUAL BEHAVIOR

It does not appear that the existing Essbase data for the Entity/Chart of Account (COA), etc combination that is being processed is cleared before the process is run. This was discovered when testing prepayment factors for a particular COA which produced data for some of the prepayment financial elements.  After removing the prepayment factors from the COA characteristics and reprocessing, the financial elements related to prepayment still had values.

EXPECTED BEHAVIOR

Expect prior Essbase data to be cleared before running so reprocessing yields correct results.  In the test case, the expectation would be that the now "Invalid" financial elements would have been cleared out since they are now longer applicable.

Steps to reproduce

The issue can be reproduced at will with the following steps:

1. Run current position cash flows for a COA that has some characteristics that create data in a subset of the financial Elements
2. Remove the characteristic related to the elements and reprocess.

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms