My Oracle Support Banner

Unable to Save New Constant Allocation Rule - Fails with 'Allocation Rule Cannot be Saved' (Doc ID 1945300.1)

Last updated on OCTOBER 04, 2016

Applies to:

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

Symptoms

When attempting to save an Allocation rule, the save is failing with the following error:

"Allocation rule cannot be saved"

Example:

Also, the following error exists in the PftApp.log from the Tomcat, Weblogic, or Websphere OFSAA log directory:

[25-04-15 11:11:23 AM] ~ INFO  ~ PFT ~  
java.lang.NullPointerException
    at com.ofs.fsapps.pft.Dao.ClsDaoAllocationID.getPortfolioInstrTables(ClsDaoAllocationID.java:4858)
    at com.ofs.fsapps.pft.action.clsActAllocationID.getAllPortfolioInstrTablesJson(clsActAllocationID.java:4241)
    at com.ofs.fsapps.pft.action.clsActAllocationID.fnLoad(clsActAllocationID.java:1720)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

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


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