Custom Parameters Are Not Used Correctly If They Are Union Joins in an Interactive Reporting Job.
Last updated on JUNE 06, 2016
Applies to:Hyperion BI+ - Version 220.127.116.11.000 and later
Information in this document applies to any platform.
A BQY job with parameters has been published into Workspace.
When the job is run with default parameters, the correct parameter values are used.
Custom parameters are then created for that job.
When the job is run again (manual or scheduled) specifying the custom parameter, the custom parameters are not used correctly for the second query.
This ONLY happens when there are Union joins defined in the BQY.
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