CUSTOMER & PRODUCT HIERARCHY

Dear SAP Gurus,
Can any one provide me step by step of Customer and Product Hierarchies?
my mail id is [email protected]
Highly rewarded.
Regards.

hi
Customer Hierarchy
All the customizing is in SD/Master Data/Bussiness 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 informacition, in the order, you obtain the bussiness partner for each partner function.
3) Assign acount groups: you indicate which accounts groups are allowed for being part or your hierarchy.
4) Assign sales areas: symple you indicate wich 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 documentos 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.
Can also refer to http://help.sap.com/bestpractices/BBLibrary/documentation/J04_BB_ConfigGuide_EN_UK.doc
Product Hierarchy Configuration:
http://help.sap.com/bestpractices/BBLibrary/documentation/Q10_BB_ConfigGuide_EN_US.doc
Reward if USeful
Thanx & regards..
Naren..

Similar Messages

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

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,

Issue in Hierarchy data upload from R/3 for info object Product Hierarchy.

Hi,
I am trying to upload the hierarchy data from R/3 system for Info Object Product Hierarchy.
Insted of business content info objects (0PRODH, 0PRODH1, 0PRODH2, 0PRODH3, 0PRODH4, 0PRODH5, 0PRODH6), we are using customized objects (ZPRODH, ZPRODH1, ZPRODH2, ZPRODH3, ZPRODH4, ZPRODH5, ZPRODH6).
In transfer rules the mapped is as specified below
Fields => Info Objects.
0ZPRODH1 => ZPRODH1
0ZPRODH2 => ZPRODH2
0ZPRODH3 => ZPRODH3
0ZPRODH4 => ZPRODH4
0ZPRODH5 => ZPRODH5
0ZPRODH6 => ZPRODH6
Now, when I schedule the Info Package, it is ending with an errors
"Node characteristic 0PRODH1 is not entered as hierarchy charactersitic for ZPRODH"
"Node characteristic 0PRODH2 is not entered as hierarchy charactersitic for ZPRODH"
"Node characteristic 0PRODH3 is not entered as hierarchy charactersitic for ZPRODH"
"Node characteristic 0PRODH4 is not entered as hierarchy charactersitic for ZPRODH"
"Node characteristic 0PRODH5 is not entered as hierarchy charactersitic for ZPRODH"
"Node characteristic 0PRODH6 is not entered as hierarchy charactersitic for ZPRODH".
when i tried to load by flat file, there is no issues. But, flat file loading is not allowed for us.
Please let me know any possible solution to handle this issue.
Thanks.
Regards,
Patil.

Hi voodi,
Insted of using the info object 0PRODH1, we should use customized info object ZPRODH1 which I added already in the external characteristic in Hierarchy.
Regards,
Patil.

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

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.

ECC Product Hierarchy to CRM

Hi all,
We have a product hierarchy created in ECC in Tcode V/76. These hierarchies have 3 levels and assigned to different materail in ECC materail master.
We have done a initial load of Materail and all the products in CRM now have the R3PRODSTYP. But none of them got assigned to R3PRODHIER when I check in Product wokbench. This is making my product search in a Sales order really difficult.
Is it a standard behavior that R3PRODHIER does not get assigned automatically even though those materail belong to that hierarchy in ECC?
I cheked the SMW01, no errors in initial load of the objects "Material", "DNL_CUST_PROD01" etc.
Any help much appreciated.
Edited by: Praveen Rangineni on Aug 4, 2008 4:10 PM

Yes..That can be a possible approach. But the product maintenance workbench will not allow you to delete the base category with which the product was created.
Instead the best way is to use this recategorization trx. COMM_PROD_RECATEG to change the category assignment of all your products on the fly.
Please use this in TEST mode first and then go for it!
Thanks,
Sudipta.
Note: Unfortunately, the report cannot be executed to delete the assignment of a category to a product when that category is assigned to the base hierarchy.
In that case, a report program to reassign the base hierarchy would be 1 option. Alternatively, you need to purge your product data in CRM and restart the download from ECC after making the customizing change.
Edited by: Sudipta Sarma on Aug 5, 2008 1:00 AM

Product Hierarchy Change - Need help

Hi,
We have a CRM 4.0 ISA for e-commerce scenario. The Production environment is LIVE now and we have a Product Hierarchy (with more than 2400 categories in multiple levels). The Settypes assigned have both SAP standard as well as custom settypes. The catalog for webshop has been created with Automatic Assignment with categories transferred from the current Product Hierarchy.
There has been a radical change in the business alignment because of which the categories are changing and the hierarchy is going to change completely.
I need a solution where without shutting down the production (or with minimal week end shutdown), where we can create the new hierarchy and transfer the existing products to the new hierarchy. The problem that i am facing is that the SAP standard and Custom settypes that are currently assigned to the existing hierarchy does not allow me to assign to the new hierarchy that i am trying to create in the system in parallel. I would be good if i can some how create the new hierarchy and keep it ready before we can shut off the existing hierarchy.
Also, do we have any way to transfer products in one hierarchy to another hierarchy? (We can recategorize within the same hieararchy, but need to know if we can do it inter-hierarchy)
Also is it possible to bring the hierarchy and the assigned products from DEV / QA system to PROD?
Please help with your inputs.
Shankar

Hi
As previously said, the changed product hierarchy value will beocme applicable only for the new documents you are going to create. For the old documents, the older PH levels exists, it wont get automatically change.
Also, the infostructures also will hold the old values for the old transactions.
So it will be better to archive /delete the data so far in those structures and hten enable it for hte new PH values. Else, you cannot arrive at a conclusion based on PH levels, as the same level will imply different things at different points of time.
Hope this helps.
Reward if this helps.

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.

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

Product hierarchy ID lost after transport

Hi experts,
could you please help me with the following problem: we have made customizing of the mapping of imported catogeries to the categories in the EBP for a schema.
The mapping is as follows: Imported category, Product hierarchy, Product category, The customizing was transported successfully but the product hierarchy ID field is empty in the target system although the hierarchy ID exists in the target system.
Any ideas what can be the problem?
Thanks for your help.
Tomas

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 discount

Hi,
We have come acorss for a typical discount condition type required.
Discount is required for product hierarchy. say for ex: there are 3 material X, Y and Z are having same product hierarchy key.
Now the requirement is for
Customer buys 15 packs of material X, therefore he should get a 15% discount.
Customer buys 10 packs of material X and 5 packs of material Y, therefore he should get a 15% discount too.
That means, mixing of materials within one product hierarchy should be possible.
How can achieve this?? will header condition work for this? Pls let me know your suggestions ASAP.
Regards,
Srikky

Thank you Navneetha...
really its a problem solving solution..
At last i wiould like to know where we can create this routine? i guess in VOFM - Formulas - Structure og Grp Key, pls correct if i am wrong. what should be logic to write code for this Product Hierarchy routine?
If i am already having a discount condition type and if i activate the 'Group condition', will this going to effect on anything? otherwise the functionality will remain same except Group Cond functionality? Can i use the same condition type for PH discount also?
Pls help me..
Thanks & Regards,
Srikky
Edited by: Srikky on Sep 7, 2010 11:12 AM
Edited by: Srikky on Sep 7, 2010 11:16 AM

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

CUSTOMER & PRODUCT HIERARCHY

Similar Messages

Maybe you are looking for