Type 1 or 2 Ledger Load Fails to Add Balances to Existing Matching Rows in Ledger Stat in 8.0.2 (Doc ID 2162647.1)

Last updated on OCTOBER 05, 2016

Applies to:

Oracle Financial Services Analytical Applications Infrastructure - Version 8.0.2 and later
Oracle Financial Services Profitability Management - Version 8.0.2 and later
Oracle Financial Services Asset Liability Management - Version 8.0.2 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)

Symptoms

In Oracle Financial Services Analytical Applications (OFSAA) 8.0.2, when you run a Type 1 or Type 2 Ledger Stat Load (using fn_ledgerDataLoader) with the "ADD" option, the existing, matching rows in LEDGER_STAT are not getting updated by the "MERGE INTO" SQL.  The new value is not added to the existing value in the MONTH_XX column.

Checking the merge code in FSI_MESSAGE_LOG, it is not using the correct column for the update.  For example, you expect the program to update MONTH_12 but the merge SQL contains the following in the "update" portion of the statement:

when matched then
update set t.m12= gtt.m12

Looking at "gtt.m12", this column stores the existing value in the LSL view.

Additionally, looking at the following section of the merge:

Merge into lsl t using ( select........v.ds,v.year_s, one, m12,

"one" contains the new value being loaded.

"m12" contains the existing value from lsl / Ledger Stat.

The month column should be updated with m12+one but this code is not used.  As a result, the new balances being loaded are not added to the existing values in the LEDGER_STAT table.

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