CPMI Report 11i ODBC Error When Adding Both Drilldown XTD Functional and Entered Balance Columns (Doc ID 885882.1)

Last updated on DECEMBER 24, 2012

Applies to:

Oracle Enterprise Performance Foundation - Version 11.5.10 to 11.5.10 [Release 11.5]
Information in this document applies to any platform.
Corporate Performance Management Intelligence (CPMI)
FEM
EPF

Checked for relevance on 24-Dec-2012.

Symptoms

In Corporate Performance Management Intelligence (CPMI), when attempting to add both columns 'Drilldown XTD Functional Balance' and 'Drilldown XTD Entered Balance' to the same worksheet, the following error occurs when attempting to display results:

ERROR
View Display Error

Odbc driver returned an error (SQLExecDirectW).

Error Details:
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P

State: HY000. Code: 10058. [NQODBC][SQL_STATE:HY000][nQSError: 10058]A general error has
occurred.[nQSError: 15018] Incorrectly defined logical table source (for fact table Balances) does
not contain mapping for [Balances.Drilldown XTD Entered Balance, Balances.Drilldown XTD Functional
Balance].(HY000)

SQL Issued: SELECT "-Balances Drilldown (Current Calendar Period)"."Drilldown XTD Functional
Balance" saw_0,"-Balances Drilldown (Current Calendar Period)"."Drilldown XTD Entered Balance"
saw_1 FROM " Corporate Performance Management Intelligence" ORDER BY saw_0, saw_1

The columns display the correct results when used individually.

Steps To Reproduce:
The issue can be reproduced at will with the following steps:
1. From the CPMI Answers screen:

Fact - Balances folder
Expanded: Balances Drilldown (Current Calendar Period)
Shows 3 columns:

Drilldown XTD Functional Balance
Drilldown XTD Entered Balance
Drilldown YTD Entered Balance

2. Results displayed successfully on Result tab for 'Drilldown XTD Functional Balance'
3. Results displayed successfully on Result tab for 'Drilldown XTD Entered Balance'

4. Adding both columns ('Drilldown XTD Functional Balance' and 'Drilldown XTD Entered Balance')
and attempting to display result shows the error.

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