Stock overview on basis of product hierarchy (PRDHA)

Hello to All,
Is there any SAP standard report of displaying stock overview on basis of the 'product hierarchy' (Field: PRDHA) or do i have to make a copy of the transaction (MMBE) and add the respective field ..
Looking forward to your feedback. Thanks
Regards,
Shehryar Dahar

check this and do modifications as per ur requirement.
https://www.sdn.sap.com/irj/sdn/wiki?path=/pages/viewpage.action&pageid=15856
get the PRDHA of MARA then report.
Regards
Prabhu

Similar Messages

Stock overview report on basis of product hierarchy ?

Is there an SAP standard report for displaying materials(product hierarchy wise) on the basis of product hierarchy or do i have to create a customer report for it. IF yes, then how do i go on creating it.. i.e how will i be showing the materials(in a hierarchical display, product hierarchy wise ?
Hope you have comprehended it ?
Thanks,
Shehryar Dahar

Hello Kirit,
the scenario is sumthing like this, the SAP transaction for stock overview (MMBE) displays the report per material. I want a report in which , if i give in the Product Hierarchy, it should display all the materials in diff levels in the product hierarchy. For example, if we choose 'Product Hierarchy' as a display level, it should display all the materrals in the hierarchy levels..!
I have been that the Stock Overview Report(MMBE) displays only one material, no matter what 'display level' you give in the selection. Does this mean, that i would have to develop a new report for this ?
Waiting for the replies.
Shehryar Dahar

Derive the category/subcategory from the product hierarchy (PRDHA)

Hi,
Is there a function module/table/transaction where I can derive the category/subcategory from the product hierarchy (PRDHA)?
Thks,
William

Hi,
I do see entries in /n/sapapo/relhshow. I don't see how the production hierarchy (Seen in /sapspo/mat1 under the properties tab) relates to it.
There is no F1 on that field in /sapapo/mat1 unfortunatly, so it acts like a free-form text field, as far as I can see. I changed it to a random value and it allowed me to save it, so it looks like there's no validation on the field?
William

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 in COPA

Hi all,
I am new to COPA. What I need to do is creating a report that is using a product hierarchy that we can define.
So I started and created a hierarchy in V/76 like we need it. Those values can now be entered into the "Prod. hierarchy" field for each material in material master - basic data 1.
Then I have created a characteristic for the field MARA-PRDHA (Product Hierarchy) in COPA and assigned it to our operating concern in COPA. Now I created a form (KE34), double clicked on a column to add a characteristic and selected my PROD HIERARCHY characteristic. Now in the window for "selected characteristics" there is a checkbox "Flag for entering hierarchies" so I checked that, but it says "No hierarchies exist for this characteristic".
So is this the right way to do it? How can I add product hierarchies to my COPA report, we would like to be able to "click" through the hierarchy, like starting on the highest level and clicking down.
Thanks
Anne

Anne,
Do not a check on checkbox "Flag for entering hierarchies" . Select value( Hierarchies from Definition drop down window) .
Thanks,
Mahesh

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

Product hierarchy query

i have to fetch materials from mara based on Product hierarchy but with one condition
If the user specify product hierarchy as 1000Y (2 levels) , it should pull all the materials with product hierarchy as 1000Y* for example either 1000Y OR 1000Y02T OR 1000Y02T09R0TT etc
code is
select matnr lvorm into table int_matnr from mara where
matnr in s_matnr and
spart = p_spart and
mtart in p_mtart and
prdha in p_prdha and
lvorm ne 'X'.
i do not want to specify "1000Y*" in selection screen rather just on ntering 1000y it shud by default get 1000y* values. right now only wen i enter 1000y* in selection screen then only it fetches all materials with PH 1000Y or greater otherwise if i enter 1000y it does not give values

try sumthing like dis:
PARAMETERS p_prdha type mara-prdha.
at SELECTION-SCREEN OUTPUT.
if p_prdha ne space.
CONCATENATE '' p_prdha '' into p_prdha.
endif.
plz reward points if dis helps

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

Incorrect Initial Stock calc for Semi-finished products in SNP PBook

Dear all,
Situation is as follows:
The Stock list on /SAPAPO/RRP3(Product View) matches the Stock in ECC (MMBE) perfectly. Also when we load the product in our SNP planning book, right click on the Stock on Hand and then Display Stock, it matches the RRP3 and the ECC stock.
Still the actual Initial stock displayed in the Planning book Cell in the initial column and thereafter is different from what the actual sum of stocks should be. This quantity is huge (in millions!). There is no Receipts planned which can contribute to this!!!
Is this a known bug in SAP? Can we rectify by running any programs?
Note: Already tried CCR, OM17, everything looks fine (which actually is because RRP3 view matched ECC perfectly.)
Kindly help.
Regards,
Rimjhim
Edited by: TEAM BASIS on Dec 18, 2008 4:00 PM

Hi ,
I couldn't find any problem with the macro.
One more observation:
The UOM in ECC is KG (in transaction MMBE). The base UOM in APO is ZUN (customized Tonnes).
The conversion in Prod Master is 100 ZUN=7484 KG
If we change this conversion to 1 ZUN = 1 KG then in the planning book the Initial Stock start showing as OK.
The random value shown earlier doesn't seem connected to the UOM conversion, it's just a very very high value. How can there be a connection between UOM conversion and the Initial Stock display.
Any ideas?
Regards,
Rimjhim
Edited by: TEAM BASIS on Dec 19, 2008 12:47 PM

Sales order stock not showing in stock overview(MMBE)

Hi,
I have a MTO scenario where against the sales order production order has been created.
Production order has been delivered & the material document showing 101E movement type.
After that the material has been transfered to another storage location with in the same plant with movement type 311E.
We can see the sales order no. on each material document.
But in stock overview no sales order stock is there against the particular sales order and because of this user is not able to create delivery for the same sales order.
Please guide in this matter.
Regards,
Susrikant

Hi,
In MMBE, check for the log on the movement type. You can find it in MMBE once the report is displayed. Select the storage location and then check for the Movement of goods from Menu > Environment > Movement types. It will have all the details of quantity moved in and qty moved out. You can easily identify thro' which movement type this material and qty is moved.
Also check the tcode MB52.
Hope this helps.
Thanks
Mukund S

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]

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

Default Account Assignment- product hierarchy

We have a requirement when any transaction posting to a write off G/L account to automatically include Product Hierarchy. I have used OKB9 before for C/C and P/C but not Product Hierarchy. Is this possible, if so, how?
Thank you!

AMS,
First make sure that the account is set to post to COPA. Make an entry in OKB9 for this account and click the Profitability segment indicator. Also, assign the account to a PA transfer structure (KEI2) to map the account to a COPA value field.
As far as assigning the product hierarchy to COPA characteristics, you have several options depending on whether you want the whole hierarchy assigned to one characteristic or if you want to split each level into seperate characteristics. Also, the hierarchy can be maintained in the material master in the general view (MARA) or the sales org view (MVKE), Let's assume you want to assign the whole hierarchy into a single field using the general data view assignment. To do this just create a table lookup step in KEDR. Select table MARA as the source. Field MATNR will automatically be match to your COPA product field (ARTNR). In the assignment section select field PRDHA from table MARA and enter the COPA characteristic field you want to store this value in. If you haven't yet assigned the product hierarchy characteristic to your operating concern you will need to do that first.
thanks,

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 doesn't works in ECC 6.0

Hello guys!
I'm working in a project that migrate to ECC 6.0 and now is facing an error in Material Master (MM01) when try to select a product hierarchy in Basic Data 1 view.
When the matchcode of product hierarchy is used, the "Next level" button of popup windown doesn't open the product hierarchy. I check with an another consultant that don't remember the SAP note that fix it.
Anyone knows this SAP note?
Thanks a lot,
Rodrigo.

Is your setup of product hierarchy consistent ? How many levels have you defined ?
In ECC 6.0 can you let us know the support pack & the patch level details (if not sure, obtain this info from your basis person)
Also it would help if you can upload screenshots of the setup done for the product hierarchy & the issue you face in material master.
Just for your info, I am on ECC 6.0 & do not face this issue.

Stock overview on basis of product hierarchy (PRDHA)

Similar Messages

Maybe you are looking for