Last updated on MAY 03, 2017
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)
On PFT 8.0.2, after adding user defined consolidation codes, allocations have started to fail.
Allocations start to fail after creating user defined consolidation codes.
The ofspa log file ends abruptly:
Module Logging OFS Access module data: SELECT
WHERE OBJECT_DEFINITION_ID = 244197.000000
Module Logging OFS Access module data: select
The following error exists in the nohup.out in $FIC_DB_HOME/bin:
Sucssefully Connected to Config schema.
Sucssefully Connected to Atomic Schema.
Connection to database ofsaaatomic successful
PLEASE provide the valid String
As per the Oracle® Financial Services Profitability Management
User defined consolidation codes are supported:
For allocation rules that source data from the Management Ledger-level, you must
select a Source scenario from the Allocation Source container. The default for new
allocation rules is . When you use this default value,
Scenario (also called Consolidation Code) is determined by the value that is set in
Application Preferences for Profitability Management for the user who is running the
rule. If you do not select , you must select a defined
dimension member value (for example, Actual, Budget, Forecast, Forecast Prior). These
values are provided with the data model, but you may add additional dimension
members in the Consolidation Code dimension.
Therefore it is expected that the allocation will complete successfully.
The issue can be reproduced at will with the following steps:
1. Create new user define consolidation codes.
2. Run allocations.
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