PRODH & CO-PA Product Hierarchy

In our project , we had a three level product hierarchy structure with length of the each level being 5,5 and 8 respectively . Based on this, the characteristics fields in COPA were defined using the standard characteristics PAPH1 ,PAPH2 and PAPH3 . When doing this in CO-PA , SAP created domains RKEG_PAPH1 ,2 and 3 with similar length as the levels in structure PRODHS.
After this was completed , the product hierarchy structure has been changed in PRODHS to four levels with length as 4,4,4,4 respectively. As a result of that the domains RKEG_PAPH1 , 2 and 3 are not matching with the new structure and the PAPH1 to 3 characteristics in COPA have been made unusable.
To fix this SAP help is suggesting two things:
1) First change the number of characters in domains/data element RKEG_PAPH1 to 3 to match the new structure in PRODHS
2) Find out the list of tables/structure where RKEG_PAPH1 to 3 is used and perform a data conversion.
From the where used list , we are able to see that this are used in 21 structures which are in turn used in numerous programs, structures, BAPIs etc.
We would like to know :
1) What is impact of doing this on numerous programs, structures, BAPIs etc ?
2) How these data conversion is done and what utilities are used for the same? Is it required to do this as our project is still not live? Only Dev and Quality systems now running.
3) Potential issues that we may face?
4) Any other alternative solution.
Thanks,
Best regards,
Prashant

Hiya,
First impressions: Since you are not live yet, the impact is much lesser than if you were live. So thats saving grace.
I gather from your post that you either don't wish to leave these Chars as they are (ignore them and create new ones instead). Have you explored the possibility of using these for some other 5-char or 8-Char Characteristics?
The impact is massive, but restricted to BAPIs and custom programs you may have built based on these Chars. Whatever method you follow (new Chars or change these existing ones), you will still need to modify your reports to reflect the new data structures. But then, do you have an option?
You could use custom programs for data conversion, mapping your lagacy data to the new fields, or simply use Excel spreadsheets - that also depends a lot on the source of your legacy data.
Is it required? You don't data convert until your first cutover and that is mostly into a Regression Test server and then into the P server. So do you really need to bother about data conversion to the Dev or the Quality servers?
You may need to explore the possibility of deleting these Chars from the Op Co and including new ones. While this is not a recommended option, that way you can still transport only the required Chars to the P server and ignore the rest. Your Test or Quality servers will go for a toss (data mismatches etc.), but you could try and not let it affect your golden client.
Alternatives: explore the possibility of ignoring these 3 Chars and creating 4 new ones instead. That, by far, could be your best option.
All the best.

Similar Messages

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

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 field in WBS

Hi Everyone
I have checked every where and still unable to find solution that whether can we add product hierarchy field in WBS or not? If yes then how can i?
I have already checked at spro>img reference>project systems>structures>operative structures>user interface settings> define layyout of WBS element deyail screens
But cannot get any answer or clue over there. I was wondering If the field Product heirarchy could add up (PRODH). please help

Hi Master mind,
What exactly do you mean by saying Product Hierarchy? As Ken said, its not a standard PS field. If you wish to add this field at the WBS element level you will need to go for an enhancement CNEX0007 Customer-specific fields in WBS elements
Regards
Varun

Product Hierarchy Derivation in COPA

Hi Gurus,
We have 6 levels of Product hierarchy defined in the system and I am able to include it in the data structure. The related Characteristics are PAPH1,PAPH2,PAPH3,PAPH4,PAPH5,PAPH6 included in my operating concern. Level 1 has 1 character in number and rest of the levels has 3 characters each in number as follows.
Level 1--1 Number of Character
Level 2--3 Number of Characters
Level 3--3 Number of Characters
Level 4--3 Number of Characters
Level 5--3 Number of Characters
Level 6--3 Number of Characters
Hence all together the total number/length is 16.
Now, when I generated the operating concern,the derivation rules for product hierarchy are created automatically as follows.
Following is the screen shot for source field if I open step number 22
The corresponding screen shot for Target field is as follows
For step 23 , the source field details are same as step 22 but target field details are as follows
We have assigned Product hierarchy in Material master in tab Sales:Sales Org 2 which is 16 digits.
Now when I try to test the derivation rule for step 22, system gives me following error
=================================================================================
Characteristic value 010 does not exist for characteristic PAPH2 (ProdHier01-2)
Message no. KE0C133
Diagnosis
The characteristic "PAPH2" ("ProdHier01-2") should be posted to Profitability Analysis (CO-PA). When the system checked the entries, it was established that the transferred characteristic value (" 010") is not valid in CO-PA.
System Response
The data is not consistent and therefore cannot be transferred to CO-PA.
Procedure
With the function Maintain Characteristic Values, you can add characteristic values to those that are valid.
==================================================================================
I am getting the same error for all steps in test mode. How to fix this error? Do I need delete the PAPH1--PAPH6 characteristics and use the user defined characteristics and write derivation rule again? Also I want to know the use of steps 28 to 31 (clear) in this regard.
I have not included characteristic PRODH in my data structure. Do I require to include it in my Operating concern?
Regards,
makrand

Dear Ajay,
Hearty Thanks for the solution. As suggested by you, I removed "move" steps and defined the Table Lookup" steps.
There are two target entries i.e MVKE (Origin) table and the field name is PRODH (Product Hierarchy) which is equivalent to second target entry COPA (Origin) field (PAPH1 -----to PAPH6) in the same line.
In field PRODH,I used offset position. I selected "Entire Field Contents" and kept character position as 0 and kept total characters as 16 in each table lookup entry.
Again I have to make offset settings in PAPH1---PAPH6 fields. I selected "Entire Field Contents" tab and system automatically changed the field length for PAPH1 to PAPH6. Now the results are correct.
I arrived at solution after making some combinations in offset. Thought, this may be useful for somebody facing the similar issue.
What's the use of "Clear" steps which are generated by system?
Thanks and regards,
makrand

User Exit - EXIT_SAPLKEAK_001 - Product Hierarchy field

Dear All,
I am trying to control the input of the Product Hierarchy in the t-code F-02 - Profitability Segment section. So far i found the user exits - EXIT_SAPLKEAK_001 is related to control the data in the profitability segment in t-code F-02. However, i cant find the product hierarchy field be store in this exits while i debugging this program.
Please kindly advise .
thank you very much

Hi,
Actually I dont want selection from any view. I want to create search help exit for this custom field. And it should be similar to.. PRODH field. In PRODH the data is coming when we press F4 from T179 table. So in place of T179 the data should come from my custom table.
This is what my requirement is.. Hope u understand now.
Thanks,
Jhings

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

Search Help - Product Hierarchy

Hi all,
is there a specific Webdynpro searchhelp for Product hierarchy?
when i use the automatically selected one PRODH, i get dumps on the
browser, complaining there is no connection to the user.
thanks in advance,
Koen

Hello Koen,
Seems like the search help for PRODH uses call screen or some other dynpro statement inside. Probably, SAP already provided a fix to be applied to this search help so that it can be used within Web Dynpro ABAP. Might be worth opening an oss ticket towards the oss queue to which the package of the search help points to.
Best regards,
Thomas

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 download into CRM from ECC6

Hi Guys,
Recently we have added few Product hierarchies into ECC6 (level 2, 3 , 4 and 5 hierarchies)
now they are not replicated into CRM...
how can I replicate them into CRM from ERP6... quick guidance....?
The object - DNL_CUST_PROD1
Thanks
KP

it will be done maually,
- On CRM
For Defining the Product Hierarchy Strucuture :
CRM IMG -> Cross Application Components -> SAP Product -> Product Category -> Define Category Numbering Schemes
   - make new entry
          Number Scheme     R3PRODHIER
   - after that select the new Scheme, and choose a new entry (should be the same as structure PRODHS on ECC)
For Defining Product ID
CRM IMG ->Cross-Application Components->SAP Product->Basic Settings->Define Output Format and Storage Format of Product Ids (tx. COMCPRFORMAT)
note : should be matched with ERP (Tx. OMSL)
refrence B09_BB_ConfigGuide
الحمد لله الذي علمنا

Product hierarchy for indirect material?

How do we maintain prodh for indirect material?
for maintaining indirect materials master which of the following attributes are important to be considered
Material Numbering
Unit of Measure
Material Type
Product Hierarchy
Valuation Class
Material Status
Country of Origin
Conflict Minerals
Material Group

Indirect material is a consumable material. Its used with direct material for procurement.
Usually this material are non stock materials and it consumed immediately when you will do goods receipt.
And for attributes, its depend on your business process. You can maintain all these above as per your requirement.
But some are necessary to create a material master record like as
Material Numbering
Unit of Measure
Material Type
Valuation Class
Material Group

Product Hierarchy Update on Existing Sales Order

Hi,
My company business process allows sales order to be created up up to 3 months before shipping. Prior to shipping, material can have the Product Hierarchy changed and pricing can also be updated for the new product hierarchy value (Pricing record with Product Hierarchy in the search key). Our company also want to make sure we bill customers with new (correct) price.
In order to support pulling in the new price for our existing backlog (orders), so that we don't mis-bill our customers, we need a way to update the product hierarchy value on the existing sales orders that have not been shipped. Our current solution is to implement some custom logic in the Sales Order Update user exit, so that when the user clicks on the "Update" button on the Condition Screen on VA02 to manually update price, the custom logic will be invoked to re-pull the Product Hierarchy from the MARA table to overwrite the old Product Hierarchy on the sales order. Next, pricing will perform the search for new price using the updated Product Hierarchy value.
This solution has worked okay for us, but we are trying to evaluate if there is any other better way to accomplish this same request. We would prefer to implement something that is offered by SAP via configurations. We try to stay away from customization as much as possible.
Have you ever experienced something similar or do you have any idea how to support this kind of business process?
Thanks very much.

Hi Hans,
We don't want to wait for until billing to update price since we have the CI created at the time of delivery not billing. CI document also needs to display correct pricing for custom purposes.
Also, we would like to keep pricing on the Sales Doc. and Billing Invoice the same. This is why we would like to trigger re-pricing on sales order. And when pricing is re-invoked, we need to re-read the PRODH data to ensure new price is retrieved.
Thanks for your response.
Hannah

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

Addign product hierarchy to purchasing conditon

Hi,
I have a problem,
I'm trying to create a vendor discount condition based on the material's product hierarchy.
I added field PRODH to the field catalog and then created a new table, then I added the new table to the access sequence.
I created a condition record to for a product hierarchy.
BUT in the purchase order the condition is not recognized.
In the analysis there is a message for the access seq :" Access not made (initialized field) "
Can you please help me solve this issue.
Thanks,
Dave

Hi ,
i think something wrong with VARKEY itself , anyhow y dont you process BDC session with "Display Error Screen" then u wil come to know hot its passing the values to PRODH.....
regards
Prabhu

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 !!!!!!

PRODH & CO-PA Product Hierarchy

Similar Messages

Maybe you are looking for