Hierarchy maintenance

Can someone tell me where or how the actual Node--> Object mapping happens for a hierarchy? I can see the hierarchy but not where each characteristic value is mapped.

Ok I guess what you meant to say was:
1) go to RSA1
2) find the object
3) right click and select "Change"
4) Select the "hierarchy" tab
5) Right click on the table /BI0/HOBJECT and select "Table Contents"
is that what you mean?
When I do that I have a normal table selection screen which is not very helpful. What I want is a hierarchical view of everything.
As I said though I also need to know where the node assignment are made and how one can change them if need be. For example Customer 123 is now part of the WEST hierarchy node but should be part of the EAST hierarchy node. How can i do this reassignment?

Similar Messages

How to create the Product Hierarchy maintenance ..?

Hi All,
How to create the Product Hierarchy maintenance (IN APO System), I know manual creation, going to the transaction : /n/sapapo/relhshow , how to create programmatically, is there any Function module?
Pls let me know
Puppy.

Hi Puppy,
Please check whether the below BAPI can be used by you.
T-code: BAPI
Object name: ProductAllocationAPO
Obj type:- BUS11305
Regards
R. Senthil Mareeswaran.

Purpose of u201CMaintain Levelu201D and u201CText Nodeu201D in Hierarchy Maintenance(RSH1)?

Hi,
1.
In RSH1, in the hierarchy maintenance screen, I played around in the u201CMaintain Levelu201D screen but could not get its purpose. What is it used for?
2.
I have also created a hierarchy and inserted characteristic nodes but what is the u201CText Nodesu201D used for and what is the difference between that and the u201Ccharacteristic nodesu201D?
e.g.
Under the Characteristic Nodes u201CRegionu201D, I created a text node XXX 1.
What is the significance from the point of view of reporting and how will XXX 1 as a Leave under u201CRegionu201D get data when the entire hierarchy is dropped in a report?
Thanks

What are the report-relevant settings in the hierarchy maintenance?

What are the report-relevant settings in the hierarchy maintenance?

Hi,
See these links.
http://help.sap.com/saphelp_nw04/helpdata/en/0e/fd4e3c97f6bb3ee10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/0e/fd4e3c97f6bb3ee10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/0e/fd4e3c97f6bb3ee10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/0e/fd4e3c97f6bb3ee10000000a114084/frameset.htm
assign points if this helps.
Thanks.....................
vasu...................

Tcode for Hierarchy maintenance

Hi experts,
My finally user has needed a custom tcode for Hierarchy maintenance.
This tcode will be usefull to open a specific Hierarchy directly, without pass to RSA1 tcode.
Another solution could also go well, but user will has to necessarily see only the maintenance screen of his hierarchy.
Any idea please?
thanks for your tips.

Hi Claudia,
Tcode RSHIER is used for Hierarchy maintenance w/o AdmWB which uses Progarm RSHIERARCHY .
Surly it will help to you.
Thanks
Abha

** DRM - Hierarchy maintenance

Hello Friends,
We are planning to use DRM (Data Relationship Management) for our hierarchy setup and Maintenance. One of the main usage of this would be to have alternate hierarchy populate for Hyperion planning/Essbase with version controls etc...
Like to know couple of things:
- Any CONS (Or) things that we can't do that we should be aware?
- Ideal Deployment? /* We are thinking to have DRM on Win2003 Server. Not sure Web Logic be optimal for having has a Web Server? */
Any feedbacks are appreciated.
Thank you!!

DRM is typically used to manage this type of environment. The only thing I would suggest is that you read up on the difference between global and local properties. When building alternate hierarchies, you want to share property values (or avoid populating property values twice) between hierarchies. Beisdes that, DRM has worked well for us here at the bank.
We also use Windows 2003.
D

Avoid "drag and drop" in hierarchy maintenance, why?

I have read in several places that drag and drop maintenance should be avoided, what is the reason?
Is it because of the default application of
- first period of consolidation?
- period of divestiture?
Or is there something else?

The reason for avoiding drag-and-drop for cons unit/group hierarchy changes is because of the reporting logic.
The hierarchy is time dependent. The reporting logic reads the hierarchy from the latest period of the query range and also considers whether or not the cons unit is divested in the cons group for that period.Thus, data may be inadvertently excluded or included with drag-and-drop when it is not intended. Creating the cons unit in the new position and leaving it in the old position with divestiture period in the cons group master data ensure the correct reported results for each cons group.

Planning Hierarchy Maintenance with Gaps

Dear Experts,
Iam using flexible planning for sales plan. I am using flexible planning. I wanted to create planning hierarchy with Gaps. I mean at some levels I will not be having any data to enter. For eg. My first level is country and second level is region. I will not have region for some countries. So when I maintain the planning hierarchy I will not have any value at the region level for a country.
How can I achieve this. When I dont enter any value, system throws the error message, enter the values without gap.
Thanks in Advance
Prathib

HI There,
SAP does not allow maintaining Plng Hier with gaps coz that breaks the planning chain. We had a similar situation & we made up "distinct" dummy values at that level & plugged them in.
The values need to be distinct for each level/segment/CVC (unique), else it'll mess up the planning. The aggregation/dis-aggregation would go for a toss, if the system finds a common value at one given level.
Bottom line, the Planning Hierarchy structure cannot converge at any intermediate level with a common value, it has to be a pyramid structure.
Good Luck

Profit Center Hierarchy Maintenance

Hello
As part of a project we need to transfer an existing Profit Center Hierarchy (including all Profit Center groups and Profit Centers) to a different Controlling Area. The hierarchy in question contains over 2500 Profit Centers and we would like to avoid doing this manually, to reduce both time and margin for error.
We know that we can use KCH1 to copy the Profit Center Groups to the new Controlling Area, using the original Controlling Area as a reference, but this does not copy across the Profit Centers master data.
Master Data transaction KE55, does not allow Controlling Area to be amended.
Questions:
- Is there a way to transfer/copy the complete hierarchy (including Profit Centers) to a different Controlling Area?
If we use KCH1 - how can we copy/reassign the Profit Centers to the new Controlling Area?
Any ideas for this would be greatly appreciated
Thanks

Hi
It can not be fully the way you like...
You can go to KCH4 and select your Prof Ctr Hie.. Click on Extras > Export... This would create a text file...
Create Std Hie with same name in new contr area and SAVE.. Then click on Extras > Import.... This would create the Hie Structure and also the profit center names under it.. But, as such the Prof Ctrs wont be created...
You need to create them again using KE51... Ideal way would be to create it using reference of the same profit center (LSMW)
Regards
Ajay M

Status Tracking system Hierarchy Maintenance.

In BPS status tracking system, is it mandatory to have a topmost node of the organisational Structure node to be text node?
for example : If I have a structure like Head Office-> Regional Sales Manager--> Area Sales Manager, then do I need to have a text node above Head office with some heading?

Santosh ,
its necessary that you have it as text node.
but not very sure why you would want it to be other than text.
Sai Vishnubhatla

MDM hierarchy Maintenance...

Hi All,
I'm new to MDM 9.3.1. i have successfully installed & able to login mdm server & client.
now i need how reflect hierarchies between Essbase & MDM.
pls help on this.
Thanks

To load the hierarchies you need to :-
Create Property Category to hold Essbase Properties in DRM.
Create Properties to hold each Essbase node attribute e.g Properties for Consolidation Operator, Data Storage, Time Balance, Two Pass etc (assuming you want to hold these details in DRM).
Once you have created the properties you need to extract the Essbase hierarchies using Outline Extractor or similar.
Create DRM import to load the extracted file using the Import wizard.
Load the dimensions into DRM.
You'll then have the dimensions in DRM. Note that this is a very simple explanation - you may want to enhance the way the attributes appear within DRM etc (e.g instead of holding the Consolidation operator as a + hold it as 'Addition') which would include further manipulation but I'd do this as a first attempt just to begin to get used to DRM functionality.

Flat File Hierarchy Datasources

We are creating several flat file hierarchy datasources. The datasources will be maintained in an external database.
I am familiar with the creation of flat file datasources for master and transactional data, but don't have good documentation for how the external flat file hierarchy is to be formatted.
We have reviewed the 2004 Netweaver Document "How to Download Hierarchies in BW" and have used the program referenced there, Z_SAP_HIERARCHY_DOWNLOAD, to download our hierarchies to then test the upload.
However, this has not worked.
Does anyone have the record layout that the flat file must be in to upload a simple 2-level hierarchy (for example groupings of 0vendor)?
Thanks, Doug

I think the URL you mention is http://help.sap.com/saphelp_nw04/helpdata/en/fa/e92637c2cbf357e10000009b38f936/content.htm.
This contains the record layout instructions as follows.
5. Maintaining the hierarchy:
Choose Hierarchy Maintenance, and specify a technical name and a description of the hierarchy.
PSA Transfer Method: You have the option here to set the Remove Leaf Value and Node InfoObjects indicator. As a result, characteristic values are not transferred into the hierarchy fields NODENAME, LEAFFROM and LEAFTO as is normally the case, but in their own transfer structure fields. This option allows you to load characteristic values having a length greater than 32 characters.
Characteristic values with a length > 32 can be loaded into the PSA, but they cannot be updated in characteristics that have a length >32.
The node names for pure text nodes remain restricted to 32 characters in the hierarchy (0HIER_NODE characteristic).
The system automatically generates a table with the following hierarchy format (for sorted hierarchies without removed leaf values and node InfoObjects):
Description
Field Name
Length
Type
Node ID
NODEID
8
NUMC
InfoObject name
INFOOBJECT
30
CHAR
Node name
NODENAME
32
CHAR
Catalog ID
LINK
1
CHAR
Parent node
PARENTID
8
NUMC
First subnode
CHILDID
8
NUMC
Next adjacent node
NEXTID
8
NUMC
Language key
LANGU
1
CHAR
Description - short
TXTSH
20
CHAR
Description - medium
TXTMD
40
CHAR
Description- long
TXTLG
60
CHAR

Error in Hierarchy activation

Hello Experts
I re loaded hierachy for 0material, infopackage failed with error "Error arose when activating the hierarchy; Hierarchy not active
I tried activating using FM RRHI_HIERARCHY_ACTIVATE got error "There is no modified version for this hierarchy"
I am able to see M and A versions of hierachy in hierarchy maintenance.
but when i mannually try to activate hierarchy i get short dump with message
Short text
    Message type " " is unknown.
What happened?
    Error in the ABAP Application Program
    The current ABAP program "CL_RSSH_MESSAGE_HANDLER=======CP" had to be
     terminated because it has
    come across a statement that unfortunately cannot be executed.
Please help.
Regards
Sudeep

Hi sudep,
                 did u done the attribute change run for hierarchy after loading the hierarchy?.....
try the below steps
1) Load Hierarchy
2) Save Hierarchy
3) Attribute CHange Run on the InfoObject.
Run these in the same sequence and see if it solves the problem.
Make sure that you have this Checkbox on:
1) In Infopackage, in tab Hierarchy Selection, there is a small checkbox for 'Flag for Activation'. Make sure its ON.
2) In Save Hierarchy Process Type, the same check box should be ON.
Harikrishna N

Display of Hierarchy Nodes as Medium Text in Web Report

Hello everyone,
Does anybody know how to display the hierarchy nodes as medium text instead of short text (default) in web report?
I know it is possible to change the display setting directly (by right clicking on hierarchy node > properties) from the web report.
However, I would love to know if there is any other way to change the settings such as through Query designer or Hierarchy maintenance in SAP GUI so that users do not need to change the display settings every time they view the web report.
Your help is kindly appreciated.

Thank you Shabar for you quick reply.
What if a Hierarchy is created under an InfoObject? How can I change the Text view of each name of the Hierarchy nodes?
In Query Designer, I tried to change the Text View to Long but it only affects the text of the InfoObject but not the Hierarchy nodes.
I tried the 2nd suggestion too. I only can find the BEx description for the InfoObject but not the Hierarchy nodes.
It would be great if anyone could tell me how to do so.
Thanks in advance.

Hierarchy format in Flat file

Hi gurus,
      please tellme the Hierarchy format in Flat file.
           ThanQ.
   Regards,
   Ramesh.

Hi
1.Defining the source system from which you want to load data:
Create For a flat file, choose: File System, Manual Metadata; Data via File Interface.
2.Defining the InfoSource for which you want to load data:
Create Application Component.
Create InfoSource , Direct Update
Choose an InfoObject from the proposal list, and specify a name and a description.
3.Assigning the source system to the InfoSource
Assign Source System. You are taken automatically to the transfer structure maintenance.
The system automatically generates DataSources for the three different data types to which you can load data.
Attributes, Texts,Hierarchies (if the InfoObject has access to hierarchies)
The system automatically generates the transfer structure, the transfer rules, and the communication structure (for attributes and texts).
4.      Maintaining the transfer structure / transfer rules
Choose the DataSource to be able to upload hierarchies.
Idoc transfer method: The system automatically generates a proposal for the DataSource and the transfer structure. This consists of an entry for the InfoObject, for which hierarchies are loaded. With this transfer method, during loading, the structure is converted to the structure of the PSA, which affects performance.
PSA transfer method: The transfer methods and the communication structure are also generated here.
5.      Maintaining the hierarchy:
Choose Hierarchy Maintenance, and specify a technical name and a description of the hierarchy.
PSA Transfer Method: You have the option here to set the Remove Leaf Value and Node InfoObjects indicator. As a result, characteristic values are not transferred into the hierarchy fields NODENAME, LEAFFROM and LEAFTO as is normally the case, but in their own transfer structure fields. This option allows you to load characteristic values having a length greater than 32 characters.
Characteristic values with a length > 32 can be loaded into the PSA, but they cannot be updated in characteristics that have a length >32.
The node names for pure text nodes remain restricted to 32 characters in the hierarchy (0HIER_NODE characteristic).
The system automatically generates a table with the following hierarchy format (for sorted hierarchies without removed leaf values and node InfoObjects):
The system transfers the settings for the intervals and for time-dependency from the InfoObject maintenance. Depending on which settings you have defined in the InfoObject maintenance, further table fields can be generated from the system.
The valid from and valid to field is filled if you select Total Hierarchy Time-dependent in the InfoObject maintenance. The time-dependent indicator is activated if you select the Hierarchy Nodes Time-dependent option in the InfoObject maintenance.
6.      Save your entries.
Depending on which settings you defined in the InfoObject maintenance, additional fields can be generated from the system. Also note the detailed description for Structure of a Flat Hierarchy File for Loading via an IDoc and for Structure of a Flat Hierarchy File for Loading via a PSA.
Further Steps:
Maintaining InfoPackages
Result
You have uploaded the hierarchy data for the corresponding characteristic.

Hierarchy maintenance

Similar Messages

Maybe you are looking for