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 ../
Product Hierarchy can be use by all sort of industires ?
For .Eg. take Paint industry .. They can have same material with different categories like Paint , interior emulsion or Exterior emulsion, white base or other color base or differetn color. For these purposes , you can have product hierarchy .
Level will be maintained in V/76..
You can maintain each one in different level in Product hierarchy and maintain in MMR?
That , you can use it for Report Purpose ?
I had got some idea about the same . But bit clarification.
As u said For .Eg. take Paint industry .. They can have same material with different categories like Paint , interior emulsion or Exterior emulsion, white base or other color base or differetn color. For these purposes , you can have product hierarchy .
In above scenario whiach finished material and which are comes under product hierarchy??
Can u explain me with more clear ??
Every finished product will have product herierarchy .
Level 1 - 01 ( Paint )
Level 2 - 0001 , 0002 - Interior Emulsion , Exterior emulsion.
Level 3 - 00001 , 00002 - White based , Color Based.
These configuration to be done in V/76.
THen , When you choose the Product hierarchy , every level will appear one by one to be selected.
Hope , it ll clear you bit clarification.
I have a material called as XYZ
If i got to material master MM03 for XYZ , its showing code in product heirachy like ABCDEFG001005..etc
So i confused about the same ..
Because hope under Prodcut heirarchy every thing should material master
Level 1 - 01 ( Paint ) .. material master (Materi code )???
Level 2 - 0001 , 0002 - Interior Emulsion , Exterior emulsion. .. material master (Materi code )???
Level 3 - 00001 , 00002 - White based , Color Based. .. material master (Materi code )???
These above material codes for product heirarchy where we can get in SAP??
Thanks a lot
Check this explanation:
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
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
PRODH1 PRODH1 CHAR 5
PRODH2 PRODH2 CHAR 5
PRODH3 PRODH3 CHAR 8
Changes according to example:
Structure Fields Data element Category Length
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
A nice link of SAP help:
Edited by: Afshad Irani on Jul 15, 2010 9:43 AM
MM group wrote:
> Then what is advantages and benefits of product hierarchy in SAP??
> Major advantages and benefits with real example for the same ???
Say you have a lot of varieties of semi finished goods, from which you can make a number of type of finished goods according to your customer's requirement & accordingly your pricing will be different based on the type of semi finished used in making.
Say you are providing a IP-VPN service along with hardware also so when pdt hrchy will be set then there will be preceeding nodes which will make the total service/pdt combination. ex IP-VPN managed 250 Mbps with 2 juniper routers & security of that network through firwall. so in this case you have the preeding nodes set for all the products & services & when finally your Pdt/Service combination will show up in the SO it will be give the price & description of features accordingly, so making your job easy to to.
you can have upto 18 level in standard & you can raise the level to 32 or 36 (i am not sure which one's right) with the help of an abaper.
It kind of gives you a short hand in keeping the pdt/service in your mind, just by looking at the combinations you can tell which all the pdt's were used in the total pack.
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).