Enterprise Resource Planning Blogs by SAP
Get insights and updates about cloud ERP and RISE with SAP, SAP S/4HANA and SAP S/4HANA Cloud, and more enterprise management capabilities with SAP blog posts.
Showing results for 
Search instead for 
Did you mean: 

With SAP S/4HANA Cloud 1911 release we have provided users with capability to maintain Product Hierarchy!!!

This feature has been enabled based on the request up voted via Influence Portal. See here.

Key Features

In SAP S/4HANA Cloud (1911), Product Hierarchy has the following key features:

  1. Reference to product from a hierarchy version.

    • In SAP S/4HANA Cloud, you assign a Product to a Product hierarchy version using the "Manage Product Hierarchies" (App ID: F4359) fiori application.

    • Thus, one product can be part of multiple hierarchies at any point of time, but note that in a hierarchy version a product can be child of only one hierarchy node.

    • No limit to the number of levels possible in the product hierarchy.

      • We do not restrict the number of levels possible for creation of a product hierarchy.

      • A hierarchy subnode/normal node has a length restriction of 24 characters, and these nodes can be configured in a Self Service Configuration UI (SSCUI). These nodes are independent and thus can be used in multiple product hierarchies or hierarchy versions.

      • But a node can be assigned only to one parent/level within a product hierarchy version. This behavior is similar to that of product assignment in a product hierarchy.

      • Option for time dependent non-overlapping product hierarchy versions

        • While creating a product hierarchy, user needs to enter the required fields like Hierarchy ID, its description and Valid From date. This hierarchy version would be valid on activation from Valid From until the Valid To dates.

        • Valid To date field is by default set to 31.12.9999. If you wish to have a time dependent hierarchy, this value can be adjusted to the required validity end date.

        • A hierarchy version can be copied to a new version for a different time period for same product hierarchy, or as a new product hierarchy altogether with a different Hierarchy ID.

        • Maintenance of Product Hierarchy in a tree structured display via Fiori application "Manage Product Hierarchies".

          • Using this Fiori application user would be able to maintain a hierarchy in an easy to understand graphical tree structure display

          • You can also maintain Product Hierarchies by importing details/data from Microsoft Excel spreadsheet/file, for specific version at a time.

          • You can easily assign multiple subnodes / products to a specific node in a single step.

          • Note that maintenance of product hierarchy is currently possible only with "Manage Product Hierarchies" application.

          • The application "Manage Product Master Data" will only display the relevant hierarchy in the "Distribution Chain" page. This display is possible only for those product hierarchies which are assigned to distribution chains using the application "Manage Product Hierarchy Assignments" (App ID: F4240)

          • How to maintain a hierarchy

            Now we explain the steps involved to maintain a product hierarchy and for example we consider a Tools hierarchy.

            Step 1: Maintain list of possible hierarchy nodes

            Content expert maintains a list of allowed hierarchy nodes and its description in the Self Service Configuration UI (SSCUI) available in the application "Manage Your Solution" for the section "Configure Your Solution". Detailed steps are as below:

            1. Open the application "Manage Your Solution".

            2. Click "Configure Your Solution" button.

            3. After the application has been loaded, set the filter for Application Area to the value "Database and Data Management".

            4. From the filtered list, click on entry for Sub Application Area "Product".

            5. Once the list of possible configuration steps for Product are loaded, we are provided with an option "Configure Nodes for Product Hierarchies".

            6. Read the "Configuration Help" available to know more about how you can configure the nodes and perform the steps mentioned.

            7. Click on "Configure" for this configuration step to obtain the Visually Harmonized GUI screen to maintain the list of possible nodes.

            8. The nodes maintained can be transported from quality system to productive system.

            9. This list of nodes will be available to the master data specialist to choose from while creating any hierarchy. Find below a list of sample nodes maintained for usage in our Tools hierarchy.

              Step 2: Create a product hierarchy version

              Once Step 1 has been completed, product master data expert can maintain a hierarchy using the Fiori application "Manage Product Hierarchies" by following the below steps.

              1. Click + ( Create new Hierarchy ).

              2. Once the Create New Hierarchy dialog is available, enter the value for Hierarchy ID, its description and Validity period

                • Hierarchy ID, would be the Level 1 entry for the hierarchy or the root node. Any further nodes addition would be made as child node of this ID only.

                • Validity period of the product hierarchy would be controlled by the Valid From/To fields. If you do not adjust the Valid To field's default value of 31.12.9999 as per requirements, the resulting Hierarchy would be equivalent to a time independent hierarchy starting from provided Valid From date.

                • Note field can be used to maintain a version specific language independent text.

                • Click "Create" to obtain a draft version of the new product hierarchy in the system.

                • Once the draft version of the new hierarchy is created, application automatically filters out the new hierarchy.

                • User can choose this draft version entry in the results to view the details of the hierarchy.

                • After the Details view is loaded, click on "Edit" button to change the version from display mode to edit mode.

                • Once the application is in edit mode, user can click on the Add button ( + ) against the root node to add Level 2 nodes of the product hierarchy.

                  • On clicking the Add button, user is provided with a "Add Node" dialog where user can select on adding multiple Subnodes or Products.

                  • Subnodes options would allow the user with option to select Level 2 nodes of the product hierarchy using the value help available for the field "Node". These nodes are those entries which were maintained in the SSCUI as part of Step 1.

                  • Add the subnodes for the hierarchy structure based on the requirements.

                    • For our example shown above, next level will be the node HAND_TOOLS.

                    • HAND_TOOLS node would be provided with subnodes - PLIERS and WRENCHES

                    • Subnode PLIERS is further provided with subnodes, CUTTING_PLIERS and ADJUST_JOINT_PLIERS.

                    • Click OK.

                    • Repeat this step for each subnode until the required hierarchy structure is in place.

                    • Add Products to the required subnodes.

                      • Click on Add button against the required subnode where product should be assigned.

                      • Change the mode to Product in the "Add Node" dialog to obtain option to select the products.

                      • Use the product value help to choose the required set of products to be assigned to the selected subnode.

                      • Click OK.

                      • Once the required set of products are assigned, save the product hierarchy version by clicking "Save" button

                      • After saving the product hierarchy version, user can click "Activate" to make the product hierarchy available for consumption outside the application.

                        • Unless the hierarchy version is activated, it is not available for consumption outside the application.

                        • An activated hierarchy version would have the status "Active" can be edited at later stages using the "Edit" option.

                        • Step 3: Updating an existing hierarchy version

                          Consider the scenario where user wants to update an existing product hierarchy version, then user can use the "Edit" button available in the details page of any hierarchy version. Once an active product hierarchy version is Edited, the version being edited would kept with status "In Revision" until it is activated again, the previous active version would be consumed by the business processes till the same hierarchy version is activated.

                          Few restrictions are introduced with respect to the the options available for adapting the hierarchy structure or deactivation/deletion of a product hierarchy version once it is consumed subsequent business processes like Product Hierarchy assignment to Distribution Chain.

                          How to consume product hierarchy in Sales

                          Refer to below two blogs to understand the usage of product hierarchy in Sales scenarios:

                          1. Using The Product Hierarchy Functionality in SAP S/4HANA Cloud 1911

                          2. How to Use Product Hierarchies in Design Studio or Web Dynpro Apps

                          3. EKT :EKT_ProductHierarchies.pdf