Allocation Ends in a Status of Failed and Stops Batch When Source Query Finds No Rows (Doc ID 1386396.1)

Last updated on DECEMBER 20, 2011

Applies to:

Oracle Financial Services Profitability Management - Version: 5.2 to 5.6 - Release: 5 to 5
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)

Symptoms

In Oracle Financial Services Profitability Management (PFT), if an Allocation's "Source Amount" query returns no rows and its Debit or Credit screen uses the Ledger Stat table, the process fails with an error.  In Operations > Batch Monitor, it has a status of "Failed".  If the Allocation is included in a batch of Allocations, the batch stops when the failure occurs.  You do not think an Allocation should fail and stop a batch when it finds no rows.

In some cases, this is a significant issue because certain Allocations will not return rows from the Source query from month to month by design.  These Allocations should not stop a large batch of Allocations and force you to run the remaining Allocations in the batch manually.  If no rows are found, you expect the Allocation to complete normally and proceed to the next Allocation in the batch.

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