BPS External Hierarchy with Postible Nodes

Hi,
I am using External Hierachy (more than 2 levels) in BW and Characteristic relationship between Account and Account Group in BPS. Account group is an attribute on Account. I have included the Account Group in the Planning Level. On the layout Account Group and acct are in the lead columns respectively. As defined in How to ... Hierarchies in Several Characteristics document.
Everything works fine but it shows nodes only upto two levels in the hierarchy. If the hierarchy contains more than two levels....it only shows two levels. On the how to document, example is for two level hier.
I want to know why it is not showing more than two levels as defined in the external hierachy.
Has anybody come across with the same situation and is there a way to show more than two levels???
Thanks in advance,
Anil

Hi Anil,
Welcome to SDN.
The reason why you are able to see only two levels is because you have just two Characteristics used in the hierarchy structure i.e. Account and Account group.
Please note the conditions mentioned in the How To document in section 2.2 which lists down the restrictions.
"For a given level in the hierarchy, every node/leaf must belong to the some characteristic, and no two levels can use the same characteristic."
What I understand from this is that the hierarchy would only display Characteristic nodes and not Text Nodes.
So if you had 3 InfoObjects like
Chart of Accounts
Account Group
Account
I believe you would be able to get three levels in the same.
Hope it helps.
Cheers
Anurag
......assigning points is just a way of acknowledging the response at SDN

Similar Messages

Hierarchy with postable node -- data will be displayed on leaves only

Hello,
I have programmed a generic data source for hierarchy of BOM which should display CO-PCP data along the BOM hierarchy, comparable to transaction CK13N on R/3.
The hierarchy is loaded successfully, having the following info objects:
0SOURSYSTEM
0PLANT
QMATERCO (header material of BOM)
QMATPLCO (BOM components of inner nodes and leaves).
QMATERCO and QMATPLCO are compounded to 0PLANT, each node is loaded with its individual unique node ID in order to post line items for each BOM component on higher and lower level. The hierarchy will be loaded for characteristic QMATPLCO (having defined 0PLANT and QMATERCO within hierachy definition).
Now I have setup an info cube containing 0PLANT, QMATERCO and QMATPLCO, additionally some other descriptive characteristics and key figures.
The line items given in R/3 source tables are posted into the info cube for inner nodes and leaves (all of them QMATPLCO), each line item is dedicated to one QMATPLCO node.
Problem: The query will display line items for leave nodes only but not for all inner nodes although the nodes are displayed with green characteristic icon if I check the hierarchy itself. Furthermore, in BeX if I drag and drop QMATPLCO into the row, I can choose the loaded top node of the hierarchy but not any inner node or leave node.
What is missing?
Message was edited by:
Stephan Hofmann
Message was edited by:
Stephan Hofmann
Edited by: Stephan Hofmann on Sep 4, 2008 2:02 PM

Complete own strategy for this problem has to be developed.

How to change the BADI to update the IO Hierarchy with characteristic nodes

I need to modify / enchance a standard hierarchy datasource as it updates my IO into floder nodes instead of characteristic nodes. Can anyone tell me the exact steps where I can modify the BADI for the standard source.
I'm trying to update 0CostElmnt hierarchy (Char 14) but my source data is (char 10).
Any help is highly appreciated.

I need to modify / enchance a standard hierarchy datasource as it updates my IO into floder nodes instead of characteristic nodes. Can anyone tell me the exact steps where I can modify the BADI for the standard source.
I'm trying to update 0CostElmnt hierarchy (Char 14) but my source data is (char 10).
Any help is highly appreciated.

BW hierarchy dummy leaf node in BPS layout

BW hierarchy with postable nodes.
I am using a cost center Hierarchy in a layout.
I get the following nodes:
4711 (inner node)
--4711 (dummy leaf, system generated, not assigned budget)
--4712 (leaf)
How can avoid displaying in the layout the dummy leaf, system generated, not assigned node?

If the dummy node is a summary of all cost centers not present in your hierarchy (thus the not assigned node BW generally allocates to your hierarchy):
then goto your info-object(cost center), enter the specific hierarchy, click on the button 'hierarchy attributes', click the flag suppress not assigned nodes.
Activate your hierarchy.
BW will now no longer display the not assigned node.
Please assign points if this helped you or solved your problem,
Filip

How to create a hierarchy with postable notes

Hi all,
Please take e look at the following case:
In BPS we want to make a planning on groups of FI-GL-accounts. For the grouping of the GL-account we make use of the Financial Statement functionality in R/3. With a BC DataSource (0GL_ACCOUNT_T011_HIER) this Financial Statement is imported in BW as a hierarchy on InfoObject 0GL_ACCOUNT. As said, we do not want to make a planning on the GL-account but on the groups, i.e. the nodes of the hierarchy. We think in this case we need a BW hierarchy with postable nodes and make the planning on the inner nodes of the hierarchy.
So far so good, but when we execute the Manual planning the system responds with Hierarchy xxxx does not contain any postable nodes Anyone has a clue? Did we forget something?
Thx,
Henk van der Haar.

Hi Henk,
For the hierarchy with postable nodes the nodes also have to be captured as characteristic values firstly. For more details refer to the document link below
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/biw/g-i/how to plan in bps using hierarchies with several characteristics.pdf
Some useful threads also on the same.
Hierarchy with Postable nodes
Bbw hierarchy with postable nodes Disabled
Hope it helps.
Cheers
Anurag

Hierarchy with Intervals and Temporal Join

Hi,
I am loading a hierarchy structure (Time dependant and with Temporal Join and Intervals)
in the flat file structure for hier loading we have leaf to and leaf from fields which means Page of the hierarchy to and page of the hierarchy from.
can anyone let me know what is the use of these fields, and the values we have to pass for these fields with an example.
i haven't come across Hier loading with intervals and termporal join.
can anyone please help me in this?
Regards,
p423168.

Hi,
BI Process (Loading Hierarchies from Flat file to BI)
Go to RSA1
Create info object for customer as zcust_b5 and activate
Create info object as zcust_b5 and activate it
Select the info object and double click on it
Select the hierarchies tab and select the option with hierarchies
And select Hierarchies not time dependent
Click external characteristics in hierarchies
Select your Infoobjects in the list and pass it and activate it
After activating the objects we will see tables of hierarchies at maintain Hierarchies
Create an application component
Create the transfer rules for the info object and activate (for hierarchies, texts, attributes)
This screen will show the communication structure.
After creating the data source at info source level the field attributes are shown in above
Create an excel sheet with required values and save it in CSV file.
Uploading the Hierarchy Data into BW
a) Create Info Package for Hierarchy Upload. Select the Hierarchy to be uploaded
and also the Full Update button as we are uploading the entire Hierarchy.
b) There are three update methods for uploading the hierarchy.
Full Update: For Uploading the entire hierarchy structure
Insert Sub tree: For appending the hierarchy with new nodes.
Update Sub tree: For modifying the nodes of the hierarchy.
Create info package and schedule the data loads
Select the Hierarchy and name it before scheduling
Schedule and Start the data loads
After creating the info package of the info object the above screen shows the initial hierarchy maintenance
Hierarchy is done successfully by extracting data from flat file.
time dependent :
a) For making the hierarchy time dependent select the u2018Time-Dependent Hierarchy structureu2019 radio button and activate the info object ZSREP
b) In the transfer structure there will be 2 more additional fields date from and date to for the time dependent nodes.
c) Consider that Sales Representative u2018SREP2u2019 was in England up to 31/12/1995 and moved to USA
d) Flat file structure for the above hierarchy is shown below . It contains two extra columns Date-to and Date-from.
e) In the info-package Update tab , select Fixed Time interval radio button and give start date as 01/01/1000 and End date as 31/12/9999 so that all nodes are uploaded.
f) Upload the hierarchy data from flat-file to BW.
g) Display the loaded hierarchy.
Regards
Sudheer
Edited by: SUDHEER on Dec 30, 2008 12:52 PM

External characteristics and postable nodes in BW hierarchy in BPS layout

Hi!
Short question: If using a hierarchical layout in BW-BPS what are the constraints on the hierarchy for values to be able to be planned on the individual levels of the hierarchy?
Typically if one has a product hierarchy with one hierarchy basic characteristic: product and an external characteristic: product group which are connected in a hierarchy. How can values be planned on the product group level? And how does this relate to postable nodes in the BW documentation: http://help.sap.com/saphelp_nw04/helpdata/en/c1/493d3854129f68e10000009b38f8cf/content.htm. Is it only postable nodes that can be planned?
Regards,
Christian

Christian,
     The attached document would answer most of your questions.
     https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/biw/g-i/how%20to%20plan%20in%20bps%20using%20hierarchies%20with%20several%20characteristics.pdf
    Hope this helps.
Cheers
Srini

How to Create and External Hierarchy and group values of IO in node

Good morning
BI 7:
Please give me guidance on the following?
I need to either to restrict a characteristic in a query to more than 800 values OR exclude values where it contains the pattern 'Z7' and 'Z8'. There are thousands of values which contains the pattern and they are not listed in such a way that I can exclude them as a value range, thus I would have to include all the values I want into the restriction, which is more than 800. An error displays when I check the query:
""In the structural component Warranty Damage Code, characteristic ZWR_DMGC is restricted to 838 values. This number is very large and will probably meet with technical limitations""
The proposed solution is:
""Create an external hierarchy for characteristic ZWR_DMGC and group the 838 values in a hierarchy node. You can then work with the node instead of the 838 individual values.
Alternatively, you can define a corresponding navigation attribute for ZWR_DMGC""
I know where to create the hierarchy, but I am confused how to only include the values of the applicable IO where pattern contains 'Z7' and 'Z8'.......??
The following are some of the steps proposed in a related thread, but I am loosing it at step 7.
5. Confirm your entries. The Maintain Hierarchy screen appears. You can define the structure of a hierarchy here. ok
6. To create a hierarchy node, you first need to choose an insertion mode: Insert as First Child or Insert As Next Neighbor (see Hierarchy Editing Functions). I selected first child
7. Choose the type of node you want to create: Text Node, Characteristic Node, <Hierarchy Basic Characteristic Node> or Interval (see Hierarchy Nodes) *this is where I am lost, which should I select to list values with pattern ' *Z7' and ' Z8' in a node or two
8. Repeat this procedure until the hierarchy structure has been set. For more information, see Modeling Nodes and Leaves.
A hierarchy can contain 50,000-100,000 leaves at most. If your hierarchy is larger, you should insert a level that is used as a navigation attribute or preferably as a separate characteristic in the dimension table.
9. You can use Level Maintenance and Hierarchy Attributes to set how the hierarchy is to be displayed and processed in reporting (see Level Maintenance and Hierarchy Attributes).
10. Save the hierarchy.
Your assistance will be appreciated.

Hierarchy not used in this case. Could not fnd an answer.

Hierarchy with External Characteristics

I have a request to create a hierarchy for a BEX query that is based on a combination of WBS Element and COORDER. I see that I can change either of these InfoObjects to allow External Characteristics and I have done this.
This hierarchy is to show costs by Project Manager. Each Project Manager can have many projects and each project can have many WBS Elements plus individual orders or nothing but individual orders. I've built the hierarchy and it works in the query as far as how the results are displayed. But I am only getting costs associated with WBS Elements not with orders. (I should add that we do not post to WBS Elements, we assign WBS Elements to orders and we post costs to orders so WBS Element is an attribute of COORDER).
For instance, one project manager could have 2 projects; Project 1 includes all orders associated with WBS Element 1 (so I assign the value for WBS Element 1 to a node); Project 2 includes all orders related to WBS Element 2 as well as Order 1 and Order 2 (which are assigned WBS Element 3 but I don't want all of the orders assigned to WBS Element 3 so I assing WBS Element 2 to a node, Order 1 to a node and Order 2 to a node).
Here is what it looks like:
1 0HIER_NODE PROGMGR1 (child ID = 2; next = 4)
2 0HIER_NODE PROJECT1 (parent ID = 1; child = 3)
3 0WBS_ELEMT 1 (parent ID = 2)
4 0HIER_NODE PROJECT2 (parent ID = 1; child = 5)
5 OWBS_ELEMT 2 (parent ID = 4, next = 6)
6 0COORDER 1 (parent ID = 4, next = 7)
7 0COORDER 2 (parent ID = 4)
I get all of the costs for both projects that are associated with WBS 1 and 2 but none of the costs for the two orders not related to a specific WBS Element.
I have created a selection variable to use the hieracrchy when selecting the query results. What is the point of assigning External Characteristics in a hierarchy? I understand logically why my query doesn't select the costs associated with the orders since my hierarchy is based on WBS Element not order. I've tried including the WBS Element associated with the individual orders in the hierarchy with the thought of restricting those particular nodes down to the specific orders in a structure in my query but I can't seem to figure that out either.
Can anyone give me any ideas on how to do this?
Thanks,
Barb Bunker
Puget Sound Energy

Hello baRbaRa,
How r u ?
You have Kept the 0HIER_NODE for the PROJECT MANAGER. Will there be only one project manager !? Assuming you will have more Project Managers,
0HIER_NODE
|_ZPROJ_MGR
...|_ZPROJECT
......|_ZWBS_ELMT
......|_ZORDERS
If you assign the WBS Element & Orders to PROJECT it should give the costs based on the PROJECT & WBS Element / PROJECT & Orders combinations.
Is this you r looking for ?
Best Regards....
Sankar Kumar
+91 98403 47141

MDX with External Hierarchy

Hi,
I have a problem with querying a BEx query cube by MDX. The BEx query contains an external hierarchy that facilitates MDX functions such as Generate(). The MDX query is working in MDXTEST transaction code in BW system. However the error - "system error in program cl_rsr_mdx_soap_handler... The server sent an unrecognizable response." is raised when trying it through XMLA provider from Microsoft Reporting Services. For other BEx queries that don't have external hierarchy, the Reporting Services can successfully query them via XMLA.
Does anyone know what the issue is?
Thanks a lot,
===================================
The server sent an unrecognizable response. (Microsoft Visual Studio)
Program Location:
   at Microsoft.ReportingServices.XmlaClient.AdomdDataReader.CompletePreviousRow()
   at Microsoft.ReportingServices.XmlaClient.AdomdDataReader.InternalRead()
   at Microsoft.ReportingServices.XmlaClient.AdomdDataReader.Read()
   at Microsoft.ReportingServices.QueryDesigners.SapBw.Controls.QueryBuilderClientControl.QueryExec.ThreadExecution()
Edited by: huaxianz on Mar 30, 2011 6:12 AM

Hello Shashi,
derivation can only work, when Profit Center Group is not in the aggregation level. When you have more than one hierarchy on Profit Center (you are using in queries) I suggest that you create one hierarchy on Profit Center with Profit Center Group as foreign characteristics to be used in characteristic relationships. This is then a fixed hierarchy that defines what can be derived from Profit Center for all hierarchies you are using in queries.
Then you need no exit implementation. In addition, the hierarchy used in the characteristic relationship defines the admissible combinations in the cube. The hierarchies used in the query are only views on the cube data, in fact the foreign characteristics in hierarchies used in queries are treated as text nodes.
Regards,
Gregor

Hierarchy with External chars, how the external char automatically derives

Hi All,
We have Profit Center hierarchy. It has 'Profit Center Group' as a external char. We have account also in the aggregation level.
The hierarchy is on Profit Center with Profit Center Group as the parent nodes to the profit centers.
There are multiple hierarchies like legal, and management. We should be able to plan on different hierarchies properply, with Profit Center Group derived / created automatiically as per the hierarchy chosen in the variable.
The Profit Center and Group Profit Center are not in the rows and the account is. We tried to plan on the the account hierarchically with diaggreation turned on.
When Data posted, we wanted the Profti Center Group get derived as per the hierarchy chosen in the variable. Right now a blank Group get's posted in the database.
This worked with the Char Relation of type Hierarchy with Hierarchy value fixed. There is no way, we can define the varialbe hierarchy and also Exit Class is not able to read the source variables.
How to make this based on hier variable, or if Char Relationship definition on the InfoProvider in the Plan Modeler not all needed as the relation between Profit Center and Profti Center Group is already in the hierachy chosen in the variable for Profit Center.
Thanks in advance,
Best Regards,
- Shashi

Hello Shashi,
derivation can only work, when Profit Center Group is not in the aggregation level. When you have more than one hierarchy on Profit Center (you are using in queries) I suggest that you create one hierarchy on Profit Center with Profit Center Group as foreign characteristics to be used in characteristic relationships. This is then a fixed hierarchy that defines what can be derived from Profit Center for all hierarchies you are using in queries.
Then you need no exit implementation. In addition, the hierarchy used in the characteristic relationship defines the admissible combinations in the cube. The hierarchies used in the query are only views on the cube data, in fact the foreign characteristics in hierarchies used in queries are treated as text nodes.
Regards,
Gregor

Build Hierarchy with nodes with ABAP for custom Infoobject

Hi,
Need to build hierarchy with nodes with abap for custom infoobject.
Thanks

Hi,
Using information from:
http://help.sap.com/saphelp_nw04/helpdata/en/fa/e92637c2cbf357e10000009b38f936/content.htm
you can bulid flat file with hierarchy data and then load in into BW...
Krzys

Alternate hierarchy with only the Leaf nodes

Hi,
I have an account hierarchy with multiple levels in it. Now I want to make an alternative hierarchy with only the leaf nodes of that hierarchy with using the same nodes. Can anyone please explain the steps how to do it.

Unless you have any special requirements it will be straight forward, get an export of all the leaf members in an action script format and execute the INSERT action on your alternate hierarchy, you can create your alternate hierarchy with only the TOP node and insert the leaf members under it, in case you have thousands of them, you can split them by introducing dummy parents, also if you wish to maintain any local properties, please have them updated accordingly.

Vendor Hierarchy with Pricing from Info Record

Hi All,
We are currently exploring configuration options available to use a 'Vendor Hierarchy' for price determination during Purchase Order processing - R/3 46C
We also have a specific business requirement that requires our Vendor Hierarchy node prices be maintained in an Info Record (using a 'PB00' type condition type) rather than the 'LH01' and 'LH02' condition types used to maintain price conditions directly in the Vendor Hierarchy.
Does anyone know if it is possible to combine a Vendor Hierarchy with pricing that is sourced from Info Record rather than the standard 'LH01' and 'LH02' Vendor Hierarchy pricing conditions in the standard system?
Thanks,
Ravelle
References:
<a href="http://help.sap.com/saphelp_46c/helpdata/en/12/08464f470311d1894a0000e8323352/frameset.htm">Vendor Hierarchy</a>
<a href="http://help.sap.com/saphelp_46c/helpdata/en/12/084676470311d1894a0000e8323352/content.htm">Vendor Hierarchy - Purchase Order Pricing</a>

A solution has not been identified...query closed.

Problem in hierarchy with sap table

One problem regarding tree hierarchy with the sap bi table example zmaterial which is having 3 fields which should show as node and there data as sub node suggest me , how to do it I have look around the example but there are of simple node with string concept none of them is of sap table

Hi Sarfaraz,
Go throgh these example programs.
WDR_TEST_TREE
WDT_TREE_TABLE_BY_KEY
and also go throgh this blog.
Dynamic Tree in ABAP WebDynpro
also check this wiki
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/wdabap/organization%2bhierarchy%2bin%2btree%2bstructure%2bas%2bf4%2bhelp
Edited by: suman kumar chinnam on Oct 17, 2008 10:04 AM

BPS External Hierarchy with Postible Nodes

Similar Messages

Maybe you are looking for