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

Similar Messages

How to put the product hierarchy in the bw?

I want to have the product hierarchy in the reporting, in a way, that the users can open and shut the elements of the tree.
So i added the foreign hierarchy criteria 0PRODH1, 2, 3 to the InfoObject 0MATERIAL.
Then I used InfoSource 0MATERIAL_LPRH_HIER to put data in 0MATERIAL.
In the result 0MATERIAL HAS the hierarchy, but without any materials added to the leafs.
What did i do wrong?
Tobias

Hi ,
Have a look on note: 407033
It says 2 main points with regarding to your problem.
1) Material master records with shared master data in the sales area cannot be assigned to a product hierarchy in BW.
This solution generates the thinnest possible hierarchy, but leads to some restrictions in the navigation options in the BW queries because you can no longer expand the hierarchy to the material numbers.
2) The 0PROD_HIER attribute of 0-MATERIAL must be active as a navigation attribute in the cube.When you expand the hierarchies by product hierarchy in the query, you can display this hierarchy.
With rgds,
Anil Kuma Sharma .P
Kindly assign points , if it really helps you.

How to create the Product Hierarchy maintenance ..?

Hi All,
How to create the Product Hierarchy maintenance (IN APO System), I know manual creation, going to the transaction : /n/sapapo/relhshow , how to create programmatically, is there any Function module?
Pls let me know
Puppy.

Hi Puppy,
Please check whether the below BAPI can be used by you.
T-code: BAPI
Object name: ProductAllocationAPO
Obj type:- BUS11305
Regards
R. Senthil Mareeswaran.

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

How to tranport the product Hierarchy?

Hi All,
i have added set types to a custom Hierarchy and need to transport how can i do ?
Regards,
Azeem.

hi
to transort set type is easy just go inside the SPRO and there in crossclient applications and then transport the product category
if you face any problem trasnporting product
see this link
http://help.sap.com/saphelp_crm40/helpdata/en/77/8906413422164FB57EB48939CF7F45/content.htm
best regards
ashish

Product Hierarchy in the t-code F-02 - Profitability Segment section.

Dear All,
I am trying to control the input of the Product Hierarchy in the t-code F-02 - Profitability Segment section. May i know how i can do that? Currently i am using field exits but it is not working in this program.
Please help.
thank you

Hi Jasmina,
When you post with PK 31 you create you post other line with PK 40.
In the 40 line you fill in the Profit segment. A Derivation rule is based on 1 posting line and not 2 or more line's
In the derivation rule from the 40 you don't have the vendor number (this is in the 31 line).
Perhaps it is possible with a user exit in CO-PA.
Regards,
Paul

Product Hierarchy - modifying the levels

We are wanting to use the Product Hiearchy but are wanting to redefine the levels. We want 4 levels, 3-6-6-3. I've done some research and find that we are able to change the SAP standard of 3 levels to the 4 levels that we want. I've also found general documentation on how to do that. When I create my new Domains (ex: zprodh4 char3) and then try to change the main structure of PRODHS I get a pop up asking for an Access Key. So, I'm either doing something wrong or changing the product hierarchy levels does not survive an upgrade? Can anyone answer this for me. If you think I'm doing something wrong can you please give me detailed instructions on how to assign the new domains to the existing structure.
Thank you!
Tami
Edited by: Tami Ayres on Nov 14, 2011 9:24 PM

I have the access key and am modifying data element PRODH1. I changed the domain to read ZPRODH1 which is my defined domain. I saved it.
1. When I go to activate it I get a list of dependent structures and tables that are to be adjusted. Of course this makes me nervous but I'm assuming this is normal.
2. When I start to modify my next data element PRODH3, I am prompted for the access key. I enter the same access key as I did for PRODH1 and there's an error telling me the access key is incorrect. Do you have to have an access key for each element and then the structure that you are modifying?
Sorry for all the questions but this modification is making me nervous and I just want it to be correct.
Thank you,
Tami

Product Hierarchy download into CRM from ECC6

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

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

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.

Change the product categories in Campaign planning

Hello Friends,
In the Marketing Planner (TCode: CRM_MKTPL), after creating a marketing plan, in the product tab if I append a row and enter a product hierarchy, and press enter then I will get all the lower level data and complete information about the product. But my requirement is that when I press enter after entering the product hierarchy, I should not get the lower level data and also for the entered product hierarchy I should not get the Product Id and description. I need to supress all the values based on a condition.
The condition is, I will create a Z table and store some Campaign Types in it. Whenever user creates a Campaign or changes a Campaign, the Campaign type should be checked with the Campaign Types in the Z table. If there is a match i.e., if the Z table contain that Campaign Type then perform the operation above i.e., supress the lower level data and product Id, Description for the product hierarchy entered.
I have found that the BAdis triggered here are
COM_PROD_MNT_ALL
COM_PRODUCT_ADD_DATA.
I thought the BAdi COM_PRODUCT_ADD_DATA is more relevant for this requirement because it had methods like INSERT_ENTRIES, READ_SINGLE etc.
But when I tried to create an Implementation for this BAdi it throws me an error saying the BAdi is for SAP internal use only.
So, how to achieve this requirement? Is there any User Exit for this? Or any event that is triggered at this point?
Regards
Raju.

Hi friends
Is there a way to achieve this? What can be the approach to solve the requirement?
Hi Pratik,
How to go with the requirement? Can this be achieved?
Regards,
Raju.
Message was edited by:
Narayana Raju Sampathirao

COPA - Product Hierarchy

Dear all experts,
My client has split the product hierarchy in COPA into 3 levels.
For example, ProdHier01-1, ProdHier01-2 & ProdHier01-3.
Then they use these values in COPA to further derive the detailed product characteristics.
By looking at the questions posted in SCN, I realized that the naming convention (ProdHier01-1, etc) and setting (create characteristic with reference to MARA-PAPH1/2/3) are the same.
So I assume this is the standard SAP way to create the prod. hierarchy in COPA.
Now my question is,
1) Is it necessary (or standard way) to create 3 COPA characteristics to derive each level from PAPH1/2/3?
2) What is the purpose to create no. of COPA characteristics according to no. of product hierarchy level?
3) Can I just create 1 COPA characteristic and map it to the full length of product hierarchy value?
I can still derive the detailed product characteristics from this 1 COPA characteristic.
Thanks.
Sincerely,
Sebastian

Hello Madhu,
Thanks for your reply.
That is my main question, why do we need to update Prod.Hier1/2/3 in COPA?
Is it the standard SAP way that's why my client just follows?
When I check in the derivation rule, this Prod.Hier1/2/3 is later being used to derive detailed product characteristics where I am able to get it if i map 1 COPA characteristic to full length product hierarchy value.
What is the purpose of splitting them into 3 levels if there is no other functionality of this piece of info in COPA?
Thank you.
Regards,
Sebastian

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.

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

Standard interface for Product Hierarchy

Dear Experts,
 I want to know the product hierarchy, i m working for a pharma project, i want the heirarchy like Category---> Molecule-->Brands---->SKU
 can anybody tell me the standard interface for finding the product hierarchy or is there any transction code for getting these hierarchy details,
plz help me,
 Regards
 eswar

Hi Eswara,
There are transaction Code for viewing the Product Hierarchy and Category.
The Transaction Code is COMM_HIERARCHY. You can find the details of the entire product in the following navigation details.
SAP -->> Master Data -->> Products from the main menu.
Thanks,
Samantak.
Rewards points for useful answers.

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,

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

Similar Messages

Maybe you are looking for