Code Values Not Displayed in Filter - Exact Match Displayed - After Upgrading to OFSAAI 7.3.1

(Doc ID 1485783.1)

Last updated on JANUARY 17, 2018

Applies to:

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

Symptoms

After upgrading to Oracle Financial Services Analytical Applications (OFSAA) Infrastructure 7.3.1, you can no longer add "Code" columns to Data Element Filters.  If you select a column like "Amortization Type Code" in Data Element Selection, the screen no longer lists the available Amortization Type Code names.  Instead, under "Specific Values", there is a drop down list with "Exact Match" in it.  This prevents you from creating a filter on a Code column.

Additionally, if you open a Data Element filter created before installing OFSAAI 7.3.1 that uses a Code column, the Filter hangs with a spinning hourglass:

Note: The following error exists in the web server's FUSIONSUBSYSTEMSService.log:

[FUSIONSUBSYSTEMS] Aug 18,12 01:20:50 : [COMMONFUNCTIONS]Exception occurred while trying to retrieve column Details for getting code values.
[FUSIONSUBSYSTEMS] Aug 18,12 01:20:50 : [COMMONFUNCTIONS]
java.lang.NullPointerException
at com.ofs.reveleus.filters.util.CommonFunctions.getColumnDetails(CommonFunctions.java:1088)
at jsp_servlet._filters.__dataelesandformulas._jspService(__dataelesandformulas.java:220)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.iflex.fic.filters.FilterServlet.doFilter(FilterServlet.java:872)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.iflex.fic.filters.EncodingFilter.doFilter(EncodingFilter.java:86)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)

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