Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 16 Oracle Analytics Lounge
- 216 Oracle Analytics News
- 43 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 79 Oracle Analytics Trainings
- 15 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
How to add a common prompt for a dashboard having two different analysis using different subject are

Hi,
I have created two seperate analysis :
-First analysis containing Payables Invoices Transactions Real Time, Supplier is added as a prompt here
-Second Analaysis containing Supplier Supplier real Time, Supplier is added as a prompt here
I created a dashboard Prompt( Column Prompt) for "Supplier" using Payables Invoices Transactions Real Time
I then created a dashboard with the dasboard prompt that i had created and the 2 analysis that i created. But the dashboard prompt filters only the results of first analysis Payables Invoices Transactions Real Time.
But i want it to sort the results of both analysis. Please help.
Thanks,
Priyanka
Answers
-
Hi,
Please find below the document:
Fusion Applications OTBI: Guidelines for creating cross subject area analyses in Oracle Transactional BI (OTBI) (Doc ID 1567672.1)
Regards,
Arun
0 -
Hi,
We had the exact requirement and when raised SR with oracle, got the below updates:
(combining Purchasing Real Time Vs DOO)
----------------------------------------------------------------------
1. Customer will create 2 simple report with each subject area (using the columns that will choose for the complex report)
Will check if data is returned. - I will provide the link with job and duty roles that need for creating a data role.2. Customer will create the complex report (cross subject area) as per:
- Advanced tab > DIMENSIONALITY need to be checked
- choose a common dimension
- attributes from both SAs
- at least one measures from each SA
------------------------------------------------------------------------
http://docs.oracle.com/cd/E36909_01/fusionapps.1111/e38447/frameset.htm?ch03.htm#fe_SAs_ch3_hcm_tableA custom data role need to be created in order to see data from a subject area.
From above link, you will find the job role that need to be inherited by the custom data role and the duty role that need to be assigned to the same custom data role.
------------------------------------------------------------------------I believe these details will be useful.
Regards,
Arun
0 -
Hi,
Another update in SR:
The below steps are the minimum set of steps required , to access data through cross subject area analysis
1. Please make sure that columns from a CONFORMED Dimension are included in the analysis (= a dimension common to both subject areas )
2. Include at least one Fact / Measure column from each subject area - In this case two Fact columns - one from each subject area - In case you do not need the Fact column to be displayed, then you can hide the column.
3. Go to the Advanced tab and check the DIMENSIONALITY check box below " Advanced SQL Clauses" option and click apply SQL before we check data in results tab
Regards,
Arun
0 -
Prompt filters the report with the same subject area ... so base the filter of the second report off the results of the first -- the assumption is that the Supplier Values are identical between the two subject areas.
0 -
Hello Thomas,
I did add "Supplier" as my prompt from my first subject area.
The values of Supplier is identical in 2 subject areas. But the prompt filters only the data of first subject area.How do i make the prompt common for both subject areas?
0 -
"so base the filter of the second report off the results of the first"
Here's an example: https://orbiscascade.org/file_viewer.php?id=4409
Effectively you are getting to: report2.Supplier is in report1.Supplier
If you have suppliers that might be in report2 and not in report1 - then use a presentation variable for your filter ... set it in the prompt and use it in report2
0 -
Hi Arun,
Could you provide more details on how to proceed with Step 2?
0 -
That's something completely different AND not really good advice.
0 -
In order for this to work the columns must have an EXACT match either in fully qualified name or in alias.
So SA1 "Time"."Year" would not match SA2 "Time Dim"."Year Number" but it can match if SA2 has
- "Time Dim" -> Alias "Time"
- "Year Number" -> Alias "Year"
0