Skip to Content
author's profile photo Former Member
Former Member

R3ProdHier,R3ProdTyp and R3Prod

Hello Everybody

Would anyone be kind enough to explain why we need the above terms in CRM ?

From my understanding, this is needed when craeting prods in CRM and also to map prods to R/3

Please correct me if I am wrong.



Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Jan 10, 2007 at 12:57 AM

    Hi Alicia,

    Your understanding is absolutely correct.

    A CRM product can't be created without a valid product hierarchy (e.g. r3prodhier), product category (e.g. finished product) and product type (e.g. material, service etc)

    To download the ERP materials into CRM, you need to first download the customizing objects DNL_CUST_PROD0, DNL_CUST_PROD1 and DNL_CUST_PROD3.

    Let me know, if you want further clarifications


    Paul Kondaveeti

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Alicia!

      I understand your question as you want a crash course in the usage of product hierarchies.

      There are a large number of reasons for which this concept is used. Category Hierarchies is a common way of grouping objects in SAP systems. It can be used in searches, transactions etc.

      One example when a hierarchy is quite useful is when you have an opportunity not for a specific product, but rather for a group of products. In the opportunity you could assign a group of products by choosing the lowest hierarchy node and all assigned products will be allocated. You could even do a generic assignment where you say that products in 1011* are involved in the specific opportunity you are working on.

      If you use ERP / R3 as the leading system you need to have the product hierarchy since it is a central part of the material master and replication to CRM cannot take place unless you have a matching structure in CRM.



Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.