Hierarchy problem inBI7

Hey, Gurus:)
We are expearencing the following problem after upgrading to BI7:
The querry which has characteristic restricted on hierarchy does not return the desired respond - actually it does not respond at all.
When I tryto restrict the characteristic on some value the Bex respond in DUMP in
RRSI_NODES_OF_TYPE_GET function. I want to emphasize that the hirarchy looks active in bw , I ca edit it and activate once again ad it looks fine, BUT .....
In bex th querries that have characteristics based on this hierarchy does not run and accessing that characteristics responds with dump.
Any ideas...

Not sure if the english version has been released ,it just came up after keying your error in service sap
wait for SAP to respond
or google it for translation
Hope it Helps
Chetan
@CP..

Similar Messages

Hierarchy problem in BEX

Hi,
Our 0material is loaded with hierarchy prdha, also
0prod_hier_attr is loaded-activated and 0prod_hier infoobject is loaded-activated as well.
The weird thing (unless for me) is that in bex only some 0materials have a data in hierarchy attribute; we check 0material records and the hierarchy is there same in 0prod_hier... the problem is only in the query.
Please some advices??
Thanks In Advance

HI Neetu..
Please check the settigns of the infoobject in use..u need to select text and key for the description in buisness explorer tab of \inoobject definition

Context menu00FA and hierarchy problem

Gurus...
I have a problem when I make the filter for a page Web,
I execute the page with
/sap/bw/BEx?sap-language=ES&bsplanguage=ES&CMD=LDOC&TEMPLATE_ID=ZADWEB0201,
and there is no problem to me, this page contains query with hierarchy,
but when the filter of the following way,
/sap/bw/BEx?sap-language=ES&bsplanguage=ES&CMD=LDOC&TEMPLATE_ID=ZADWEB0201&FILTER_IOBJNM_2=0COMP_CODE&FILTER_VALUE_2=0061
I cannot see the hierarchy of query and the context menu.
Somebody can say to me if I need parameters for the presentation of the page.
Greetings.

Hi Noe,
why are you working with "_2" after the filters? Try using
sap/bw/BEx?sap-language=ES&bsplanguage=ES&CMD=LDOC&TEMPLATE_ID=ZADWEB0201&FILTER_IOBJNM=0COMP_CODE&FILTER_VALUE=0061.
If you are using more than one data provider maybe you have to set the correct data provider, too:
sap/bw/BEx?sap-language=ES&bsplanguage=ES&CMD=LDOC&TEMPLATE_ID=ZADWEB0201&DATA_PROVIDER=DATAPROVIDER_1&FILTER_IOBJNM=0COMP_CODE&FILTER_VALUE=0061.
(if DATAPROVIDER_1 is your data provider)
Greetings,
Daniel

Hierarchy Problem

Hi,
We have a query with several free characteristics, one of which is SEGMENT and this has a hierarchy. I run the query, the report comes up. Then, I click on the filter button next to SEGMENT. The first 4 nodes of the hierarchy come up. I expand the first node, and this gives me the 6 leaves of node 1. In this, I select the first 3 leaves, and then I click on the Transfer button. The report runs again, no problems. Now I click on the same filter button again, and again, the first 4 nodes of the hierarchy come up. I expand the first node, and the first 3 leaves, which I had selected, are now showing with no ticks. Why has the ticks for the first three leaves diappeared?
Why is the selection diappearing? Any help is gteartly appreciated. We use BW 3.1
Sujoy

Well, the first question is what do you want the end result to be?
Do you want it to be the case that the sum of the "children" of net income is not equal to the value of net income (since 578004 is counted in multiple children, but only once in NET_INCOME)?
Is 578004 really intended to aggregate into both intermediate results?
One possibility if you want to keep things inconsistent is to add a third hierarchy which explicitly tells Aggregate how to calculate NET_INCOME. The way that Aggregate resolves inconsistent hierarchies is that it gives precedence to the definition of the later hierarchies.
So something like this:
Hierarchy 1:
578004 -> Intermediate A
Hierarchy 2:
578004 -> Intermediate B
Intermediate A -> NET_INCOME
Intermediate B -> NET_INCOME
Hierarchy 3
578004 -> NET_INCOME
Creates an inconsistent, hierarchy (NET_INCOME has different definitions in different hierarchies), but since Aggregate will use the Hierarchy 3 version there is no longer an undirected loop from 578004 back to itself (i.e. it would not longer be double counted).
If you want 578004 to aggregate into Intermediate A when you are looking at the view for hierarchy 1, but NOT to aggregate into Intermediate A when looking at the view for hierarchy 2 then what you are really suffering from here not the undirected loop, but the inconsistent definition of the Intermediate A.
Which leads to the second potential solution - to create distinct dimension values for "Intermediate A_H1" and "Intermediate A_H2".
Hierarchy 1:
578004 -> Intermediate A_H1
Hierarchy 2:
578004 -> Intermediate B_H2
Intermediate A_H2 -> NET_INCOME
Intermediate B_H2 -> NET_INCOME
Here it is completely clear that NET_INCOME is the sum of the intermediates in the second hierarchy, and the intermediate in the first hierarchy is something completely different.
In summary it all depends on what you want as output.

Hierarchy problem in sql query

Hello Experts,
               I am using oracle 11g database with sql developer tool at windows 7.I am trying to make hierarchy for my table data.I have a table tbl_state as
State_Code
State_Name
Country_Code
1
AH
0
2
BH
91
3
CI
72
4
DI
72
5
EH
91
6
FI
72
7
GJ
83
8
HJ
83
I want hierarchy as: set all states under their country for this I have tried a query as:
SELECT 1, LEVEL, STATE_NM, null, to_char(SATE_CODE) FROM tbl_state CONNECT BY PRIOR SATE_CODE = COUNTRY_CODE start with COUNTRY_CODE=0
but there is no output as i want.Please suggest me what is going wrong here and if there is any better optimized way to make such hierarchy then please give me.
thank you
regards
aaditya

Hi,
You always need to post CREATE TABLE and INSERT statements for sample data, so that the people who want to help you can re-create the problem and test their ideas. If you post statements that don't work, you're just wasting your own and other peoples' time. Do you wnat to get answers that work? Then show the same courtesy to the people who try to help you. Test (and, if necessary, correct) your statements before you post them.
None of the INSERT statements you posted work with the given CREATE TABLE statement. You should always explicity list the columns in an INSERT statement, like this:
INSERT INTO tbl_state (sate_code, state_nm, country_code)
               VALUES (1,         'AA',     0);
If you add new columns to the table, old INSERT statements like this will still work.
Here's one way to do what you requested:
SELECT    CASE
              WHEN GROUPING (state_nm) = 1
              THEN country_code
          END    AS country_code
,         state_nm
FROM      tbl_state t
GROUP BY country_code
,         ROLLUP (state_nm)
ORDER BY t.country_code
,         state_nm        NULLS FIRST
Output:
COUNTRY_CODE STATE_NM
           0
             AA
          72
             CI
             DI
             FI
          83
             GJ
             HJ
          91
             BH
             EH
             IH
Is the order of countries in your desired output important? If you really need 91 between 0 and 72, explain why, and we'll find a way to code it.

Hierarchy problem when creating IDoc with multiple headers

Hi,
In general, When you create an inbound IDoc for the IDoc Type FIDCCP02, you have all the data records arranged in hierarchical order (while viewing it in the we02 transaction).
Our requirement is to have m number of headers(E1FIKPF) and in turn it has n number of items(E1FISEG) inside a same IDoc. We have a problem in viewing the hierarchy of them in the data records tab. It comes down in a flat order without hierarchical division.
If we have only one header, we get the hierarchy sorted by default. If we have multiple headers we see the same problem again.
We guess some make-ups in the EDIDD structure which contains segnum, hlevel etc needs to be done.
Let us know the correct method to get this fixed.
Points will be rewarded.Thanks in advance.
Regards,
Reni

Every Idoc segment has a place to put in the parent segment for that Idoc. When you "fill" the Idoc , this tsep might not be executing for some reason.
Is this some customer development?
in EDID4 ,see these fields
PSGNUM-Number of the hierarchically higher SAP segment
HLEVEL Hierarchy level.
Regards

Hierarchy problem once again

Dear All;
I have the following sample data shown below
create table t1_concept
list_id varchar2(1000),
list_model varchar2(400),
list_num varchar2(1000)
insert into t1_concept
(list_id, list_model, list_num)
values
('A11-11', '1', 'A22-2');
insert into t1_concept
(list_id, list_model, list_num)
values
('A11-11', '1', 'A33-3');
insert into t1_concept
(list_id, list_model, list_num)
values
('A11-11', '2', 'A44-4');
insert into t1_concept
(list_id, list_model, list_num)
values
('A11-11', '1', 'A55-5');
insert into t1_concept
(list_id, list_model, list_num)
values
('A44-4', '13', 'B11-1');
insert into t1_concept
(list_id, list_model, list_num)
values
('A44-4', '8', 'B22-2');
insert into t1_concept
(list_id, list_model, list_num)
values
('A44-4', '8', 'B33-3');
insert into t1_concept
(list_id, list_model, list_num)
values
('A44-4', '8', 'B44-4');
insert into t1_concept
(list_id, list_model, list_num)
values
('A55-5', '9', 'C11-1');
insert into t1_concept
(list_id, list_model, list_num)
values
('A55-5', '9', 'C22-2');
create table t2_concept
list_num varchar2(1000),
max_list_model varchar2(1000)
insert into t2_concept
(list_num, max_list_model)
values
('A44-4', 'A');   --changed to show that we can have letters
insert into t2_concept
(list_num, max_list_model)
values
('A55-5', '9');
insert into t2_concept
(list_num, max_list_model)
values
('A66-6', '10');I know things would have been easier with a good normalized table design. however unfortunately, I am taking over another programmer works and I am trying to look for a good solution.
I am here trying to create a hierarchy structure. the idea behind it is as following
if we start-off with List_ID = A11-1 and List_model = 1, then we are going to have the have the following children associated with it
A22-2, A33-3 and A55-5
now, these children have children of their own and the idea is to look in the t2_concept table to determine the latest list_model and utilize it in the recursion, so in this case if you look at t2_concept for A44-4 it has a max_list_model of A and we are then going to go back to t1_concept and determine all the associated children for A44-4 which are B22-2, B33-3 and B44-4 and we continue with this approach till the end.
this is output I want by the way
LEVEL      List_ID
   1          A22-2
   1          A33-3
   1          A44-4
   2          B22-2
   2          B33-3
   2          B44-4
   1          A55-5
   2          C11-1
   2          C22-2I know things would have been easier with a good normalized table design. however unfortunately, I am taking over another programmer works and I am trying to look for a good solution.
All help and questions are appreciated.
Edited by: user13328581 on Aug 16, 2011 10:25 AM
Edited by: user13328581 on Aug 16, 2011 12:00 PM

Hi,
If you can't normalize the tables in reality, you can normalize them on the fly, like this:
WITH     joined_data      AS
     SELECT     t1.*
     ,     t2.max_list_model
     FROM           t1_concept     t1
     LEFT OUTER JOIN      t2_concept     t2 ON    t1.list_num     = t2.list_num
--     WHERE        ...      -- If you have other filtering, do as much as possible here
SELECT       LEVEL
,       list_num
FROM       joined_data          j
START WITH        list_id     IN ('A11-11')     -- Or any given values
CONNECT BY        list_id     = PRIOR list_num
     AND        list_model     >= PRIOR max_list_model
ORDER SIBLINGS BY list_num
;You may not need a sub-query; joins are done before START WITH and CONNECT BY, but it's often faster if you do the joins in a separate sub-query.
Is the problem here that, for purposes of this query, you don't want to consider 'B11-1' to be a child of 'A44-4' because list_model > list_num? That's what the 2nd condition in the CONNECT BY clause is doing. The query above produces the results you want, but the condition I posted looks backwards to me.
Edited by: Frank Kulash on Aug 16, 2011 2:37 PM
Mystery solved: list_model and max_list_model are strings, so '8' is greater than '13'.
The following works for the sample data already given:
WITH     joined_data      AS
     SELECT     t1.*
     ,     t2.max_list_model
     FROM           t1_concept     t1
     LEFT OUTER JOIN      t2_concept     t2 ON    t1.list_num     = t2.list_num
--     WHERE        ...      -- If you have other filtering, do as much as possible here
SELECT       LEVEL
,       list_num
FROM       joined_data          j
START WITH        list_id     IN ('A11-11')     -- Or any given values
CONNECT BY        list_id     = PRIOR list_num
     AND        LPAD ( list_model                    -- This condition has been changed
                  , 1000
               )     <= PRIOR LPAD (max_list_model, 1000)
ORDER SIBLINGS BY list_num
;and it may even work in your real data. (I have no way of knowing yet.)

Hierarchy Problem ( Duplicates records Problem)

Gurus-
I'm having a problem with cost center Hierarchy ,
my problem is if a person is the head of cost center , he can manage 4 to 5 Cost center, I configured in bw Ex: Mr X as a Text Node
Under him is all the Cost center Character under the tedxt node .
But when I'm running my query , I'm getting every thing getting Duplicate Values...One for the MR X & Other for the Cost Center Character
Report out put:
1, MR X (Which is a Text Node) cost center 1001, emp id 100.....
and othe value for Cost center 1001, emp id 100
2 , MR Y Cost center 2001 , emp id 2000
and othe value for Cost center 2001 , emp id 2000
How should i eliminate the Duplicates .Please, help me out....

if thats the case, then the values arent duplicating, it is just the structure ur business wants to display. As MR.X is both the text node as well as the char value. thats the reason they seem to duplicate, but actually they are not. If observe, the totals would be different for both the node and value. As the node would be having mutiple values beneath it .. meaning mr.y and mr.z can aslo be under X.
If this is the case, I dont think there is a way to supress the nodes of hierarchy if the IO has hierarcy set in the properties to display.

SEM-BCS Load Hierarchy Problem

Hello Experts!
I´m getting a problem loading the hierarchy in SEM-BCS.
I have a method to load hierarchy from BW into BCS and the main customizing is:
Data Type: 21 Items
InfoObject: 0ACCOUNT
Options for Master Data and Hierarchies: Load Hierarchy
Updata Mode: Delete All
When I execute extractors of BW and get the hierarchy from ECC, the infoobject 0ACCOUNT gets hierarchy and accounts loaded from ECC perfectly.
When I execute the method to load hierarchy from BW into BCS using t-code UCWB, I get several warning messages as bellow:
"Leaf IFRS2.30.10.02 belongs to type Hierarchy Node(s)
Diagnosis
Value IFRS2.30.10.02 of characteristic Hierarchy Node(s) is defined as a leaf in the hierarchy -- that is, no further nodes are attached to it. However, a leaf must belong to the hierarchy-defining characteristic Item.
Procedure
Modify the hierarchy either by deleting the node from the hierarchy or by adding more nodes beneath."
The problem is, I don´t have leafs without an account or another node beneath in the source hierarchy. I have updated all of them, but SEM-BCS still tries to get leafs that even does not exist in the source provider.
Does anybody have any clue about what is still going on with the load hierarchy?
Any help is appreciated. Thanks!

With uploads in Delete All mode, you may have a problem with the deletion of the existing hierarchy - try in overwrite mode to see if you get the same warnings.
Also, as this is a "warning" message only, it does not stop you from saving the hierarchy, so you can see what value you get in the hierarchy and what/where it was before you ran the upload - this may help you identify the problem.

Hierarchy problem when Reporting on Infoset

Hi,
I am reporting on Infoset which is made up of 2 ODS and Customer Master.
ODS 1: General ledger: Line items 1
ODS 2: General ledger Line items- additional fields.
ODS 1 consists of G/L Account.
I have put G/L Account in the filters and i have restricted it by means of the Hierarchy Node Variable.But when am executing the report its giving the error as Variable is Invalid.
By restricting in this similar way i have created quite number of reports in Infocube that contains G/L Account.Moreover in those reports also G/L Account has been restricted by the same Hierarchy Node Variable as in the report on Infoset.
I would like to know whether any constraints when reporting on Infosets?
Thanks,
Rajesh janardanan

Takeaways ..
<b>Design Recommendations</b>
To avoid problems caused by duplicated key figure values (see SAP Note 592785), we recommend that you only stage the key figures of one DataStore object or InfoCube of the InfoSet for the query (indicator in the first column in InfoSet maintenance).
SAP recommend that you only use one InfoSet object (DataStore object, InfoCube, or master data table) with ambiguous characteristic values. This means that when you join a DataStore object with an InfoCube, as long as the InfoCube contains the visible key figures, all the key characteristics of the DataStore object are used in the join condition for the InfoCube. Equally, when joining a master data table with compounding to an InfoCube, all of the key characteristics of the master data table are joined with the characteristics of the InfoCube.
http://help.sap.com/saphelp_nw2004s/helpdata/en/05/7ce2416149c717e10000000a155106/content.htm
Hope it Helps
Chetan
@CP..

[iPhone] View Hierarchy Problems

I have a program laid out with the navigation controller and a bar button item that leads to the next view... my problem/question is why when I load the program, does it automatically go down a level even farther than i have programmed. It starts on mainView -> Settings -> Settings(the one i never programmed).
my aim would be to have it just start on the mainView with the button leading to the Settings view.
Code is as follows:
- (id)init
if (self = [super init])
self.title = @"mainView";
self.tabBarItem.image = [UIImage imageNamed:@"mainViewTabBar.png"];
self.navigationItem.rightBarButtonItem =
[[[UIBarButtonItem alloc] initWithTitle:@"Settings" style:UIBarButtonItemStylePlain
target:self action:@selector(loadView)] autorelease];
return self;
- (void)loadView
SettingsViewController *settingsView = [[[SettingsViewController alloc] init] autorelease];
[self.navigationController pushViewController:settingsView animated:YES];
thanks for any help

so far, i haven't put any code into SettingsViewController beyond the pre written stuff.. and setting the navBar title. Putting the code in viewDidLoad rather than loadView helped. Instead of going to the view i never programmed, it goes straight to the settingsView. So thankyou for that. When the program starts, i see the transition from the mainView to the settingsView without me touching any buttons... so my guess is that im missing some property for the button or the view im pushing onto the stack? something that inhibits it from automatically drilling down? im not exactly sure.
#import "SettingsViewController.h"
@implementation SettingsViewController
- (id)init
if (self = [super init])
self.title = @"Settings";
return self;
Implement loadView if you want to create a view hierarchy programmatically
- (void)loadView {
If you need to do additional setup after loading the view, override viewDidLoad.
- (void)viewDidLoad {
- (BOOL)shouldAutorotateToInterfaceOrientation:(UIInterfaceOrientation)interfaceOrientation {
// Return YES for supported orientations
return (interfaceOrientation == UIInterfaceOrientationPortrait);
- (void)didReceiveMemoryWarning {
[super didReceiveMemoryWarning]; // Releases the view if it doesn't have a superview
// Release anything that's not essential, such as cached data
- (void)dealloc {
[super dealloc];
@end
Message was edited by: Bourne89

WAD Hierarchy problem

Hello,
Sometimes when I open a hierarchy in WAD report, it opens a new session of IE instead of opening the hierarchy.
I don't have a clue how to fix it.....
Please Advise!
David

The problem happened only in MAXTHON browser... I installed it again and the problem disappeared.

Null value in Hierarchy Problem

Hi, all:
I have the following issue that need your help, any comments would be greatly appreciated.
We have a table, say sponsor, sponsor has four different levels, say level1, level2, level3, level4, but not all sponsors have 4 levels, some may only have 1 or 2 level2. For example:
Level1     Level2     Level3     Level4
Federal     DOD     ARMY     RAH
Federal     DOE
Industry
When I built a hierarchy for this four levels and use it in discoverer plus, even some of sponsors only have level1, it will still drill down to level2, level3, and level4, with the same value of its level1. That is not pretty. My question is how to not drill down to level2, level3 and level4 if they don't exist?
Regards,
Li

Hi, all:
I have the following issue that need your help, any comments would be greatly appreciated.
We have a table, say sponsor, sponsor has four different levels, say level1, level2, level3, level4, but not all sponsors have 4 levels, some may only have 1 or 2 level2. For example:
Level1     Level2     Level3     Level4
Federal     DOD     ARMY     RAH
Federal     DOE
Industry
When I built a hierarchy for this four levels and use it in discoverer plus, even some of sponsors only have level1, it will still drill down to level2, level3, and level4, with the same value of its level1. That is not pretty. My question is how to not drill down to level2, level3 and level4 if they don't exist?
Regards,
Li

Hierarchy problems in cross tab

Hello,
we are using DS 1.3 and I have a query which want to use with several views.
I configured the initial view like the screen shot shows. The problem is, if I assign this data source to a cross tab, no data is available for this component. But the initial view shows some data. Is there something else I have to consider?
This behavior only appears if I use queries with hierarchies.
Thanks
Robert

Hello Robert - please see SAP Note http://service.sap.com/sap/support/notes/2001504 to see if it may apply; SP1 is planned in a few weeks

Customer master Hierarchy problem

Dear Gurus,
I 'm configuring customer hierarchy first time ,need your suggestion how to configure the below mentioned structure
Goodyear HQ
Goodyear EMEA                               Goodyear AMERICAs                               Goodyear A/P
(Europe&Middle east)                      ( NAFTA&South America)                          ( Asia/Pacific)
Germany                                              US                                                           India
France                                                 Brazil
Poland
Czeh Rep
Great Britan
South africa
My doubt is how many levels we need to define for above structure? Looking for your inputs
Thanks and regards
Venkat

Hai Venkat,
This is the step by step config for the cust master hierarchy...
<< Moderator message - Cut and paste response from http://www.sap-basis-abap.com/sd/customer-hierarchy-in-sales-order-processing.htm removed and points unassigned. Plagiarism is not allowed in SCN >>
Hope this works..
Thnks.
Saravanan
Edited by: Rob Burbank on Feb 29, 2012 12:01 PM

Hierarchy problem inBI7

Similar Messages

Maybe you are looking for