This is an advanced concept in SAP CRM Training and should only be attempted when you have a thorough understanding of the user-transaction part of the Product Master.
In this post we will attempt to define a product master from scratch. When I mean “from scratch”, I mean defining the structure of the product master, the attributes, set types etc. Typically product masters are transferred over from ECC ( Some times, Service and warranty items are created in SAP CRM ). When product master is transferred over from SAP ECC, it fundamentally belongs to a product hierarchy R3PRODSTYP. You can go to [ COMM_HIERARCHY ] to understand the structure of this product hierarchy as defined by standard SAP.
As you can see, the Product Hierarchy R3PRODSTYP contains a bunch of categories ( like APPL, ICMP ..etc ). The SAP Material types as defined in SAP ECC , map to these categories or sub-categories.
As you can see from the categories above, here is the structure ( hierarchy ) in which the product categories are arranged.
so on and so forth.
The reason why this has been created as a hierarchical structure is to allow for flexibility in defining products. We will discuss a simple example below and you will be able to appreciate all the work done by standard SAP for us in the product master in terms of defining views, screens, attributes , set types etc.
If you want to create a computer from scratch without the use of existing Hierarchies/ categories, here is how you can do it.
Step 3 : You should have already created the respective SAP CRM Product Set types using [ COMM_ATTRSET ] transaction.
Step 4 : Finally, a crucial step. Assign the Product Type per Application Product – In this step you assign the default hierarchy ID to the product type. Please do NOT do this step as this affects all the users of the system. The menu path for this is [ spro -> IMG -> Cross-Application Components -> SAP Product -> Product Category -> Assign Category Hierarchies to Applications ]
and when you create the product, you will see the respective set types in the basic view of the product master. ( Because, we have not assigned a specific view to the Set Type )
Now that we understand the process of creating a new product master from scratch, let me remind you again, that this is a process that is rarely done in real-time. Most of the time, ECC or MDM systems are the leading systems when it comes to CRM. Now, let’s revisit the standard MAT_ categories to understand them better.
The set types as discussed are all inheritable. So, standard SAP has defined MAT_ with a bunch of Set types that MAT_FERT or other sub-categories automatically inherit.
Similarly, MAT_FERT or MAT_HAWA ( the sub-categories of MAT_ category ) will have additional set of types apart from the inherited set types from MAT_
And that is how your product master is structured. This concept could be a little bit intimidating for someone who is just starting to learn SAP CRM. So, I request all the students of our SAP CRM Training to ask questions in the class to have a better understanding of product hierarchy, product category.
Let’s solve a scenario to have a hands-on understanding of this.
SAP Product Master Structure – Case Study 1
SAP Product Master Structure – Case Study 2