BI Statistics - query level of detail

Hi,
Is it possible for us to specify the level of detail for the queries we create? If its possible please tell me how to do it?
Regards,
Suraj

Hi Suraj,
   Yes its possible to specify the level of details for query objects. Here is some info...
<b>Statistics Detail Level for the Query Object Type</b>
For queries, you also have the option of selecting a detail level for the statistics data. You can choose from the following:
●      0 Aggregated Data: The system writes only one OLAP event (event 99999) for the query. This contains the cumulative times within the OLAP processing of the query. The system does not record data from the aggregation layer of the analytic engine or aggregation information.
●      1 Only Front End/Calculation Layer Data: The system records all OLAP events, but not separate data from the aggregation layer of the analytic engine. The system writes only the general data manager event 9000 in the OLAP context as well as the aggregation information.
●      2 All: The system records all data from the area for the front end and calculation layer as well as data from the area for the aggregation layer and aggregation information.
●      9 No Data: The system does not record any data from the front end and calculation layer or from the aggregated event 99999. However, it does record data for the BEx Web templates and workbooks, depending on the setting.
When you select the detail level, keep in mind that a very large amount of data is recorded when the system records data manager times.
Hope this helps...
Regards,
Habeeb

Similar Messages

Passing YTD selection from a main query to a detailed query using RRI

Hi,
We have created two queries: one main query on an infocube for aggregated data, one detailed query on the feeding DSO for data at the level of sales document items.
Both queries show monthly and YTD (year-to-date) actual cost figures.
The user enters for instance the month of 05.2005 on the main query in a variable ZP_MONTH.
A user exit variable ZS_YTD is calculated so that the interval 01.2005 - 05.2005 is stored in ZS_YTD.
Revenues in the month are displayed in one column.
Revenues in the YTD period are displayed in another column.
Assume the data is displayed by document types.
Then the user should select the document type and perform a jump target (Goto) to the detailed query to see which sales document items are contributing to the total revenues behind the document type.
We have defined a ZS_YTD_2 variable on the detailed query. It is used in the field assignments in the RSBBS transaction to receive the 0CALMONTH selection (in our case 01.2005 - 05.2005). Then on the detailed query, we defined another userexit variable to capture the selected month based on ZS_YTD_2.
Our issue is that when the user goes from the main query to the detailed query, the variable screen of the detailed query is being displayed with the variable ZS_YTD_2 open and the user can even change the selection there.
Is it possible to remove the display of this intermediate variable screen?
Thanks.

Well. If you unflag the variable for ready for input on the detailed query, then it is not possible for that variable to receive the period selected on the main query. Even worse, the query crashes with the message that the variable is not correctly defined.
Any other suggestion?
Thanks.

[nQSError: 14025] No fact table exists at the requested level of detail:

Hi All,
I am using OBIEE 11.1.1.6.8.
I have below senario...My fact table contains 3 LTS(yearly, Monthly, Weekly) and TimeDim contains3 LTSs(yearly, Monthly, Weekly)
Fact-Weekly joins with (D1,D2,D3) & TimeDimWeekly
Fact-Monthly joins with (D1,D2,D3) & TimeDimMonthly
Fact-Yearly joins with (D1,D2,D3) & TimeDimYearly
I hv also set the Fact source content to appropriate level of TimeDIM and details level of other Dimensions.
when i build a report using only year_code or month_code_or week_code as filter the query is going to appropriate physical sources
ie. if i take week_code as filter then the query firing to FactWeek, TimeDimWeekly & other Dimensions
if i take Month_code as filter then the query firing to FactMonthk, TimeDimMonthly & other Dimensions
Problem is when I use dynamic filter its is giving [nQSError: 14025] No fact table exists at the requested level of detail: error.
My filter is something like this using presentation variable pvTime (filter is prompted)
case '@{pvTime}'
when 'Weekly' Then "Calendar"."Week - WYYYY"
when 'Monthly' Then "Calendar"."Month - MONYYYY"
when 'Yearly' Then "Calendar"."Year ID" end
Please help me if I missed any step
Thanks
Smita

Its a guess but try the below.. As you are using the CASE statement in your filter, use it in the below way.
Store the value that is prompted into a presentation Variable
YOUR WAY
case '@{pvTime}'
when 'Weekly' Then "Calendar"."Week - WYYYY"
when 'Monthly' Then "Calendar"."Month - MONYYYY"
when 'Yearly' Then "Calendar"."Year ID" end
SUGGESTED WAY
(case '@{pvTime}'='Weekly' and "Calendar"."Week - WYYYY" = '@{new PV}' THEN 1
when '@{pvTime}'='Monthly' and "Calendar"."Month - MONYYYY" = '@{new PV}' THEN 1
when '@{pvTime}'='Yearly' and "Calendar"."Year ID" = '@{new PV}' THEN 1 ELSE 0 END) =1
This might correct the way your are using your CASE statement in Filters..

No fact table exists at the requested level of detail Error.

Hi Everybody,
Facing a issue on the using Fact less Fact tables.
Scenario:
========
Using two subject areas to develop a report.OBIEE 11g
Fact1 --> Compensation Plan Assignments Real Time
Fact2 --> Participant Detail Real Time"."Participant Details
On both facts we created dummy metrics on respective table id's and aggregated to ROWCOUNT.
As i said in earlier we are using the above 2 subject areas to develop reports.
Logical SQL:
===========
SELECT
0 s_0, "Incentive Compensation - Compensation Plan Assignments Real Time"."Role"."Role Name" s_1,
"Incentive Compensation - Participant Detail Real Time"."Participant Details"."Cost Center" s_2,
"Incentive Compensation - Participant Detail Real Time"."Participant Details"."Country Code" s_3,
"Incentive Compensation - Participant Detail Real Time"."Participant"."Participant First Name" s_4,
"Incentive Compensation - Participant Detail Real Time"."Participant"."Participant Last Name" s_5,
"Incentive Compensation - Participant Detail Real Time"."Participant"."Party Number" s_6
FROM "Incentive Compensation - Earnings Real Time" FETCH FIRST 65001 ROWS ONLY
Error Message:
==============
Expression 'RowCount:[DAggr(Fact - Compensation Plan Assignment.RowCount by [ Dim - Participant Details.Cost Center, Dim - Compensation Role.Role Name, Dim - Participant.Participant Name] )]' converted to NULL because [nQSError: 14020] None of the fact tables are compatible with the query request RowCount:[DAggr(Fact - Compensation Plan Assignment.RowCount by [ Dim - Participant Details.Cost Center, Dim - Compensation Role.Role Name, Dim - Participant.Participant Name] )]..
[2013-10-21T12:18:45.000-05:00] [OracleBIServerComponent] [TRACE:2] [USER-34] [] [ecid: 004uJx90aHO9lZ73VJJNB80007eh000gl_,0:2:1:9:5] [tid: 457c2940] [requestid: f2e001b] [sessionid: f2e0000] [username: [email protected]] -------------------- Query Status: [nQSError: 14025] No fact table exists at the requested level of detail:
Please share some ideas on this or any guidelines will be very much helpfull.

Govardhan,
Did u configured any Dimension Hierarchy please set the levels in that particular Fact LTS.
For more info,check the below thread
https://forums.oracle.com/thread/2134934
Thanks,

No fact table exists at the requested level of detail

We have two fact tables F1,F2 and D1, D2, D3, D4, D5 dimensions.
They are connected line this.
F1 to D1, D2, D3 and self dimension D_of_F1
F2 to D2, D3 and self dimension D_of_F2
Means D2 and D3 are common dimensions between two facts.
D_of_F1
         |
         |
D1--F1--D2
         |      |
         |      |
        D3   |
        |       |
        |       |
        |-F2-|
        |
        |
        |
   D_of_F2
Hierarchies
H1 for D1
H2 for D2
H3 for D3
H_of_F1 for D_of_F1
H_of_F2 for D_of_F2
and pinned LTS of F1 --> H1 detail, H2 Detail,H3 Detail, H_of_F1 Detail
and pinned LTS of F2 --> H2 Detail,H3 Detail, H_of_F2 Detail
We are selecting these columns
D1.C1, D1.C2, D2.C1, D2.C2,D3.C1 and report works perfactly.
But when I add D_of_F2.C1 then report gives this error
Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 14025] No fact table exists at the requested level of detail
Please help me to solve this error....
I m new in OBIEE concepts so not able to trubleshoot...
Thank you.

i'm try to do an analysis between two tables (that have a relatinship), we had inclued first the FACTURA.FACTURA_COD, then columns from COBRANCAS and it work's. When we inclued the FACTURA.COMISSIONISTA_ID it return the fowlling error :check the level set in content tab in fact table.it can happen that FACTURA.COMISSIONISTA_ID is at a lower level than specified in fact table.
Regards,
Sandeep

How to create 3 levels of detail based on Wizard code

I have 3 tables: Orders, Recipes, Ingredients. An Order can
have several Recipes attached, and each Recipe has multiple
ingredients. I want to create a data entry form for these 3 levels
of detail. What I have in mind is a window which shows a form for
the Order details and a tabbed panel with one tab for each recipe
Within each recipe panel there would be a form for the recipe
details (preparation method) and a datagrid to display/enter
ingredients.
I'm a CF'er new to Flex so I'm so I'm relying a lot on the
CFApplication Wizard. The best I can get it to do is create a
detail page with an included datagrid, e.g. using the example
artists database to display details about an artist and an included
datagrid to list the art ( see
http://www.adobe.com/devnet/coldfusion/articles/wizards.html)
Is there any way I can adapt the CF generated code to do what
I want? Better yet can anyone point me to a similar example?
Thanks
Bob

Easy!
Create you group, on "dynamic members" screen select "SQL Database" as the class and click add, then on the dropdown list under the "and group [...]" go all way to the bottom and chose "(Host = SQL DB Engine) > Display
Name" .
Finally, adjust the rest of the query to your needs.

Post-generating 3-level master-detail-detail screens

Hi all,
for a consulting project, I had to create several three-level master-detail screens using JHeadstart. For the JHS demo app, this would mean for example that a location page contained a list of departments at the location and underneath it a list of employees working at the currently selected department.
From what I have learned so far using JHS, this is not supported by the wizards and should be done by post-generation changes. This forum has a few topics mentioning the problem and possible solutions, but most of the time just fragments of the complete solution/approach. As I had to create several of these 3-level detail screens, I tried to uniformly document them, providing the 7-step guide as outlined below. I only started working with JHS recently, so please let me know where I take a long way round or where my approach is not appropriate at all :o)
NOTE1: Terminology-wise, for the example given above, I will call the departments the 2nd level detail and employees the 3rd level detail, while locations are the first level masters. I hope this is not too confusing ;o)
NOTE2: the example code is not guaranteed to work with the JHSdemo. I just changed the names of variables and classes from my own application to the familiar entities of the demo.
STEP 1: Generate plain MD screens for the first and second level entities (table-form) using the JHS application generator and make sure all generated features you want in your page are OK. Afterwards, switch off the UIX generation in your application structure file. If you want multiple entities at the third detail level,
STEP 2: Add the functional contents of the generated 3rd level detail UIX page to the main master UIX page, right underneath the 2nd level detail-table but still inside the <header> entity of this 2nd level detail. (I'm not too sure whether this really matters, but at least the indentation looks nice). What I call "functional contents" is the <header> entity containing the 3rd level detail table.
STEP 3: Edit the java file of the 3rd level view object, adding a variable storing the identifier (primary key) of the currently selected 2nd level detail row. If you haven't used the java file before, generate it by doubleclicking the view object and checking the generate view object box in the Java screen.
private String $selectedDeptID;
public void setSelectedDeptID(String id) {
$selectedDeptID = id;
STEP 4: Edit the java file of your application module (in the model layer) and add a method for updating the view objects search queries like the example below:
public void updateEmployeeView(String deptID) {
// fetch the view object instance
EmployeeViewImpl view = (EmployeeViewImpl)this.getEmployeeView1();
// register the currently selected departments ID
view.setSelectedDeptID(deptID);
// re-execute the view objects query
view.executeQuery();
// reset the selected ID
view.setSelectedDeptID(null);
STEP 5: Create a java class for handling the event when a user selects a different 2nd level detail row.
package view;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpSession;
import oracle.adf.controller.struts.actions.DataActionContext;
import oracle.adf.model.BindingContext;
import oracle.adf.model.bc4j.DCJboDataControl;
import oracle.adf.model.binding.DCDataControl;
import oracle.adf.model.binding.DCUtil;
import oracle.cabo.servlet.BajaContext;
import oracle.cabo.servlet.Page;
import oracle.cabo.servlet.event.EventResult;
import oracle.cabo.servlet.event.PageEvent;
import oracle.cabo.servlet.ui.data.PageEventFlattenedDataSet;
import oracle.cabo.ui.data.DataObject;
import oracle.cabo.ui.data.DataSet;
import oracle.cabo.ui.beans.table.SelectionUtils;
import oracle.jbo.ApplicationModule;
* USER-DEFINED EVENT-HANDLING CLASS
* this class is triggered after the user selects another row in the Department
* table/form in the Locations.uix screen. It derives the ID (pk) of the
* selected row and launches the AppModule method to update the view objects
* select queries with the selected DeptID.
public class RowSelector
* private variable holding the name of the DataControl module for this
* Application Module
private static final String DATACONTROLNAME = "AppModule" + "DataControl";
* private variable holding the name of the table/form object in the uix page
* from which we want to derive the selected row data.
private static final String TABLEFORMNAME = "DepartmentsView2";
* private variable holding the name of the form field holding the database
* ID (pk) of a row in the ${TABLEFORMNAME} table/form
private static final String IDFIELDNAME = "Dept_ID";
* This method fetches the ID of the user-selected row in the DepartmentsView2
* table/form in the Locations.uix form.
* Afterwards, it fires the ApplicationModule method for updating the view objects
public static EventResult doSelectionEvent(BajaContext bc, Page page, PageEvent event)
try {
// create a new FlattenedDataSet for the table name
DataSet tableInputs = new PageEventFlattenedDataSet(event, TABLEFORMNAME);
// fetch the UI table index from the DataSet (NOT the pk from the db)
int index = SelectionUtils.getSelectedIndex(tableInputs);
// fetch the DataObject representing all the input elements on the current table row.
DataObject row = tableInputs.getItem(index);
// fetch the value of the input field holding the ID (pk) of the selected department row
Object value = row.selectValue(null, IDFIELDNAME);
if (value != null) {
// tell the AppModule to update the appropriate view object(s)
getAppModuleImpl(bc.getServletRequest()).updateEmployeeView(value);
// quick and dirty exception handling. not too many exceptions possible due to
// hard-coded field/table/module names. anyway, taking no action at all is not
// that bad an option for a demo ;o)
} catch (Exception e)
e.printStackTrace();
return null;
* method for fetching the active Application Module
public static AppModuleImpl getAppModuleImpl(HttpServletRequest request)
BindingContext ctx = DCUtil.getBindingContext(request);
DCDataControl dc = ctx.findDataControl(DATACONTROLNAME);
AppModuleImpl service = (AppModuleImpl)dc.getDataProvider();
return service;
STEP 6: Override the executeQueryForCollection method in your view object java file to make sure it uses the selected 2nd level detail rows ID for the bound variable specifying the 3rd level select query. Otherwise, the select query for the 3rd level detail set appears to use the ID of the first 2nd level detail row selected for the currently selected 1st level master. In the example below, no other bound variables are used in the view object, otherwise, the indexing might have to be adjusted.
protected void executeQueryForCollection(Object qc, Object params[], int noUserParams) {
if ($selectedDeptID != null) params[0] = $uur;
super.executeQueryForCollection(qc, params, noUserParams);
STEP 7: In the Locations.uix page, set a primaryClientAction for the radio select input in the 2nd level detail screen. This action should fire an event (fe 'userChoseDepartment') and refresh the 3rd level detail tables using the partial refresh options in the primaryClientAction dialog window. Afterwards, add an event handler to the bottom of your Locations.uix page, linking the event specified before to the doSelectionEvent in the RowSelector class.
So, that's how it worked for me. I hope it does the same for you and please do post any comments or remarks if problems arise or simplifications are possible. The more remarks or bugs appear in the above code, the more the JHS team is hinted to enable auto-generated 3rd level detail screens :-D
Cheers,
benjamin

Benjamin,
Thank you for sharing your expreinces with us!
A few remarks:
1. With JHeadstart 10.1.2.1 you can generate unlimited master-detail levels in the same page when using UIX and table-layout for the detail groups This feature is implemented usin g UIX table detail disclosure: when you click on the "show" link in a row in of the level 2 detail table, you will see in the detail disclosure area the level 3 detail table.
There is a screen shot of this feature in the JHeadstart Developers Guide for 10.1.2.1, chapter 3, section "Creating Table Pages". You can now download the dev guide from the JHeadstart Product Center:
http://www.oracle.com/technology/consulting/9iservices/jheadstart.html
2. You have a lot of steps related to synchronizing the level 3 ViewObject with the level 2 ViewObject. You can leave all this work to ADF Business Components, by adding the l;evel 3 ViewObject as a nested usage to the level 2 ViewObject in your application module data model.
Ths would save you the work you aredoing in steps 3 to 6.
Steven Davelaar,
JHeadstart Team.

Convert Char as KF at Query Level

Hi,
I have a query will all line Item Details with GI Date details.
But my requirement is the for all line Item details i want the GI date as mentioned for Line Item 10. (i,e First Schedule Line Date) at query level.
Is there any way i can convert the GI date Char to KF and then apply Restriction on Item 10 in Restricted Key Figure.
Is there any other way to archive this at query Level only.
Thanks for your suggestions,
Joseph M

Hi Joseph,
Probably we could try the following solution
Create two formula variables of replacement path type. - one for line item and one for GI date.
Create a formula with logic - if line item 10 then display actual GI date, else date 01/01/1000 or any date which will be surely smaller than the GI dates available in the system.
In the properties, maintain, calculate result as the highest value.
Then probably you could use SUM(CT) data function for another formula and use the formula we created above.
I am not sure that this will work, but worth giving a try. Else, we would have to accomodate the requirement in the model.
Lastly, do take a look at virtual characteristics and key figure. That might be one option.
Looks like we are reporting on item level, which means we would be dealing with huge data, in such cases virtual characteristic would be too much bearing on performance.
Hope it helps,
Regards,
Sunmit.

URGENT HELP PLS : Issue with Multi Level Master Detail block

This is an issue someone else had posted in this forum few years back but there was no solution mentioned, I have run into this same issue , The problem is as explained below.
Any help on this is appreciated.
Scenario:
There are 3 Blocks in the form : A (Master Block)
: B (Detail of A )
: C (Detail of B )
There is master detail relation created between A and B and B and C. So initially when we query for a record in Master A, it shows all records properly in B and C.
Now if i navigate to the first record of B , and then second record of B , records corresponding to that record shows up properly in C block.
Till now everything works fine.
Issue 1:
But in case after querying initially on Master Block A,If I go directly to the second record of B block, it clears the whole B block and C block.
Issue 2:
Same thing happens if I am on C block ( corresponding to second record of B block) and then navigate to first record in B block , it again clears the whole B block and C block.
Please Help !!
Thanks !

Thanks Xem for Your reply , I tried those settings but it did not help..here is the original link that to the thread that talks about the same problem ,
Issue with Multi Level Master Detail block
The last update to this was the following :
"I figured out that this is happening because Block Status is set to 'Changed' and this is causing it to clear out the blocks.
But cant figure out why the status is setting to 'Changed' "
Any Help from the form Gurus on this form in this matter is truely appreicated !!
Thanks,
Zid.

OBIEE 11g - No fact table exists at the requested level of detail

My dimesion tables are snow-flake.
Table1 has Key, ProductName, ProductSize, Table2Key
Table2 has Key, ProductDepartment, Table3Key
Table3 has Key, ProductDivision
I have created 2 hierarchies (in same dimension Product). Note: ProductSize is in Table1.
ProductDivision > ProductDepartment > ProductName (shared level)
ProductSize > ProductName (shared level)
There are 2 fact tables
Fact1 is at ProductName level
Fact2 is at ProductDepartment level
When I create a request with columns as ProductSize and some measure; and filter it on ProductDepartment. The request fails with error "No fact table exists at the requested level of detail", but the request can ideally be answered using fact with ProductName level.
I have properly defined logical level keys in the hierarchies and logical level in the LTS (content tab)
Can anyone point me what I am doing wrong here?

Since both fact tables are at same granular level I would suggest to map each other (Signon_A maping Signon_B) in BMM layer logical fact @source.
Considering them as Fact and with fact extension.
BTW: Did you try by setting implicit fact at subject area properties?
Edited by: Srini VEERAVALLI on Feb 1, 2013 9:04 AM

Query level filter not working in Webi report

Hi All,
I am using BOXI R3.1 (SP3), m facing one problem when refreshing Webi report on daily basis. I am using three query level filter as a prompt, but i checked one filter is not working then i need to reapply this filter and rest 2 filter is working fine.
Can anyone suggest me why problem is coming?
Regards,

Hi,
Prompts are interactive, and come from the query panel. Filters are not interactive, and are set on the report or block. There are also input controls, which are interactive filters
1. Select the universe in the list of universes to open the Query Panel.
2. Drag the Year object to the Result Objects pane.
3. Drag the Number of Guests object to the Query Filters pane and create a report filter that restricts Number of Guests to greater than n.
4. Click Combined Query.
The Combined Query pane appears in the bottom left of the Query panel with the two queries joined by UNION.
5. Click on the second query and remove the Year and Number of Guests objects.
6. Drag the Reservation Year object to the Result Objects pane.
7. Drag the Future Guests object to the Query Filters pane and create a report filter that restricts the future guests to greater than n.
8. Click Run Query.
Best Regards
Naveen

Date to Month Conversion at Query Level.

Hi,
I have Net due date in the Info provider.
At query level i have to create a restricted keyfigure based on Net Due Month.
Is there any way i can calculate Net due month at runtime and then create the restricted keyfigure using the net due month instead of using net due date directly(linke 01-10-2010 to 31 -10-2010 for october 2010).
Thanks and Regards,
MuraliManohar.

Hi,
Is there any way i can calculate Net due month at runtime and then create the restricted keyfigure using the net due month instead of using net due date directly(linke 01-10-2010 to 31 -10-2010 for october 2010).
you can calculate , but as he said you can add in cube , may be for cal month you are taking som eother date field.
in this case write one customer exist code .
create one varaibel on netdue date with customer not ready input (if user wants to enter input then ct=reate user entry varaible with reday input by using customer exit).
in routine wriet the code as when that varaible .
l_s_range - high , low and give then take the month form that date
like netdue date +0(6)-- gives month and year
netdue date +0(2)-- gives month
then rtestrict that variable with your keyfigure.
Thanks & Regards,
sathish

No Fact Table Exists at the request level of Detail

Hi,
I'm new to BI.can anybody come across more than one fact table in BMM layer,currently i working with AP module,i am getting the error Error NO:14025 No Fact Table Exists at the request level of Detail.
Even i check with content tab where i have given detail level for confirming tables and total for non-confirming tables.
can any one have document related more than fact table in BMM layer, any body give me the right solution.
Thanks in advance !

thanks for your response,i did for the selected measures also. in Account payable model i have two fact.
F1 with dimension D1,D2,D3,D4
F2 with Dimension D5,D6,D7,D8
when i'm trying to generate reports F1 with D1,D2,D3,D4 i am getting the output,but with the non-conforming table D5,D6,D7 i am getting the error. can you give some document to work more than 1 fact table.

No fact table exists at the required level of detail

Hi All,
I am getting the below error in report level(11.1.1.6.4).
No fact table exists at the required level of detail.
Thanks & Regards,
Chandra

Hi Chandra,
One of the possibility for this error can be:
if you have 2 sets of dimension and fact say (D1 & F1) , (D2 & F2) and these are 2 sets are not connected to each other. In report criteria if you have columns from all the tables. Then the result will be.'No fact table exists at the required level of detail' error.
Regards,
Arjun.

OBI Joining two lookup tables. [nQSError: 14025] No fact table exists at the requested level of detail

Hello,
I basically have only fact tables that I need for my analysis. No dimensions, no hierarchies.
When add two tables in OBI Answers to start the analysis I see this error:
[nQSError: 14025] No fact table exists at the requested level of detail
I have them defined as lookup tables. How can I join lookup tables?
In order to pre-filter them using the user_name session variable.

Hi Nagireddy.
As described:
open your rpd. go to "manage" -> Variable Manager / New / Session / Variable. so to create a new session variable in the .rpd.
then you create a variable NO_FORCE_TO_DETAIL_BIN and se the default to 1.
BUT....this did actually not do the trick
I have created a logical table that is a table made up of the two that I just want to join and as soon as I create a bi answers report that contain columns from those two tables I see the error 14025.

BI Statistics - query level of detail

Similar Messages

Maybe you are looking for