Is it possibole to implement mutiple layer hierarchies in Essbase?

Hi experts,
I want to know whether the following layout is implemented. How to create different layer hierarchies in ESSBASE?
If it does work , I want to drag this hierarchy into presentation. Please help me as soon as possible. Thanks.
For example:
Presentation Hierarchy
Total
---Region(Region Table)
-----District(Region Table)
---------Brand(Product Table)
-------------Product Type(Product Table)
-----------------Product Detail(Product Table)

Well, I have to say that I do not really not OBIE so I can not make a good comparaison.
What I could say is that in Essbase we use to have multiple dimension that we cross all the time
Therefore in your exemple I would have 2 dimension, one called Entity :
Total
----Location
--------Region1
------------District1
------------District2
--------Region2
------------District3
------------District4
An other called Product:
-Product
-----Brand
---------Product Type
-------------Product 1
Then you "cross" the two dimension like:
Product Type
Product1 | Product 2 | Prodcut 3 ...
Distric1 100 200 300
Distric2 110 220 250
There is on exemple here of hierarchy done in Outline Editor in Essbase:
http://2.bp.blogspot.com/__2AaArK5lW8/TUWdz2-HQbI/AAAAAAAACzc/pp7vUsTRhmQ/s1600/1.png
One exemple of the result in essbase:
http://3.bp.blogspot.com/-9yQ4tsNOd-s/TWhGeHjK53I/AAAAAAAAAXw/B4lU72dEUPg/s1600/AddinMode.jpg
Hope it will help you
PS: Could you mark my answer as helpfull :)

Similar Messages

OBIEE 11.1.1.6 different layer hierarchies

Hi experts,
I want to know whether the following layout is implemented. How to create different layer hierarchy in BMM in OBIEE 11.1.1.6?
If it does work , I want to drag this hierarchy into presentation. Please help me as soon as possible. Thanks.
For example:
Presentation Hierarchy
Total
---Region
-----District
---------Brand
-------------Product Type
-----------------Product Detail

Hi SPowell42,
I am using OBIEE 11.1.1.6 to design and develop anything.
I have searched some related help information in RPD, and found 'modeling dimensions with multiple hierarchies in the presentation layer ' title which introduced some simple hierarchy information,such as
Country
--Region
-----City
-------Supplies
-------------Product
-------------------Product detail.
I am not sure whether it can do different layer hieiarchy in hieiarchy persenation. Maybe the sample column data stored in one table, however, it is my assumption.

How to Display Mutiple CostCentre Hierarchies in the Report

Hi Team,
As we have multiple Hierarchy groups defined in R/3 for Cost Centres, I would like reflect he CC values in the CC report where it is showing the default Hierarchy (only) whereas others are appearing in NotAssigned, is there a way to handle the system to display all Hierarchies listed in the 'Restrictions' more than one Hierarchy.
your expert adivse is highly appreciated.
Thanks in Advance, BR.

Gentlemen any luck..!

Implementing a layer 7 Protocol

Hi everybody
Ive learned Java for three years at school, but I am not really an expert
Im playing around with Java networking (a small client / server architecture) and now I want to implement a small protocol. The protocol should be modular and quite simple, but I don't know how to implement it.
My idea up to now was to write messageobjects which implement an interface and therefore contain a method called invokeAction. When any part receives such an object, the invokeAction Method is invoked. This means that the message contains all the logic needed to do something. But then it's difficult for the message to access Server / Client components and also the messages will become very big when the logic becomes more complex.
How can this be done in a more efficient way and how is such a protocol implemented in a real program
Sry for my bad english ;)

From what you describe, it sounds like you simply want to serialize an object using, for example, [ObjectOutputStream.writeObject()|http://java.sun.com/javase/6/docs/api/java/io/ObjectOutputStream.html#writeObject(java.lang.Object)].
You'll also have to serialize any other objects and primitives used by that method and not present on the other end.
As for efficiency, there's no point asking how to make it "more efficient" until you have specific performance requirements and specific problems where those requirements are not being met.

Mutiple layer installation on one PC possible ?

I trying to learn from the cDS supplied during i/develop 2000 conference. There are multi layer servers and the software for multi track. Can any one suggest me how to categorically install the software and learn.
Incidently the developer/designer tools and the enterprise manager do not share the same oracle home. So it is largly confusing which should me primary home.
Above all the installation step suddenly stops without completion..
Please help and send mail through [email protected] or [email protected]
null

RustyF if you do not have reliable high speed Internet access then we would recommend you utilize Creative Suite 6. You can purchase or upgrade to CS6 at http://www.adobe.com/products/catalog/cs6._sl_id-contentfilter_sl_catalog_sl_software_sl_c reativesuite6.html?start=10.
If you do want to proceed with a Creative Cloud membership then I would recommend moving the computer to a location with a stable high speed access to download and install the software. It is likely many of the updates could then be fetched without difficulties under less stable conditions.
As an alternative you can download the installation files by following the directions listed at http://prodesigntools.com/adobe-cc-direct-download-links.html. Please make sure to complete the Very Important Instructions section prior to clicking on the download. This will also only get you the base installers. You will still need to download the remaining updates on the installed computer. This is why I would recommend the first option if you wish to proceed with a Creative Cloud Membership without having stable high speed Internet access.
Finally you can find more information on this topic in our Creative Cloud FAQ at http://www.adobe.com/products/creativecloud/faq.html.

How to update all hierarchies in Essbase Studio

Hi All,
Currently I am building ASO cube using Essbase Studio.We are having 6[Stored]+1[Accounts] hierarchies in that 3 hiearchies contains 4 generations and remianing 3 hiearchies contains 3 generations with 20 attricbutes each.When I am trying to use "INCREMENTAL LOAD" with "Update all hierarchies" option records gets rejected.When I am using "Incremental Load" with "Rebuild hierarchies" it taking very long time.
Since our ware house is huge I cannot reset all and load from first.
Can someone assist me how to update the hierarchies on daily basis in less time
Note: In our cube we dont have any shared members
Thanks,
SatyaB

The == and !== are to set conditions for filtering. the ! meand not. In esscense these allow you to get a subset of rows that meet the conditions specified. In your case where Gender == "M" you will only get those rows where the value is "M". What you want to do is transform rows not filter them. I have not looked at studio enough yet to know how to do this, but a few things come to mind. First, you could use text to create the outline menbers instead of values from the tables, you could crete a reference table with the M = Male and F = Female and join to it to get the values or you could use a standard load rule and sql interface to load the data and just build the dimensions and drill through from Studio. I think I would opt for the second option

Import Hierarchies into Essbase Studio

Hi all,
I am running Essbase Studio 11.1.1.3.00.I have exported hierarchies into text files from an EAS database. I want to use the files to create the hierarchies in Studio. Is this possible and how can I do it?
Thanks in advance.

Sorry I slightly misunderstood. If you are talking about an export, then it will not give you what you need. You would have to get the hierarchies from your Essbase model. Options for doing that would be
ODI,
the outline extractor available at appliedOlap.com (there is also one from Star Analytics that I don't remember the name of)
or from the API.
Each of the dimension extracts would have to be in a format acceptable to Studio like Parent child. You would have to include all the properties of each member to get it to build properly. Then you could load your data (either from within studio or with just a load rule.

Ask the Expert: Hierarchical Network Design, Includes Core, Distribution, and Access

Welcome to the Cisco® Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about hierarchical network design.
Recommending a network topology is required for meeting a customer's corporate network design needs in their business and technical goals and often consists of many interrelated components. The hierarchical design made this easier like "divide and conquer" the job and develop the design in layers.
Network design experts have developed the hierarchical network design model to help to develop a topology in discrete layers. Each layer can be focused on specific functions, to select the right systems and features for the layer.
A typical hierarchical topology is
A core layer of high-end routers and switches that are optimized for availability and performance.
A distribution layer of routers and switches that implement policies.
An access layer that connects users via lower-end switches and wireless access points.
Ahmad Manzoor is a Senior Pre-Sales Engineer at AGCN, Pakistan. He has more than 10 years of experience in first-rate management, commercial and technical skills in the field of data communication and services lifecycle—from solution design through sales pitch, designing RFPs, architecture, and solution—all with the goal toward winning projects (creating win/win situations) of obsolete solutions. Ahmad also has vast experience in designing end-to-end data centers, from building infrastructure design to data communication and network Infrastructure design. He has worked for several large companies in Pakistan and United Arab Emirates markets; for example, National Engineer, WATEEN Telecom, Emircom, Infotech, Global Solutions, NETS International, Al-Aberah, and AGCN, also known as Getronics, Pakistan.
Remember to use the rating system to let Ahmad know if he has given you an adequate response.
Because of the volume expected during this event, Ahmad might not be able to answer every question. Remember that you can continue the conversation in the Solutions and Architectures under the sub-community Data Center & Virtualization, shortly after the event. This event lasts through August 15, 2014. Visit this forum often to view responses to your questions and the questions of other Cisco Support Community members.

Dear Leo,
We are discussing the following without any product line, discussing the concept of hierarchical design, which will help you to take decision which model is better for you Two Layer or Three Layer hierarchical model.
Two-Layer Hierarchy
In many networks, you need only two layers to fulfill all of the layer functions—core and aggregation
Only one zone exists within the core, and many zones are in the aggregation layer. Examine each of the layer functions to see where it occurs in a two-layer design:
Traffic forwarding—Ideally, all interzone traffic forwarding occurs in the core. Traffic flows from each zone within the aggregation layer up the hierarchy into the network core and then back down the hierarchy into other aggregation zones.
Aggregation—Aggregation occurs along the core/aggregation layer border, allowing only interzone traffic to pass between the aggregation and core layers. This also provides an edge for traffic engineering services to be deployed along.
Routing policy—Routing policy is deployed along the edge of the core and the aggregation layers, generally as routes are advertised from the aggregation layer into the core.
User attachment—User devices and servers are attached to zones within the aggregation layer. This separation of end devices into the aggregation permits the separation of traffic between traffic through a link and traffic to a link, or device. Typically, it is best not to mix transit and destination traffic in the same area of the network.
Controlling traffic admittance—Traffic admittance control always occurs where user and server devices are attached to the network, which is in the aggregation layer. You can also place traffic admittance controls at the aggregation points exiting from the aggregation layer into the core of the network, but this is not common.
You can see, then, how dividing the network into layers enables you to make each layer specialized and to hide information between the layers. For instance, the traffic admittance policy implemented along the edge of the aggregation layer is entirely hidden from the network core.
You also use the core/aggregation layer edge to hide information about the topology of routing zones from each other, through summarization. Each zone within the aggregation layer should have minimal routing information, possibly just how to make it to the network core through a default route, and no information about the topology of the network core. At the same time, the zones within the aggregation layer should summarize their reachability information into as few routing advertisements as possible at their edge with the core and hide their topology information from the network core.
Three-Layer Hierarchy
A three-layer hierarchy divides these same responsibilities through zones in three vertical network layers,
Traffic Forwarding—As with a two-layer hierarchy, all interzone traffic within a three- layer hierarchy should flow up the hierarchy, through the layers, and back down the hierarchy.
Aggregation—A three-layer hierarchy has two aggregation points:
At the edge of the access layer going into the distribution layer
At the edge of the distribution layer going into the core
At the edge of the access layer, you aggregate traffic in two places: within each access zone and flowing into the distribution layer. In the same way, you aggregate interzone traffic at the distribution layer and traffic leaving the distribution layer toward the network core. The distribution layer and core are ideal places to deploy traffic engineering within a network.
Routing policy—The routing policy is deployed within the distribution layer in a three- layer design and along the distribution/core edge. You can also deploy routing policies along the access/distribution edge, particularly route and topology summarization, to hide information from other zones that are attached to the same distribution layer zone.
User attachment—User devices and servers are attached to zones within the access layer. This separation of end devices into the access layer permits the separation of traffic between traffic through a link and traffic to a link, or device. Typically, you do not want to mix transit and destination traffic in the same area of the network.
Controlling traffic admittance—Traffic admittance control always occurs where user and server devices are attached to the network, which is in the access layer. You can also place traffic admittance controls at the aggregation points along the aggregation/core edge.
As you can see, the concepts that are applied to two- and three-layer designs are similar, but you have more application points in a three-layer design.
Now the confusion takes place in our minds where do we use Two Layer and where the Three layer hierarchical model.
Now we are discussing that How Many Layers to Use in Network Design?
Which network design is better: two layers or three layers? As with almost all things in network design, it all depends. Examine some of the following factors involved in deciding whether to build a two- or three-layer network:
Network geography—Networks that cover a smaller geographic space, such as a single campus or a small number of interconnected campuses, tend to work well as two-layer designs. Networks spanning large geographic areas, such as a country, continent, or even the entire globe, often work better as three layer designs.
Network topology depth—Networks with a compressed, or flattened, topology tend to work better as two-layer hierarchies. For instance, service provider networks cover large geographic areas, but reducing number of hops through the network is critical in providing the services they sell; therefore, they are often built on a two-layer design. Networks with substantial depth in their topologies, however, tend to work better as three-layer designs.
Network topology design—Highly meshed networks, with many requirements for interzone traffic flows, tend to work better as two-layer designs. Simplifying the hierarchy to two levels tends to focus the design elements into meshier zones. Networks that focus traffic flows on well-placed distributed resources, or centralized resources, such as a network with a large number of remote sites connecting to a number of centralized Data Centers, tend to work better as three-layer designs.
Policy implementation—If policies of a network tend to focus on traffic engineering, two-layer designs tend to work better. Networks that attempt to limit access to resources attached to the network and other types of policies tend to work better as three-layer designs.
Again, however, these are simple rules of thumb. No definitive way exists to decide whether a network should have two or three layers. Likewise, you cannot point to a single factor and say, “Because of this, the network we are working on should have three layers instead of two.”
I hope that this helps you to understand the purposes of Two Layer & Three layer Hierarchical Model.
Best regards,
Ahmad Manzoor

Multiple Hierarchies in one dimension - comments?

multiple hierarchies
Hi Experts,
I'd like your comments on my implementation of multiple hierarchies in one dimension.- especially if this can be done in a way that:
a) still enables users to choose the hierarchy in a dashboard prompt
b) reduces maintenance to a minimum
The dimension groups ages into several different groups like the example below:
Hierarchy1 Hierarchy2
Age......Groups........Groups.....
0........0-2...........0-5
1........0-2...........0-5
2........0-2...........0-5
3........3-5...........0-5
4........3-5...........0-5
75.......70-75.........70-80
76.......76-80.........70-80
Right now I've implemented this by defining one dimension having one hierarchy:
Total
....Hierarchy
.......Group
.........Age
The underlying logical table is based on several logical table sources (LTS) - one for each hierarchy as shown in the first example(Hierarchy1, Hierarchy2).Every LTS has a fragmentation definition filtering on values on 'hierarchy-level'.
Columns in the logical table (and of course in the underlying LTS) are:
Column               mapped to hierarchy-level
- Hierarchy          Hierarchy
- Hierarchy_id          Hierarchy
- Group          Group
- Group-id          Group
- Age               Age
Advantages:
A answers / dashboard user can select one or more hierarchies by using a dashboard prompt.
Adding a new hierarchy (a new grouping) doesn't need changes in the dimension itself
Disadvantages:
A new grouping needs manual steps to implement
- a new physical table
- a new LTS attached to the logical table (including the fragmentation content)
Thanks for your time and comments
Regards
Andy

multiple hierarchies
Hi Experts,
I'd like your comments on my implementation of multiple hierarchies in one dimension.- especially if this can be done in a way that:
a) still enables users to choose the hierarchy in a dashboard prompt
b) reduces maintenance to a minimum
The dimension groups ages into several different groups like the example below:
Hierarchy1 Hierarchy2
Age......Groups........Groups.....
0........0-2...........0-5
1........0-2...........0-5
2........0-2...........0-5
3........3-5...........0-5
4........3-5...........0-5
75.......70-75.........70-80
76.......76-80.........70-80
Right now I've implemented this by defining one dimension having one hierarchy:
Total
....Hierarchy
.......Group
.........Age
The underlying logical table is based on several logical table sources (LTS) - one for each hierarchy as shown in the first example(Hierarchy1, Hierarchy2).Every LTS has a fragmentation definition filtering on values on 'hierarchy-level'.
Columns in the logical table (and of course in the underlying LTS) are:
Column               mapped to hierarchy-level
- Hierarchy          Hierarchy
- Hierarchy_id          Hierarchy
- Group          Group
- Group-id          Group
- Age               Age
Advantages:
A answers / dashboard user can select one or more hierarchies by using a dashboard prompt.
Adding a new hierarchy (a new grouping) doesn't need changes in the dimension itself
Disadvantages:
A new grouping needs manual steps to implement
- a new physical table
- a new LTS attached to the logical table (including the fragmentation content)
Thanks for your time and comments
Regards
Andy

Leave Request two layer approval

Dear Experts,
I'm trying to implement two layer approval leave request workflow by copying and modifying standard workflow WS12300111.
I follow the guide from this link:
http://wiki.sdn.sap.com/wiki/display/ERPHCM/CustomizingtheESSLeaveApprovalusingBusiness+Workflow
My workflow step is as follow:
1. first approver has approve the request
2. reset req object status to SENT
3. set next approver using method if_pt_req_request->set_next_processor
4. send the request to the second approver
I have implement badi PT_GEN_REQ to set first approver (method IF_EX_PT_GEN_REQ~FIND_RESP_AND_DEFAULT_NEXT_PRC) so that the first approver name shown correctly when requestor create the request.
Now there are 3 problems I'm facing:
1. After the FIRST approver approve the request, the note he input is shown twice. I found out this is because the status change create new version of the document. I have tried to clear this note when changing the status using method if_pt_req_request->set_notice. However, the method ignore if the notice is set to blank. Is there anyway to hadle this?
2. When SECOND approver reject the request, I want the request to be revised by the requestor, and then forwared to FIRST approver after that. For this purpose, before send the workitem to requestor back, I put step to set approver back to FIRST approver again using method if_pt_req_request->set_next_processor. But it seems this doesn't work and the request is sent to SECOND approver after revised. The supervisor name that is shown when requestor revise the request also show the SECOND approver name instead the FIRST approver.
3. I find difficulties to create email notification if the request is changed by the requestor during approval process, since there are no event triggered. Is there anyway to trigger this event or is there any workaround?
Thank you.
Regards,
Ponty

Hi Ponty,
I am trying to implement two layer approval for leave request, too.
I took a copy of standard WS12300111 as you did.
I followed the guide, you mentioned. For one level approval this works nearly out of the box.
But I don't understand the second half of the guide.
For me it will be the first time to implement a BAdI. I never did this before.
Can you please explain me, how to do it and how you enhanced the workflow for two layer approval?
Some screenshots might be useful. Eventually you can enhance the guide you mentioned.
Regarding the numerous questions on multi level approval, these hints might be useful for a large number of users.
I would be very happy, If somebody can help me, becaus I didn't know any workflow experts who can help me implementing the BAdI.
Thank you.

Why are tables disappearing when Engineering Logical Entity Hierarchies to Relational

Tables disappearing when Engineering Entity Hierarchies Logical to Relational
We are using 4.0.3. We have a model with imported from Designer with a number of Entity Hierarchies.
The model has a three of entity hierarchies (ORD, PLAN and STEP) each with a number of subtypes. Single tables are built for each of the entity hierarchies and are called (ORD, PLAN and STEP).
If I make a change within an entity hierarchy in the subtype (ORD_METRIC) and forward engineer the only ORD entity hierarchy as single table, the table ORD gets update but the tables STEP and PLAN disappears from the Relational table list. They only remain if I select all three entity hierarchies when engineering to relational.
Have I a missed selecting an option?

Hi,
in current implementation for entity hierarchies (only) - "engineering to" flag is used also as implementation flag for entity, i.e. if entity is not set to be engineered there will be no implementation as table for that entity in relational model. Attributes of such entity will be implemented in another entity engineered to relational model. If no one entity from hierarchy is engineered (no implementation) then existing corresponding table(s) will be removed.
We'll change it in the future to be less confusing.
Philip

How to decide implementation way for share point site ?

Hi,
I am developing new share point site where i want to manage more hierarchical data with its own business requirements and flows.
lets assume following scenario
there are multiple companies at very top level
Every company contains multiple departments
and every department have multiple groups (group of working people)
I want to manage communication between each group within each company, and no two group from two diff companies should interact with each other.
For this implement what will be the better approach for site design ? and how can i implement such a hierarchical structure ?
As i am new to share point , any help will be appreciable.
Thanks,
C Mahone

Create a separate site collection for each company. For every department you can have a sub site. You can create groups within the sub site.
Once you separate the each company details in a separate site collection you will have more control over the security.
Check the below link for site planning in SharePoint
http://technet.microsoft.com/en-us/library/ee476994%28v=office.15%29.aspx
My Blog- http://www.sharepoint-journey.com|
If a post answers your question, please click Mark As Answer on that post and Vote as Helpful

Value based hierarchies, Skip Level Hierarchies

Hello,
I need to create hierarchy based on column value , Please give me some details on implementing value based hierarchies and skip level hierarchies in obiee 10.1.3.
Thank you

With 10.3 i do not think we have a inbuilt solution to build value based hierarchies, you have to flatten the hierarchy and build a level based hierarchy.
OBIEE 11g has value based hierarchies feature.
refer this one for 11g.
http://sandybi.wordpress.com/2010/08/17/hierarchies-in-obiee-11g-part-1/
- Madan
Edited by: Madan Thota on Sep 14, 2010 11:15 AM

Mutiple enhancements in BADI

Hello SDNites,
I have some queries related to BADI implementation,
1. BADI can be implemented mutiple times. But can multiple implementation be active at the same time.
If no, what is the use of saying that BADI can be implemented multiple times.
If yes, how can we do it and how do we know in which order which implementation is triggered. Also if I do not want some implemntations to be called, is there any option other than deactivating the BADI?
If there is some example availble which will help in giving a better insight of the topic, provide the same also.
Abhishek

Hi Abhishek,
yes BAdi can be implemented multiple times.
you just need to check the "Multiple use" check box in definition. and also for the implementations which you want as active maintain the "Implementation is active " checkbox.
Calling mutiple implemented BADi.
1. for each implementation create the filters. these filter values you need to get from some DB elements.
and also this filter values you need to mention during the calling of BAdi implementation.
based on the filter value mentioned, the respective BAdi implementation will be called.
2. If the BAdi's are not filter dependent, the call may be in the order of how we see in badi definition.
refer to http://help.sap.com/erp2005_ehp_04/helpdata/EN/e4/5c3642eca5033be10000000a1550b0/frameset.htm
Regards
Edited by: Seemanthini R on Mar 10, 2009 4:57 AM

View and Layer help

I'm trying to make a simple program to help me learn layers that when a touch event happens a layer with a red bg color is created from the initialtouch point to the final. Here's my code so far for the touchmove method
CGPoint pt = [[touches anyObject] locationInView:self];
CGRect boundMe=CGRectMake(startLocation.x, startLocation.y, (pt.x-startLocation.x), (pt.y-startLocation.y));
addMe=[CALayer layer];
addMe.frame=boundMe;
CGColorSpaceRef rgbColorspace = CGColorSpaceCreateDeviceRGB();
CGFloat values[4] = {1.0, 0.0, 0.0, 1.0};
CGColorRef fml=CGColorCreate(rgbColorspace, values);
addMe.backgroundColor=fml;
[self setLayer:addMe];
However I keep on getting an error when i try to set the view(this is in a class which implements view) layer to the addMe layer. How do I do this?

I also tried moving thius code into the view controller class and I got it to atleast compile by using a UIView instead of a CALAyer but nothing is being drawn on the screen

Is it possibole to implement mutiple layer hierarchies in Essbase?

Similar Messages

Maybe you are looking for