Lowest Level of Details

Hello All,
I have one planning area which containts 33 Characteristics.Can any one please let me know how to find the lowest level of details out of the above 33 characteristics combinations ?
For example out of these 33 characteristics, there could be some 7 characteristics which are at the most detailed or lowest level and my problem is how to find these 7 characteristics combinations ?
Thanks in advance !!
Regards,
Pawan.

Hello Srinivas,
Thanks for the solution. Need one more clarification. In my last mail, i have just mentioned as an example of 7. Lets say i do not know how many characteristics out of the 33 form my most detailed level. Is there any way to find the number of characteristics out of 33 which make the detailed level and then apply the logic u have mentioned. I have tried to find but iam not sure of the result. As you said i have dumped all the possible CVC from planning area using remote infocube in excel. I applied advanced filter of unique records for all of the above CVC excluding time and KF columns. i got 1750 unique records. Then i tried generating same 1750 unique records using different combination of characteristics.I was able to get these 1750 records using as few as 10 char combinations values and also using 13 char combinations values. Then in this case does my 10 char combinations values are the most detailed level or 13 CVC ? Also this most detailed level char combinations remains constant through out the entire forecast horizon.??
I really appreciate your last prompt reply of my question. Thats what makes you the highest contributor in the last month.
Thanks,
Pawan.

Similar Messages

Hierarchy drill down issue at the lowest level

Hi,
In OBIEE 11.1.1.5 I face an issue with drill down to lowest level of presentation hierarchy (expanded by "+" in report). It happens only for combination of 2 dimensions presentation hierarchies in analytics report (parent-child organizational structure + level based product categorization). Aggregated date comes from OLAP but lowest level product information comes from relational database and this details are not displayed.
First I drill to particular sales rep in organizational structure. Then for that sales rep I need to drill down product hierarchy and it works except lowest level of details. At the lowest level of product hierarchy, query sent to database (I have it from logs) return proper results (checked directly in db) but report behaves the way like there are no details at the lowest level and product details are not displayed.
Both (Organizational structure, Product) dimension presentation hierarchies works ok at all levels when used separately. Also product hierarchy works well at all levels (including OLAP->relational drill) when used togather with other level-based hierarchies in subject area.
I am wondering what I could have done wrong...
Advices are very welcome!

Hierarchy keys are set properly and "use for display" is checked.
Dimension presentation hierarchies does not work only when I use particular two hierarchies togather in one report table. When each of hierarchies is displayed separately it works ok.

Cannot drill down from 2nd lowest level to lowest level of hierarchy

In my item master hierarchy, I cannot drill down from the 2nd lowest level (Product Class) to the lowest level (Item Detail).
When I add another level between these 2 levels, then I can drill down from Product Class to this new level, but I cannot drill down from this new level to the lowest level.
Also, if I set the preferred drill path at any level to drill down to the lowest level, it instead drills down to next level down intead of of drilling to the lowest level.
Any thoughts as to why I would not be able to drill to the lowest level of this hierarchy?
Thanks,
Travis

OK, next check, any security in place on the presentation columns which would make the lowest level column unavailable to the user account?
Are you running the report as Administrator?

Promotion planning and lowest level KF

Hai,
The promotion key figure has to be the lowest level of detail, which means the KF has to be the lowest in the hierarchy. This means, I can only assign promotions at the lowest level?
For example, a product called DOW white color soaps and a group level called DOW soaps. So as per the promotion planning, I can only set promotions at the DOW white color soaps and not at the group level of DOW soaps? is that true? What if I have a case that I have to specify a promotion at group.
Thank you.

Hi Vishu ,
Firstly let me clear you that Promotion Key figure is the key figure in which the data for the promotion is to be stored and the Promotion level is the characteristic at which level the promotion is maintained ,this may be the Locaion or the Product .Yes you need to assign promotion to the lowest level but this does not mean that you can not add promotions at higher level like product grp or Brand .
In promotion base you can define Characteristics (Grp/Brand etc) on which you want to plan promotion.
For more clarification go thro.
<a href="http://help.sap.com/saphelp_scm40/helpdata/en/0d/429ba838ee11d3982b0000e8a49608/frameset.htm">Creating a Promotion</a>[url
Regds //Digs...

How to confine various level of planning in to limited and lowest level of planning in DP by the users

Hi Gurus,
May I know the various methods to confine planning level at the lowest level and re-define the Primitive methods where business currently uses in excel sheet and plans at all level into demand planning with a minimum and lowest level by which the business reduces manual work and increases visibility and planning.
Example: Business currently plans at customer Hierarchies which has about 6 levels, product has Hierarchies at 5 levels, location hierarchies at 3 level in excel sheet and on monthly level for an year and then quarterly for 2 years and yearly basis for one year. This we need to confine to lowest level of customer, product and location.
HEIRARCHY LEVEL
PRODUCT
CUSTOMER
LOCATION
LEVEL
P0
C0
L0
HIGHEST
1
P1
C1
L1
2
P2
C2
L2
3
P3
C3
L3
4
P4
C4
SOLD-TO
5
P5
C5
6
P6
CUSTOMER
LOWEST
SKU
PLANNING LEVEL
PRODUCT
CUSTOMER
LOCATION(DISTRIBUTION CHANNEL)
HEIRARCHY LEVEL
P6
C5
L3
LOWEST LEVEL
WHERE
P6
SKU
C5
CUSTOMER
L3
SOLD-TO- PARTY
CVC
P6_C5_L3
So in this case, the cvc are created at lowest level of planning, at P6_C5_L3.
Now how to convenience the business that they need to do the planning at this level for planning, as the rest levels will be aggregated automatically in demand planning.
Is the grouping level place a major role? if so how to do that as the business says for some products they do at p4_c2_L1 level for some they do at P5_C4_L2 level.
Could someone guide us in giving some solution which ease the business need of planning at any level. Hope you have understood my requirement by the above example. If not do let me know, so that I may try to inform by further details. Thanks in advance.
Praveen

Praveen,
Not really sure what the question is. You say you want to 'confine' planning to the most detailed level, but you also want to support planning at an intermediate level.
No matter. DP transparently supports planning at any/all levels simultaneously. Data in DP is always stored at the detail level, no matter which level (or combination of levels) the forecast is entered at.
Creation of the Demand Forecast - SAP Library
Best Regards,
DB49

Why do we need to plan promotions at the lowest level of aggregation

Hi,
The documentation says that we need to plan the promotions at the lowest level of aggregation i.e., the material level. Why? Is there a specific reason for this? Can we plan at other levels of aggregation as well? What happens if we plan at higher level;s of aggregation?
Thanks.

I think it is possible to do it in an aggregated level however you need to define your distribution rules in order to get the desired result, you need also to consider that if distribution rules changes and the value after promotional planning returns the same value, it is possible that detailed level are not realigned to the new distribution rule (e.g. regarding another ratio).
Maybe this is one of several causes.
Regards,
Carlos

Lowest Level in Dimension

HI guys
i have rdbms 9.0.4
can i define lowest level of dimension that is not the primary key of the dim table ( this field has unique values)
or the lowest level of dimension should be the primary key of the dimension table.
thanks alot.
Brad

Hi Matt!
Glad to read you again!
I agree with you that in this simple example, I should be able to make this a star schema.
but :
- on a functional point of view, this date is an attribute of a vehicle, not of an invoice. But let's ignore this.
- this problem is the same as one we have in another part of the BM, which is much more complex. In this complex BM, I can't use star schemas because it removes some joins we need in order to perform some reports.
This is why I'm looking for another way to proceed.
If you have time to spend on the complex BM, here is a simplified description :
* in the physical layer, I have:
- a calendar table with multiple aliases to be used with each dates in the following,
- an invoice header table
- an invoice detail table
with
some header date -> header table -> detail table
some detail table -> detail table
* in the logical layer (stars), i have:
- my calendar dates with their dimensions
- an invoice dimension table with the two sources (header + detail) + its dimension
- an invoice header fact table
- an invoice detail fact table
header date -> header fact
invoice dim -> header facts
invoice dim -> detail facts
detail date -> detail facts
I mus be able to query details facts while showing or filtering the header date. In such a configuration, you'll understand it isn't possible as there isn't any relationship between the detail facts and the header date. This is why the header date should be kept as a dimension of the invoice dimension, which is similar to my basic example.
Unless I went wrong somewhere?
Thanks!
Ced.
Message was edited by:
ced

Exluding lowest level dimensionmembers from a total report.

Hi,
I know this thread might belong in the Discover part of the forum, but based on previous experience it seems that Discoverer for OLAP help is difficult to come by in that part. Also I think this quickly might end up with being a bit more OLAP technical.
To the issue:
Say that you have a sales cube with 3 dimensions, time, product and customer.
The customer dimension has three levels with one standard hierarchy in the following order: Total, customerclass and customertype.
For the lowest level there is a customertype member thats named "internal". This means that all employees buying from their own company with a special discount is placed under this member.
Now to the report:
Using discoverer for Olap, management want two total reports. One where the Internal member is included, and one where it is excluded. This meaning that the initial report should just show the total levels for all dimensions, just with different totals.
Now I thought of just not include the internal member when you choose different dimensions in the query builder, but as far as I know this would only work for the lowest level. Total and customerclass would still show sums that include the internal level since the cube has aggregated these levels in advance.
Does anyone a way to work around this?
some cube facts:
database version 10.2.0.3. with the OLAP A patch
cube compressed and partitioned along month, fully aggregated for all levels(except year).
regards Ragnar

Rangar,
Simplicity is in the eye of the beholder, but you should be able to make it work. The details will depend on your source mapping, but I will assume that you have a single dimension star table with three columns, one per level.
CREATE TABLE CUST
Total varchar2,
CustomerClass varchar2,
CustomerType varchar2
I'll assume further that the member 'INTERNAL' appears as CustomerType. Define a VIEW on top of the table like this.
CREATE VIEW CUST_VIEW AS
SELECT *
FROM CUST
WHERE CustomerType != 'INTERNAL'
Now create two new levels
TOTAL_EXTERNAL
CUST_CLASS_EXTERNAL
Create a new level hierarchy, EXTERNAL_HIER say, that includes the two new levels along with the existing CustomerType level.
TOTAL_EXTERNAL
CUST_CLASS_EXTERNAL
CUSTOMER_TYPE
Note that even though the CUSTOMER_TYPE level appears in two hierarchies, the members in that level can vary be hierarchy. This is important since it means you do not have to reload the leaf data for the cube.
Now map the new hierarchy to the three key columns in CUST_VIEW. To do this correctly you need to switch to the "Snowflake Schema" view on the AWM mappings tab. This allows you to explicitly set the parent column for each hierarchy. So, in your new EXTERNAL_HIER hierarchy the parent of CUSTOMER_TYPE is CUST_VIEW.CustomerClass. In your old hierarchy, INTERNAL_HIER say, the parent of CUSTOMER_TYPE is CUST.CustomerClass. If you don't switch to the "Snowflake Schema" view then you will end up with null values for the parent dimension. (I just wasted 45 minutes discovering this fact.)
You now have two hierarchies and five levels. Your aggregation strategy for the cube should reflect this in some way. If you want full pre-aggregation, then you will need to add the two new levels to the cube. If not, then you are probably set.
David

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

My battery life at a full 100% charge is about 2 hours 22 minutes (backlight and key lights at lowest level). Should I go complaining to Apple or do I just need different software?

My battery life at a full 100% charge is about 2 hours 22 minutes (backlight and key lights at lowest level). Should I go complaining to Apple or do I just need different software? I've only had my mac book since August 2011. The battery dies in 2 to 3 hours with some web surfing (little video play) and photo editing etc. I really don't feel like taking my computer all the way to the apple store to wait there for 5 hours to hear that I need to call someone blah blah blah. Any advice? (BTW Safari hasn't been working since I last updated my mac, WHYYYY?)

emsavage1127 wrote:
Should I go complaining to Apple or do I just need different software?
emsavage1127 wrote:
I really don't feel like taking my computer all the way to the apple store to wait there for 5 hours to hear that I need to call someone blah blah blah.
Make an appointment at the genius bar, that way, you wont have to wait. http://www.apple.com/retail/geniusbar/

Modify Chart Legend Data Behaviour to show only lowest level of drill

I have a chart with a legend in OBIEE 11g.
When I click on chart data or legend it drills to the next level of the hierarchy which is what I want.
However the legend show all levels of the hierarchy in the legend data like this:
"Level 1"."Level 2"."Level 3".
This is very cluttered and redundant as Level 1 & Level 2 are the same for all items.
What I want is that it only shows the lowest level of a hierarchy that has been drilled to eg.
"Level 3"
Is it possible to do this? I've already tried the user guide, on this forum or on google search.
Thanks in advance.

Not sure its doable out the box,
You could hack the popchart JS files I guess, John Minkjan's blog describes some changes , in particular on mouse-hover activity but they should show where to start.

SYST: Tax Jurisdiction code at lowest level not transferred

Dear Experts,
I am getting the above error while Releasing the Billing document to Accounting. I have created a ZTAX - Manual Tax (for enterring VAT% manually). Created the Sales Order, Delivery and Billing. At the time of document releasing to accounting i am getting above error.
Please help.
Thanks in advance

Check this thread
Error: SYST: Tax jurisdiction code at lowest level not transferred
G. Lakshmipathi

Components in the lowest level of costing structure in SO

Hi,
Could you please let me know is any function module to get Components in the lowest level of costing structure in Sales order.
Thanks,
Harinath

Yes, you can manipulate your components any way you like. Becareful about the layout manager though as it likes to handle the positioning and sizing, so there is an intimate relationship there.
Also call validate() on the container after you make your changes.

[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,

Lowest Level of Details

Similar Messages

Maybe you are looking for