SAP BRIM - Subscription Order Management Part 1 - 7 - by Geetanjali Verma - Medium

3/14/24, 4:18 PM SAP BRIM : Subscription Order Management Part 1/7 | by Geetanjali Verma | Medium
Sign in to Medium with Google
Arpita Biswas
biswasarpita@google.com
SAP BRIM : Subscription Order

ARPITA BISWAS
bis.arp1990@gmail.com
Management Part 1/7

Introduction and Master Data
Geetanjali Verma · Follow

21 min read · Feb 20, 2023
2 1
SAP Billing and Revenue Innovation Management is a business process

designed for subscription model businesses, where products are not sold
outright but rather the right to use them is sold. Initially managed outside of
SAP S/4HANA using SAP CRM, it now resides in SAP S/4HANA as of version
1809 FPS01. This process is similar to the telecom industry’s business model,
where consumers are charged a monthly fee for the right to use a telephone
service, regardless of usage, with actual usage being measured and billed in
the next billing cycle. This same model can be applied to other industries
that use this concept.
SAP Billing and Revenue Innovation Management, subscription order

management, uses SAP S/4HANA as its frontend system to connect
customers with services they purchase and use. While configurations from
SAP CRM-based SAP Billing and Revenue Innovation Management have been
utilized in the SAP S/4HANA-based version, there are ongoing improvements
https://medium.com/@vgeetanjali/sap-brim-subscription-order-management-part-1-7-a564ea62758f 1/31
in each SAP S/4HANA release to add new capabilities and accommodate

evolving business models like Device as a Service (DaaS) and Anything as a
Service (XaaS).
Master Data
Master data in SAP Billing and Revenue Innovation Management refers to

any data used in a business transaction and managed through the SAP Billing
and Revenue Innovation Management, subscription order management
process. This includes information on customers, vendors, contact persons,
billable accounts, and subscription products that do not frequently change
during the lifecycle of the process. If changes occur in master data, a
governance process is usually followed to ensure traceability and proper
validation. By not regularly changing master data, relevant data does not
need to be repeatedly entered since SAP Billing and Revenue Innovation
Management automatically copies it into related business functions.
In SAP Billing and Revenue Innovation Management, subscription order

management, the following master data is set up in detail:
Business partner
Contract account
Subscription products
1) Business Partner
A business partner in SAP Billing and Revenue Innovation Management is a
master data object that can represent different entities such as a customer,
vendor, contact person, employee, and organizational unit. SAP has defined
different roles for business partners to manage various business functions
and features independently, with the sold-to party being the unique and
usually nonmodifiable partner in any transaction. Other mandatory
partners in a transaction include the ship-to party, bill to party, and payer.
A business partner can have multiple roles, such as being a customer,

vendor, and contract partner, depending on their interaction in a
transaction. This enables a legal entity to be represented by a single business
partner in SAP Billing and Revenue Innovation Management. Business
partner roles define how the business partner interacts in each transaction,
such as the sold-to party being the entity for which the transaction is placed
and maintained, the end customer being the entity the service or product is
for, the vendor being the supplier of the goods, and the employee being the
person involved or responsible for the transaction at the company.
To configure business partner roles in SAP, it’s important to understand the

role of the sold-to party in a business transaction. The sold-to party
represents the customer or legal entity and is divided into three main areas:
general, sales, and company code data. The general business partner role
stores basic customer data, while the sales and distribution section stores
sales and company code data.
Setting up Business partner Functions
Before you can use business partner functions, you first need to activate
them. Once these functions are activated, the required fields in the business
partner views are activated. To activate business partner functions in SAP,
follow the menu path Cross Application Components -> SAP Business Partner ->
Activation Status for Functions.
Configure business partner roles
After setting up business partner functions in SAP, the next step is to

configure business partner roles. These roles define the function a business
partner takes on during a transaction and include related information that is
populated when creating a new business partner. There might be no need to
configure any new business partner roles where standard roles are already
provided by SAP.
To view standard roles or define new roles, follow menu path Cross Application
Components-> SAP Business Partner ->Business Partner ->Basic Settings -
>Business Partner Roles->Define BP Roles.
Assignment of Role Categories
Each business partner role is assigned to a role category, which groups

together specific types of business partner roles. This allows the same
characteristics to be assigned to business partner roles within the same
category and enables programs to use groupings internally. Role categories
can be defined as an organization, person, and/or group, and they help to
organize business partner roles. For example, there can be a business
partner role for each type of contact, but all are assigned to the same role
category for the company’s contacts.
Define Number Ranges
The next step in configuring business partners in SAP is to define number

ranges and groupings. A unique number range should be defined for each
category of business partners to easily identify them. Number ranges can be
numerical or alphanumerical and set to internal or external. Internal
number ranges are generated by the system, while external number ranges
can be entered manually by users or external systems if they fall within the
defined range and aren’t already used in the system. Number range intervals
are assigned to a business partner grouping, which cannot be changed after
assignment. The grouping determines the number range and helps keep
different types of business partners separated. Number ranges can be
defined in the menu path Cross Application Components ->SAP Business Partner
->Business Partner ->Basic Settings ->Number Ranges and Groupings-> Define
Number Ranges or using Transaction SNRO (Number Range Object
maintenance) with object BU_PARTNER.
Fields that need to be defined when creating a number range for business
partners. These fields include the two-character number that defines the
range, the lower and higher limits of the range, NR status (the number that
was last used in the range), and whether the range is internal or external. If
the range is external, then the number can be entered manually by the user
or an external system if it falls within the range and hasn’t already been used
in the system.
Define Groupings and Assign Number Range
Next, you can define the groupings and assign a number range that was
defined in the previous step. Grouping is a concept to enable you to organize
different sets of business partners together and follow the same numbering
scheme.
To define a grouping and assign a number range, go to menu path Cross

Application Components > SAP Business Partner > Business Partner > Basic
Settings > Number Ranges and Groupings > Define Groupings and Assign Number
Ranges. Here, you can create a new four-character grouping with a short
name and description and assign a number range that was defined
previously. The assigned number range will be inherited by the business
partners created with this grouping. The fields include Grouping, Short
name, Description, Number range, External, Int.Std.Grping, and
Ext.Std.Grping. You can assign a specific number range to multiple groups,

allowing for the sharing of the number range, and the internal or external
indication is inherited from the number range. Int.Std.Grping indicates the
use of an internal number range as the standard, and Ext.Std Grping
indicates the use of an external number range as the standard if no specific
number range is used.
Define Customer Account Group
To effectively manage customer accounts, it is necessary to define customer

account groups. A customer account group is a classifying feature that
groups together customer accounts based on specific criteria. An account
group determines the necessary screens and fields for entering customer
master data, the number range assigned to each account group, and the valid
partner functions that will be populated for each account group. An account
group should be defined for each type of customer that needs to be classified
separately. To define an account group, follow menu path Financial
Accounting ->Contract Accounts Receivable and Payable ->Customer Accounts -
>Master Data ->Preparation for Creating Customer Master Data-> Define Account
Groups with Screen Layouts (Customers).
You can also define the screen layout for each account group, indicating
which fields are required, optional, displayed, or suppressed. It’s
recommended to define the screen layout at the customer account group
level, but it can also be defined at the company code or dependent on the
transaction.
Define Number Ranges
To uniquely identify customer accounts, it is necessary to define number

ranges for each customer account group. Number ranges can be set to either
internal or external intervals. To define number ranges, follow menu path
Financial Accounting-> Contract Accounts Receivable and Payable ->Customer
Accounts ->Master Data-> Preparation for Creating Customer Master Data->
Create Number Ranges for Customer Accounts.
Assign Interval to Customer Account Group
After defining number ranges for customer accounts, the unique intervals
can be assigned to the customer account groups. Number ranges can be
shared across multiple account groups or have different ranges for different
customer groups. To assign a number range, follow menu path Financial
Accounting ->Contract Accounts Receivable and Payable-> Customer Accounts -
>Master Data ->Preparation for Creating Customer Master Data ->Assign Number
Ranges to Customer Account Groups. The system will prompt you to assign a
number range, and customers created with this grouping will inherit the
assigned number range.
The business partner setup and customer setup are related but different. A
business partner is a single entity with multiple roles, including customer
roles, which require an account with specific attributes. After setting up
business partner groupings and number ranges, and defining customer
account groups and number ranges, the next step is to complete the master
data synchronization configuration to ensure that customer data is updated
simultaneously with business partner data. It is possible to use the same

number range as the business partner being processed at this step.
2) Contract Account
A contract account is a master data entity used for generating invoices at the
contract account level. It represents a billable account and is where posting
data for contracts occurs. Every business partner requires at least one
contract account for billing and payments, but they can have multiple
contract accounts
The number of contract accounts for a business partner is determined by

several attributes, including company code (a separate contract account is
created for each legal entity), group company code (determines which
company codes can post to a contract account), payment terms (such as net
0 or net 10), auto pay (controlled by payment method information), account
determination ID (determines the general ledger account for transactions),
and tolerance group (defines tolerance values for payment differences).
If a customer’s contract requires different billable accounts (such as for a

company with four regions), then four contract accounts will be needed. In
order to create a contract account for a business partner, they must have the
MKK (Contract Partner) role. This role allows the business partner to see the
contract account(s) linked to them from their business partner view.
At the contract account level, the following data can be defined:
1. General data: Cross partner data, Account management data, Invoicing

settings, General remarks
2. Payments and taxes: Payment data, Taxes and tax exemption
3. Dunning and correspondence: Dunning control, Correspondence control,

Correspondence to other partners
To configure a contract account, the following steps should be taken:
Step 1 : Define the contract account class that is required to process business
relationships.[To define the contract account class, follow menu path Service->
Master Data ->Contract Account ->Define Contract Account Class, and add a
description (Text field) and country (Country/Region field) and Define the
internal and external number ranges] .
Step 2 : Maintain internal and external number range assignments in the class
to determine the correct contract account category during replication.
Step 3 : Maintain the number range, which can be numerical or

alphanumerical in nature and can be defined as internal or external. [To
create a number range, follow menu path Financial Accounting ->Contract
Accounts Receivable and Payable ->Basic Functions-> Contract Accounts ->
Number Ranges and Contract Account Categories-> Define Number Ranges]
Step 4 : Ensure that the contract account is set up to be used across both SAP
Billing and Revenue Innovation Management, subscription order management,
and SAP Convergent Invoicing.
Define Contract Account Parameters
Define Contract Account Class:
To define a contract account class, go to Service > Master Data > Contract
Account > Define Contract Account Class. Add a description and country.
Define the internal and external number ranges. The defined fields include
Contract Acct Class (name of the class), Text (description of the business
agreement class), Country/Region (setting for the country), Int. No. Range
(internal number range), Ext. No. Range (external number range), and CA is
usable for collective bills (indicates that the class is for a collective bill
business agreement and can be assigned to an alternative account).
Define Basic Settings
To define the basic settings for the contract account, you need to choose the
form of open item accounting that is active in the system, which can be FI-
AR, FI-CA Active, Mixed, or undefined. If you select FI-CA Active, then the
contract account is activated automatically. The basic settings can be defined
by following the menu path: Service > Contract Account > Define Basic Settings.
The fields to be defined include a description of the contract account active
indicator, dropdown values for the method of open item accounting that is
active in the system, options for shipping address derivation, the maximum
number of contract accounts displayed in the table, and an indicator for
whether the direct debit limit is activated for a specific period.
Define Correspondence Variant
The correspondence variant defines control parameters, such as execution

intervals and the charges schema, and is primarily used in SAP Convergent
Invoicing. It is maintained in SAP Billing and Revenue Innovation
Management, subscription order management. To set the correspondence
variant, go to Service > Master Data > Contract Account > Define Parameters for
Contract Account > Define Correspondence Variant. Click the New Entries
button to create new entries, and define the Correspondence Var and CV
Text fields. This value must be set to ensure that the replication of the
contract accounts from SAP Convergent Invoicing does not fail.
Maintain Correspondence Variant
Define Payment Method
To define payment methods for incoming and outgoing payments, you need
to go to the menu path SPRO ->Service ->Master Data ->Contract Account -
>Define Parameters for Contract Account ->Define Payment Methods Then, click
the New Entries button to create the entries for each payment method. The
defined fields include the key value for the payment method, the
country/region for which it is valid, a description of the payment method, the
direction (incoming or outgoing), whether payment is via a bank or a credit card
and if either is mandatory, whether the actual address needs to be present in
the business partner master record to use the payment method, whether
mandates are required (mandatory for direct debit), and the origination of the
values (manually created in SAP CRM or replicated from SAP ERP). These
values need to be aligned with corresponding values defined in SAP Convergent
Invoicing.
These values are essential during the creation of business agreements (

Contract Accounts) and must be synchronized with the corresponding
values defined in SAP Convergent Invoicing.
Payment Methods
Define Shipping Control
The shipping control allows for flexible document sending options, such as
dispatch method and archive method. Menu Path for Shipping Control SPRO
->Service ->Master Data ->Contract Account ->Define Parameters for Contract
Account ->Define Shipping Control.
Define Tax Types
The tax type can be set as the default during contract account creation. It
will be utilized to determine the accurate tax amount. Menu Path for Tax
Types SPRO ->Service ->Master Data ->Contract Account ->Define Parameters for
Contract Account ->Define Tax Types.
Define Tax Characteristics
Tax characteristics can be defined for contract accounts, which include

control characteristics that determine the account determination ID for a
contract account based on its tax characteristics and class. Tax
characteristics can be used to group customers according to their tax
requirements. To define tax characteristics, follow menu path SPRO ->Service
->Master Data ->Contract Account ->Define Parameters for Contract Account -
>Define Tax features
The two fields that need to be filled in are Tax Char., which defines the value
of the tax characteristic, and Text, which provides a description of the tax
characteristic. These fields are used to group contract accounts according to
their tax requirements.
Assigning Contract Account Class
After defining the contract account parameters such as tax types, tax
characteristics, and shipping control, these values can be assigned to the
contract account class. By doing this, the values will be automatically set as
default options when creating a contract account with the corresponding
class. Additionally, you can also assign the correspondence variant and
shipping control to the defined class. Menu Path for Assigning General
Parameters for CA Class is SPRO ->Service ->Master Data ->Contract Account ->
Creation of Contract Account ->Allocate General Parameters to New Contract
Accounts
Define Usage Type
The usage type for a contract account can be defined to determine whether
an item will use standard payment data or alternative payment data. This
setting determines how the system will determine payment data for ordered
items when a provider order is saved. The contract account class specifies
whether the contract account to be created will use standard payment data
or alternative payment data. The alternative payment data usage type is only
relevant when alternative payment data is entered during order entry. Menu
Path for defining Usage Type SPRO ->Service ->Master Data ->Contract Account
-> Creation of Contract Account -> Allocate Contract Account Class
The fields that need to be defined include Channel, which specifies the sales
channel used in the company, Usage, which defines whether standard or
alternative payment data is used for an item during order entry, Risk Class,
which determines payment-related business parameters of the contract
account, Contract Account Class, which specifies the values for the contract
account created with the payment data options, and Duplicate, which checks
for duplicate contract accounts. These fields ensure accurate payment data
usage and prevent duplication of contract accounts, leading to efficient sales
and payment processes.
The duplicate checkbox checks whether a business partner with identical values
already exists to prevent a duplicate contract account from being created.
3) Subscription Materials
The material master stores all the information needed to sell products or
services on a subscription basis. Think of it as a centralized hub for all the
necessary details about what is being sold. While it is traditionally used for
managing physical goods, it can also be used for intangible goods like
services or software.
Products can be tangible (like physical goods) or intangible (like services or

software). Subscription orders can handle both types of products — whether
they are hardware goods, software goods, or services.
Software goods/Service don’t need to be physically delivered, so they

don’t require delivery processing to complete billing.
To initiate billing for a service, a service confirmation is usually required.

However, in SAP Billing and Revenue Innovation Management for
subscription order management, no confirmation is needed. Service
goods are simply offered as a subscription service to fulfill the sales
order process.
Product Master:
The product master (also known as the material master) is a central

source of information for all the products that a company buys or sells
For subscription products, we can manage the terms of duration, billing

cycles, discounts, and charges, among other core attributes
Subscription-specific products have their own set of features, including

bundle and sharing products, product replication, and more
Subscription Specific Product Data:
Subscription products are classified based on their business purpose,

which supports their use in subscription orders, master agreements, or
partner agreement orders.
The system validates the product’s purpose in the transaction where it’s
used. For example, a standard product cannot be used in a partner
agreement order, and a sharing product cannot be used in a subscription
order or master agreement.
To align the product’s purpose with the right transaction type, it’s
important to classify them as follows:
a) Standard products: Used in subscription orders and contracts by default,

but cannot be used in partner agreements or sharing orders.
b) Partner agreement products: Used in partner agreements and orders

associated with vendors or partners, but cannot be used in other scenarios.
c) Master agreement products: Used in master agreements or in

subscription orders and contracts created from or referencing the master
agreement.
d) Sharing products: Used in sharing orders or contracts, but cannot be used

in master agreements.
Subscription products need to be classified based on their business purpose,

which determines where they can be used. Standard, partner agreement,
master agreement, and sharing products all have their own unique use cases
and cannot be interchanged. It’s important to correctly classify products to

ensure they can be used in the appropriate transaction type.
Menu path for subscription product purposes
SAP Customizing Implementation Guide ->Service ->Master Data ->Settings for

Subscription Master Data ->Subscription Product-Specific Data->Assign Product
Purpose to Product Types
Bundle Products
Products can be combined and sold together as an offering (e.g, subscription

software can be sold with support), or they can be offered as an option.
Bundle products can be maintained by using the SAP Fiori app called
Manage Product Bundles.
The products to be bundled should already be created and should exist as

individual products. The product bundle needs to have a Product Bundle ID,
and then the individual products are added to the bundle.
Create New Product Bundles
Maintaining Bundle Products
If the products always need to be sold together, select the Default checkbox.
If it’s an optional component of the bundle, select the Optional checkbox.
Before grouping products together as product bundles, we first need to

decide which types of products are allowed to be bundled together
This is done in the Customizing activity Define Product Types for Bundle
Products in the following menu path:
SAP Customizing Implementation Guide ->Service ->Master Data->Products -

>Product Bundles->Define Product Types for Bundle Products
Define Product Types for Bundle Products
Sharing Products
Sharing products can be used to manage usage sharing scenarios. This

feature is particularly useful for companies that want to offer their
customers a flexible way of sharing usage allowances across multiple
contracts or subsidiaries.
For instance, let’s say that ABC company is providing 100GB of storage space
per month to XYZ Limited. If XYZ Limited wants to allow its subsidiaries to
also share the storage space, the sharing concept can be used to manage the
process. This can be done by creating a sharing contract, also known as the
root contract, and then creating shared contracts, also known as dependent
contracts, that can share counters or allowances during the rating process
in SAP Convergent Charging.
Sharing products allows us to share usage allowances during the rating

process in SAP Convergent Charging by creating a hierarchical relationship
between different contracts. The root contract contains the shared counters
or allowances, and the dependent contracts inherit those counters or
allowances. This means that when usage data is rated for a dependent
contract, the counters or allowances of the root contract are taken into
account as well.
To use sharing products in SAP Bling and Revenue Innovation Management,

there are certain rules that need to be followed. In a sharing contract, only
subscription products with the product purpose of “sharing product” can be
used. This means that the product must be designated for sharing in order to
be used in a sharing contract.
In a shared contract, we can only assign a reference to a sharing contract if

the product used in the shared contract and the product used in the sharing
contract are allowed for sharing. This ensures that only the appropriate
products can be used in a shared contract.
Sharing products are defined as fees for the usage of counter sharing over
several subscription orders, with or without reference to a single master
agreement. They can be used in sharing orders or sharing contracts to allow
multiple parties to share usage allowances or counters.
SAP provides a standard material type called SUBC (Subscription Sharing

Product) to manage sharing scenarios. This material type can be used to
define the products that are allowed for sharing and to set up the necessary
contracts for sharing usage allowances. By using SUBC, companies can
streamline the process of managing sharing scenarios and ensure that the
appropriate products are being used in the right contracts.
In the Manage Subscription Product-Specific Data app, we define which

products can be shared under Shared Products.
Product Replication Using the Data Replication Framework

We can use Data Replication Framework (DRF) to copy information about

a subscription product to external systems
Before we can copy the information, the subscription product must

already exist in the target system before data specific to subscription
product can be replicated
There are different ways to copy the information, which are called
“communication channels.” The standard communication channels
available are: Services, IDocs, Files and Remote function calls (RFCs)
There are also different ways to set up the DRF to copy the information,
called “replication models”
The standard replication model and outbound implementation for

copying subscription product information is called SOM_PROD
To replicate data specific to a subscription product, the business object to

be used in the outbound implementation is DRF_0073
To configure the DRF and replication model, we use Transaction DRFIMG
Organizational Units
In SAP Billing and Revenue Innovation Management, setting up

organizational units is a critical step in defining a company’s structure and
business functions. The organizational model is composed of these units and
is a vital component of the master data setup, transactions, reporting, and
finance structure.
Organizational units in SAP Billing and Revenue Innovation Management

can include departments, groups, or teams, and are linked as a hierarchy to
display how each unit fits together. This hierarchy then creates the
organizational model of the company.
There are several options for linking organizational units in SAP Billing and
Revenue Innovation Management. These units, such as sales organization,
service organization, and sales office, can be defined in configuration if they
are not already defined. Not all levels are required, and new levels can be
created as needed.
Organizational units are defined in SAP S/4HANA Sales, and sales

organization, distribution channel, and division can be assigned to the SAP
Billing and Revenue Innovation Management organizational units. This
assignment is necessary for automatically determining organizational data
in transactions.
Open in app
An organization can be activated for several scenarios, enabling itSign up
to be a Sign in
sales organization and Search
a service organization at the same time. TheWrite
organizational model is time-dependent, and validity dates can be set to
allow for organizational changes in the future.
In addition, a business partner can be automatically created for an

organizational unit with the organizational unit role. This allows for better
management of business partner relationships and simplifies the process of
assigning business partners to organizational units.
The organizational model in SAP Billing and Revenue Innovation

Management is closely linked to the organizational management set up in
the sales area of SAP S/4HANA. This means that the organizational units in
SAP Billing and Revenue Innovation Management are based on the
organizational data defined in SAP S/4HANA Sales, such as sales office, sales
area, and distribution channel.
To create the organizational units in SAP Billing and Revenue Innovation

Management, the data from SAP S/4HANA Sales can be copied over. This
transfer of data can be done by running a program in Customizing. This
method is useful if you already have a system with the organizational model
set up in sales.
However, if you don’t have the organizational model set up in sales, you can
manually set up the organizational model in SAP Billing and Revenue
Innovation Management. This involves defining the organizational units and
linking them in a hierarchy to create the organizational model of the
company.
Regardless of the method used, setting up the organizational model in SAP

Billing and Revenue Innovation Management is essential for accurately
determining organizational data in transactions, reporting, and finance
structure.
To transfer the organizational units from the sales area of SAP S/4HANA to
SAP Billing and Revenue Innovation Management, you can access the
program by following the menu path Service -> Master Data -> Organizational
Management -> Data Transfer -> Copy SD Sales Structure. From there, select the
row of organizational units you want to copy to the service organizational
units and click Generate.
The organizational attributes in SAP S/4HANA can be mapped to the

organizational units in SAP Billing and Revenue Innovation Management,
allowing for more accurate data in transactions and reporting. Multiple
attributes can be mapped to a single organizational unit, such as combining
a sales office and sales group. However, only the organizational units can
have a counterpart in SAP S/4HANA, and this can be defined in customizing.
One way to link the sales organization in SAP Billing and Revenue Innovation
Management to the sales and distribution sales organization is by assigning
them together. This allows the sales organization to be automatically
displayed on service transactions, ensuring accuracy in organizational data.
To link sales organizations, sales offices, and sales groups in SAP Billing and
Revenue Innovation Management to sales and distribution, you can set
assignments in the Service node under Assignments of Organizational Units
to SD in the Organizational Management section. You need to click on the
relevant link, such as Assign Sales Organizations in Service to SD Sales
Organizations, Assign Sales Offices in Service to SD Sales Offices, and Assign
Sales Group in Service to SD Sales Group, and create new entries for each.
Additionally, you can assign the plant and storage location to service
organizational units in the Cross-Application Assignment of Organizational
Units section under Assign Plant and Storage Location to Service
Organizational Units. You need to create new entries for the relevant service
organization, plant, and storage location.
Written by Geetanjali Verma Follow
13 Followers
Learner
More from Geetanjali Verma
Geetanjali Verma Geetanjali Verma
SAP BRIM : Subscription Order SAP BRIM : Subscription Order

Management Part 3/7 Management Part 2/7
Transaction Types Configuration in SOM
19 min read · Mar 19, 2023 9 min read · Mar 19, 2023
Geetanjali Verma Geetanjali Verma
SAP BRIM : Subscription Order SAP BRIM : Subscription Order

Management Part 6/7 Management Part 7/7
Subscription Lifecycle Management Reporting and Analytics
10 min read · Mar 19, 2023 3 min read · Mar 19, 2023
See all from Geetanjali Verma
Recommended from Medium
Artturi Jalli Vaishnav Manoj in DataX Journal
I Built an App in 6 Hours that Makes JSON is incredibly slow: Here’s

$1,500/Mo What’s Faster!
Copy my strategy! Unlocking the Need for Speed: Optimizing
JSON Performance for Lightning-Fast Apps…
· 3 min read · Jan 23, 2024 16 min read · Sep 28, 2023
13.4K 159 14.1K 164
Lists
Staff Picks Stories to Help You Level-Up

600 stories · 820 saves at Work
19 stories · 518 saves
Self-Improvement 101 Productivity 101

20 stories · 1484 saves 20 stories · 1368 saves
Benedict Neo in bitgrit Data Science Publication Martin Heinz in ITNEXT
Roadmap to Learn AI in 2024 Modern Git Commands and

A free curriculum for hackers and Features You Should Be Using
programmers to learn AI It’s not 2005 anymore and git offers more
than just add, commit, push and pull. Let’s…
11 min read · 3 days ago · 6 min read · Mar 4, 2024
5.7K 74 1K 6
Gowtham Oleti Julie Zhuo in The Year of the Looking Glass
Apps I Use And Why You Should Average Manager vs. Great
Too. Manager
Let’s skip past the usual suspects like Explained in 10 sketches
YouTube, WhatsApp and Instagram. I want t…
10 min read · Nov 14, 2023 2 min read · Aug 11, 2015
19.1K 346 29K 303
See more recommendations

SAP BRIM - Subscription Order Management Part 1 - 7 - by Geetanjali Verma - Medium

Uploaded by

Copyright:

Available Formats

SAP BRIM - Subscription Order Management Part 1 - 7 - by Geetanjali Verma - Medium

Uploaded by

Document Information

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

SAP BRIM - Subscription Order Management Part 1 - 7 - by Geetanjali Verma - Medium

Uploaded by

Copyright:

Available Formats

3/14/24, 4:18 PM SAP BRIM : Subscription Order Management Part 1/7 | by Geetanjali Verma | Medium

Sign in to Medium with Google

SAP BRIM : Subscription Order

Management Part 1/7

Geetanjali Verma · Follow

SAP Billing and Revenue Innovation Management is a business process

SAP Billing and Revenue Innovation Management, subscription order

in each SAP S/4HANA release to add new capabilities and accommodate

Master data in SAP Billing and Revenue Innovation Management refers to

In SAP Billing and Revenue Innovation Management, subscription order

A business partner can have multiple roles, such as being a customer,

To configure business partner roles in SAP, it’s important to understand the

Setting up Business partner Functions

Configure business partner roles

After setting up business partner functions in SAP, the next step is to

Assignment of Role Categories

Each business partner role is assigned to a role category, which groups

Define Number Ranges

The next step in configuring business partners in SAP is to define number

Define Groupings and Assign Number Range

To define a grouping and assign a number range, go to menu path Cross

Ext.Std.Grping. You can assign a specific number range to multiple groups,

Define Customer Account Group

To effectively manage customer accounts, it is necessary to define customer

Define Number Ranges

To uniquely identify customer accounts, it is necessary to define number

Assign Interval to Customer Account Group

simultaneously with business partner data. It is possible to use the same

The number of contract accounts for a business partner is determined by

If a customer’s contract requires different billable accounts (such as for a

At the contract account level, the following data can be defined:

1. General data: Cross partner data, Account management data, Invoicing

2. Payments and taxes: Payment data, Taxes and tax exemption

3. Dunning and correspondence: Dunning control, Correspondence control,

To configure a contract account, the following steps should be taken:

Step 3 : Maintain the number range, which can be numerical or

Define Contract Account Parameters

Define Contract Account Class:

Define Basic Settings

Define Correspondence Variant

The correspondence variant defines control parameters, such as execution

Maintain Correspondence Variant

Define Payment Method

These values are essential during the creation of business agreements (

Define Shipping Control

Define Tax Types

Define Tax Characteristics

Tax characteristics can be defined for contract accounts, which include

Assigning Contract Account Class

Define Usage Type

Products can be tangible (like physical goods) or intangible (like services or

Software goods/Service don’t need to be physically delivered, so they

To initiate billing for a service, a service confirmation is usually required.

The product master (also known as the material master) is a central

For subscription products, we can manage the terms of duration, billing

Subscription-specific products have their own set of features, including

Subscription Specific Product Data:

Subscription products are classified based on their business purpose,

a) Standard products: Used in subscription orders and contracts by default,