Cl_salv_hierseq_table= factory 3 Level Hierarchy

Hi Gurus,
I need to construct a Hierarchy with 3 Levels. If you could provide me example code. Or if it can be constructed by tree., kIndly let me know know. Hoe to create 3 Levels.

Hi Raj,
SAP provides two hierarchy levels only.
If you need more, you have to provide own programming, i.e. open pop-up with grid for next dimension.
Regards,
Clemens

Similar Messages

Issue with Skip Level Hierarchy in OBIEE 11g

Hi,
I have implemented Ragged and Skip Level Hierarchy as explained in the links below in OBIEE 11g RPD.
(checked the 'Ragged' and 'Skipped Levels' check boxes)
http://www.rittmanmead.com/2010/07/obiee-11gr1-support-for-ragged-skip-level-value-based-hierarchies/
http://docs.oracle.com/cd/E17904_01/bi.1111/e10540/dimensions.htm#BABFBBFG
When the Presentation Hierarchy is dragged in the OBI Answers, the leaf level beyond the skip (null) levels is not shown in the report.
When any level finds intermediate null values, OBIEE is failing to show the existing value of the leaf level (Most Granular Level) or any values after Skipped Levels.
For example, following is the values in database for different levels of department hierarchy.
A -> B -> C -> Null -> Null -> F
The OBIEE Presentation Hierarchy can only drill down till C, not beyond that. (does not show the leaf level value 'F').
Could you please suggest whether I am missing any step?
Thanks.

Hi, My problem is that in my report it is showing me that levels as -- A -> B -> C -> Null -> Null -> F, however I want to show data as A -> B -> C -> F, i.e the null valus(columns) should be skipped. Please help.
Thanks and Regards,
Deepak

FCC for Multi-level Hierarchy

Hi Friends,
Can someone please help me out with this.Below is my Sender Data Type which needs to be converted:
DT_TRAC_MESG
(Hierarchy 1)         TRAC_INFO
                  (Hierarchy 2)   TRAC00
                     (Hierarchy 2)GROUP1
                                (Hierarchy 3)TRAC05
                                (Hierarchy 3)GROUP2
                                             (Hierarchy 4)TRAC10
(Hierarchy 4)                                             GROUP3
                 (Hierarchy 5)                                         TRAC11
and my input data is as below :
XXXXXXXXX TRAC00 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX (occurance 1)
XXXXXXXXXXXXXXXXXXTRAC05XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX (occurance 1)
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXTRAC10XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXTRAC11XXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXTRAC11XXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXTRAC11XXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXTRAC10XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXTRAC11XXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXTRAC11XXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXTRAC10XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXTRAC11XXXXXXXXXXXXXXXXXXXXXXX
I know Std SAP XI doesnt support more than 3 hierarchies but we are using a JMS adapter and this support more than 3 hierarchies.So please help us in achieving this mutli hierarchy conversion.Please atleast provide me the procedure to convert a 3 level Hierarchy structure.
It would be of great help for me if someone can answer this and asap.
Thanks & Regards,
Pradeep.

Hi
follow this weblog
File Content Conversion for Multi Hierarchical Structure
or
you can use seeburger to use multi level hierarchy
SAP PI/XI : Content conversion using Generator mapping functionality of SeeBurger : Part 1.
SAP PI/XI : Content Conversion using Generator mapping functionality of SeeBurger : Part 2.
regards
sandeep
Edited by: sandeep sharma on Dec 15, 2008 10:45 AM

OBIEE 10g - Ragged & Skip Level Hierarchy

Hi Frnds,
I'm aware of the fact that OBIEE 11g supports Ragged & Skip Level Hierarchy. But I'm looking for some heads up while implementing the same on OBIEE 10g using Oracle DB as source. I have done this before for Essbase Data Source but now waiting for my Oracle dataset for design.
Has anyone actually implemented in Real Time Project? Pls share your challenges like:
- Dimensional Hierarchies Challenges
- Drill Down Challenges
- Report Challenges
Thanks,
Deepak
Edited by: Deepak Gupta on Aug 11, 2011 5:18 AM

Deepak,
10g does not handle the idea of Skip hierarchies and the ragged hierarchies definitely has its limitations.
We've implemented several projects using Essbase and SAP BW for Oracle BI 10g. The biggest issue is that in Answers creates a new column for each drill down selection when attempting to navigate down a hierarchy. Though this is klugy it does work and provides the data the user is looking for. It is however, not aesthetically please when compared to other tools or now Oracle BI 11g which satisfies this issue with a native drill-down tree folder structure.
My opinion and advice would be to upgrade to 11g as soon as possible to enjoy these new features.

Ragged Hierarchy and Skip Level Hierarchy

Hi all,
I am confused with ragged and skip level hierarchy, as i read some documents related to obiee 11g.
Will you please explain with an example the difference between ragged hierarchy and skip level hierarchy and also when to use these hierarchies?
regards
chandra kanth.

Chandra Kanth,
Hope this helps you
http://blogs.simba.com/.a/6a00e3932f172e88340133f4d758b5970b-800wi
Thanks,
Saichand.v

OBIEE Essbase skip-level hierarchy

Is it possible to setup OBIEE and Essbase to be able to model skip-level hierarchy? It is obvious with connection to the relational database. How the essbase should designed and populated with data to faciliate this type of hierarchy?

Refer this http://www.oracle.com/technetwork/middleware/bi-enterprise-edition/overview/obiee-essbase-modeling-guide-130897.pdf for Modeling. And for any Essbase releated question post it in Essbase forum Essbase

Failed validation as a level hierarchy

Hi,
I have dimension called SKU in my analytic workspace with a hierarchy PRODUCTS defined as ALLPRODUCTS<--MD<--MG<--PG<--STYLE<--PRODUCT. I have used composite keys as Members to maintain uniqueness. For example the member expression for PG is CUBE_DEV.DIMSKU.MDID || CUBE_DEV.DIMSKU.MGID || CUBE_DEV.DIMSKU.PGID. I'm not using Surrogate keys. When I hit the maintain Dimension SKU, LOAD NO SYNCH succeeds but the compile step fails with error
"INI: error creating a definition manager, Generic at TxsOqConnection::generic<BuildProcess>INI: XOQ-01712: "SKU.PRODUCTS" failed validation as a level hierarchy., Generic at TxsOqStdFormCommand::execute"
I looked at the rejected records and every record has the error "(XSRWLD13) Cannot change the level of a dimension member within a single load." Can anyone help me resolving this issue ?
I'm using AWM 11.2.0.1.0 on Oracle 11g R2 server.
Thanks,
RK

David,
I looked at the data and found out that there were NULLs in many key columns. I updated all of them to the value 'Unknown'. Also I re-implemented Composite keys because I thought Type 2 dimension would pose problem in determining uniqueness. Now there are no errors and I could successfully load data into the dimension.
Below is the latest definition
<!DOCTYPE Metadata [
<!ENTITY % BIND_VALUES PUBLIC "OLAP BIND VALUES" "OLAP METADATA">
%BIND_VALUES;
]>
<Metadata
Version="1.2"
MinimumDatabaseVersion="11.2">
<StandardDimension
Name="SKU"
ETViewName="SKU_VIEW"
ETKeyColumnName="DIM_KEY"
ETLevelColumnName="LEVEL_NAME"
ETMemberTypeColumnName="MEMBER_TYPE"
ETDimensionOrderColumnName="DIM_ORDER"
DefaultHierarchy="PRODUCTS"
ETHierarchyOrderColumnName="HIER_ORDER"
ShortValueDescriptionAttribute="SHORT_DESCRIPTION">
<Organization>
<AWPrimaryDimensionOrganization
AW="&AW_NAME;"
AddUniqueKeyPrefix="True"
MVOption="NONE"
HierarchyConsistencyRule="CONSISTENT">
<MVCreationOptions
RefreshType="COMPLETE"
RefreshOn="DEMAND"
UsingConstraintsClause="TRUSTED">
</MVCreationOptions>
<DefaultBuild>
<![CDATA[BUILD SPEC SYS_DEFAULT
LOAD,
COMPILE
)]]>
</DefaultBuild>
<AttributeOrganization
Attribute="SHORT_DESCRIPTION">
</AttributeOrganization>
</AWPrimaryDimensionOrganization>
</Organization>
<DimensionLevel
Name="MERCHDIVISION"
ETKeyColumnName="MERCHDIVISION">
<Description
Type="LongDescription"
Language="AMERICAN"
Value="MERCHDIVISION">
</Description>
<Description
Type="ShortDescription"
Language="AMERICAN"
Value="MERCHDIVISION">
</Description>
<Description
Type="Description"
Language="AMERICAN"
Value="MERCHDIVISION">
</Description>
</DimensionLevel>
<DimensionLevel
Name="MERCHGROUP"
ETKeyColumnName="MERCHGROUP">
<Description
Type="LongDescription"
Language="AMERICAN"
Value="MERCHGROUP">
</Description>
<Description
Type="ShortDescription"
Language="AMERICAN"
Value="MERCHGROUP">
</Description>
<Description
Type="Description"
Language="AMERICAN"
Value="MERCHGROUP">
</Description>
</DimensionLevel>
<DimensionLevel
Name="PRODUCTGROUP"
ETKeyColumnName="PRODUCTGROUP">
<Description
Type="LongDescription"
Language="AMERICAN"
Value="PRODUCTGROUP">
</Description>
<Description
Type="ShortDescription"
Language="AMERICAN"
Value="PRODUCTGROUP">
</Description>
<Description
Type="Description"
Language="AMERICAN"
Value="PRODUCTGROUP">
</Description>
</DimensionLevel>
<DimensionLevel
Name="STYLE"
ETKeyColumnName="STYLE">
<Description
Type="LongDescription"
Language="AMERICAN"
Value="STYLE">
</Description>
<Description
Type="ShortDescription"
Language="AMERICAN"
Value="STYLE">
</Description>
<Description
Type="Description"
Language="AMERICAN"
Value="STYLE">
</Description>
</DimensionLevel>
<DimensionLevel
Name="PRODUCT"
ETKeyColumnName="PRODUCT">
<Description
Type="LongDescription"
Language="AMERICAN"
Value="PRODUCT">
</Description>
<Description
Type="ShortDescription"
Language="AMERICAN"
Value="PRODUCT">
</Description>
<Description
Type="Description"
Language="AMERICAN"
Value="PRODUCT">
</Description>
</DimensionLevel>
<Description
Type="LongDescription"
Language="AMERICAN"
Value="sku">
</Description>
<Description
Type="ShortDescription"
Language="AMERICAN"
Value="sku">
</Description>
<Description
Type="Description"
Language="AMERICAN"
Value="sku">
</Description>
<Hierarchy>
<LevelHierarchy
Name="PRODUCTS"
IsSkipLevel="True"
IsRagged="True"
ETParentColumnName="PARENT"
ETDepthColumnName="DEPTH"
ETViewName="SKU_PRODUCTS_VIEW">
<HierarchyLevel
DimensionLevel="MERCHDIVISION">
<HierarchyLevelMap
KeyExpression="DIMSKU.MDID"
Query="DIMSKU">
<AttributeMap
Name="SHORT_DESCRIPTION"
Attribute="SHORT_DESCRIPTION"
Expression="DIMSKU.MDID">
</AttributeMap>
</HierarchyLevelMap>
</HierarchyLevel>
<HierarchyLevel
DimensionLevel="MERCHGROUP">
<HierarchyLevelMap
KeyExpression="DIMSKU.MDID || DIMSKU.MGID"
Query="DIMSKU">
<AttributeMap
Name="SHORT_DESCRIPTION"
Attribute="SHORT_DESCRIPTION"
Expression="DIMSKU.MDID || ':' || DIMSKU.MGID">
</AttributeMap>
</HierarchyLevelMap>
</HierarchyLevel>
<HierarchyLevel
DimensionLevel="PRODUCTGROUP">
<HierarchyLevelMap
KeyExpression="DIMSKU.MDID || DIMSKU.MGID || DIMSKU.PGID"
Query="DIMSKU">
<AttributeMap
Name="SHORT_DESCRIPTION"
Attribute="SHORT_DESCRIPTION"
Expression="DIMSKU.MDID || ':' || DIMSKU.MGID || ':' || DIMSKU.PGID">
</AttributeMap>
</HierarchyLevelMap>
</HierarchyLevel>
<HierarchyLevel
DimensionLevel="STYLE">
<HierarchyLevelMap
KeyExpression="DIMSKU.MDID || DIMSKU.MGID || DIMSKU.PGID || DIMSKU.STYLE"
Query="DIMSKU">
<AttributeMap
Name="SHORT_DESCRIPTION"
Attribute="SHORT_DESCRIPTION"
Expression="DIMSKU.MDID || ':' || DIMSKU.MGID || ':' || DIMSKU.PGID || ':' || DIMSKU.STYLE">
</AttributeMap>
</HierarchyLevelMap>
</HierarchyLevel>
<HierarchyLevel
DimensionLevel="PRODUCT">
<HierarchyLevelMap
KeyExpression="DIMSKU.MDID || DIMSKU.MGID || DIMSKU.PGID || DIMSKU.STYLE || DIMSKU.SKU"
Query="DIMSKU">
<AttributeMap
Name="SHORT_DESCRIPTION"
Attribute="SHORT_DESCRIPTION"
Expression="DIMSKU.MDID || ':' || DIMSKU.MGID || ':' || DIMSKU.PGID || ':' || DIMSKU.STYLE || ':' || DIMSKU.SKU">
</AttributeMap>
</HierarchyLevelMap>
</HierarchyLevel>
<Description
Type="LongDescription"
Language="AMERICAN"
Value="PRODUCTS">
</Description>
<Description
Type="ShortDescription"
Language="AMERICAN"
Value="PRODUCTS">
</Description>
<Description
Type="Description"
Language="AMERICAN"
Value="PRODUCTS">
</Description>
</LevelHierarchy>
</Hierarchy>
<Attribute>
<BaseAttribute
Name="SHORT_DESCRIPTION"
IsVisibleForAll="True"
SQLDataType="NVARCHAR2(100)"
ETAttributeColumnName="SHORT_DESCRIPTION">
<Description
Type="ShortDescription"
Language="AMERICAN"
Value="Short Description">
</Description>
<Description
Type="LongDescription"
Language="AMERICAN"
Value="Short Description">
</Description>
<Description
Type="Description"
Language="AMERICAN"
Value="Short Description">
</Description>
<Classification
Value="STAR"/>
</BaseAttribute>
</Attribute>
</StandardDimension>
</Metadata>
But I'm facing problem if I put Names in Short Description attribute. I have fields MerchGroupName, MerchDivisionName, ProductGroupName, StyleName in the database table which I would love to use for short description. When I use them, the error is
INI: error creating a definition manager, Generic at TxsOqConnection::generic<BuildProcess>INI: XOQ-01600: OLAP DML error "ORA-34034: 1 is already a value of DEMANTRADW!SKU_MERCHDIVISION_SURROGATE." while executing DML "SYS.AWXML!R11_LOAD_DIM('SKU.DIMENSION' SYS.AWXML!___R11_LONG_ARG_VALUE(SYS.AWXML!___R11_LONG_ARG_DIM 1) 'MATCH' 'YES' 'YES' 'SKU.MERCHDIVISION.LEVEL' 'SKU.MERCHGROUP.LEVEL' 'SKU.PRODUCTGROUP.LEVEL' 'SKU.STYLE.LEVEL' 'SKU.PRODUCT.LEVEL' 'SKU.SHORT_DESCRIPTION.ATTRIBUTE' 'SKU.PRODUCTS.HIERARCHY')", Generic at TxsOqStdFormCommand::executeINI: XOQ-01601: error while loading data for Cube Dimension "CUBE_DEV.SKU" into the analytic workspace, Generic at TxsOqStdFormCommand::execute

Skipped and ragged level hierarchy in OBIEE11g

Hi
I tried creating aboth skipped and ragged hierarchy in OBIEE 10g
It works fine without error
SO I have doubt why they have introduced this concept in OBIEE 11g, Is there any more feture about this
Please help me

@Abdul : can you please let us know how you have implemented skip level hierarchy in 10g..
actually we need to implement it ,didn't find anything in google search ...
thanks In advance

Multiple Levels Hierarchy - Value Sets

Hello all,
I have a request from our client to create a four level hierarchy in E-Business Suite. I have tried creating dependent value sets but with this way I can create only two levels hierarchy since I can not make the dependent value set parent of another value set.
Does anybody have any idea?
Thank you in advance,
Christina

Hi Hiren,
According to your description, you will not select Country, State & City at the same time, right?
So as per my understanding, you needn't to create the hierarchy, just create three attributes Country, State and City. Then when you select one of the attributes in the PowerPivot table, the attribute can be the filter which you can see on the screenshot
below.
Regards,
Charlie Liao
TechNet Community Support

Heading level hierarchy errors when topics are in TOC more than once

I have discovered that the hierarchy in the Heading levels in
the Printed Documentation will differ from than in my online help
table of contents hierarchy, and that the problem is due to topics
that are intentionally in the TOC more than once.
For example, in chapter 5 of a particular help system the
hierarchy should be:
Heading 1 < Chapter 5 title from top-level book>
Heading 2 <title of second level book>
Heading 3 <title of topic that appears under second-level
book>*
What I actually get is:
Heading 1 < Chapter title from top-level book>
Heading 2 <title of second level book>
Heading 4 <title of topic that appears under second-level
book>*
* This same topic appeared in an earlier chapter. In that
chapter it was really at a Heading 4 level.
Due to company styles, etc. we use a numbering system at the
headings and in the TOC, so instead of
5
5.1
5.1.1
I erroneously get
5
5.1
5.1.1.1
This type of hierarchy issue appears multiple times in this
particular document (which I inherited by the way.)
Other than restructuring the document to not reuse topics in
different places in the TOC, is there a solution or a workaround
for this problem?
What I am doing so far, is generating the Print Documentation
one chapter at a time. As long as a topic is not reused with the
same chapter, my hierarchy of heading levels is maintained;
otherwise, it is not. Then I can put the chapters back together
after fixing the few places that still have heading level problems.
This however, will be quite cumbersome as this document is
translated into nine other languages.
I am using RoboHelp X5 for Word / Word 2003 for the source
and most of the translations; RoboHelp Asian Edition, Simplified
Chinese / Word 2003 for the Chinese translation. The heading level
hierarchy error occurs in both versions.

>> AF: I've commented in sections...
Without Maintain Heading Levels, RH will apply heading levels
to the books and then the topic levels will get bumped down. So a
top level book will be Heading 1 and the Headings in the topic will
get bumped down to 2, 3 and 4 etc. If then you have another book
one level down so that it gets Heading 2 applied, the same topic
but under the level two book would then get 3, 4 and 5 applied.
That is not the original problem but hopefully we are agreed
that is how things work on that.
>> Yes - that is the expected behavior. When it didn't
happen as expected, that's what led me to the discovery of the
cause of the problem (topic reuse).
Your problem was that firstly Heading 3 got bumped to Heading
4 if the same topic was inserted into the TOC twice. I assume it
was OK in the first instance, or is it that when you add it twice
it goes wrong everywhere?
>> Your assumption is correct. First occurrence is
correct. Second, third, and fourth (yes - there is one topic that
is used 4 times! ) are not correct based on TOC hierarchy.
On the numbering, nothing surprises me. If you look at my
site you will see that for RH HTML, i gave up on getting it right.
I have had many queries on this and more than a few people have
indicated they will work on the problem and get it working. I'm
still waiting. There are many posts about outline numbering
problems. Has anyone got it working satisfactorily?
>> I don't really have numbering problems. The
numbering is following the RoboHelp-generated hierarchy and the
.dot template that I apply. It's just that the RH-generated
hierarchy and its heading levels don't correspond to the "real"
hierarchy because of the reuse issue.
I have seen various Word gurus maintain that numbering has
not worked entirely satisfactorily since Word 2! Also enough posts
to convince me this is a Word issue, not a RH issue.
If you want to create a new project and knock something up
that demonstrates this problem, by all means zip it up and send it.
I'll assume it will be a small project and zip to less than 5mb. If
more, contact me first.
>> Unless you have RoboHelp X3 Asian Edition,
Simplified Chinese, there is really no need. I plan to either avoid
the reuse issue in the source, or build the print doc in sections
which is easy enough in RoboHelp X5 for the non-Chinese languages.
It is in the older Asian edition where the problems are compounded
by the omitted reuse topics. If you do have RoboHelp X3 Asian
Edition, Simplified Chinese and want to experiment, I can send you
a cut-down version of the project. Don't feel obligated though;
unless you can read Chinese (I can't) it is very tedious to work
with.

HRI Load All Competence Level Hierarchy Concurrent programm

HRMS application
11.5.10.2
windows 2003
db 10.2.0.4
How do I do the following?
Run the HRI Load All Competence Level Hierarchy concurrent program with the following parameters:
o Collect From Date: earliest reporting date required
o Collect To Date: current date (default)
o Full Refresh: Yes (default)
You should incorporate the above process into your Request Group.
I can see Concurrent : Program/define but not in submit request drop down.
Immediate Help is appreciated
Thanks.

I am able to do this.
I was registering under wrong security group.
Thanks.

Building 3 level hierarchy in AII (item-case-palette)

Reading the help pages of AII, it indicates that only a two level hierarchy can be build (case-palette). I'm wondering if I can use AII also to create a three level hierarchy for item-case-palette.
Thank you,
Ron

HI Ron,
You can use SAP AII to build three level hierarchy. The pages you are mentioning are with respect to hierarchy building through Mobile.
Regards,
Vivek

Highest level hierarchy

Hi ,
What is Highest level Hierarchy in BMM Layer?
Thanks........

Can you elaborate your question a bit more please..?
The highest level in your hierarchy is the first level in your hierarchy from a top-down perspective. You need to check the "Grand total level" checkbox, for this level in your hierarchy.
Regards,
Stijn

How to display 3 level hierarchy alv report using SALV

Hi ,
      I need to display a Hierarchy ALV report with 3 level.I thought of trying CL_SALV_HIERSEQ_TABLE but i am able to display only two level report.
      How can i display the 3 - level heirarchy report using SALV. I don't want to use SALV_TREE.
      Regards,
      Aditya Tanguturi.

Hi Aditya,
Please check this thread
Is it possible to display more than 2 levels us... | SCN
Thanks !
Amit

Cl_salv_hierseq_table for 3 level

Hi
I need to implement the 3 level of Hierarchical display using class cl_salv_hierseq_table.
Also we are not able change the column text in hierarchical output. Please provide the sample code/ any inputs to display the the hierarchical output.
thanks,
Shrinivas

Hi shrinivas,
Kindly let me know how you had carried out the 3rd level of Hierarchy.

Cl_salv_hierseq_table= factory 3 Level Hierarchy

Similar Messages

Maybe you are looking for