Max number of level in Account/Product Hierarchy

While creating an Account hierarchy & Customer hierarchy. Precisely how many levels are possible to maintain ?

Hi,
For product hierarchy you can have a maximum of nine levels and hierarchy number can have a maximum of 18digits.
For customer hierarchy, a maximum of 26 levels of hierarchy is permisible in standard SAP.
Hope this helps you.
Regards.

Similar Messages

Account Hierarchy / Max number of levels

Hello to the community,
I would like to know what is the max number of levels in an account hierachy ?
Thanks for your help.

Hello,
you can use up to 30 levels in the hierarchy.
That's really enough, your accountants have already lost the overview after 10 levels:-)
Ciao,
David

Max number of levels in territory hierachy

Hello,
I would like to know if there's a max number of levels in territory hierarchy ?
Thanks for your help.

Hello,
you can use up to 30 levels in the hierarchy.
That's really enough, your accountants have already lost the overview after 10 levels:-)
Ciao,
David

Max Number of levels in ECCS FS Item heirarchy

Is there any limit on the maximum number of levels in EC-CS FS Item heirarchy or Consolidation Group heirarchy ? Is there any limit on the maximum number of sub-group level ?

Hello,
you can use up to 30 levels in the hierarchy.
That's really enough, your accountants have already lost the overview after 10 levels:-)
Ciao,
David

HT204053 Hello l bought second hand iphone 4 and l cant Log in lclood because System says that l reach max number of free Apple accounts so how can l erase old accounts that l dont know ???

Where l have to write msg or do to solve my ıd problem l want to use l cloud but there are multiple accounts on my ıphone from old user l need to erase old accounts to use mine pls help me

You can't erase or delete iCloud accounts, you can only stop using them. If the previous owner already created the maximum number of iCloud accounts on your phone, all you can do is either re-use one of the accounts previously created, or create a new account to use on another iOS device or Mac (running OS X 10.7.2 or later), if you have one.

Product hierarchy level in TPM Pricing condition records

Hi all,
we're setting up TPM scenarios in CRM7.0.
A question arosen about the level of the product hierarchy we need to create pricing records.
We have a 5 level product hierarchy structure and we're using the CRM feature to spread the product category at the lates level while creating trade promotion. In example if the user put in the product category tab a level 1 category the system spread down to the 10 level 5 underneath.
My question is: shall i generate pricing records at that level (lev5) or can i create the pricing records at higher level and keep the campaign dtermination one at the lowest?
Appreciate any reply
Regards

Hi Carmine,
It's not mandatory to create conditions at the lowest level, but my recommendation is to keep a match between the level you allow users to plan their promotion and the level of the condition records.
However depending on the scenarios, it may be valid to do otherwise. Some examples:
- A user assign a Level1 Category, and it's exploded into 5 lower categories. Then he creates a trade spend exception for 1 of the categories, the conditions should have (at least) the same level in order to create this exception.
- A user assign a Level1 Category, and it's exploded into 5 lower categories. The user wants to create only 1 condition at a higher level, then yes it can make sense to have condition with the higher level.
An option to allows both would be to have different condition generation type (one for High Level planning and one for lower level).
Some additional thoughts:
The feature that "explode" the high level category into lower categories, was developed for customers that wanted to restrict their users in planning at a lower level. It also helps to ensure a KAM does not create a condition for a whole Brand, but only to the level he's allowed.
The system is build to manage a high number of conditions.
Best regards,
Guillaume

Level in product hierarchy ??

Hi
Some body can explain me about the levelin product hierarchy ??
Diefinition of level ?
Purpose of level??
Thanks

Product Hierarchy:
Product hierarchies are the domain of materials management. A product hierarchy is assigned to the material master record. This hierarchy is broken down into specific levels, each level containing its own characteristics. A product hierarchy is recorded by the sequence of digits within a hierarchy number. This hierarchy number may have a maximum of 18 digits with a maximum of 9 levels. The custom Product hierarchies can be maintained in V/76.
Product Hierarchy Number of chars at Various level
In the standard system, the product hierarchy consists of up to 3 levels. The first and second levels have 5 digits and the third level has 8. The maximum number of digits is 18 and the maximum number of levels is 9.
You can define hierarchy nodes at the individual levels of the product hierarchy.
The product hierarchy can be structured via DDIC structure PRODHS. In the standard system, a product hierarchy can be created with up to three levels. The individual levels can contain the following number of digits:
Level number of allowed digits
1 5
2 5
3 8
This can be changed as of Release 3.0, where it is possible to extend the maximum number of levels to 9.
If you want to change the standard setting of PRODHS, e.g. you want to change the number of levels, proceed as follows:
1. Create an appropriate domain in the Data Dictionary (type CHAR with the required length).
2. Assign these domains to the standard data elements PRODH1, PRODH2, ..., PRODH9.
Please note that you should use these standard data elements.
3. Change the structure PRODHS by creating or deleting fields with reference to the data elements.
Choose ZZPRODHN as field name, where n is the position of the field in the structure PRODHS.
You want to change the structure of the product hierarchy from 5/5/8 digits to 5/5/5/3. Proceed as follows:
Create the following domains:
ZPRODH3 with length 5, category CHAR,
ZPRODH4 with length 3, category CHAR,
Change structure PRODHS:
Structure PRODHS in the standard system:
Structure Fields Data element Category Length
PRODHS ->
PRODH1 PRODH1 CHAR 5
PRODH2 PRODH2 CHAR 5
PRODH3 PRODH3 CHAR 8
Changes according to example:
Structure Fields Data element Category Length
PRODHS ->
PRODH1 PRODH1 CHAR 5
PRODH2 PRODH2 CHAR 5
PRODH3 PRODH3 CHAR 5
ZZPRODH4 PRODH4 CHAR 3
please take help of ABAPER in extending the levels of Product hierarchy
Configure for Product hierarchy at
SPRO -> IMG -> Logistics - General -> Material Master -> Settings for Key Fields -> Data Relevant to Sales and Distribution -> Define Product Hierarchies

Product Hierarchy Levels in the material Master.

Plz let me know the Levels to which product hierarchy can be maintained for a Finished good in its Material Master.
What I know it is 9 and is limited to 18 characters.
The T- code for it is v/76, and is maintained thru it, but while I am trying to maintain 4th level it is automatically taking 3rd Level. please point out the mistake which i must be doing.

Hi
As per standard SAP allowed up to 3 steps only
Here i am furnishing small example
1 step allowed 5 digits - 00001- Electronics
2 Step allowed 5 digits- 00001 - Home Appliances
3 step allowed 8 digits- 00000001- Steam iron
The above hierarchy can be assigned in material master as 000010000100000001

CO-PA: product hierarchy predefined from best practice

Hi guys,
unfortunately I have as basis a best practice system, where product hierarchy with 3 levels is already defined in CO-PA:
PAPH1     ProdHier01-1     ProdH01-1     CHAR     5     MVKE     PAPH1
PAPH2     ProdHier01-2     ProdH01-2     CHAR     10     MVKE     PAPH2
PAPH3     ProdHier01-3     ProdH01-3     CHAR     18     MVKE     PAPH3
PRODH     Prod.hierarchy     Prod.hier.     CHAR     18     MVKE     PRODH
Those ones are already assigned to a best practice operating concern:
10UK     Best Practices
1. we have 7 levels in our product hierarchy
2. I need to read it from mara and not mvke
When trying to ad product hierarchy as characteristic in KEA5 in our new operating concern, I gut the message below.
This data element is used in tons of tables and the whole precdure looks risky + after transport I might have issues again?
Creating ww* characteristics for product hierarchy is not an option, since then I would need to maintain the whole product hiearchy as characteristc values again (like before release 4.5) and this is far more than 1000 entries and is double maintenance after go live.
Deleting the best practice operating concern is also difficult, since there are several clients where customizing still sits for 10UK.
Anybody experience? What did you do?
regards
Bjoern
Here is the text from KEA5 when trying to ad mara fields (since date elment lenghts is different due to more levels):
Product hierarchy field PAPH1 cannot be adapted to the new structure
Message no. KE691
Diagnosis
The definition of the product hierarchy has changed (structure PRODHS). The hierarchy field generated in CO-PA, PAPH1 cannot be adapted to the new definition, because it is already being used in structures or tables.
System Response
The field PAPH1 does not appear in the list of fields that can be selected.
It can no longer be used as a characteristic.
Procedure
If you still want to define hierarchy field PAPH1 as a characteristic, proceed as follows:
1. Display the where-used list for data element RKEG_PAPH1 in database fields using transaction SE12. For hierarchy field PAPH1 to be adapted, a data conversion must be carried out for all the tables listed!
2. First change the number of characters in the domain RKEG_PAPH1 to match the new definition of the product hierarchy, following the example below. You can do this using transaction SE11.
Structure PRODHS     Domain
Field    Length      name       Number of characters
PRODH1     3         RKEG_PAPH1      3
PRODH2     2         RKEG_PAPH2      5
PRODH3     5         RKEG_PAPH3     10
PRODH4     8         RKEG_PAPH4     18

Just as Info,
I needed to go for deletion of those characteristics - quite some work, like:
1. delete all where-used entries for the characteristics in ALL CLIENTS of this system (important: e.g. planning layout - recommended to change and not simply delete, because the change can be transported)
2. when then trying to delete characteristics (with "unlock" in KEA0 > value fields) - tons of tables and strucutres popped up, where this data element is still needed - follow note 353257
3. generate best practice operating concern new (10UK in our case)
4. create PAPH1 etc. new from table MARA (not mvke in our case - depends)
all good - hopefully no issues after transport - we will see.

Customer Hierarchy and product Hierarchy

Hi friends what is customer Hierarchy and what is product hierarchy?
please explain step by step with examples.
mail id: [email protected]
Thanx.

Hi Sirivas,
CUSTOMER HIERARCHY:
Customer hierarchies are available in Sales and Distribution, so that you can create flexible hierarchies to reflect the structure of customer organizations. If your customer base includes multi-level buying groups, cooperatives, or chains of retail outlets, for example, you can create hierarchies to reflect the structure of these groups. Use customer hierarchies during sales order processing and billing for determining pricing and running statistics.
 A customer hierarchy consists of nodes.
 To create a customer hierarchy:
1. Create master records for each node.
2. Assign the nodes to each other.
3. Assign the customer master records to the relevant nodes.
 Hierarchy nodes are only valid for a certain period of time. They may also be moved. If a node is moved, the system automatically reassigns all related nodes and customer master records.
With customer hierarchies, you can assign price or rebate agreements to a higher level node. The agreements are then valid for customers at all subordinate levels to this node. You can create pricing condition records for each node indicated as relevant for pricing. If one or more nodes in the hierarchy path of a sales order contain pricing information, the system takes them into account automatically during pricing.
'How to check'
All the customizing is in SD/Master Data/Business Partner/Customers/Customers hierarchy
All the customizing is in SD/Master Data/Business Partner/Customers/Customers hierarchy
1) Define hierarchy type: just put and ID and a name to the new hierarchy.
2) Set partner determination: if you want to user the hierarchy in price determination, then, in the orders, at the header level, you have to have a Partner Procedure with a partner function for each level. In the partner procedure, in each partner function you must indicate the source partner function. With this information, in the order, you obtain the business partner for each partner function.
3) Assign account groups: you indicate which accounts groups are allowed for being part or your hierarchy.
4) Assign sales areas: simple you indicate which sales areas are allowed in your hierarchy. (Here you can customize common sales areas, just for not having to build de hierarchy in all the different sales areas).
5) Assigning hierarchy type for pricing: you indicate which classes of documents uses hierarchy in pricing determination.
It is possible to maintain so called customer hierarchies. This might be useful when for example you create a condition discount for a customer that is part of such a hierarchy structure. All subnodes in the hierarchy below that customer, will thus receive the same discount.
Customer hierarchy setup, firstly decide the hierarchy type to be used.
The standard is type A.
You can also assign a partner function to the customer so that the higher level customer in the hierarchy is copied into a sales order as a partner function - but you don't need that right?
Next assign your customer account group to the hierarchy type. And enter the combinations that will be allowed for creating the hierarchy.
You want to assign a ship-to to a payer. So enter the ship to account group and enter the payer account group as the higher level.
You must also make an entry for permitted sales area assignments. So if you want to a hierarchy for customers in the same sales area then enter the sales area and enter the same one as the higher level sales area.
All these settings can be found in the IMG. Under SD - master data - business partners - customers - customer hierarchy
You use for example customer hierarchy when you have an company like Unilever and you agree both on a discount. Unilever does have different locations / businesses and you have to maintain the discount for all customers. If you use a customer hierarchy you can maintain the discount for the partner in the top of the hierarchy and in this way it will be valid for all customers in the hierarchy.
Product Hierarchy:
The product hierarchy on the Basic Data screen is used to depict the competitive materials of competitor 1 in relation to those of competitor 2. Here, your own company and its materials are also regarded as a competitor and as competitive materials respectively. You can use this representation as a basis for market analyses.
Normally we enter competitive materials using material type WETT. When entering your own materials as competitive materials, you can, however, display the product hierarchy on the Basic Data screen for other material types too.
Requirement type determination is based on the "Origin of requirement type in requirement type determination"
In this field you can select an alternative search strategy (source):
Source 0 = Material master strategy, then item category and MRP type
Source 1 = Item type and MRP type strategy
Source 2 = Item type and MRP type strategy (as for source 1) with additional check of the allowed requirements type
e.g. If you set value "0" system will first strategy group in material master based on that it will determine requirement type and no value found then it will determine requirement type based on item category and MRP type.
Above settings can be found at SD --> Basic Functions --> Availability Check and transfer of requirement --> Transfer of Requirement --> Determination of Requirement type using Transaction
For make to order std strategy group 20 is used to which req type KE is assigned.
Check
Check in Tcode OVZH, what requirement class is assigned to your requirement type
Check in Tcode OVZG, what value is assigned to field "Consumption" in requirement class because that determines consumption posting.
The product hierarchy is used to group materials by combining different features. It is used for analyses and pricing. A product hierarchy can consist of up to Eighteen characters. Its features can be combined in various ways.
Example: A dishwasher can be described by product hierarchy 000010000200000002. This series of characters states that dishwashers belong to the category electrical appliances (series of characters 00001, position 1-5), and also to wet appliances (series of characters 00002, position 6-10) and, finally, to dishwashers (series of characters 00000002, position 11-18).
One can maintain the product hierarchy via transaction "OVSV" and "V/76.
Path = IMG-Logistics General-Material master-Setting for Key fields-Data relevant to SD-Define Product hierarchy.
The product hierarchy is maintained in the Basic Data view of the material master record, and is used for evaluation as well as price determination in materials management.
The standard SAP allows only 3 levels, but you can go up to 6 levels, for additional 3 levels u will have to take abapper help and add 3 more fields and corresponding data element into structure. So that in material master drop down you will see 6 levels.
The transaction which will be useful to change product hierarchies for material master will be V/76.
Yes, You can print the levels of the product hierarchy through a report.
Use the view SE16 - V_T179 (Table Name) to display Product hierarchy with level numbers.
Field Name is PRODH
Please Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula

Searching for products via Product Hierarchy ID in CRM Webclient 2007

Hello,
When creating a sales order in CRM Webclient 2007 I would like to be able to search for products by using the Product Hierarchy ID. When clicking the search help for product in the order entry screen in the webclient UI, I get a pop-up with the available search criteria. I select Product Hierarchy ID and click on Input Help. A new pop-up is displayed with the three Hierarchy ID:s:
R3MATCLASS Material Group
R3PRODSTYP Product Subtype
R3PRODHIER Product Hierarchy
I select R3PRODHIER. When hitting the search button, I get all materials which have Hierarchy ID R3PRODHIER assigned as a product category in the material master data. I can however not search for materials which belong to a certain hierarchy node in the product hierarchy.
In transaction VA01 in ECC it is possible to drill down through the three levels of the product hierarchy to find the desired material. Is the same type of searching possible in CRM?
Any help much appreciated.
Kind regards,
Johan Wigert

Hi Johan
I want to know if finally you have found the way to deal this problem.
Thank you very much,
Yannuchi

Stock overview report on basis of product hierarchy ?

Is there an SAP standard report for displaying materials(product hierarchy wise) on the basis of product hierarchy or do i have to create a customer report for it. IF yes, then how do i go on creating it.. i.e how will i be showing the materials(in a hierarchical display, product hierarchy wise ?
Hope you have comprehended it ?
Thanks,
Shehryar Dahar

Hello Kirit,
the scenario is sumthing like this, the SAP transaction for stock overview (MMBE) displays the report per material. I want a report in which , if i give in the Product Hierarchy, it should display all the materials in diff levels in the product hierarchy. For example, if we choose 'Product Hierarchy' as a display level, it should display all the materrals in the hierarchy levels..!
I have been that the Stock Overview Report(MMBE) displays only one material, no matter what 'display level' you give in the selection. Does this mean, that i would have to develop a new report for this ?
Waiting for the replies.
Shehryar Dahar

Default Account Assignment- product hierarchy

We have a requirement when any transaction posting to a write off G/L account to automatically include Product Hierarchy. I have used OKB9 before for C/C and P/C but not Product Hierarchy. Is this possible, if so, how?
Thank you!

AMS,
First make sure that the account is set to post to COPA. Make an entry in OKB9 for this account and click the Profitability segment indicator. Also, assign the account to a PA transfer structure (KEI2) to map the account to a COPA value field.
As far as assigning the product hierarchy to COPA characteristics, you have several options depending on whether you want the whole hierarchy assigned to one characteristic or if you want to split each level into seperate characteristics. Also, the hierarchy can be maintained in the material master in the general view (MARA) or the sales org view (MVKE), Let's assume you want to assign the whole hierarchy into a single field using the general data view assignment. To do this just create a table lookup step in KEDR. Select table MARA as the source. Field MATNR will automatically be match to your COPA product field (ARTNR). In the assignment section select field PRDHA from table MARA and enter the COPA characteristic field you want to store this value in. If you haven't yet assigned the product hierarchy characteristic to your operating concern you will need to do that first.
thanks,

Product Hierarchy upto 6 levels

Dear All,
In SPRO Transaction, I am checking the Material Hierarchy, there I am able to create the Hierarchy only upto 3 Levels. But my company requirement is that Hierarchy can easily go upto 6 or 7 Levels. So please suggest solutions how can I maintain this?
Regards,
Vishal

In Standard the product hierarchy consists of 3 levels. The first and second level have 5 characters and the third level has 8 characters.
Component Component Type Dtype Length
PRODH1 PRODH1 CHAR 5
PRODH2 PRODH2 CHAR 5
PRODH3 PRODH3 CHAR 8
This structure can be modified according to the documentation (IMG: 'Logistics General -> Material Master -> Settings for Key Fields -> Data Relevant to Sales and Distribution -> Define Product Hierarchies: Maintain Product Hierarchy Structure').
The maximum number of characters is 18 and the maximum number of levels is 9.

How to Restrict the node level in account hierarchy

Hi experts,
I want to restrict the node level in account hierarchy. I attached one example. in that if i click 6000 node again it want to show error message. for one parent node i want to create only two child node. Further if i create means it want to show error msgs and not allow to create the node..
Regards,
gopi

Hi ,
The component is bp_hier, and method is onnew_node.
IF lv_tree->is_locked( ) = abap_false.
     lv_tree->lock( ).
   ENDIF.
   CHECK lv_tree->is_locked( ) = abap_true.
   lv_index = typed_context->accounthierarchy->selected_index.
   lv_tree_node = typed_context->accounthierarchy->get_node_by_index( lv_index ).
*key = lv_tree_node->node_key.
CALL METHOD lv_api->get_node_parent
     EXPORTING
       iv_node_key        = key
     IMPORTING
       ev_parent_node_key = lv_paent_key
*      ev_tree_guid       =
*   lv_parent = lv_tree_node->parent_entity.
*    typed_context->accounthierarchy->parent_entity.
CALL METHOD lv_tree_node->get_children
   receiving
     rt_children = rt_child.
   CHECK lv_tree_node IS BOUND.
   lv_tree_node->is_leaf = abap_false.
   TRY.
       lv_proxy_node ?= lv_tree_node.
       TRY.
           lv_object ?= lv_proxy_node->bo.
         CATCH cx_sy_move_cast_error.
           lv_mixed_node ?= lv_proxy_node->bo.
           lv_object ?= lv_mixed_node->if_bsp_wd_ext_property_access~get_model_node( ).
       ENDTRY.
       lv_object_name = lv_object->get_name( ).
       IF lv_object_name = 'BuilHierarchyNode'.
         lv_relation_name = 'BuilHNodeRel'.
       ELSEIF lv_object_name = 'BuilHierarchyHeader'.
         lv_relation_name = 'BuilHeaderNodeRel'.
       ELSE.
         RETURN.
       ENDIF.
       lv_tree_node->get_children( ).
       lv_object = lv_object->create_related_entity( lv_relation_name ).
       lv_child_node = lv_proxy_node->node_factory->get_proxy(
           iv_bo = lv_object
           iv_proxy_type = 'CL_BP_HIER_HIERARCHYTREEV_CN05'
           iv_parent_proxy = lv_tree_node ).
       lv_tree_node->expand_node( ).
       typed_context->accounthierarchy->refresh( ).
       typed_context->accounthierarchy->deselect_all( ).
       lv_child_node->selected = abap_true.
       lv_child_node->is_leaf = abap_true.
*accounthierarchy
*      selectedhierarchynode
       lv_col_wrap = typed_context->selectedhierarchynode->get_collection_wrapper( ).
       lv_col_wrap->clear( ).
This is the code.
i wrote . but its not getting.

Max number of level in Account/Product Hierarchy

Similar Messages

Maybe you are looking for