Hierarchies modeling in DP

Hi All
I want to model a product hierarchy in DP with 2 different views.
A corporate view for the marketing dept to maintain their forecasts and a sales view for the sales dept.
Demand Planners will use both the views and would like to toggle and see aggregations in both views.
Corp View
All Products
BU
Product Family
Product Line
Item/SKU
Sales View
All Products
BU
Product Family
Product Group
Item/SKU
How can we model this?
Also, how do I associate relationship between the various levels in the hierarchy.
i.e. I would like to make Product Line/Group a parent level to Item and similarly BU will be parent level to Product Family.
Thanks for your time.
Regds
Martian
Edited by: Martian on Mar 24, 2009 5:13 PM

Hi Martian,
DP does not work with hierarchies directly like R/3 but instead it derives them from the sales that it gets through BW.
Here is an example:
You have a product hierarchy like below:
Level1: Finished Product (FM1)
Level2: Assembly (A1 and A2)
Level3: Raw materials (RM1for A1, RM2 for A2)
The sales data that you get in BW should be like this:
Plant________Finished Product_______Assembly_____Raw Material______Qty.
__P1____________FM1_______________A1___________RM1____________10
__P1____________FM1_______________A2___________RM2____________10
The system creates CVCs from the above two records as:
Plant________Finished Product_______Assembly_____Raw Material
__P1____________FM1_______________A1___________RM1_
__P1____________FM1_______________A2___________RM2_
The DP system go ahead with the above two combinations but would never have a hierarchy as such specially.

Similar Messages

Hierarchie Model

Hi,
I have Created "COSTELEMENT" Hierarchie Model in SAP VC,using SAP BI Hierarchies.But i got Error msgApplication Error: " Unspecified Error" while hit on the DrillDown Button.I was mention below My Formulas:
DrillDown::::::::: 'FILTER_NODE_IOBJNM=0HIER_NODE; FILTER_VALUE='&#ID[ACCELUL]@costelement_key&';FILTER_COLLAPSE= ;FILTER_IOBJNM=Z0CSTELMT;CMD_1=CMD%3DDRILL_TO_LEVEL%26LEVEL%3D%26IOBJNM%3DZ0CSTELMT%26DATA_PROVIDER%3DDP;R%3DDP;'
Drillup is working fine.
*DrillUP* 'CMD_1=CMD%3DDRILL_TO_LEVEL%26LEVEL%3D'&NSTR(@costelement_node_level,'B')&'%26IOBJNM%3DZ0CSTELMT%26DATA_PROVIDER%3DDP;'
Can you Suggest me?
Thanks

Basically it will look something like...
http://download-west.oracle.com/docs/cd/B13789_01/appdev.101/b10790/xdb06stt.htm#sthref747
You will need a type with contains an element which is of the type..

Showing non hierarchical model in a jtree

Hi all,
I have the following model:
- 3 classes:
* A Day, consists of a number of Events
* A Project, also consists of a number of Events, a Project has 1 or 0
parent Projects and 0 or multiple childprojects.
* An Event is always linked to 1 Day and 1 Project
I want to create the following tree-structure:
root
+-- Day1
####+-- Project1
####+-- Project2
########+-- Project2_1
########+-- Project2_2
############+-- Event1
############+-- Event2
I have created a custom model to display this. The problem is the following. In the model (which implements the TreeModel), there is a method getChild() to retreive and display the children. Obviously, the events underneath a project (e.g. Project2_2) should only be shown if the following is true:
- event belongs to Project2_2
- event belongs to Day1
The first condition is easy, the last condition is causing the problem. How do I know I am underneath Day1?
regards,
Kenneth

westelinckk,
Your diagram leaf-indentation seems to indicate that, say, Day1 contains Project1, but you've stipulated only that "* A Day, consists of a number of Events". If Days may contain projects, your custom model needs to reflect that.
Also, you say:
Obviously, the events underneath a project (e.g. Project2_2) should only be shown if the following is true:
- event belongs to Project2_2
- event belongs to Day1
I suppose you mean furthermore than both conditions be true. From your post'd title I suspect that an Event may belong to a Day and to a Project, with no implied relationship between the Day and the Project. In that case indenting Project1 under Day1 is misleading.
Incidentally, when working with trees I suggest you use a custommodel-to-treemodel adapter, rather than making your custom model implement treemodel. That way your custom model remains the same, and you write an adapter per view type.
--A

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

SCHEMA: Flat vs. hierarchical

All,
I'd like your feedback on another topic relating to the schema, this
one at a higher level. Basically, the question is whether you think we
should adopt a flat schema, or a hierarchical schema. To explain:
- With a flat schema, we assign some number of "buckets" to hold event
data, give a name to each bucket, and then for any event that comes in
we extract the relevant data and drop it into that bucket
- With a hierarchical schema, we would have a set of "objects" with
attributes that we could attach to events, and then for any given event
that we receive we extract the relevant data and set the various
attributes of the various objects.
You may have already noted that to some extent we already have a
hierarchical schema, in that we define four top-level containers - the
Initiator, Action, Target, and Observer - and then we have some
pseudo-objects under those like User, Host, etc. Right now we sort of
"fake" an object-based schema by using CamelCase, e.g. InitUserName,
InitUserDomain, etc. With a true hierarchical schema, we'd actually have
an object calling Initiator, which might have a child object called
User, which might have attributes Name, Domain, ID.
Please again ignore details about how this would actually be
implemented; you could always convert from one to the other for internal
storage if need be. Instead focus on whether it would be easier to
access the data you want to see by using a hierarchical model or a flat
model.
These are the pros and cons as I see it:
- The flat schema is a little easier to display in a table and easier
to read in a single-line format, but on the other hand the object schema
yields much more interesting, interactive displays (the SLM event
display, again, sort of "fakes" an object schema but putting the Init*
fields at left and the Target* fields at right.
- If we go to an object schema, we could actually reference almost any
type of object we wanted by re-using something like DMTF's Common
Information Model, which describes virtually any manageable IT resource.
Right now if we want to include, say, a MAC address and we hadn't
thought about that before, we have to completely revise our flat schema
and define a new field. The potential downside is that not every event
would then have even a standard set of fields if the values for those
fields were null.
- The other downside of course is how we migrate from one schema to
another if we fundamentally change how this works. I think this is
do-able, however, if we come up with some migration plans and perhaps
support both models in some way for a while (the flat schema, for
example, is just a representation of some subset of object attributes).
So let's give some examples. Let's say that we have a user opening a
file - simple enough. In a flat schema, this might look like:
{ "InitUserName": "user2", "InitUserID": "104", "InitHostName": "dc01",
"TargetDataName": "syslog-ng.conf", "TargetDataContainer":
"/etc/syslog", "TargetHostName": "dc01" }
Note that it's a little ambiguous that this particular username
represents an account on host 'dc01'
But in an object schema, this might look like:
{ Initiator: { Account: { Name: user2, UserID: 104, Host:
dc01}},
"Target": { "File": { "Name": "syslog-ng.conf", "Container":
"/etc/syslog", "Host": "dc01"}}}
OK, so what do you all think?
DCorlette
DCorlette's Profile: http://forums.novell.com/member.php?userid=4437
View this thread: http://forums.novell.com/showthread.php?t=419793

Hi Rokie,
What's the difference between Flat & Qualified Flat table?
    Genarally to avoid the redundancy of data, both Lookup[Flat] and Qualified Flat will be used.
    But What's the difference between Flat & Qualified Flat table?
    Lookup[Flat] contains some set of legal values which can be shared by main table .But in some cases
    we may have the data in some fields changes frequently based on other fields in that table.
    Suppose Price of a particular product changes based on region.Here what we need to understand is
    there are multiple values for each main table product.Obvisouly it increases redundancy of data.
    Qualifer table contains qualifier and non-qualifier fields.
    Data which is frequently changes based on other fields considered as Qualifier fields.
    Non-Qualifier fields contains the data which is responsible of changes in qualifier fields.
     I am giving differences between Lookup[Flat] and Qualified lookup.
     1) Lookup[Flat] contains predefined set of records (Ex: List of manufactures for particular product)
        whereas Qualified lookup contains conditional set of records (Ex: Pricing based on manufaturer and
         region)
   2) Lookup within lookup is possible whereas qualified lookup is possible only on main table
   3) Lookup table record need to be maintained before main table record whereas qualified record is
      maintained after main table gets created.
4) Lookup[Flat] contains relatively small no of records when compared to main table whereas qualified
     lookup contains large no of records when compared to main table.
    For better understanding, go through the above blogs given by others.
   Hope it helps,
   Reward points,if found useful.
   Thanks,
   Narendra.M

How to Display folder structure in Content repository as a tree model

Hi,
I have a requirement in which i need to display a hierarchical folder structure in UCM as a hierarchical model in my portal. Which approach should I follow. Expecting suggestions.. I'm using jdeveloper 11.1.1.5.
Thank you

Sorry , my earlier reply was a bit hasty...
So do you need a navigation model based on a UCM content query ?
Or
Would the document manager taskflow work ?
And you don't need any MDS customization (Terribly sorry for my post above). The default behavior of the document manager is to display the folder structure on the left and the contents on the right.
After you add the DocManager taskflow, go to its properties in composer and make sure the layout is selected as "Explorer". Once you do this, you should notice that a new split pane has appeared, and its collapsed by default. Save the page and open the split pane to see a tree structure of the folder hierarchy in UCM.
Would this work for you ?
-Jeevan

Hierarchical DATA?

I KNOW WHAT IS hierarchical DATA
IN WHICH THE A RECORD HAVE A CHILD AND PARENT RELATION SHIP.
IN WHICH A RECORD SHOULD HAVE ONLY ONE PARENT DATA.
IS THIS RIGHT ANSWER??????
AND I CAN DISPLAY EMP TABLE RECORDS IN hierarchical MODEL
BUT THESE TABLES WILL HAVE THE EXACT MODEL OF hierarchical????????????
IF A TABLE HAVE ONLY hierarchical DATA HOW CAN I RETRIVE THAT DATA???????

I KNOW WHAT IS hierarchical DATA
IN WHICH THE A RECORD HAVE A CHILD AND PARENT RELATION SHIP.
IN WHICH A RECORD SHOULD HAVE ONLY ONE PARENT DATA.
Not Necessary...there can be many to many relationships also
IS THIS RIGHT ANSWER??????
AND I CAN DISPLAY EMP TABLE RECORDS IN hierarchical MODEL
BUT THESE TABLES WILL HAVE THE EXACT MODEL OF hierarchical????????????
What do you mean by "exact model of hierarchy". Plz ask questions clearly...
IF A TABLE HAVE ONLY hierarchical DATA HOW CAN I RETRIVE THAT DATA???????
If i understood your point, then I think you want to ask that if in a table, 2 columns are sharing dependency. Eg: empid and manager_id relationship in employee table. In this case also, we can retrive the data using connect by
select level, manager_id,empid
from employees
start with manager_id=null
connect by prior employee_id = manager_id
I hope this clarifies to you

Model Hierarchy

Hi,
What is the concept of hierarchical Model List. Why do we create model hierarchies. Does this help in efficient vehicle search.If yes, how.
Appreciate your response.
Thanks
Rakesh

Anyone?

Changing name of directory created after source file is extracted

This seems like it should not be a big problem, but I can't figure out how to fix it. I'm writing a PKGBUILD for a program called JAGS (http://calvin.iarc.fr/~martyn/software/jags/). When I use "pkgname = JAGS", the PKGBUILD works perfectly for my purposes, but in the spirit of providing public goods I thought I'd submit it to AUR, which requires the pkgname to be all lower caps. This little detail is causing me problems. (The non-working PKGBUILD is below, and becomes the working PKGBUILD if you switch out the pkgname.)
The source file online is called JAGS-1.0.3.tar.gz. Fine, so I added "$pkgname-$pkgver.tar.gz::" to the beginning of the source url. However, when this file is extracted, it takes the name of the original source file (JAGS in all caps), and then when the build function tries to cd $pkgname-$pkgver it gives errors.
How would you deal with this? Of course I can just change the cd command, but I prefer that the directory be consistent with the package name. Should I add the whole tarball to the noextract argument and include a different tar command in the build function?
pkgname=jags
pkgver=1.0.3
pkgrel=1
pkgdesc="Bayesian hierarchical models using Markov Chain Monte Carlo (MCMC) simulation"
arch=('x86_64')
url="http://calvin.iarc.fr/~martyn/software/jags/"
license=('GPL')
makedepends=('gcc-fortran')
source=($pkgname-$pkgver.tar.gz::http://calvin.iarc.fr/~martyn/software/jags/JAGS-1.0.3.tar.gz)
md5sums=('fa94031290e23d47e26affc571f76e38')
build () {
cd "$srcdir/$pkgname-$pkgver"
./configure --prefix=/usr
make
make DESTDIR="$pkgdir/" install

Change:
cd "$srcdir/$pkgname-$pkgver"
to:
cd "$srcdir/JAGS-$pkgver"
Edit: You may also avoid renaming the tarball on download since this doesn't serve any purpose.
Last edited by foutrelis (2009-11-26 16:56:11)

Migration Essbase Studio Application form 11.1.1.3 to 11.1.2.1

Hi All,
Could please provide the steps or any documents related to the below issue
Migrate 1 Essbase Studio Application (Dimension elements, Schema, Hierarchies, Model, Drill through report) from 11.1.1.3 environment to 11.1.2.1 environment
Thanks in Advance
Venu

Have a read of - Essbase studio Upgrade from 11.1.1.3 to 11.1.2.1 or how to Migrate 1 Essbase Studio Application from 11.1.1.3 to 11.1.2.1
Cheers
John
http://john-goodwin.blogspot.com/

Two 2911 routers and 3560 switches (load balancing and redundancy)

Good day, Sir !
I have a model with hierarchical model. Two routers 2911 and two core switches 3560, two providers.
I want to design redundancy scheme. Can you advice me how is better to do it ? here you can find image with topology, can you say is it good idea to connect with devices in this way ?
Hope on you help ! Thank you !!!

Hi,
If you want to configure redundancy in your network on LAN you can use HSRP and from the WAN side depending on the connection with the provider you can either use BGP or any IGP.
If you want to have load balancing as well with redundancy you can define differnt HSRP group for different vlan and on the wan with BGP you can use multipath option or with IGP you can manipulate the route matric.
Thanks & Regards
Sandeep

How to handle large data sets?

Hello All,
I am working on a editable form document. It is using a flowing subform with a table. The table may contain up to 50k rows and the generated pdf may even take up to 2-4 Gigs of memory, in some cases adobe reader fails and "gives up" opening these large data sets.
Any suggestions?

On 25.04.2012 01:10, Alan McMorran wrote:
> How large are you talking about? I've found QVTo scales pretty well as
> the dataset size increases but we're using at most maybe 3-4 million
> objects as the input and maybe 1-2 million on the output. They can be
> pretty complex models though so we're seeing 8GB heap spaces in some
> cases to accomodate the full transformation process.
Ok, that is good to know. We will be working in roughly the same order
of magnitude. The final application will run on a well equipped server,
unfortunately my development machine is not as powerful so I can't
really test that.
> The big challenges we've had to overcome is that our model is
> essentially flat with no containment in it so there are parts of the
We have a very hierarchical model. I still wonder to what extent EMF and
QVTo at least try to let go of objects which are not needed anymore and
allow them to be garbage collected?
> Is the GC overhead limit not tied to the heap space limits of the JVM?
Apparently not, quoting
http://www.oracle.com/technetwork/java/javase/gc-tuning-6-140523.html:
"The concurrent collector will throw an OutOfMemoryError if too much
time is being spent in garbage collection: if more than 98% of the total
time is spent in garbage collection and less than 2% of the heap is
recovered, an OutOfMemoryError will be thrown. This feature is designed
to prevent applications from running for an extended period of time
while making little or no progress because the heap is too small. If
necessary, this feature can be disabled by adding the option
-XX:-UseGCOverheadLimit to the command line."
I will experiment a little bit with different GC's, namely the parallel GC.
Regards
Marius

Running DMVPN Hub and Spoke on same router?

My client has a project in which traffic flow is hierarchial in nature. Using DMVPNs, the design is for a "center" router to be a DMVPN spoke to the cloud above it, and a DMVPN Hub to the cloud below it. I have tried to lab this up, but no success. I initially build the center router as a DMVPN spoke to teh upper cloud and all is well. As soon as I had the second tunnel config (as the DMVPN hub to the lower cloud), the first tunnel goes down and my EIGRP flaps. Im running EIGRP across the DMVPN tunnels. The two DMVPN clouds are using different network IDs and are running separate EIGRP routing instances.
I can post configs if desired - just wanted to see if anyone is doing this or knows whether it is possible.
Jeff

Hi,
I know it is possible using two DMVPN clouds, but it seems that you need DMVPN phase 3 in this situation. This is suitable for the hierarchical model you want. Take a look at the following link
http://www.cisco.com/en/US/partner/prod/collateral/iosswrel/ps6537/ps6586/ps6660/ps6808/prod_white_paper0900aecd8055c34e_ps6658_Products_White_Paper.html
Hope this helps.

Graphic user interfaces

Does oracle olap have graphic user interfaces like SQL Server Analysis Services?

At Escendo we also offer products that have direct access to the OLAP Option including write back. Escendo Analytics, and Architect. Check us out or contact us at http://www.escendo.com
Escendo Analytics*
* Full graphic Calculation builder including support for aggregations, allocations, models and many others even including the standard regression and forecasting, Geneva Forecasting and Monte Carlo simulation.
* Process Management which utilizes DBMS_SCHEDULER making for multiple threaded processes such as as parallel loading/processing a snap - full dependency mapping and approvals and flexible scheduling.
* Direct Read/Write access through our ad-hoc reporting with all the usual slice and dice features you would expect in a flash front end
* User access control and management through our Business Perspectives (users, groups
* Easy sharing and collaboration - use any standard SQL reporting tools against the the same data (obviously since this is an Oracle Forum I must add that OBIEE, Publisher, APEX etc - literally any reporting tool)
Architect* is a multi-simultaneous developer workbench which allows full direct access to the OLAP Option capabilities, while our Analyzer web interface to Analytics provides
*version Control including optional integration with subversion, promotion management (dev->test->QA->PROD for example)
*partition templates
*Fullly automated multi-user access
*both Visible and non-user visible measures
*aggregation and allocation management
*native support for both level and value based(ragged) hierarchies
*model and Program editing with lots of Features for productivity and quality enhancements (we use it to develop our flagship products)
*Conversion utilities for legacy Express Applications (Like OFA) - we have converted OFA systems (including reports and saved selections) with huge performance boosts in under a week.
Don't forget that since we are inside the database with Oracle OLAP, there are huge benefits in managing a truly integrated solution. As part of the database kernel, you have scalability, performance and reliability which is unrivaled. (Things like rman, imp/exp etc.
A partner has an excel add-in which has native support the Escendo application platform. http://myobjectiveolap.com/index.htm It is very useful in that you have very advanced control and interaction with the OLAP option allowing complete control over your excel formatting and layout.
Edited by: user467608 on Jul 8, 2010 7:41 AM

JTree customization icons

Hello,
Introduction:
The hierarchical model is a part of the reality, a lot of real examples could be implemented, however the difficulty is to make the nodes of the Jtree closer as possible to the real model.
My needs:
1\I need a JTree which should executed as applet.
2\the top , the branches, and the leaves should customizable.(I would like to have a special icons for each)
3\when clicking the user should have a data from a java servlet throught tomcat according to each node.
4\Internationnalization.
The actual situation:
1\I have the tree which executes as applet,
2\I can customize the leaf only by asigning an icon, according to displayed text for the leafe!!!!!!!!!:(
what about the top of the tree and the branches?
also, that will be a reall problem when I will try to make an internationnalization!, isn't it?
so I need a way to make a difference for displayed text and something like an identificator for the tree.
3\When clicking a tree node the action is to launch an url for a servlet whith passing the displayed text in the tree as a parameter, then the servlet will display the corresponding document(jsp).
as it's explained in 2\ that will be a real problem when internationnalizing.
My Questions:
1\Is there any way the customize all the icons in a tree?, one by one...
2\Is it possible to refer to a node with an identificator?, as an internal identificator for the programme.And of course the displayed text will different?
3\Please, provide my with some working codes sources.
Thanks and Regards,
kifwet

Hi,
I was working on tree icons last week. I used a tree renderer.
Something like that :
JTree tree;
tree.setCellRenderer(new MyRenderer());
private class MyRenderer extends DefaultTreeCellRenderer {
          Icon treeCollapsedIcon;
          Icon treeExpandedIcon;
          Icon leafIcon;
          public MyRenderer() {
               super();
public Component getTreeCellRendererComponent(JTree tree,
                                                                                          Object value,
                                                  boolean sel,
                                                  boolean expanded,
                                                  boolean leaf,
                                                  int row,
                                                  boolean hasFocus) {
     super.getTreeCellRendererComponent(tree, value, sel, expanded, leaf, row, hasFocus);
     if (leaf ) {
               setIcon(leafIcon);
               } else {
                    if (expanded) {
               setIcon(treeExpandedIcon);
               }else{
                    setIcon(treeCollapsedIcon);
     return this;
I hope this will help you
Zauz

Hierarchies modeling in DP

Similar Messages

Maybe you are looking for