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.

Similar Messages

  • Product Hierarchy - modifying the levels

    We are wanting to use the Product Hiearchy but are wanting to redefine the levels.  We want  4 levels, 3-6-6-3.  I've done some research and find that we are able to change the SAP standard of 3 levels to the 4 levels that we want.  I've also found general documentation on how to do that.  When I create my new Domains (ex: zprodh4 char3) and then try to change the main structure of PRODHS I get a pop up asking for an Access Key.  So, I'm either doing something wrong or changing the product hierarchy levels does not survive an upgrade?  Can anyone answer this for me.  If you think I'm doing something wrong can you please give me detailed instructions on how to assign the new domains to the existing structure. 
    Thank you!
    Tami
    Edited by: Tami Ayres on Nov 14, 2011 9:24 PM

    I have the access key and am modifying data element PRODH1.  I changed the domain to read ZPRODH1 which is my defined domain.  I saved it. 
    1.  When I go to activate it I get a list of dependent structures and tables that are to be adjusted.  Of course this makes me nervous but I'm assuming this is normal.
    2.  When I start to modify my next data element PRODH3, I am prompted for the access key.  I enter the same access key as I did for PRODH1 and there's an error telling me the access key is incorrect.  Do you have to have an access key for each element and then the structure that you are modifying?
    Sorry for all the questions but this modification is making me nervous and I just want it to be correct.
    Thank you,
    Tami

  • Product hierarchy V/76 - new level

    Hi,
    I want to create a new product hierarchy in V/76.
    I click on new entries and I can enter the product hierarchy and the description, but the "Level no." is greyes out so I cannot enter anything into that field. After saving every production hierarchy row has level 1 assigned, so how can I assign the level?
    Thanks
    Anne

    I only entered 1 character for first level instead of 5.

  • 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.

  • Product Hierarchy to COPA

    Hi All,
    We have defined and maintained product hierarchy as 4 levels with each level as 2 CHAR. This was done by appending the structure. Now in COPA,, how do we get this? Bcoz in COPA the characteristics are different. What changes needs to be done by COPA to pull this?
    rgds..Ameet

    hi
    you can define the characterstics which is similar to the appended structure.
    in SPRO - while defining the OPERATING CONCERN.
    hope this clears your issue.
    balajia

  • Related to product hierarchy level change

    Hi all,
    we got a requirement to change the product hierarchy level from 3 to 5.can any body guide us for this.
    thanks in advance,
    karna

    hi,
    in std sap u can have only three levels,but u can go upto 6 levels.
    follow this steps
    1.append the std prod hierarchy structure with adition of zzprod4 and zzprod5
    2.new data element can be created 0r use prodh field data element and attach it to new fields as per above.
    3.in customiising v/76 y should reorganise 18 chars amongst 5 levels.
    by doing this in material master u can see in drop down list with 5 levels.
    hope it helps.
    reward if so  !!!!!!

  • 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

  • Product Hierarchy level 2 code and description details

    Hi BW Experts,
    In our report we want to display Material wise 'Product Hierarchy level 3 code and level 2 description.
    Here, we have loaded material master hierarchy data to BW but we are not able to get the level 3 code and level 2 desc.
    In R/3 side we can see product hierarchy level 3 code and level 2 description using transaction code.
    Could some one help me how do we get these details.
    Thanks in advance.
    mahantesh

    Folks,
    Any solution?
    Laks

  • 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

  • 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.

  • 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

  • Transfer product catalog  hierarchy sales area level

    Hi all,
    We are creating a catalog in CRM  based on the product hierarchy (in CRM, Catalog->transfer->product hierarchy). The hierarchy is well copied into the catalog, but the products are not automatically added to the hierarchy. The problem is thatin our product master data,  the products are on "Sales Area" level (in the field dist.ch.dep. category), not in the "General" tab
    Please do you have any suggestions? Thanks

    modification of the program was made

  • Creating Product hierarchy

    Dear All
       We are using COPA in our organisation. The problem I am facing in the material codification.  The material coding has been done in such a way that not all the 18 characters has not been used for the finished goods.
    Some finished goods are having 12 Characters whereas some have 18 and some have 16. How can I create the product hierarchy in this scenario.
    Need kind advice in this regards
    Regards
    Vasantha

    Dear All,
       The product hierarchy is defined in such a way that i can create upto 3 levels. There is requirement for us to go for 5 or 6 level of reporting based on material codification. The standard structure of 5510 has to redifned as 55323. How to proceed further.
    Regards
    Vasantha

  • Pricing issue with Product hierarchy - Urgent

    Hello,
    I have an issue on pricing determination with product hierarchy.
    I created product hierarchy as following,
    level1 - A0001
    level2 - A0001B0001
    level3 - A0001B0001C0001
    Then, assigned A0001B0001C0001 to material D in material master.
    I created condition record with A0001B0001C0001(level 3),  the system found the condition sucessfully when I created a sales order with material D.
    However, I created condition record with A0001(level1) but the system didn't get the price when I created the sales order with material D.  Since A0001B0001C0001 belongs to A0001, the system is supposed to get the price from the condition record with A0001... 
    Could you please let me know how to fix it?

    Hi,
    Thanks a lot for your kind explanation.
    Here is the access sequence I defined.  I wonder if there is anyway I can define PRODH1, PRODH2, PRODH3 in access sequnce the same way with customer hierarchy so that the system can check higher level data.  If it's not allowed, I think I should define routine in requirement as you advised.  Thanks!
    *Accesses
    AcNo       Description
      1           Customer Hierarchy/Product Hiearchy
      2           Customer Hierarchy/Product Hiearchy
      3           Customer Hierarchy/Product Hiearchy
      4           Customer Hierarchy/Product Hiearchy
    Fields
      AcNo   Condition    Doc. field      field lable
         1      HIENR      HIEBO01     CustomerHierarchy 01
                 PRODH     PRODH       Product hierarchy
         2.     HIENR      HIEBO02     CustomerHierarchy 02
                 PRODH     PRODH       Product hierarchy
         3      HIENR      HIEBO03     CustomerHierarchy 03
                 PRODH     PRODH       Product hierarchy
         4       HIENR      HIEBO04     CustomerHierarchy 04
                 PRODH     PRODH       Product hierarchy
    I wonder if I can assign product hierachy fields, PRODH1, PRODH2, PRODH3 to access sequence like customer hierarchy so that the system can check higher level data to get the price...

  • Different product hierarchy in sales order and in service order

    Dear experts,
    In VA03, I notice that
    - under Line Item > Sales B, there is a field Product Hierarchy
    - under Line Item > Account assignment, there is a field Order. From here, it links to a service order. In the service order, I can see a field Product Hierarchy too.
    I would like to know if there is an implication when the field Product Hierarchy in sales order and in service order are different. Is it possible that this will cause an inconsistency?
    Usually these two fields have the same value, since the value in sales order is copied from service order. However, in my case, the product hierarchy is changed/updated in service order, but not in sales order.

    Hi,
    We have document pricing procedure maintained at two levels for Sales order or Billing type.
    The pricing procedure is determined based on SAles Area Customer pricing procedureDocument Pricing procedure+pricing procedure.
    Example :For Sales Document type the document pricing rpocedure will be A and for billing type 'B"
    Sales Area1A+Pricing procedure A
    Sales Area1B+Pricing procedure B
    Now A will be maintained in VOV8 and B will be maintained in VOFA.So two pricing procedures.
    Regards,

Maybe you are looking for

  • Shopping for a new mouse

    Whats your favorite and why? Thanks

  • Attached docs cause Mail to guit

    For about three days whenever I try to open an email with an attached document, or to send one with an attachment, Mail quits unexpectedly (does not just "hang up").

  • How can i Change the currency symbols for swiss francs?

    Hi, i use Numbers '09. How can i change the  currency symbol for swiss franks from SFr to CHF. Because the international ISO abbreviation is CHF and not SFr. Thanks, Bye

  • Background scheduling changing period values.

    hai abapers. i have on req ,previously we have on job.that is scheduled in background(on for specified time:23.04.2008 and time 12:00:00) but now i want to schedule this job in background for every day and send mail to concerned persons..here i want

  • K8t master 2 questions....

    Ok, soon I'm picking up a k8t master 2 and two opteron 240s with an Antec 550watt EPS12V PSU. But I have a question. Are the CPU heatsink mounting wholes compatible with p4 heatsinks? I'd like to pick up a pair of Swifttech MCX4000s, but need to be s