Discussing Product Training Examples and Customizing

Objective

After completing this lesson, you will be able to discuss Product Training examples

Product Training Examples

A table listing various products with details such as product ID, type, category, transaction type, order item type, discount availability, configurability, and condition type. The products include subscription services, software licenses, hardware, and service contracts.

This figure shows an overview of possible product setups with technical information. All named products are also examples shown during our training system. It's important here to highlight the needed Product Type in combination with the item category settings. The condition type is related to the standard scenarios, so this can vary.

A table lists various products with details such as Product ID, MM Product Type, MM Item Product Category, Transaction Type, Order Item Type, CCM, Discount, Configurable, and Condition Type. The products include Sharing Child Product with Counter, Sharing Root Product with Counter, Product for Partner Settlement, Configurable Bundle Product for Cloud Services, and Master for Bundle Exercise.

This figure shows up an overview of possible product setups with technical information. All named products are also examples shown during our training system. It's important here to highlight the needed Product Type in combination with the item category settings. The condition type is related to the standard scenarios, this can vary.

Overview of the Product and Material Customizing

The image shows the configuration of material types in SAP, highlighting predefined product types SUBS for Subscription Product and SUBP for Subscription Partner Product, and indicating that product types for subscription products must have Type Group 3 Subscription.

You can define the attributes of each material type in the Implementation Guide (IMG):

SPROLogisticsGeneralMaterial MasterBasic SettingsMaterial TypesDefine Attributes of Material Types.

For subscription orders and contracts, two product types are predefined:

  • SUBS Subscription Product
  • SUBP Subscription Partner Product
The image illustrates the configuration steps for assigning product purposes to product types in a subscription management system, emphasizing that product and document purposes must align. It includes navigation paths, settings, and examples of product types and purposes.

You can maintain the settings to assign product type to product purpose in IMG:

ServiceMaster DataSettings for Subscription Master DataSubscription Product-Specific DataAssign Product Purpose to Product Types.

A product is classified using this product type, and the assigned product purpose defines for which business processes this product can be used. The following product purposes are available:

  • Standard Product: Standard product can be used in subscription orders or contracts. Products that are classified with a product type, for which no product purpose is defined, are always used as standard products.
  • Partner Agreement: Product Partner agreement products define the rules for distribution of revenue for third-party companies or partners if customers buy or consume services that these partners are involved in providing. Partner agreement products can only be used in partner agreements or partner agreement orders.

If you use products in a manner that the purpose derived from the document does not conform to the purpose derived from the product type, the system displays an error during document processing.

You can maintain the settings for document purpose in IMG:

ServiceTransactionsSettings for Subscription TransactionsDefine Settings for Transaction Types.

The image shows SAP configuration screens for defining types of identification and schema details, with navigation through the Service module to Technical Resources. The screens illustrate settings for Customer ID and IP Address identification types.

The resource type specifies the kind of technical resource, the source and uniqueness of the technical resource, and the stage in the subscription order or contract processing when it would be required.

The assignment schema defines which and how many resources of certain resource types can, or have to, be assigned to a contract using this schema.

The image shows the navigation path to BRF+ settings in an SAP system and a list of predefined BRF+ assignment definitions with sample BRF+ applications. The highlighted section includes various BRFplus application names and their corresponding texts.

There are assignments that are related to the maintenance of subscription product-specific data. All delivered applications are template BRFplus applications. If this template BRFplus application does not fit to your requirements, you can create and assign your own BRFplus application.

  • Discount/Charge Activation: Determine if a discount or charge is activated in a subscription order –CRMS4_SOM_PROD_DISC_CHRG.
  • Charge Plan Activation: Determine if a charge plan is activated in a subscription contract – CRMS4_SOM_PROD_CHARGE_PLAN.
  • External Object Activation: Determine if an external object is activated in a subscription order or contract – CRMS4_SOM_PROD_EXTOBJ.
  • External Object Date / String / Numeric Parameter Value: Determine the value of a date, string, numeric, or parameter of an external object – CRMS4_SOM_PROD_EXT_DATE_PARAM / CRMS4_SOM_PROD_EXT_STR_PARAM / CRMS4_SOM_PROD_EXT_NUM_PARAM.
  • Technical Resource Location: determine the location in the contract where the technical resource can be found – CRMS4_SOM_PROD_CP_TECRES.
  • Charge Plan Date / String / Numeric Parameter Value: You can determine the value of a date / string / numeric parameter of a charge plan – CRMS4_SOM_PROD_CP_DATE_PARAM / CRMS4_SOM_PROD_CP_STR_PARAM / CRMS4_SOM_PROD_CP_NUM_PARAM

Log in to track your progress & complete quizzes