Hierarchy Modelling

Dear Experts,
I am new to SAP BI world. I need your expert advice.
I am modelling a hierarchy for 0material. My client has 5 different levels for each material.
Business Unit
   Department
   Category
    Class
     Sub Class
     0MATERAIL
A Business Unit can have multiple departments, a department can have multiple categories etc.
All the tranactional data will be posted at 0MATERIAL level and reports needs to be generated to allow the customer to drill down and up along the material hierarchy.
- Do i need to include all the 5 levels as NAV attributes in 0MATERIAL attributes tab ?
- We have business unit heads and Departments heads. When they execute the queries, they should get their own department of business units. Is it possible to model this in BI ?
- What will happen to history, when a material moves from one sub class to another sub class. I am not using any time dependency?
Any help is highly appreciated.
Regds,

Hi ,
Welcome to SDN........
Check here.....
http://help.sap.com/saphelp_nw04/Helpdata/EN/0e/fd4e3c97f6bb3ee10000000a114084/frameset.htm
http://www.sap-img.com/business/load-master-data-hierarchies-from-r3-system.htm
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/20a709c1-0a8e-2a10-21b4-f779728c63bf
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/6ce7b0a4-0b01-0010-52ac-a6e813c35a84
Thanks,
Vijay.

Similar Messages

WebAPI question about Hierarchy modeling

Hi all,
I have come to a issue about Hierarchy modeling. I want to use WebAPI to drill down the query in the visual composer. And I have follow every steps mentioned in this PDF file
</people/prakash.darji/blog/2006/08/24/overcome-limitations-around-using-bi-hierarchies-in-vc-by-using-ui-elements-from-wad
Here is my webapi:
'FILTER_NODE_IOBJNM=0COUNTRY;FILTER_VALUE='&@Country_key&';FILTER_COLLAPSE= ;FILTER_IOBJNM=0COUNTRY;
CMD_1=CMD%3DDRILL_TO_LEVEL%26LEVEL%3D2%26IOBJNM%3D0COUNTRY%26DATA_PROVIDER%3DDP;'
It's really same to the webapi in the PDF file except the different characteristic. and my model structrue is also the same as that one. And I has also confirmed the displaying hierarchy is checked in the query.
The issue is that the "drill to level" part of the webapi works well, but the filter doesn't work. I have no idea why. Can anyone help me?
Regards,
Dicky

Dicky,
I struggled with this for 3 days, I understand your pain. After a deep investigation I found that my mapping was incorrect. Try this:
1) Double click on DRILLDOWN connection between output and input ports
2) Check if WEBAPI inputfield has the web api commands
3) Make sure that none of the other input fields have values set. It usually happens that when you connect the output to the input port, similar (or like) variables are mapped automatically, for example in my case, I had Org_unit mapped to @Org_unit automatically. Delete such mappings. You should have only the WEBAPI input field with an assigned value.
Hope this helps,
Kiran

SCM Master Data (BOD) hierarchy modelling question

Hello BI Modelling Experts!
I'm an SCM developer and we are experimenting with modelling a special SCM master data (BOD hierarchy - see [SAP Help BOD|http://help.sap.com/saphelp_scm70/helpdata/en/1a/d92d412ac9f323e10000000a155106/content.htm] and [product BOD assignment|http://help.sap.com/saphelp_scm70/helpdata/en/77/5f41418da8db2be10000000a1550b0/content.htm] for more details) in BI.
The problem is, I'm not really sure how we should go ahead.
The modelling difficulties can probably be understood if we condider the following scenarios for using BOD:
1. A BOD contains APO locations, but of course the same location can be in different BODs (having a different hierachy of locations)
2. BOD is assigned to an SCM product
3. Only one BOD is valid for a product at a specific time, but the BOD can be different for different time periods
4. A BOD structure (for a specific BOD name, i.e. BOD01) doesn't change, so the hierachy itself is not time dependent, but the actual assignment of a specific BOD to an SCM product is (or can be) time dependent
5. A BOD can have theoretically any number levels, so it can be 1 level or even 4-5 level as well
Any ideas are welcome!
Let me know if you need further details.
Thanks in advance!
Best regards,
Bence
Edited by: Bence Blaske on Jun 2, 2009 10:00 AM

Hello BI Modelling Experts!
I'm an SCM developer and we are experimenting with modelling a special SCM master data (BOD hierarchy - see [SAP Help BOD|http://help.sap.com/saphelp_scm70/helpdata/en/1a/d92d412ac9f323e10000000a155106/content.htm] and [product BOD assignment|http://help.sap.com/saphelp_scm70/helpdata/en/77/5f41418da8db2be10000000a1550b0/content.htm] for more details) in BI.
The problem is, I'm not really sure how we should go ahead.
The modelling difficulties can probably be understood if we condider the following scenarios for using BOD:
1. A BOD contains APO locations, but of course the same location can be in different BODs (having a different hierachy of locations)
2. BOD is assigned to an SCM product
3. Only one BOD is valid for a product at a specific time, but the BOD can be different for different time periods
4. A BOD structure (for a specific BOD name, i.e. BOD01) doesn't change, so the hierachy itself is not time dependent, but the actual assignment of a specific BOD to an SCM product is (or can be) time dependent
5. A BOD can have theoretically any number levels, so it can be 1 level or even 4-5 level as well
Any ideas are welcome!
Let me know if you need further details.
Thanks in advance!
Best regards,
Bence
Edited by: Bence Blaske on Jun 2, 2009 10:00 AM

Hierarchies in SAP MDG data model

Hello Gurus,
Could any one please let me know how to create hierarchies in SAP MDG Data models..I have gone though the SAP Help document and but couldn't understand it..If any one has worked on this , please let me know.
Regards,
Raghu.

Hi Jose,
I'll start with simple hierarchy demo containing HIERARCHY NAME, GROUP and OBJECT.[HIERARCHY NAME is the top node, GROUP is the middle node and OBJECT is the end node]
1.In data model, you have to create all the as 3 entity types.
2.In the middle node,i.e. GROUP here, choose the hierarchy option as version dependent or Non-version dependent as per your requirement.
3.In the middlle node,i.e. GROUP here, build hierarchy by assigning
Entity Type for hierarchies ->Entity Type of Node , Use
Here the top node,i.e. HIERARCHY NAME ,will be assigned use as Hierarchy names
You can find related documentation by using F1 help on specific field.
4.Your hierarchy model is now ready.
Regards,
Vkanc9

Reassignment of hierarchy nodes dynamically

Hi Experts,
I have a requirement wherein I need to re-assign the hierarchy node for an account based on Functional area.
Currently, we load 0ACCOUNT info object with hierarchy defined in KDH3 transaction in R/3. Here, the account 650000000 is defined under local accounts node of the hierarchy. Hence, when we use the 0account infobject in BEx with hierarchy activated, all the records in transaction data with account no. 650000000 are aggregated under local accounts node.
However, the user wants us to check the functional area for each of the record with 65000000 account and re-assign it to a different node of the hierarchy. For example, if the transaction data has account number 65000000 and functional area 400, then the record needs to be aggregated under a different node in hierarchy, say overhead costs. Similarly, if there is another record with account 650000000 and functional area 300, then the record needs to be aggregated under Sales & marketing.
How do we handle such conditional assignment of hierarchy nodes?
Regards,
SS

Hi,
I really doubt if dynamic reassignment of hierarchy nodes is possible in BW, but could be wrong.
Alternatives which you can consider
a. A flat hierarchy modeled in the dimension of the cube i.e. higher levels of 0ACCOUNT can be filled during transformations based on functional area. Major disadvantage here is that any change to the hierarchy or assignment could require reloads depending on your requirement i.e. touch history data or not
b.Customized Hierarchy created by combining the original hierarchy and the assignment details
for eg
Leaf Node: 650000000_400 under parent Overhead Costs
Leaf Node: 650000000_300,under parent Sales & Marketing
Regards,
Advait

How to achieve parent-child relationship using self join?

my table structure is as follows
parent child name
-1     1     A1
1     2     A2
1     3     A3
how to achieve the hierarchy model using self join. this can be easily achieved using "connect by prior". but how to achieve the same using self join?

Hi,
Yes, that's definitely possible. If you only need to display two levels from the hierarchy, a self-join is a good option. Make it an outer join if you need to show everyone on one level, regardless of whether they have a match on the other level or not; for example, if you want the output:
child_name     child_id     parent_name     parent_id
A1          1
A2          2          A1          1
A3          3          A1          1It's good that you posted some sample data. Now post the results you want from that data, and your query (what you think is the best attempt you've made so far). If you haven't tried anything so far, then look at some other simple self-join to get ideas.

Java 1 vs. Java 2 Event Handling

Prelude: This question relates to writing code for event handling.
Java 1 is based on a hierarchy model to handle events, ie. inheritance from superclasses. Java 2 uses delagation event handling method. Java 2 code will not compile if it includes Java 1 code still modeled according to Java 1 event handling.
Question:
Is it generally easier to start completely over in trying to convert Java 1 code into Java 2 code by not retaining any Java 1 code and begin reconceptualizing what is needed for a conversion to Java 2?

From what I understand java2 should support both models, however not both at the same time, you cant mix the modles...
I also think that the older models methods or at least most have been depreciated, meaning that the old model will, if it hasnt allready in the latest release, dissapear.. For that single reason I would recommend updating the event model to the delegation model if you hope to keep it around and running for years to come. You gain a bit by doing this since the newer model is much faster!!!

OLAP View generator 10.2.0.3

Hi,
I am trying to use OLAP view generator plug in with AWM 10.2.0.3A. My all the dimensions are value based and only time dimension is level based.
I am not able to generate views for the value based dimensions but view for time is getting generated without any issues. I am getting following error when generating for account dimension.
AUG-03-2009 09:50:40: ... populating dimension map for ACCOUNT
AUG-03-2009 09:50:40: ..... clearing mappings for the dimension
AUG-03-2009 09:50:40: ..... retrieving physical objects
AUG-03-2009 09:50:42: ..... checking for value hierarchies
AUG-03-2009 09:50:42: ..... retrieving label for dimension levels
AUG-03-2009 09:50:42: ..... populating mapping info for the DIMENSION clause
AUG-03-2009 09:50:42: ..... populating mapping info for the INHIERARCHY clause
AUG-03-2009 09:50:42: ..... retrieving hierarchy information
AUG-03-2009 09:50:46: ..... populating mapping info for the HIERARCHY and FAMILYREL clauses for hierarchy COMPLETEPL
AUG-03-2009 09:50:46: ..... creating ACCOUNT_DEPTHVAR object to support value hierarchies
AUG-03-2009 09:50:46: ..... populating depth information in variable ACCOUNT_DEPTHVAR
AUG-03-2009 09:51:08: ..... populating mapping info for the HIERARCHY and FAMILYREL clauses for hierarchy GRA
AUG-03-2009 09:51:08: ..... populating mapping info for the HIERARCHY and FAMILYREL clauses for hierarchy MODEL
AUG-03-2009 09:51:08: ..... populating mapping info for the ATTRIBUTE clause
AUG-03-2009 09:51:09: ... completed populating mapping for ACCOUNT
AUG-03-2009 09:51:58: . Creating view for dimension ACCOUNT
AUG-03-2009 09:51:59: ... generating limitmap for ACCOUNT
AUG-03-2009 09:51:59: ..... mapping table out of date for dimension ACCOUNT. Updating mapping table.
AUG-03-2009 09:51:59: ... populating dimension map for ACCOUNT
AUG-03-2009 09:51:59: ..... clearing mappings for the dimension
AUG-03-2009 09:51:59: ..... retrieving physical objects
AUG-03-2009 09:51:59: ..... checking for value hierarchies
AUG-03-2009 09:51:59: ..... retrieving label for dimension levels
AUG-03-2009 09:51:59: ..... populating mapping info for the DIMENSION clause
AUG-03-2009 09:51:59: ..... populating mapping info for the INHIERARCHY clause
AUG-03-2009 09:51:59: ..... retrieving hierarchy information
AUG-03-2009 09:52:00: ..... populating mapping info for the HIERARCHY and FAMILYREL clauses for hierarchy COMPLETEPL
AUG-03-2009 09:52:00: ..... populating mapping info for the HIERARCHY and FAMILYREL clauses for hierarchy GRA
AUG-03-2009 09:52:00: ..... populating mapping info for the HIERARCHY and FAMILYREL clauses for hierarchy MODEL
AUG-03-2009 09:52:00: ..... populating mapping info for the ATTRIBUTE clause
AUG-03-2009 09:52:01: ... completed populating mapping for ACCOUNT
AUG-03-2009 09:52:02: **
AUG-03-2009 09:52:02: ** ERROR: View not created.
AUG-03-2009 09:52:02: ** CAUSE: CREATE VIEW statement failed
AUG-03-2009 09:52:02: ORA-22309: attribute with name "ACCOUNT_COMPLETEPL_LEVEL" already exists
AUG-03-2009 09:52:02: *** DEBUG INFORMATION ***
AUG-03-2009 09:52:02: VIEW CREATION DDL ((truncated after 3900 characters)
AUG-03-2009 09:52:02: CREATE OR REPLACE VIEW XPRO_OLAP_AGG.ACCOUNT_DIMVIEW AS
SELECT *
FROM table(OLAP_TABLE ('XPRO_OLAP_AGG.OLAP_AGG duration session',
'&(ACCOUNT_LIMITMAP)'))
MODEL
DIMENSION BY (
ACCOUNT)
MEASURES (
ACCOUNT_LEVEL,
ACCOUNT_PRECOMPUTE,
ACCOUNT_RELATED_STATISTICAL,
ACCOUNT_BENEFIT_UPLIFT,
ACCOUNT_STATISTICAL,
ACCOUNT_CLOSED_FLAG,
ACCOUNT_CLOSED_DATE,
ACCOUNT_PARENT_CD,
ACCOUNT_SDSC,
ACCOUNT_LDSC,
ACCOUNT_CD,
ACCOUNT_MODEL1_LVLDSC,
ACCOUNT_MODEL_LEVEL,
ACCOUNT_MODEL_PRNT,
ACCOUNT_GRA4_LVLDSC,
ACCOUNT_GRA3_LVLDSC,
ACCOUNT_GRA2_LVLDSC,
ACCOUNT_GRA1_LVLDSC,
ACCOUNT_GRA_LEVEL,
ACCOUNT_GRA_PRNT,
ACCOUNT_COMPLETE7_LVLDSC,
ACCOUNT_COMPLETE6_LVLDSC,
ACCOUNT_COMPLETE5_LVLDSC,
ACCOUNT_COMPLETE4_LVLDSC,
ACCOUNT_COMPLETE3_LVLDSC,
ACCOUNT_COMPLETE2_LVLDSC,
ACCOUNT_COMPLETE1_LVLDSC,
ACCOUNT_COMPLETEPL_LEVEL,
ACCOUNT_COMPLETEPL_PRNT
) RULES UPDATE SEQUENTIAL ORDER()
AUG-03-2009 09:52:02: LIMITMAP (truncated after 3900 characters):
AUG-03-2009 09:52:02: DIMENSION ACCOUNT FROM ACCOUNT WITH -
HIERARCHY ACCOUNT_COMPLETEPL_PRNT FROM ACCOUNT_PARENTREL(ACCOUNT_HIERLIST \'COMPLETEPL\') -
INHIERARCHY ACCOUNT_INHIER -
HATTRIBUTE ACCOUNT_COMPLETEPL_LEVEL FROM ACCOUNT_DEPTHVAR -
HATTRIBUTE ACCOUNT_GRA_LEVEL FROM ACCOUNT_DEPTHVAR -
HATTRIBUTE ACCOUNT_MODEL_LEVEL FROM ACCOUNT_DEPTHVAR -
FAMILYREL ACCOUNT_COMPLETE1_LVLDSC, -
ACCOUNT_COMPLETE2_LVLDSC, -
ACCOUNT_COMPLETE3_LVLDSC, -
ACCOUNT_COMPLETE4_LVLDSC, -
ACCOUNT_COMPLETE5_LVLDSC, -
ACCOUNT_COMPLETE6_LVLDSC, -
ACCOUNT_COMPLETE7_LVLDSC -
FROM ACCOUNT_FAMILYRELVAL(GID_DIMENSION 63), -
ACCOUNT_FAMILYRELVAL(GID_DIMENSION 31), -
ACCOUNT_FAMILYRELVAL(GID_DIMENSION 15), -
ACCOUNT_FAMILYRELVAL(GID_DIMENSION 7), -
ACCOUNT_FAMILYRELVAL(GID_DIMENSION 3), -
ACCOUNT_FAMILYRELVAL(GID_DIMENSION 1), -
ACCOUNT_FAMILYRELVAL(GID_DIMENSION 0) -
LABEL ACCOUNT_DSCR-
HIERARCHY ACCOUNT_GRA_PRNT FROM ACCOUNT_PARENTREL(ACCOUNT_HIERLIST \'GRA\') -
INHIERARCHY ACCOUNT_INHIER -
HATTRIBUTE ACCOUNT_COMPLETEPL_LEVEL FROM ACCOUNT_DEPTHVAR -
HATTRIBUTE ACCOUNT_GRA_LEVEL FROM ACCOUNT_DEPTHVAR -
HATTRIBUTE ACCOUNT_MODEL_LEVEL FROM ACCOUNT_DEPTHVAR -
FAMILYREL ACCOUNT_GRA1_LVLDSC, -
ACCOUNT_GRA2_LVLDSC, -
ACCOUNT_GRA3_LVLDSC, -
ACCOUNT_GRA4_LVLDSC -
FROM ACCOUNT_FAMILYRELVAL(GID_DIMENSION 7), -
ACCOUNT_FAMILYRELVAL(GID_DIMENSION 3), -
ACCOUNT_FAMILYRELVAL(GID_DIMENSION 1), -
ACCOUNT_FAMILYRELVAL(GID_DIMENSION 0) -
LABEL ACCOUNT_DSCR-
HIERARCHY ACCOUNT_MODEL_PRNT FROM ACCOUNT_PARENTREL(ACCOUNT_HIERLIST \'MODEL\') -
INHIERARCHY ACCOUNT_INHIER -
HATTRIBUTE ACCOUNT_COMPLETEPL_LEVEL FROM ACCOUNT_DEPTHVAR -
HATTRIBUTE ACCOUNT_GRA_LEVEL FROM ACCOUNT_DEPTHVAR -
HATTRIBUTE ACCOUNT_MODEL_LEVEL FROM ACCOUNT_DEPTHVAR -
FAMILYREL ACCOUNT_MODEL1_LVLDSC -
FROM ACCOUNT_FAMILYRELVAL(GID_DIMENSION 0) -
LABEL ACCOUNT_DSCR -
ATTRIBUTE ACCOUNT_CD FROM ACCOUNT_CD -
ATTRIBUTE ACCOUNT_LDSC FROM ACCOUNT_DSCR -
ATTRIBUTE ACCOUNT_SDSC FROM ACCOUNT_SDSCR -
ATTRIBUTE ACCOUNT_PARENT_CD FROM ACCOUNT_PARENT_CD -
ATTRIBUTE ACCOUNT_CLOSED_DATE FROM ACCOUNT_CLOSED_DATE -
ATTRIBUTE ACCOUNT_CLOSED_FLAG FROM ACCOUNT_CLOSED_FLAG -
ATTRIBUTE ACCOUNT_STATISTICAL FROM ACCOUNT_STATISTICAL -
ATTRIBUTE ACCOUNT_BENEFIT_UPLIFT FROM ACCOUNT_BENEFIT_UPLIFT -
ATTRIBUTE ACCOUNT_RELATED_STATISTICAL FROM ACCOUNT_RELATED_STATISTICAL_ACCOUNT -
ATTRIBUTE ACCOUNT_PRECOMPUTE FROM ACCOUNT_PRECOMPUTE -
ATTRIBUTE ACCOUNT_LEVEL FROM ACCOUNT_LEVELREL
AUG-03-2009 09:52:02: **
AUG-03-2009 09:52:02: ** ERROR: Unable to create view over dimension ACCOUNT.
AUG-03-2009 09:52:02: ORA-22309: attribute with name "ACCOUNT_COMPLETEPL_LEVEL" already exists
Am I missing something? Can I generate the views for the value based dimensions?
Thanks
Brijesh

Hi Brijesh
I had a similar problem when creating cube views for OBIEE under OLAP with multiple value-based hierarchies using the plugin.
The view generator makes several HATTRIBUTES for the _LEVEL metadata that is mapped in the OLAP AW, some of which are not part of the hierarchy that is being created, this is why it detects repeating fields.
What you need to do is create the view as you normally would. When you receive the error below, copy the SQL out of the error windows and save it somewhere.
CREATE OR REPLACE VIEW XPRO_OLAP_AGG.ACCOUNT_DIMVIEW AS
SELECT *
FROM table(OLAP_TABLE ('XPRO_OLAP_AGG.OLAP_AGG duration session',
'&(ACCOUNT_LIMITMAP)'))
MODEL
DIMENSION BY (
ACCOUNT)
MEASURES (
ACCOUNT_LEVEL,
ACCOUNT_PRECOMPUTE,
ACCOUNT_RELATED_STATISTICAL,
ACCOUNT_BENEFIT_UPLIFT,
ACCOUNT_STATISTICAL,
ACCOUNT_CLOSED_FLAG,
ACCOUNT_CLOSED_DATE,
ACCOUNT_PARENT_CD,
ACCOUNT_SDSC,
ACCOUNT_LDSC,
ACCOUNT_CD,
ACCOUNT_MODEL1_LVLDSC,
ACCOUNT_MODEL_LEVEL,
ACCOUNT_MODEL_PRNT,
ACCOUNT_GRA4_LVLDSC,
ACCOUNT_GRA3_LVLDSC,
ACCOUNT_GRA2_LVLDSC,
ACCOUNT_GRA1_LVLDSC,
ACCOUNT_GRA_LEVEL,
ACCOUNT_GRA_PRNT,
ACCOUNT_COMPLETE7_LVLDSC,
ACCOUNT_COMPLETE6_LVLDSC,
ACCOUNT_COMPLETE5_LVLDSC,
ACCOUNT_COMPLETE4_LVLDSC,
ACCOUNT_COMPLETE3_LVLDSC,
ACCOUNT_COMPLETE2_LVLDSC,
ACCOUNT_COMPLETE1_LVLDSC,
ACCOUNT_COMPLETEPL_LEVEL,
ACCOUNT_COMPLETEPL_PRNT
) RULES UPDATE SEQUENTIAL ORDER();Go into AWM and OLAP Worksheet and you will need to find the LIMITMAP variable, in your case ACCOUNTLIMITMAP.
Execute:
show convert(ACCOUNT_LIMITMAP infile)
This will print the contents of the variable in infile format as you will be loading it back later.
Copy this into an editor and what you will find is that under each dimension hierarchy (defined as HIERARCHY ACCOUNT_<hierarchy>_PRNT ...) there will be repeating HATTRIBUTE declarations.
You need to go through and delete the HATTRIBUTES that do no belong to the HIERARCHY pointed out above, which appears as:
HATTRIBUTE ACCOUNT_<hierarchy>_LEVEL
--HATTRIBUTE ACCOUNT_<hierarchy1>_LEVEL--
--HATTRIBUTE ACCOUNT_<hierarchy2>_LEVEL--
In your case i believe you will have these repeating:
ACCOUNT_MODEL_LEVEL
ACCOUNT_GRA_LEVEL
ACCOUNT_COMPLETEPL_LEVELDo this for each hierarchy in the limitmap leaving only the correct hierarchy HATTRIBUTE under each HIERARCHY ACCOUNT_<hierarchy>_PRNT
After that at the top of your notepad add ACCOUNT_LIMITMAP = 'DIMENSION ACCOUNT FROM ACCOUNT WITH ... etc
Load the file into AWM using the infile command, this will set the ACCOUNT_LIMITMAP correctly.
You will then need to execute the SQL from the error windows in SQL Developer and you should be able to see the view.
Edited by: birchy on Aug 4, 2009 9:35 AM

Hierarchies About

Hi,
Can some one let me know
1. When should we use hierarchies, pls. explain with a scenario ?
2. What is the concept behind hierarchies ?
3. How to create a hierarchy - step by step ?
4. Are there any varieties in hierarchy ?
5. what are the components of hierarchy ?
KINDLY NOTE: Pls. dont give me any links to any forums or any std. docs.
Answers will be appreciated by suitable points.
Thanks,
bwlearner

Hi,
Hierarchies in general are essential structures for
navigation. Having characteristics and attributes in the
dimension and master data tables that are related in a
sequence of parent-child relationships, obviously
involves hierarchies. But as the real world is sometimes
irregular, so are hierarchies. In BW there are essentially three possibilities for modeling hierarchies:
 as a hierarchy of characteristics within a dimension table
 as a hierarchy of attributes attached to a characteristic
 as an external hierarchy
Hierarchies within a Dimension
A typical example of a hierarchy of this type is a time
hierarchy with levels such as millenium century
decade year month day hour etc. Another typical
example is a geographic hierarchy with levels such as
continent country state region city etc.
Hierarchies within a master data table of a characteristic
This case is very similar to the one discussed in section
before. The difference is the increased flexibility (i.e.
realignment facilities) that comes with navigational
attributes. The hierarchy should still have a fixed
number of levels. However, changes to that hierarchy
(i.e. changes to attribute values) can be easily applied
to facts that are already loaded into a cube.
A typical example is the hierarchy of sales office
sales group sales person. This hierarchy has a fixed
number of levels but is frequently reorganized.
In terms of performance, this is the least attractive of the hierarchy modeling techniques.
External Hierarchies
This is the ideal type if a hierarchy
 frequently changes
 has no fixed number of levels (sometimes referred to as a "ragged" or unbalanced hierarchy).
A typical example is a cost center hierarchy in which
several (sub-) cost centers belong to one cost center
which itself belong to another cost center and so on.
Such a hierarchy has no fixed number of levels as cost
centers usually correspond to departments or groups
within a company, which might be reorganized into new
subgroups. Thus new levels might be introduced, old ones
disappear. The hierarchy might be deeper at one end (due
to a deeper hierarchical organization) and shallower at
the other.
Another major advantage of external hierarchies in
comparison to their alternatives is that an InfoObject
can have several such hierarchies and all these can be
used within the same cube. With the alternative
approaches the same effect could only be achieved through
difficult work-arounds.
3. Creating a hierarchy
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a6736e07211d2acb80000e829fbfe/content.htm

How to download a hierarchy to a flat file
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/0403a990-0201-0010-38b3-e1fc442848cb
4.Varieties in hierarchy
 Time dependent Hierarchies
 Time independent Hierarchies
 Version dependent Hierarchies
hope this helps
sham'm

FAQ: Why isn't the anchor point centered in shape layers?

[UPDATE: In After Effects CC (12.1) and later, you can center the anchor point within the visible content of a layer. ]
Short answer
Because in shape layers you can have two distinct kinds of anchor points - the anchor point in the main transform properties, as in any other layer type, and also an anchor point in the specific transform properties for each shape. When you create shapes by dragging with the shape tools, it's the anchor point for the shape group that will be centered. If you want to animate the whole layer from the main transform properties, you may need to shift the anchor point so it matches the visual center of your content.
Long answer
Shape layers are a unique type of content in After Effects.
In fact, they introduce a bit of the object/group hierarchy model in Adobe Illustrator, rather than follow the typical layer model in After Effects.
In other words, while you can definitely use them to quickly create a vector shape and then animate that shape as any other layer in After Effects, you also get the ability to create, edit and animate multiple shapes (each with its' own set of visual appearances) nested in a single shape layer.
This allows all kinds of cool animation opportunities, but it also means that a shape layer is not your typical After Effects layer.
So, when you create a shape by dragging with the shape tool, there actually is an anchor point that is perfectly centered - that's the anchor point in the transform property group for that shape group. If you double click a shape, you'll see a bounding box. This a visual representation of the transform properties for the shape group, and the anchor point specific to this group will default to the middle of that bounding box.
However, the main anchor point for the whole shape layer may not be centered relative to the shape content. This is normal behavior - Note that if After Effects tried to center the layer anchor point relative to the first shape group you create, it would be immediately wrong when you add more shape groups to the layer. Or when you animate shape groups around.
Now, as many other things in After Effects, shape layers are designed to let you go as deep as you want. Ideally, you may want to try animating the transform properties for each shape group, since there's when things get really powerful. However, if you want to consider shape layers as a one shape per layer entity and animate in that way, you can of course do that. Bear in mind that you may need to center the anchor point yourself relative to the visual center of the content. If you don't do this, the shape layer's content will be offset from motion paths, or behave in a different way from what you may expect when animating scale or rotation.
To do this, make sure you're not selecting a nested shape group but the shape layer itself, then you can do the following:
Use the Pan Behind tool as with any other layer (this may not give what you want if you do it after creating a motion path, since it will modify position values).
Drag the hot text for the Anchor Point property in the Timeline panel, as if it was a slider. You can then re-thread the content relative to the motion path. You can also achieve this by Option- (Mac OS) or Alt- (Windows) dragging with the Pan Behind tool.
For more information on shape layers, see Drawing, painting and paths in After Effects Help.

THANK YOU SO MUCH :-)
I didn't knew this shortcut as I didn't have to use it anyway.
but it's weird because all the other tools like even the circular gradient tool have their point visible.
Anyway, I guess you can press H with any tools.
Again, thank you, I should have ask it before. ;-)

EPMA shared library relational representation

I want to use EPMA shared libraries to manually maintain certain dimensions for Planning, but also access that metadata to update other external environments requiring the same hierarchy information. I am running on SQL Server 2005. Hierarchies are managed nowhere else in the company and DRM is not a desired option.
I see HYP_HPLAN tables that contain numeric IDs for dimension members and a HYP_UNIQUE_NAMES table that appears to contain the mappings. Am I on the right track looking at these? How would you recommend going about extracting EPMA shared library hierarchy information into a meaningful table or tables for use elsewhere?
Thanks for your ideas!

It is not more useful to create metadata first in relational if you want to leverage the user interface of EPMA libraries for the maintenance of manual dimensions. Given the business need for some manually maintained dimensions, I think it is much friendlier to have a key user add members, etc. in a hierarchial interface rather than populate a table (likely based on submission of a manually maintained spreadsheet). In my way of thinking, coming from "old school" Essbase, there is intuitive benefit in having hierarchy modeling tools (App Mgr, EAS). So my question still stands and is based on the desire do use EPMA as that tool in a Planning context.

Create BMM for my data structure

Hi
I am newbie on OBIEE.after two weeks work on OBIEE I could create my repository from our data sources.but in our needs,I have to answer to some question that I could not create BMM correctly from our sources.because I need to hierarchy and some conversion on my database.
I describe our database and our need :
I have 3 table with primary key
Table A: (ItemID, NameItem, description,SerialNumber,PriceItem) ItemID is primary key
Table B: (ProductID,NameProduct,TimeCreated,ListItemsID,ProductType) ProductID is primary key
Table C: (ListItemsID,ItemID) ListItemID is primary key
Our Questions:
1- number of produced product based on year,quarter,month,week,day in hierarchy model
2- number of all items in one special product
3- total price of one product
4- total price of all product
5- total price of one month production,year production
6- list of all items of one product
7- group by product type
8- total price of one type
Unfortunately I could not create correct BMM layer and presentation layer in order to create analysis.
Thanks for any help or guidance

If you have entity based VOs which you are using to insert/update data, the most suitable place in terms of integrity of business objects is in the doDML() of the entityImpl
protected void doDML(int operation, TransactionEvent e) {
super.doDML(operation, e);
switch(operation){
case EntityImpl.DML_INSERT:{
// logic to insert the new log data
break;
case EntityImpl.DML_UPDATE:{
if(this.getEntityState()==EntityImpl.STATUS_MODIFIED)
//logic to find and update row in the log table
break;
default: break;
If you want to keep your logs in a different table, i would suggest to keep the "Primary_Key" column along with the "Table_Name" so that you can find the appropriate log rows for update operations.

Cascading delete - rowcount

It would be nice if there was a a variant of SQL%ROWCOUNT that included the effects of cascading deletes. If I have a multi-level hierarchy modeled with a bunch of 'ON DELETE CASCADE' constraints, it would be good to report back the actual total number of records deleted, including cascading deletes. Right now, I'd have to recursively count up everything manually in order to put up a message like 'This operation will delete a total of N records. Are you sure you want to continue?'

Hi,
OK - if there is something on the master record that determines whether or not any user can delete data, then I would do a conditional Delete button (and probably the Delete process) based on that something. For example, suppose there is a flag on the master record that holds its current status - say D for Draft and C for Complete - and users can delete data only if the flag is D. Then, I would make the Delete button conditional on STATUS='D' (probably using a SQL Exists statement or, if the STATUS field is on the page somewhere, using Value of Item in Expression 1 = Expression 2 and have P1_STATUS in Expression 1 and D in Expression 2). Then, the user will never get the option to delete the record(s) unless the master record was in Draft status.
Andy

R/3 Product Hierarchy in BW data model.

Hi all,
We have been told by our implementation partner that the scenario described below is not feasible to design in our BW 3.5 system and if we were to implement this scenario there would be a significant amount of user maintenance to maintain the hierarchy structure in BW.
I was a query user in previous BW versions and my datawarehouse modeling experience is mostly in Cognos and Business Objects. The scenario described below is very easily implemented in these other datawarehouse software packages and I would be suprised if SAP does not have a standard solution to address the problem.
I would like to understand if:
(1) Yes this solution can be easily implemented in BW 3.5
(2) A brief explanation on the design approach, implementation, and considerations
I am already familiar with the link on http://sap.help.com that explains BW hierarchy design and considerations, but I would like to get a "real world" understanding of an approach and design and if you experienced this requirement.
Thank You in advance for your input.
Regards,
-Anthony
Scenario:
In R/3 we have modified the standard delivered product hierarchy structure for material master from 5,5,8 to be 5,5,4,4.
The 4 levels represent: BRAND --> PRODUCT LINE --> PRODUCT CATEGORY --> PRODUCT SUBCATEGORY
Our intent is to use this structure to satisfy current BW reporting requirements for COPA and R/3 Billing infocubes.
In BEx Explorer we would like to perform product analysis using the following dimension paths:
BRAND --> PRODUCT LINE --> PRODUCT CATEGORY --> PRODUCT SUBCATEGORY
PRODUCT LINE --> PRODUCT CATEGORY --> PRODUCT SUBCATEGORY
PRODUCT CATEGORY --> PRODUCT SUBCATEGORY
We are told that since we have multiple values at the BRAND node we will not be able to perform grouped reporting the starts at PRODUCT LINE node(which would be independent of the BRAND node). For example:
BRAND, PRODUCT LINE, PRODUCT CATEGORY
HONDA, AUTOMOBILE, CIVIC
HONDA, AUTOMOBILE, ACCURA
HONDA, BLOWER, CIVIC
HONDA, MOTORCYCLE, ODESSY
FORD, AUTOMOBILE, EXPLORER
FORD, BLOWER, EXPLORER
FORD, MOTORCYCLE, CHAMPION
So for example we would like to start our dimensional anaylsis to show all AUTOMOBILE or BLOWER sales independent of the fact they were for HONDA or FORD.
In other datawarehouse systems I have either: (1) created 3 dimensions called: BRAND, PRODUCT LINE, and PRODUCT CATEGORY or (2) created one dimension called BRAND with alternate dimension paths for PRODUCT LINE and PRODUCT CATEGORY. I am not sure if this is feasible in BW.
We were also told in order to achieve this design a structure would have to be maintained in BW every time we introduce a new material master and the material master would need to be manually entered into the structure so that reporting can be achieved for both the standard structure and the alternate structure(s).

Antony ,
there will be maintenance involved every time you add a material to the material master. However you could maintain the hierarchy through a GUI also depending on the number of values.
Ideally if this can be maintained in a table in the source system , it can be imported into BW. Otherwise if you were to maintain it in BW , you will have a lot of problems when :
1. Change in the hierarchy - A new Product Line coming in and many product category onwards change over to the new product line.
2. Viewing the changed hierarchy over time - If you have GM and a separate category called Daewoo , earlier they were separate and now they are one - what are my product sales due to the merged entity vis-a-vis separate entities earlier...
Things that you will need to consider from a design stand popint are :
1. Should the hierarchy be time dependent ?
2. Should it be maintained in the source system or in BW?
3. Change process for the same - Flat file / Manual
4. Estimate of how frequent the hierarchy would change?
5. Will you have display hierarchies - Ad-Hoc hierarchies to view certain combinations?
Depending on the above your hierarchy creation can go from easy to complex and hard to maintain.
One way to amintain it is to have a SAP ABAP program to populate a hierarchy table to have the relations in R/3 and transfer them into BW. You could automate it in such a way that the hierarchy is changed every time there is a new material
Otherwise , there can be a flat file to create the relationships
Or someone could log a request and if the change is minimal it couldbe done thru a GUI Interface provided by BW.
Arun
Assiging points is a way of saying thank you in SDN

How to model multiple parent hierarchy in obiee

hi,
I have product hierarchy with multiple parents for a single level. and i want to display all the levels of hierarchy at a same time.
Below mentioned is wht data i am getting from product table in OLTP
current product diamension
root1--level 1
child product1--level 2
child product2--level 3
child product3 ----level 4
and
root2----level 1
child product4----level 2
child product2----level 3
child product3 ----level 4
If u see we have child product2 belongs to two diff hierarchies.
My report req is i want to show all the levels of product in single row.Some thing like
Mb no. level 1 level 2 level 3 level 4
123 root1 CP1 Cp2 CP3
123 root2 CP4 CP2 CP3
How to model this scanario in OBIEE?

H,
Refer this
http://oraclebizint.wordpress.com/2007/11/30/oracle-bi-ee-101332-one-dimension-multiple-hierarchies/
http://www.rittmanmead.com/2010/11/oracle-bi-ee-11g-parent-child-hierarchies-multiple-modeling-methods/
Thanks
Deva

Hierarchy Modelling

Similar Messages

Maybe you are looking for