Product master data: a cheat code to optimize your search and save time
As an S/4HANA Cloud consultant, master data is a topic that is omnipresent during any implementation project. Regardless of which LoB we consider such as Manufacturing, Procurement, Sales or Service, all core business transactions operate on the basis of master data, which makes it important to ensure that this master data is maintained with the correct attributes. Some common examples of master data in S/4HANA Cloud are Business Partner and Product (formerly material) master data.
As a consultant, it is crucial that the product master data is maintained and configured correctly in accordance with how they are used in a customer’s business. Factors such as the business context and usage of a product are determined by the values of certain attributes that are assigned to the product’s master record. For example, products with a product type “HAWA” (trading goods) are procured externally and will therefore not have any production planning data associated to them. Besides Product Type, some other key attributes to consider while maintaining product master data are Product Group and Item Category Group.
With this in mind, it is often the case that consultants need to check the values of these attributes in order to understand whether a particular product can be used in a particular business scenario. For example, the stock part SRV_05 used in service orders cannot be processed in a Sales Order due to it having the item category group SVST. So the main message to understand here is that is important for consultants to know which product type, group and item category group a particular product has to better understand how and where this product can be used. Depending on the customer involved, there could be up to tens of thousands of product master data records in the system. Usually, one has to go into the ‘Manage Product Master Data’ app, search for the required product, and set the necessary filters to display the desired fields. Instead of repeating this process every time I want to look up these values for a new product, I can setup my own database of all the products in the system along with the respective fields I wish to see. This can be done using a Custom CDS View and a Custom Analytical Query. Let’s look at the steps involved in this and how the end result can end up saving you a considerable amount of time in the long run.
- Create a Custom CDS View as an analytical Cube
- In the App “Custom CDS Views”, create a new CDS View (Scenario “Analytical Cube”)
- In the CDS View Details page, select I_Product and I_ItemCategory_Group as data sources. Choose I_ItemCategory_Group as a primary data source and I_Product as an associated data source. Maintain the following Join Condition:
- Add the fields you want to see. I would recommend the following elements to start with:
- Add a filter to show the values only in 1 language
- Check and publish the Custom CDS View.
- The next step is to create a Custom Analytical Query to consume the data from the Custom CDS View.
- Create a Custom Analytical Query
- In the App “Custom Analytical Queries”, create a new query with the custom CDS View created in the previous step as a data source.
- In the Field Selection tab, select all available fields.
- Go to the Preview. In the preview page, add all the fields to the rows axis. After that use the icon on the top right to export the table as an excel file.
Let me know in the comments if this helps you and feel free to share your feedback!