Maintain product hierarchy

Hi Expert,
How do i maintain product hierarchy in material master? Our product hierarchy has few categories, i want to maintain the last node.How will i do that? Can anyone please guide me?
Thanks

Hi,
Go to T-Code V/76 to maintain Product Hierarchy.
Also refer following links;
[How To Configure Product Hierarchy|http://www.sap-basis-abap.com/sd/how-to-configure-product-hierarchy.htm]
[Define Product Hierarchies|http://help.sap.com/saphelp_46c/helpdata/en/77/1a39516e36d1118b3f0060b03ca329/content.htm]

Similar Messages

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

Standard field to be used in place of Product Hierarchy

HI,
We are going to have a new material in our system but we do not want to create a new Product Hierarchy for that. Infact we want that if any new material is created, we need not creata any new product hierarchy for that.
Please suggest what standard field can we use instead of Product Hierarchy without impacting the system .
Thanks.
Rudresh

Hi Rudresh,
Product Hierarchy is a informative field and can be used for reporting purpose. For a specified material type, if you dont want to maintain product hierarchy, make that field optional using OMS9.
Regards,
Amol

Product Hierarchy Not Updating in KE30 Report

Hi,
We are Maintaining Product Hierarchy in the Material Masters and we are using a KE30 Report from CO-PA here we are able to see all the feilds getting updated in the report except for product hierarchy. that too only when the material are belonging to WBS Stock.
Can any one help me in exploring the reason for the same
Best Regards,

Hi
In the absence of info, its very difficult to comment
1. Is the new sales material code assigned to Prod Hie?
2. During billling is the COPA doc generated? Or the revenue is posted to WBS Element?
If it is posted to COPA directly, then check point 1 above should be the reason
If it is posted to WBS, then check the settlement rule of the WBS... PSG will be the settlement receiver.... Have you mentioned Prod No in the settlement rule?
Br,Ajay M

Block/lock Product hierarchy

Hi Everyone,
We are maintaining product hierachies up to 5 levels in Materail Master Sales data.
If a brand with Product hierachy level 1 and 2 is obsolete and not going to be used in future, i want to block all the postings to this brand (product hierarchy).
can this be achieved by configuration in Product hierachy maintenance OR guide me how this can be done.
Thanks & Regards
Ram

Hi ,
how can i block or lock the materail (master record) for all postings?
Setting a flag for deletion will do? OR is there any other process to Block the material in customizing?
Here the requirement is we identified a brand which is maintained product hierarchy in Sales data as OBSOLETE.
So we dont want any postings should be allowed for the material master in which this Product hierarchy is maintained.
what is the best approach that will meet this requirement???
Regards,
Ram

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.

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,

SQVI Report for SAP CRM Product Hierarchy and its Product

Hi
How to create a SQVI report for generating a list for SAP CRM Product Hierarchy which should show the outputs->Level 1, level 2, level 3 and level 4 categories and its products?
I tried COMM_Hierarchy table and Comm_product but not able to achieve this requirement.
or Is there any chance of getting related tables so that I could try more for this requirement.
In which table both product id and its category Id can be found?
Pravin

Thanks DJ
Is there any possibility to get a report for product hierarchy in SQVI ?
say in SAP CRM system, the product category is maintained in COMM_HIERARCHY as
Parent category Id->
                                Level2 Category Id->
                                                                 Level 3 Category Id->
Level 4 category Id ->
Product Id's
(I understood the link between Level 4 category id and product id with your info.) but not able to achieve the requirement fully.
Is there any possiblity to achive for generateing a report?

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.

CO-PA Realignment: Changes in Product Hierarchy

Hello all,
We have changed the product hierarchy on some of our materials and we want to realign the PA data to reflect the same.
Our product hierarchy which we have three levels is maintained in KES1. There are no derivation rules. KES1 is updated manually everytime any changes occur.
For example:
OLD
Product: 1-189-01
Hierarchy 1: 100
Hierarchy 2:A7300
Hierarchy3: B56220
So on the material master the prod hierarchy is 100A7300B56220
NEW
Product: 1-189-01
Hierarchy 1: 125
Hierarchy 2:A7500
Hierarchy3: B56120
I tried using KEND for realignment and this does not change anything. Any help, how to proceed with the realignment is appreciated.

Hi Anusha,
Did u also update PH level in KES3 - in specific hierarchy variant ? Also would like to know how did u reset the operating concern
Thanks,
Samik (SAP MM)

R/3 Product Hierarchy in BW data model.

Hi all,
We have been told by our implementation partner that the scenario described below is not feasible to design in our BW 3.5 system and if we were to implement this scenario there would be a significant amount of user maintenance to maintain the hierarchy structure in BW.
I was a query user in previous BW versions and my datawarehouse modeling experience is mostly in Cognos and Business Objects. The scenario described below is very easily implemented in these other datawarehouse software packages and I would be suprised if SAP does not have a standard solution to address the problem.
I would like to understand if:
(1) Yes this solution can be easily implemented in BW 3.5
(2) A brief explanation on the design approach, implementation, and considerations
I am already familiar with the link on http://sap.help.com that explains BW hierarchy design and considerations, but I would like to get a "real world" understanding of an approach and design and if you experienced this requirement.
Thank You in advance for your input.
Regards,
-Anthony
Scenario:
In R/3 we have modified the standard delivered product hierarchy structure for material master from 5,5,8 to be 5,5,4,4.
The 4 levels represent: BRAND --> PRODUCT LINE --> PRODUCT CATEGORY --> PRODUCT SUBCATEGORY
Our intent is to use this structure to satisfy current BW reporting requirements for COPA and R/3 Billing infocubes.
In BEx Explorer we would like to perform product analysis using the following dimension paths:
BRAND --> PRODUCT LINE --> PRODUCT CATEGORY --> PRODUCT SUBCATEGORY
PRODUCT LINE --> PRODUCT CATEGORY --> PRODUCT SUBCATEGORY
PRODUCT CATEGORY --> PRODUCT SUBCATEGORY
We are told that since we have multiple values at the BRAND node we will not be able to perform grouped reporting the starts at PRODUCT LINE node(which would be independent of the BRAND node). For example:
BRAND, PRODUCT LINE, PRODUCT CATEGORY
HONDA, AUTOMOBILE, CIVIC
HONDA, AUTOMOBILE, ACCURA
HONDA, BLOWER, CIVIC
HONDA, MOTORCYCLE, ODESSY
FORD, AUTOMOBILE, EXPLORER
FORD, BLOWER, EXPLORER
FORD, MOTORCYCLE, CHAMPION
So for example we would like to start our dimensional anaylsis to show all AUTOMOBILE or BLOWER sales independent of the fact they were for HONDA or FORD.
In other datawarehouse systems I have either: (1) created 3 dimensions called: BRAND, PRODUCT LINE, and PRODUCT CATEGORY or (2) created one dimension called BRAND with alternate dimension paths for PRODUCT LINE and PRODUCT CATEGORY. I am not sure if this is feasible in BW.
We were also told in order to achieve this design a structure would have to be maintained in BW every time we introduce a new material master and the material master would need to be manually entered into the structure so that reporting can be achieved for both the standard structure and the alternate structure(s).

Antony ,
there will be maintenance involved every time you add a material to the material master. However you could maintain the hierarchy through a GUI also depending on the number of values.
Ideally if this can be maintained in a table in the source system , it can be imported into BW. Otherwise if you were to maintain it in BW , you will have a lot of problems when :
1. Change in the hierarchy - A new Product Line coming in and many product category onwards change over to the new product line.
2. Viewing the changed hierarchy over time - If you have GM and a separate category called Daewoo , earlier they were separate and now they are one - what are my product sales due to the merged entity vis-a-vis separate entities earlier...
Things that you will need to consider from a design stand popint are :
1. Should the hierarchy be time dependent ?
2. Should it be maintained in the source system or in BW?
3. Change process for the same - Flat file / Manual
4. Estimate of how frequent the hierarchy would change?
5. Will you have display hierarchies - Ad-Hoc hierarchies to view certain combinations?
Depending on the above your hierarchy creation can go from easy to complex and hard to maintain.
One way to amintain it is to have a SAP ABAP program to populate a hierarchy table to have the relations in R/3 and transfer them into BW. You could automate it in such a way that the hierarchy is changed every time there is a new material
Otherwise , there can be a flat file to create the relationships
Or someone could log a request and if the change is minimal it couldbe done thru a GUI Interface provided by BW.
Arun
Assiging points is a way of saying thank you in SDN

Condition maintained at Hierarchy not appearing in Sales document

Hi
We have a Condition for Discount, maintained for key combination "Sales area/Customer/ Product hierarchy".
There are two condition records maintained for the above key combination.
1 - Sales area/Customer/ Product hierarchy/group/ subgroup
2 - Sales area/Customer/ Product hierarchy/ group
In Access sequance of this condition, subgroup has priority 1 and group has priority 2.
In condition record for the first combination (Sales area/Customer/ Product hierarchy/group/subgroup)has 'deletion indicator' checked.
Condtion record found by the system in sales document pricing is the first combination which has 'deletion indicator' and condition record for second combination which is also maintained is IGNORED So in the pricing the condtion is not appearing.
Please let us know if this is standard SAP functionality or a defect.
Thanks.

Amritpal Singh ,
You have a Condition for Discount, key combination "Sales area/Customer/ Product hierarchy".
According to what i perceive
1 - Sales area/Customer/ Product hierarchy/group/ subgroup - Delete indicator is activated which means the value for this ondition record will not be displayed.
2 - Sales area/Customer/ Product hierarchy/ group is ignored
If it is so, check by double clicking item details screeen --> Conditions tab --> and Click Analysis Tab then choose the condition type then in right side of the screen you can see the details.
Inform us what details it is posting, if value is showing or not showing, also check whether you have mainatined condition type as Manual.. Check it....
Revert
Regards
Sathya

Product hierarchy IN MATERIAL MASTER ?

Hi experts
Can some body explain me about the Product hierarchy in material master under basic data view .??
Explain me about the purpose of Product hierarchy??
Which ind of industries will do with Product hierarchy??
And What the configuration has to done and where ??
What are the tyransaction in front to maintain the Product hierarchy??
In short without any links can some body explain ../
Many Thanks

Implement the Product Allocation Functionality
We are required to implement product allocation functionality in SAP R/3 (Enterprise Version).
We tried to do the elaborate steps as per the implementation guide but are not successful. Can you kindly help by giving the simple steps for implementation.
Please see if the following helps:
Configuration Overview; Allocation Specific Usage
1.Allocation Procedure (OV1Z) The product allocation procedure is the parent of the entire allocation process. All materials that are to be included in the allocation scheme are required to have an allocation procedure assigned to it in the material master. In addition, as of release 4.0, it is in the procedure that the method of allocation is defined. The user has the opportunity to set an indicator to identify their choice of two different methods (discrete and cumulative allocation) to evaluate the quantities to be considered for product allocation.
2.Allocation Object (OV2Z) The allocation object is the root level of the allocation process where actual data is entered and planned in LIS. The object allows the user to further break down a procedure into smaller parts for future validation of components comprising a specific material
3.Allocation Hierarchy Mapping (OV3Z) Primarily, this transaction permits the assignment of an allocation procedure to an LIS information structure. Secondly, a character is assigned to the information structure to permit collective planning. Finally, the user can assign a step level to the procedure and information structure to sequence the order in which allocation quantities are checked. This functionality allows the user the opportunity to check product allocation against several product allocation scenarios, before the required quantity is confirmed
4.Define Consumption Periods (OV5Z) The allocation consumption periods functionality is only valid if the allocation method flag has been set (OV1Z). If you have de-selected the method field, this functionality is not available. The consumption window indicates the number of past and future periods to be used in the allocation check.
5.Control Product Allocation (OV4Z) In order for the allocation process to function properly, allocation control records are created primarily to map allocation procedure steps to their corresponding objects so that the allocation data records can be located for validation. Secondly, validity periods must be established to indicate when the allocation control records are active. Finally, the user has the option of establishing a conversion factor per allocation control record to accommodate BOM listings of constrained materials
6.Activate Allocation for Requirement Class (OVZ0) In order to turn on allocation in the standard order processing functionality, the requirements class must have a flag indicating that allocation is relevant.
7.Activate Allocation for Schedule Line Category (OVZ8) In order to turn on allocation in the standard order processing functionality, the schedule line must have a flag indicating that allocation is relevant
8.Create Planning Hierarchy (MC61) In order to adequately establish allocation quantities, the user must initially determine the level at which the allocation is to take place and the aggregation factor of the allocation quantities. In this step, the levels for the collective allocation search procedure are also identified.
9.Generate Masking Character (OV7Z) Upon completion of the level determination for the planning hierarchy, the collective allocation masking character must be generated to allow aggregation indicators to be established. This transaction simply reads the hierarchy established in the planning table and then generates a collective mask character for each level of the hierarchy
10.Modify Planning Hierarchy (MC62) This step is a repeat of MC61 where the initial hierarchy was established. In order to complete the hierarchical set up, the collective allocation (mask character) hierarchy must now be maintained with the appropriate aggregation factors
11.Allocation Procedure Assignment to Material Master (MM02) At the root level of the allocation process are the materials. Each material that is to be considered in allocation scenario must be mapped to an allocation procedure. In order entry, then, when a material is entered with a valid allocation procedure in the material master, the allocation data is verified prior to confirming the line item ordered
12.List of Suitable Structures (OV9Z) This report is used to identify potential LIS information structures that can be used in the product allocation process. This report simply reads through the data dictionary and selects all the active information structures that contain the field product allocation object (KONOB) as the first field. This data can then be utilized in the mapping transaction (OV3Z) to link the allocation procedure step to an information structure (previous step).

Invoiced Quantity grouped by Product Hierarchy

Hello,
I am trying to create an Evaluation (tCode MC11) which will report on Invoiced Quantity grouped by Product Hierarchy. I created an evaluation referencing an evaluation structure which references two other eval. structures: one - for data tables VBRP and the second for info. struct.S004. One of the characteristics is Product Hierarchy. The problem is, that when I execute the evaluation - I only get 4th level of product hierarchy, but I need to see all four, starting with the first one.
(I would like it to look like this:
level 1
     level 2
          level 3
                level 4
Thank you in advance for your help,
Olga

Antony ,
there will be maintenance involved every time you add a material to the material master. However you could maintain the hierarchy through a GUI also depending on the number of values.
Ideally if this can be maintained in a table in the source system , it can be imported into BW. Otherwise if you were to maintain it in BW , you will have a lot of problems when :
1. Change in the hierarchy - A new Product Line coming in and many product category onwards change over to the new product line.
2. Viewing the changed hierarchy over time - If you have GM and a separate category called Daewoo , earlier they were separate and now they are one - what are my product sales due to the merged entity vis-a-vis separate entities earlier...
Things that you will need to consider from a design stand popint are :
1. Should the hierarchy be time dependent ?
2. Should it be maintained in the source system or in BW?
3. Change process for the same - Flat file / Manual
4. Estimate of how frequent the hierarchy would change?
5. Will you have display hierarchies - Ad-Hoc hierarchies to view certain combinations?
Depending on the above your hierarchy creation can go from easy to complex and hard to maintain.
One way to amintain it is to have a SAP ABAP program to populate a hierarchy table to have the relations in R/3 and transfer them into BW. You could automate it in such a way that the hierarchy is changed every time there is a new material
Otherwise , there can be a flat file to create the relationships
Or someone could log a request and if the change is minimal it couldbe done thru a GUI Interface provided by BW.
Arun
Assiging points is a way of saying thank you in SDN

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

Maintain product hierarchy

Similar Messages

Maybe you are looking for