OTBI Fin Reporting Tips
OTBI Fin Reporting Tips
OTBI Fin Reporting Tips
The following is intended to outline our general product direction. It is intended for information purposes
only, and may not be incorporated into any contract. It is not a commitment to deliver any material,
code, or functionality, and should not be relied upon in making purchasing decisions. The development,
release, and timing of any features or functionality described for Oracle’s products remains at the sole
discretion of Oracle.
Table of Contents
Purpose 3
Introduction 3
1. What are the common reasons that reports created from the
‘General Ledger – Balance Real Time’ subject area fail? 3
Miscellaneous Topics 18
BI Extension / Trees 18
Performance Tips 18
Reference 20
The purpose of this White Paper is to share tips and techniques by answering frequently asked questions and make
OTBI report authoring more efficient. The document is aimed at any role in a customer or partner organization
chartered to develop OTBI reports in Oracle Financials Cloud.
Introduction
The following FAQ’s have been compiled based on commonly encountered issues reported by Oracle Financials
Cloud customers to the Oracle OTBI Product Development teams. They should not be seen by any means as
exhaustive nor do they serve as alternative to product documentation. This is a living document and is expected to
be updated with even more tips as more such feedback is received.
1. What are the common reasons that reports created from the ‘General Ledger – Balance Real Time’
subject area fail?
This subject area uses Essbase in the back end. To use this subject area, you need to:
(ii) run ESS programs to import Fusion data extensions for OTBI
Users may encounter the following issues if they miss any one of the required steps above.
The reports fail or return incorrect results without required filters and columns. Please make sure those pre-
requisites are implemented in your report. For the list of the required filters and columns, please refer to the
following document, available in the My Oracle Support Knowledgebase:
Fusion Applications OTBI/Essbase : General Ledger - Balances Real Time fails to Query The Essbase Cube,
instead it queries the transactional database FSCM_OLTP (Doc ID 1965181.1)
This subject area has required filters “Time – (Fiscal Calendar) Name”, and “Ledger – Chart of Accounts”. For
example, when you do not apply one of the required filters “Time – (Fiscal Calendar) Name”, the report return an
error “You may be able to evaluate this query if you remove one of the following column references..”,
Fiscal Calendar Name has two sources - ADF & Essbase. The column “User Period Set name” and “Period Set
Name” are mapped to ADF and Essbase respectively. The choice list for Fiscal Calendar Name hits the ADF
objects. Your report may not return records if you use the choice list to specify the fiscal calendar filter. Currently
you need to type in Period Set Name for Balance Real Time as workaround.
In the following example, the report has a filter on period set name “Accounting”.
In the Choice List for (Fiscal Calendar) Name, you cannot find “Accounting”. Instead, you see “user” period set
name “AccountingMon1” for “Accounting”.
Report Output
However, in this case, the report does not use Essbase. Instead, it retrieves data from a relational database
source and may not return correct results. Please make sure you apply the required filters when using this
subject area.
Note: If you do not use Ledger Name as filter, then you must add it as a selected column. Otherwise the report
does not return data. The same applies to Accounting Period Name.
Case 3: Did Not Run ESS Programs to Import Fusion Data Extensions
You need to run the following ESS programs for each cube to import Fusion Data Extensions. Please make sure
you have run them:
Create Rules XML File for BI Extender Automation
Import Oracle Fusion Data Extensions for Transactional Business Intelligence
When using ragged hierarchies in General Ledger – Balances Real Time, filters on the code column (e.g. Account
Code) may result in no data returned.
The code column (e.g. Account Code) returns the last level of the deepest hierarchy when your query
retrieves data from Essbase.
Dimension only queries hit ADF sources not Essbase. The ADF has a flattened hierarchy where the last
level is repeated.
Each GL segment has a default tree “All <GL Segment> Values” which has all the nodes added as children
for this tree.
In the following example, Account 52386 is a leaf node of the ragged hierarchy but when you apply filter “Account
Code is equal to / is in 52386”, the report does not return any data. This is because account 52386 is not at the last
level of the hierarchy and Account Code is null for the balance record.
On the other hand, if you run a dimension only query or do search in the filter for “Account Code”, you see all
nodes at different levels.
The filtering could be challenging unless you are familiar with the tree structure.
2. Create a new column returning leaf nodes and apply filters on it.
Add a new column to your report with the following formula which returns leaf nodes. You need to change
the expression based on the depth of your tree structure. The following example is for the case the last
level is 25.
CASE
WHEN "Natural Account Segment"."Account Code" IS NULL THEN
CASE
WHEN "Natural Account Segment"."Account Level 25 Code" IS NULL THEN
CASE
WHEN "Natural Account Segment"."Account Level 26 Code" IS NULL THEN
CASE
WHEN "Natural Account Segment"."Account Level 27 Code" IS NULL THEN
CASE
WHEN "Natural Account Segment"."Account Level 28 Code" IS NULL THEN
CASE
WHEN "Natural Account Segment"."Account Level 29 Code" IS NULL THEN
CASE
WHEN "Natural Account Segment"."Account Level 30 Code" IS NULL THEN
"Natural Account Segment"."Account Level 31 Code"
You will see balances for the specified criteria irrespective of the node levels.
3. Use tree “All <Segment Name> Values” and apply filter on “Level 31 Code”.
Each segment has a default tree called “All <Segment Name> Values”. For this tree, the Level 31 Code
column returns all leaf nodes (again, you need to apply required filters to see them).
For given GL journals, you may want to view their corresponding SLA journals. The following steps describe the
details to implement drill from a GL journal line to corresponding SLA journal lines.
Step 3: Expose “Journal Header Identifier” and “Journal Line Number” in your GL journal report.
Modify your GL journal report to expose “Journal Header Identifier” and “Journal Line Number”.
4.3. Enter Link Text (e.g. “SLA Journals), click “+”, and then select “Navigate to BI Content”.
Run the GL journal report and click the amount column. Then, select the link text “SLA Journals”.
When you include GL segments (Balancing Segment, Natural Account, Cost Center, and so on), the report
fails with nQSError 15018.
[nQSError: 10058] A general error has occurred. [nQSError: 43113] Message
returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 15018]
Incorrectly defined logical table source (for fact table Fact - Fins -
Intercompany Transaction
Distribution) does not contain mapping for [Dim - Balancing Segment.Balancing
Segment Description].
In this case, please make sure you have run ESS program “Import Oracle Fusion Data Extensions for
Transactional Business Intelligence" to import flexfield related extensible data.
» Report attributes are sourced from tables with different levels of granularity. Adding certain attributes brings
in a large table which affects the report performance. For example, in the following report, “Invoice
Accounting Date” under “Invoice Details – General Information” is sourced from invoice headers.
If you replace “Invoice Accounting Date” with “Accounting Date” under “Accounting – Accounting Date”, the
report could take longer. This is because this new column brings in additional tables for subledger journal
entries. If header information satisfies your requirement, in general, you better off not including attributes at
more granular level in your report for better performance.
If you add the more detail attributes (Approval Action and Approver) to the report, the amount does not multiply,
» When you define multiple tree versions for an attribute (e.g. Balancing Segments, Natural Account, and Cost
Center), you need to add a filter to your report to specify a unique tree version. Otherwise your amounts will be
multiplied.
[Edit Journal]
The report returns the correct debit amount after applying the tree filter.
When the issue still persists after applying the tree filter, you may have defined duplicate nodes for the tree
version. In this case, you need to either filter out one of the nodes in your report or fix the tree version to eliminate
the duplicate entries.
7. How do I create a report that shows AP invoices, corresponding payments, holds and installments?
» For given invoices, you may want to display payment information. The following steps describe the details to
implement the report.
Note: All cross subject area rules must be applied here. See the following document for the details:
Fusion Applications OTBI: Guidelines for creating cross subject area analyses in Oracle
Transactional BI (OTBI) (Doc ID 1567672.1)
2.2. Select “Payables Payments – Disbursements Real Time” and click OK.
2.3. Add subject area “Payables Invoices – Holds Real Time” and “Payables Invoices – Installments Real Time”.
Payables Invoices – Transactions Invoice Details – General Information Invoice Cancelled Date
Real Time
Invoice Date
Invoice Description
Invoice Created By
Invoice Number
Pay Group
Supplier Supplier
Supplier Number
Invoice Amount
Hold Name
Hold Reason
Release Reason
Hold Count
Invoice Amount
Invoice Currency
Ledger Currency
Supplier Supplier
Supplier Number
Check Number
Payment Type
More FAQ's can be found in the OTBI Help Center accessible from Oracle Business Intelligence pages: Help ->
Help Contents -> OTBI Help.
Fusion Applications OTBI: Guidelines for creating cross subject area analyses in Oracle Transactional BI
(OTBI) (Doc ID 1567672.1)
BI Extension / Trees
Please refer to the following document:
Fusion Financials OTBI : Setting up General Ledger (GL) Accounting Segments (Key Flexfields KFFs) for
OTBI reporting (Doc ID 1980180.1)
Performance Tips
More often than not, end users need information to answer specific business questions that can be best met by
targeted queries. You should avoid creating reports that return large data sets. The following is a list of tips which
can be used as guidelines.
1. When large reports are needed, consider using Contextual Action Links to navigate to detailed reports
from the main summarized report.
2. Avoid table prompts on columns with huge data volumes (e.g. Bill-to Customer Name).
3. Include sufficient filters for reports that need to show hierarchical dimensions,
4. When using attributes at various levels (Header, Line, Distribution, Accounting), ensure that there is at
least one measure included in the report from each of the attributes at that level.
5. Use report filters that present summarized information. The following table shows the list of filters that
should be applied on reports created from respective subject areas:
Receivables – Customer Account Site Tax Profile Real Time » Time – Month
Receivables – Customer Tax Profile Real Time » Customer – Customer Information – Customer Name
Reference
Fusion Applications OTBI: Guidelines for creating cross subject area analyses in Oracle Transactional BI
(OTBI) (Doc ID 1567672.1)
Fusion Financials OTBI : Setting up General Ledger (GL) Accounting Segments (Key Flexfields KFFs) for
OTBI reporting (Doc ID 1980180.1)
Fusion Applications OTBI/Essbase : General Ledger - Balances Real Time fails to Query The Essbase
Cube, instead it queries the transactional database FSCM_OLTP (Doc ID 1965181.1)
CONNECT W ITH US
blogs.oracle.com/oracle
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the
contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other
facebook.com/oracle warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or
fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are
formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any
twitter.com/oracle means, electronic or mechanical, for any purpose, without our prior written permission.
oracle.com Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and
are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are
trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. 0116
White Paper Tips and Techniques for Using OTBI Financials Reporting
March 2017
Author: OTBI Development Team