LS Brim Onprem PPT en 09

BRIM S/4HANA
Subscription Order Management –

Live Sessions
SAP S/4HANA for billing and revenue innovation management
Subscription Order Management
in S/4HANA Service (S/4HANA 2020 FSP00)
PUBLIC
Main Feature Overview 2020 FSP00
▪ Managing Recurring Fees in SAP Convergent Charging

▪ Supporting Price Version
▪ Autorenewal of Subscription Contracts
▪ Device as a Service (DaaS) - Equipment Integration
▪ Contract Changes with Payments in Advance
▪ Dependent Items
▪ Account Split and Subscriber Tables
▪ Solution Quotation API
▪ Product Distribution for Subscription product-specific data
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Recurring Fees in SAP CC
Key Facts Recurring Fees in SAP CC
Definition
Recurring fees can be managed either via CI Billing Plans or via SAP Convergent Charging. This is
especially required for scenarios with a complex logic for the recurring fee.
Features
▪ Transfer price data for SAP CC using Data Replication Framework (DRF)
▪ Create and update price tables in SAP CC
▪ Create subscription orders / solution quotations with recurring fees
▪ If required maintain manual recurring fees
▪ Derive CC price table or create CC price table (entry) in case of manual fees during contract
distribution
▪ SAP CC can now create recurring fees and pass them to Convergent Invoicing for further
processing

Process Steps for Recurring Fees in SAP CC
Master Data Set Up Price Replication Contract Processing &

Distribution
 Create price table class  Define condition types to be  Create subscription order / solution
 Create charge plan with recurring fee replicated in customizing quotation using a product with
and price key parameter  Replicate prices to CC using DRF recurring fees in CC
 Create Subscription Product Framework  Optional maintain manual price
 For configurable Products Create  Price tables in CC are created  Release / accept and receive
Product Model Contract
 Assign Condition Type or Variant  Price table key is determined
Key Alias to price key in Cross or in case of manual fee price table
Catalog Mapping (entry) is created in CC
 Create prices for recurring fees or  Price table key is assigned to
variant prices contract
 Contract is distributed to CC
 Recurring fees can be determined
via price table / price key during
Charging in CC

Master Data Set Up SAP CC:
Sample for Defining a Charge Plan for Recurring Fees in CC
Define a charge including the pricing macro and assign it to a
1 Define a mapping table class of name “Price Table” 3 charge plan
2 Define a pricing macro with a mapping table

of mapping table type price table
Use this charge plan during cross catalog

4
mapping in subscription product specific data

Master Data Set Up: Subscription Product Specific Data
Price Key Assignment in Charge Plan Mapping
Charge Plan
Price key parameter in charge plan and charge interface
Price key parameter Condition Variant

can be defined as a Type can be Condition
part of the charge plan assigned Key Alias
interface in CC can be
assigned
Prices are replicated as agreement tables to SAP CC
Price key is a
reproducible
hash Key
based on
Condition
One Agreement Table per Product in CC Table and
Table Key
Contract with base fee and variant price

Contract with Manual Price
Note:
When working with manual prices in
combination with list prices, you
need to model the different recurring
fees in two charge plan mappings in
CCM. Nevertheless, you can use the
same charge plan.
Manual prices are stored in generic

agreement tables, which are
determined by an algorithm which
agreement table to use for which
contract. The number of required
agreement tables can be defined in
customizing.
Pricing: Price Version
Key Facts Price Version
Definition
Price versions support the management of price lifecycles of long running contracts and are used
for recurring fees. Especially when working with CC price data is read with the actual date (volatile
pricing) as always the latest prices are replicated to CC.
Behavior without price versions:
▪ Price 10$ is maintained for 2019, starting from 2020 Price will be 11$, all contracts using this
price table in CC will get more expensive starting from 2020.
Price versions support own life cycle management of prices depending on the time of contract
creation or contract change.
Use Cases
▪ Use Case 1 - Stable Prices dependent on contract start time:
Price is 10$ with key version 1 starting from 2019, new contracts starting from 2020 shall have
the price 11$, so a new price with version 2 is created with 11$ and new contracts will find price
table key for version 2
▪ Use Case 2 - Restricted price update without change process:
All contracts already started in 2019, prices for these contracts shall be raised to 13$ starting
from mid of 2020, but all contracts from 2020 (with price version 2) shall be untouched. Without a
change process, the price for price version 1 can be updated e.g. from 30.6.2020 to 13$. So
already for July, these contracts will be billed 13 $ instead of 10$.

Key Facts Price Version
Features
▪ Assign price version in subscription product
▪ Prices supporting price versions are available as a new condition table for pricing
▪ Access sequence of the pricing procedure of PSMB is enhanced
▪ Prices can be replicated to CC via DRF as normal recurring fees
▪ If price with price version is found during pricing this price will be used in order / quotation and
Contract
▪ CI Billing Plans work as used with the billing plan line item fee derived from the subscription item
price, which can also be based on the price with a price version as a key field

Price Version in Subscription Product Specific Data

Auto Renewal
Key Facts Auto-Renewal
Definition
The auto-renewal feature extends a Subscription Contract automatically for a defined
period beyond the current contract expiration date.
It is a mechanism by which the execution of the change process ‘Contract Extension’
can be performed without user intervention.
Features
▪ Define Autorenewal behavior in subscription product
▪ Define Autorenewal behavior in subscription item
▪ Extend your subscription contracts automatically via background monitoring
▪ Auto-renewed contracts shall only cease when a termination or cancellation is
requested for

Auto-Renewal Overview
Subscription Contract
Validity: 01.01.2019 – 31.12.2020 (2 Years) or
01.01.2019 – 31.12.9999
Term: 01.01.2019 – 31.12.2020 (2 Years)
Subscription Contract
Validity: 01.01.2019 – 31.12.2019 (1 Year) or Time-slice 1

Auto-renew
01.01.2019 – 31.12.9999 (Evergreen) Validity: 01.01.2019 – 31.12.2019
Term: 01.01.2019 – 31.12.2019 (1 Year) Term: 01.01.2019 – 31.12.2019
Time-slice 2
Validity: 01.01.2020 –
Term: 01.01.2020 – 31.12.2020

Auto-Renewal attribute on Product
▪ (blank) – No auto renewal by default, user shall be able to change the indicator on the Subscriber Order or Solution
Quotation or Subscription Contract
▪ 1 – auto renewal will be set to true by default, user shall be able to change the indicator
▪ 2 – no auto renewal allowed for the product, user shall not be able to change the indicator
▪ 3 – auto renewal shall be mandatorily set, user shall not be able to change the indicator
Based on these indicators, subscription orders/ solution quotations and subscription contracts have been designed to work
in a specific way to support auto-renewal.

Auto-Renewal attributes on Subscription Item
Assignment Block on Subscription Item in

Subscription Order and Solution Quotation
Auto Renewal Indicator enabled/disabled based

on attribute on Product. Persisted on
CRMS4D_SERV_I.
AR_PERIOD – can be populated based on

default value from the Date Profile. Available for
user to change.
AR_EXTENSION – set to Default Extension

Period from the Product when Indicator is set.
Available for user to change. Possible values are
the 3 Extension Periods defined on the Product.

Auto-Renewal execution result
New time-slice is created with the

activation scheduled in the future
The Contract End Date is changed to

reflect the extension period.
In the case of evergreen contracts only
the End of Term shall be changed.

Change Auto-Renewal Indicator on active contract
New change process of type ISTF that allows the

change of the auto-renew indicator on an active
contract. No Change Order is created. The process
only affects the Subscription Contract. No change
is triggered to downstream objects.

Change Auto-Renewal Indicator on Product Change
New tab in the Product Change UI that allows the

setting of the auto-renewal attributes based on the
new product that is selected.

Device as a Service
Key Facts Device as a Service (DaaS)
Definition
Service Providers take a typical hardware device (such as a laptop, desktop, tablet, printer or
mobile phone), bundle it with a variety of services and software, and offer it to a customer
for a monthly subscription fee. It gives customers one contract and just one provider to hold
accountable.
Solution Quotations already

combine these services. In addition
equipment masters can be directly
linked to subscription items.
Features Device as a Service (DaaS)
Features
▪ Linking of equipment to subscription contracts
▪ Early Distribution
▪ Distribution and Activation based on equipment activation
▪ Billing Start Date based on equipment activation
▪ Equipment ID as Technical Resource
▪ Change Processes – Replace and Scale

Sample Product
Product that represents the Device

Subscription that results in a subscription
contract. The equipment ID(s) are to be
maintained against this item.
Product that represents the Device

Hardware that results in a Sales Order. The
relevant equipment are determined based
on the Serial Numbers that are assigned in
Delivery. Thus, determined equipment ID(s)
are to be maintained on the related
Subscription Item.
Product that represents a related

Subscription, that is dependent on the
Device, results in a subscription contract.

Equipment IDs on Subscription Item
New assignment block is available on the

subscription item for maintenance of equipment
ID(s).
Search based on serial number, reference

product etc. is possible.

Equipment ID as Technical Resource
It might be required for distribution of
equipment IDs to the CC contract, where it
can be used in the calculation of usage-
based charges.
To facilitate this, equipment IDs maintained
in the object list are copied to technical
resources and distributed to the CC
contract, if a resource type of category
equipment is configured for the product.
The technical resource type should be defined

with the category Equipment.
SPRO -> Service Transactions -> Settings
for Subscription Transactions -> Technical
Resources -> Define Types of Identification
Note: if for example serial numbers are
different from equipment IDs and are to be
used as technical resources instead
of equipment IDs then a BADI is available
Distribution and activation based on Equipment activation
Subscription contract will remain inactive until the

related hardware has been delivered and
activated.
This is achieved by using the ODI framework.
Equipment ID(s) may be determined based on
downstream processes such as delivery. Until
such determined equipment ID(s) are maintained
on the contract, the step will not be successfully
executed.
This step will not be successfully executed until a

particular status (e.g. At Customer) is set on the
equipment.

Billing Start Date based on Equipment Activation
The ‘Start of Billing’ date of the subscription

contract is mapped to the ‘Term From’ date of the
billing plan item.
The amount in the BIT that is generated will be
prorated based on the ‘Term From’.
Note: in 2020 release there will be a gap with

respect to RAR.

E.g. Equipment IDs maintenance on Contract upon Delivery
When serial numbers are assigned in a delivery and the

document is saved, then the event CREATED/CHANGED
for the object LIKP is raised
If equipment is created and activated when serial numbers
for a product are created, then during delivery it is possible
to identify the relevant equipment IDs.
By tracking back from the delivery, it should be possible to
identify the relevant Sales item in subscription order /
solution quotation.
If the products are structured in such a way that the Sales
item is a sub-item of a subscription item or vice versa,
then that Subscription item is the one on which
maintenance of equipment is required.
By registering an event receiver and leveraging the still
open for change subscription order or the new ‘Maintain
Equipment IDs’ change process, equipment IDs can be
maintained on the relevant subscription contract.

E.g. Equipment activation trigger to start Contract Activation
When equipment status is changed,

then the event CHANGED for the
object EQUI is raised.
If this equipment, which is changed, is
maintained in the object list of a
subscription contract, then potentially
depending on the status different
processes can be triggered on the
subscription contract.
In this example, the status ‘At
Customer’ is being checked for and if
it is set, an attempt is made to trigger
the ODI step of the relevant
subscription contract to start the
distribution and activation process.

Change Processes – Replace Equipment
This change process can be used to

change the equipment ID(s) on an active
subscription contract.
The Object List is shown in the Change

Process popup where the list of
equipment ID(s) can be maintained.

Change Processes – Scale Up/Down Equipment
This change process can be used to scale

the quantity of the equipment up or down on
an active subscription contract.
The Quantity and Object List views are

shown in the Change Process popup, where
the new Quantity and list of equipment ID(s)
can be maintained.
In the case of Scale Up, if the product bundle
contains a relevant sales product then in the
change order the sales product will be added
with the delta quantity.

Contract Changes with Payments in
Advance
Key Facts for Contract Changes and Payment in Advance
Definition
Subscription contract change processes are available to execute the contract changes when required.
It can happen that by the time of a contract change, BITs from a CI billing plan have been requested, billed
or even invoiced for the period that shall be changed e.g. in case of billing at start of period. Payment
processing might also have happened against those invoices.
CI provides the feature of reversing the BITs even if they are billed or invoiced. In CI the BITs have to be
reversed manually first for the affected period of the effective date and then the change process is
executed. This means if the change is done in the middle of the period, the BIT’s reversal would reverse
BITs for the entire period (month or year) and they have to be re-requested for the reversed period.
These process steps are automated from the change process execution in subscription order
management.
Features
▪ Run a contract change in the middle of a period for a contract for which payment in advance is
processed or even the invoice has already been created
▪ Trigger the automatic BIT reversal and recreation processes in combination with CI billing plans
▪ This is not supported with recurring fees in CC

Contract with advance payment w/o auto reversal and re-requesting of BITs
Without this process, the contract distribution fails if BITs are already created in a billing plan for the period the change affects.

Contract change with automatic reversal and re-requesting of BITs –
Sample Change of Quantity
Old BIT reversed New BIT for time New BIT for changed
before change time frame
Quantity 10
1.1. – 16.12 Quantity 10 Quantity 20
1.1. – 14.7. 15.7. – 16.12.

Dependent Items
Key Facts Dependent Items
Definition
Dependent items in SAP CI can now be used from subscription order management. Dependent
item types can be assigned to the subscription item via the subscription product and can be passed
to SAP CI for further processing. There they can e.g. be used to generate partner BITs when
working with CI billing plans.
Features
▪ You do not need a partner product and partner agreement if you work with CI billing plans
▪ Assign dependent item type to subscription product specific Data
▪ During Contract Distribution, the dependent item type is assigned to the billing plan
▪ CI can now derive the partner BIT based on the Depended item type

Process Steps for Dependent Item Types
Master Data Set Up Order / Quotation / Contract Transfer Billable Item Creation
Contract with CI Billing Plan
 Assign dependent item  Assign subscription  During contract transfer to  When recurring BITs are
type to subscription product for which a FI-CA dependent item type requested CI billing plan,
product specific data dependent item type is is assigned to billing plan CI recognizes the
maintained item dependent item type and
 Release / Accept creates the dependent BIT
 Create subscription
contract

Dependent Item Type Assignment in Subscription Product Specific Data
Assign dependent item type to subscription product

Subscription Contract and Billing Plan
A subscription contract using this product is

created
The billing plan item is created with the

dependent item type assigned to it

Billing Plan Requested BIT and Dependent Partner BIT
Original BIT from billing plan
Dependent BIT derived via dependent item type on original billing plan item

Subscriber Tables in Account Split
Key Facts Account Split with Subscriber Tables
Background 1909
When a customer is using the account split in S/4HANA 1909, only agreement tables are
supported. The reason for that is that there is a difference between the business partner and the
aSUAC. But at the time of creation, the aSUAC is not known. Therefore, only agreement tables
could be supported as they could be shared across subscriber accounts and are linked to the
business partner number.
Nevertheless, this was an object specific agreement table, which could not be reused for other
documents. Especially in a B2C or B2B2C case, this would lead to a huge amount of agreement
tables, which has a negative impact on the performance in SAP CC.
Changes with 2020

Therefore CC Tables, which are created as redefined tables from a subscription item during order
or quotation creation, are created as subscriber mapping tables instead of object specific
agreement tables even if account split is active.
Features
▪ When you redefine a mapping table in an order or a quotation, a subscriber specific mapping
table is created.
▪ If reusable tables shall be assigned it is still possible to assign an agreement table.

Managing CC Mapping / Range Tables for Redefined Tables
S/4 Product Sales
Manager Representative
Product App Master Agreement App Subscr. Order / Contract App

M/R-Table Maintenance App
(Redefinition of M/R-Table) (Redefinition of M/R-Table) (Redefinition of M/R-Table)
Already created
Agreement tables
can still be assigned
Catalog M/R Tables Agreement M/R Tables Subscriber M/R Tables
Independent if Account Split is active

M/R-Table Maintenance App or not during Redefinition from Order
/ Quotation Subscriber Mapping
Tables are created
Pricing Manager
CC
Solution Quotation API
Key Facts Solution Quote API
Definition
Solution Quotations can be accessed by external systems via an OData API.
Features
▪ Support of Variant Configuration Data for Subscription, Sales and Service Contract Items
▪ Provide Additional Fields in Subscription Item Interface
▪ Enable transfer CC Parameters and Mapping Tables
▪ Read Contract Number of FI-CA Provider Contract

OData Service
Solution quotations including subscription items

can be created via an OData service.
Service Name:
“API_BUS_SOLUTION_QUOTATION_SRV”
Meta Data:
GET
“/sap/opu/odata/SAP/API_BUS_SOLUTION_QUO
TATION_SRV/$metadata”
Test Environment
TA: /IWFND/GW_CLIENT Gateway Client

OData Service important segments for subscriptions
Subscription
Item Fields
Header
▪ A_BusinessSolutionQuotation
Subscription specific segments:
▪ to_SubscriptionContract (header and item)
▪ to_SubscriptionItem
▪ CC Parameters:
to_DateParameters,
to_NumericParameters, to_StringParameters,
to_TableParameters
Configuration
▪ to_Configuration
Price
▪ To_ A_BusSolnQtanItmPriceElement
With Transaction Gateway Builder you can deep

dive into the interface TA: SEGW Gateway Builder

Solution Quotation API in API Hub
API Hub:
https://api.sap.com/

API to Replicate Subscription Product
Specific Data
Key Facts Subscription Product-Specific Data Replication
Definition
Subscription product-specific data can be replicated to external systems.
Features
▪ Replicate subscription product-specific data to external applications using DRF

Replicate subscription product-specific data from an SAP S/4HANA system
to an external system
External Receiver
▪ The API SubscriptionProduct
ReplicationRequest_Out is based on
Send
Data the SOAP protocol.
S/4HANA ▪ To receive the data, an endpoint for

AIF Monitoring
this service must be implemented in
Namespace /CMSOM the external system.
Interface SBPROD_OUT
▪ Data outbound from SAP S/4HANA is
triggered via Data Replication
API DRF (Replication) Framework (DRF). DRF enables you
SubscriptionProductRepli
cationRequest_Out to replicate data from a source system
Retrieve Data
to one or more target systems
Replication Model
Subscription Product-Specific
SOM_PROD ▪ Messages sent are monitored using
Data Application Interface Framework (AIF).
On create / change /
initial load

Miscellaneous
Important Hints
SAP Help
▪ https://help.sap.com/viewer/ Product SAP S/4HANA
Enterprise Business Applications -> Service -> Subscription Order Management
Enterprise Business Applications -> Service -> APIs for Service
▪ https://help.sap.com/BRIM
BRIM Scenarios and Guides -> Integration Guide, Migration Guide, Product Page
API Hub
▪ API Hub: https://api.sap.com/
Application Component
▪ CRM-S4-SOM
Quick Sizer
▪ Quick Sizer : S/4HANA Service

Thank you.

LS Brim Onprem PPT en 09

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

LS Brim Onprem PPT en 09

Uploaded by

Copyright:

Available Formats

BRIM S/4HANA

Subscription Order Management –

▪ Managing Recurring Fees in SAP Convergent Charging

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4

Master Data Set Up Price Replication Contract Processing &

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

2 Define a pricing macro with a mapping table

Use this charge plan during cross catalog

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6

Price key parameter in charge plan and charge interface

Price key parameter Condition Variant

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10

Manual prices are stored in generic

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 13

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 14

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 16

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 18

Validity: 01.01.2019 – 31.12.2019 (1 Year) or Time-slice 1

Term: 01.01.2019 – 31.12.2019 (1 Year) Term: 01.01.2019 – 31.12.2019

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 19

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 20

Assignment Block on Subscription Item in

Auto Renewal Indicator enabled/disabled based

AR_PERIOD – can be populated based on

AR_EXTENSION – set to Default Extension

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 21

New time-slice is created with the

The Contract End Date is changed to

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 23

New change process of type ISTF that allows the

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 24

New tab in the Product Change UI that allows the

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 25

Solution Quotations already

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 28

Product that represents the Device

Product that represents the Device

Product that represents a related

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 29

New assignment block is available on the

Search based on serial number, reference

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 30

The technical resource type should be defined

Subscription contract will remain inactive until the

This step will not be successfully executed until a

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 34

The ‘Start of Billing’ date of the subscription

Note: in 2020 release there will be a gap with

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 36

When serial numbers are assigned in a delivery and the

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 37

When equipment status is changed,

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 38

This change process can be used to

The Object List is shown in the Change

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 39

This change process can be used to scale

The Quantity and Object List views are

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 40

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 42

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 43