In cloud service business, new sales products are new combinations of basic products. These are typically bundles containing several products. For example, you're selling a product bundle containing Data Storage for Data Service Storage, with one-time installation service fee, and a yearly recurring insurance fee. Another example is, you're selling a product bundle containing Hardware, installation service from a technician, a Support Contract, and a recurring insurance fee.
Explaining the Bundle in an Overview
Objectives
After completing this lesson, you will be able to:
- Define product bundles.
- List and explain product bundle features.
- Describe the sales bundle.
- Explain the contract bundle.
- Define the customizing for bundles.
Business Example: Product Bundle Definition
Product Bundle Definitions
In our training, the main Product Bundles will be our Cloud Service Selection Product, BSU_CLOUD_SEL_SERV and our Notebook Care for your package, BSV_NOTEBOOKS_C4U.
Product Bundle Features
Product Bundle Features
The product bundle features are as follows:
- Add product as a component to the bundle. A pop-up shows the product search to select the products to add. Each of them will become a sub-item in the order.
- Products of a group are alternatives: they appear in a dropdown box. One product can/must be chosen at runtime.
- An optional product can be selected or deselected by the customer.
- The validity period can be maintained.
- BRF+ rules and prerequisite products can be defined. Prerequisite is a qualifier for this product. It can be a product or a group.
- Language dependent descriptions for the components can be maintained, which are only valid for the bundle.
The first step to creating a bundle product is to define the product type, sales bundle, or subscription bundle.
In the second step, the master data is created with all relevant attributes and conditions.
The last step is the bundle explosion in the subscription order or in the solution quotation, with creation of all defined subitems within the bundle.
- Bundles are modeled in SAP S/4HANA for Service. They're not specific for subscription order management but are also used by service management.
- The single bundle components must already exist as product masters in SAP S/4HANA product master.
The Sales Bundle
In our training, our sales bundle is a Notebook Care for your package, BSV_NOTEBOOKS_C4U.
Results:
- The bundle product is not taken over to the contract.
- Each sub-item with a subscription product will become an independent subscription contract.
- One-off items will not be taken over to the contract.
To distinguish between the sales bundle and the contract bundle, the corresponding item category needs to be maintained.
Our example has item category SRVP, the item category for Solution Quotation.
Example of a product structure:
In this case, the bundle is the container for each product. You can either define a price on bundle product level or the price is determined by the selected products. This product example is used for the solution quotation, where you can sell hardware-, services-, and contract-relevant items in one order. Resulting from the shown bundle, each item triggers a transaction type. Prices are defined for each product.
The Contract Bundle
In our training, our Contract Bundle is a Cloud Selection Service, BSU_CLOUD_SEL_SERV.
Example of a product structure:
In this case, a bundle is the container for each product. You can either define a price on bundle product level, or the price is determined by the products selected.
Configurable products can be used for each type of product and on each level of granularity. This means, that it's also possible to have multiple configurable products within one configurable root product.
You can define the price for the configurable product, either in a fixed way on root level or by calculating it using the configuration of the product.
The interlinkages can be used for either bundling or for process products. Process products will automatically be recognized by the system if all constraints for it are fulfilled. Accordingly, there's the possibility to map specific requirements just for certain transactions in the system, like activation fee for certain products, and so on.
Customizing for Bundles
Before similar sales components can be put together to be used as alternative products in a bundle, the component group has to be created:
SPRO→Service→Master Data→Products→Product Bundles→Define Component Groups for Product Bundles.
Product type defines certain attributes of a product and has some control functions. Before products of a certain product type can be used as a bundle, the corresponding product type must be defined.
SPRO→Service→Master Data→Products→Product Bundles→Define Product Types for Bundle Products.
A product role is used to distinguish between several types of products for product bundling, (Sales Package, Subscription Bundle):
SPRO→Service→Master Data→Settings for Subscription Master Data→Subscription Product-Specific Data→Assign Product Roles to Product Types.