The Account Split functionality in SAP Subscription Order Management (SOM) is a performance optimization feature designed for high-volume scenarios. When a single business partner accumulates a large number of contracts, it can cause processing bottlenecks. To mitigate this, Account Split automatically distributes new contracts across multiple, technically created "alternative" business partner accounts once a predefined threshold is met. This distribution of contracts into smaller bundles allows downstream systems, such as SAP Convergent Charging (CC) and Convergent Invoicing (CI), to process them in parallel, significantly improving overall performance and throughput for rating, billing, and invoicing.

A: The split is primarily triggered by a contract count threshold defined in customizing, not directly by the item category.

C: This function splits contracts among technical business partners for parallel processing, not the values of counters within SAP CC.

1. SAP Help Portal

SAP S/4HANA 2022

"Account Split": "To improve performance in high-volume scenarios

you can use the account split function to distribute the contracts of a business partner with a very large number of contracts to multiple alternative business partners. [...] The distribution of contracts to multiple business partners enables parallel processing of these contracts in follow-up processes

such as billing and invoicing in SAP Convergent Invoicing (FI-CA) and rating in SAP Convergent Charging (SAP CC)." (Path: SAP S/4HANA -> Enterprise Business Applications -> Sales -> Subscription Order Management -> High-Volume Scenarios in Subscription Order Management -> Account Split).

2. SAP Training Course BR235 (SAP Billing and Revenue Innovation Management - Subscription Order Management): Unit on "High Volume Scenarios" explains that Account Split is a key technique for handling customers with a massive number of contracts by distributing them across technical accounts to enable parallelization in follow-on processes.

In SAP S/4HANA Subscription Order Management (SOM), Cross-Catalog Mapping is the central configuration that links a commercial product from the sales catalog to a technical product in the master catalog. This mapping explicitly defines which rate plan, and consequently which specific charge plan(s) within that rate plan, should be activated in the backend SAP Convergent Charging system when a customer orders the commercial product. This mapping acts as the direct trigger for activating the correct charging logic for a new subscription.

A. BRF+ function: While BRF+ can be used for complex rule-based determinations, the fundamental link between a sold product and its charge plan is defined in cross-catalog mapping, not a BRF+ function.

C. Product model: The product model defines the structure and attributes of a product, including its potential rate plans, but it does not contain the mapping logic that triggers a specific one upon sale.

D. Resource assignment: This is a fulfillment step concerned with linking technical resources (e.g., a phone number) to a subscription, which occurs after the charge plan has already been determined.

1. SAP Help Portal

SAP S/4HANA for Subscription Order Management

"Cross-Catalog Mapping": The official documentation describes Cross-Catalog Mapping as the mechanism to map products from different catalogs (e.g.

sales to technical). It specifies that this mapping determines the rate plans to be used for the subscription

which directly controls the charge plan activation. (See section on Product and Master Data Management).

2. SAP Help Portal

SAP S/4HANA for Subscription Order Management

"Product Modelling": This documentation details how products are structured. It clarifies that the model defines the components of a product

but the activation logic for a specific sales scenario is handled by the mapping

not the model itself.

3. SAP Learning Hub

Course SOM100 - "SAP S/4HANA for subscription order management": Unit 3

"Master Data in Subscription Order Management

" explicitly covers the concept of cross-catalog mapping. It details how a sales product is mapped to a subscription product

and this mapping includes the assignment of a rate plan from SAP Convergent Charging

which is the trigger for the charge plan.

In SAP S/4HANA Subscription Order Management (SOM), the Technical Resource represents the unique, identifiable instance of a service or object being subscribed to. Each subscription contract item that requires provisioning is linked to a specific technical resource. For example, in a telecommunications contract, the unique phone number or SIM card ID is the technical resource. This same unique resource cannot be assigned to another active subscription contract item simultaneously, making it the object that must be unique across all items in the system.

B. Contract account: A contract account is a billing-related object that can be assigned to multiple subscription contracts and their items for a single business partner.

C. Business partner: A business partner is the customer, who can have numerous subscription contracts, each with multiple items. It is not unique per item.

D. Product ID: The product ID represents the item from the sales catalog (e.g., "Premium Subscription Plan"). The same product is sold in countless different contract items.

1. SAP Help Portal

SAP S/4HANA 2020

"Technical Resources": "A technical resource is a uniquely identifiable object that is required to use a subscribed service. [...] You can create technical resources for each subscription contract item." This statement confirms that the technical resource is the unique object linked at the item level.

2. SAP Help Portal

SAP S/4HANA 2020

"Structure of a Subscription Contract": This document outlines the contract structure

showing that the Business Partner and Contract Account are at the header level

shared by all items within that contract

and therefore cannot be unique per item. The Product is at the item level but is not a unique instance.

To generate follow-up documents from a Solution Quotation, two key steps are required. First, the quotation must be commercially accepted by the customer, which is recorded in the system by setting the status to 'Accepted' (D). This action confirms the customer's agreement and makes the quotation eligible for fulfillment. Second, the individual items within the accepted quotation must be 'Released' (B). This release action is the technical trigger that initiates the orchestration process, creating the corresponding follow-up documents (such as sales orders, service orders, or provider contracts) in the relevant backend systems.

A. Submit the quotation: This is a preliminary step to send the quotation to the customer for review; it occurs before acceptance and does not trigger follow-up document creation.

C. Create a Call Off: A call-off is a specific type of follow-up document, typically used against a contract, not a general prerequisite step for creating documents from a quotation.

1. SAP Help Portal

SAP S/4HANA

Solution Quotations: "When a customer accepts a solution quotation

you can create follow-up transactions

such as a solution order

from the solution quotation. The system copies the data from the solution quotation to the solution order." This confirms that acceptance is a mandatory prerequisite. (Path: SAP S/4HANA -> Sales -> Solution Order Management -> Solution Quotations -> Processing Solution Quotations).

2. SAP Help Portal

SAP S/4HANA

Solution Order: The process for creating follow-up documents is detailed in the context of the Solution Order

which is the direct successor to an accepted Solution Quotation. The documentation states

"Once a solution order is saved and the items are released

the system creates the follow-up documents in the connected components." This highlights the 'Release' step as the trigger. (Path: SAP S/4HANA -> Sales -> Solution Order Management -> Solution Order -> Processing Solution Orders).

3. SAP Learning Hub

Course BR245 (SAP Billing and Revenue Innovation Management - Solution Order Management): Unit 2

"Solution Quotation Management

" describes the process flow where a quotation is first accepted. Unit 3

"Solution Order Orchestration

" details how releasing items in the subsequent solution order triggers the creation of backend documents. The principle of acceptance followed by a release/trigger action is a core concept.

In SAP Subscription Order Management (SOM), when a change is initiated for an active subscription contract, such as modifying a product, the system generates a specific transactional document to manage this process. This document is called a Change Order. The Change Order captures all the details of the requested modification. Once the Change Order is submitted and processed, the system updates the original subscription contract to reflect the changes, ensuring a clear and auditable trail of all modifications made during the contract's lifecycle.

A. Change contract account: A contract account is a master data object used in FI-CA for billing and payments; it is not the transactional document generated for a product change.

B. Change contract: This is a description of the overall business process's outcome, not the specific name of the transactional document created by the system to manage the change.

C. Change sales order: While a subscription order is related to a sales document, the specific document type for managing modifications in SOM is a "Change Order," not a standard SD sales order.

1. SAP Help Portal

SAP S/4HANA

Subscription Order Management: "Change Processes for Subscription Orders". The documentation states

"When you make changes to an existing subscription contract

the system creates a change order. This change order contains the changes that you want to make to the subscription contract." This confirms that the "Change Order" is the specific document generated.

2. SAP Help Portal

SAP S/4HANA

Subscription Order Management: "Processing Change Orders". This section details the lifecycle of the change order document

from creation and validation to submission

which then triggers the update of the subscription contract. It explicitly refers to the document as a "change order".

The subscription order capturing process in SAP S/4HANA Subscription Order Management (SOM) is the phase where a sales or service agent creates the order in the system. The core activity is selecting a subscription product for a customer and then configuring the specific details of its associated rate plan. This includes defining the services, setting quantities, applying specific pricing conditions, and adding any one-time charges. This configuration step is fundamental to capturing the exact terms of the customer's subscription before it is submitted for fulfillment and contract creation.

A. Monitor order status: Monitoring is a subsequent activity performed after an order has been captured and submitted. It involves tracking the order's progress through its lifecycle stages (e.g., submitted, in fulfillment, completed).

B. Advise customer on services being offered: This is a pre-sales or sales activity that happens before or at the beginning of the order capture process. It is part of the customer interaction, not the system transaction itself.

C. Update order and contract status: Status updates are typically system-driven events that occur automatically as the order and subsequent contract progress through fulfillment and activation. This is a result of the process, not the capturing action.

1. SAP Help Portal

SAP S/4HANA Cloud

"Subscription Order Management (4I9)": The process flow for this scope item details the creation of a subscription order as a key step. This step explicitly involves "entering subscription-specific data such as the subscription start date and contract duration" and configuring the items based on the product's rate plan. This directly supports that configuration is the central activity. (Search for "Process Flow for Subscription Order Management (4I9)" on help.sap.com).

2. SAP Help Portal

SAP S/4HANA Cloud

"Manage Subscription Orders" App Documentation: This documentation describes the user actions within the Fiori app. The primary function when creating a new order is to add products (which contain rate plans) and configure the line items

including pricing

dates

and technical resources. This aligns perfectly with "Configure rate plan and its services". (Search for "Manage Subscription Orders" on help.sap.com).

An allowance group definition serves as a template that specifies the properties and rules for a set of allowances. The primary process directly triggered by this definition is the creation of allowance instances. When a subscription contract is created in SAP Subscription Order Management (SOM) and includes a product linked to an allowance group definition, the system automatically instantiates the corresponding allowances for that specific contract. This creation process reads the definition to determine the type, validity, and quantity of allowances to be generated for the subscriber.

A. Expiration of allowances with contract cancellation: Expiration is a subsequent lifecycle event triggered by the contract cancellation process itself, not by the initial allowance group definition.

C. Change of allowances with contract change: A contract change process is the trigger for modifying allowances. The definition is used as a blueprint for the change, but it is not the trigger.

D. Activation of allowances with contract activation: Activation is a status change triggered by the contract becoming active. The allowances are typically created before this step and then activated.

1. SAP Help Portal

SAP S/4HANA

Subscription Order Management

Allowances

Allowance Creation and Activation: "When a subscription contract is created

the system creates the corresponding allowances for the contract items to which an allowance definition group is assigned. The system uses the allowance definition group as a template for creating the allowances." This statement directly confirms that the creation process is initiated based on the assignment of the definition group during contract creation.

2. SAP Learning Hub

Course SOM100 (SAP Subscription Order Management)

Unit: Allowances: The course material explains that allowance definition groups are master data used to model allowances. It details the process where

upon the creation of a subscription contract

the system generates allowance instances based on the assigned allowance definition group

linking them to the contract.

In the SAP organizational model, particularly for sales scenarios as used in Subscription Order Management (SOM), organizational units (such as a sales organization) are defined by specific attributes that control their behavior and responsibilities. The Division is a key attribute that specifies the product lines or business areas for which the sales unit is responsible. Currency is another standard attribute that can be maintained for an organizational unit, often used for statistical reporting and local processing within that unit. These attributes are directly maintained on the organizational unit master data.

B. Service Level Agreement: SLAs are related to service contracts and performance targets for service processes, not a direct master data attribute of a sales organizational unit.

D. Company Code: A sales organization is assigned to a single Company Code. This is a fundamental structural link in the enterprise structure, not an attribute maintained on the organizational unit in the same manner as Division or Currency.

1. SAP Help Portal

SAP S/4HANA

Organizational Model: The official documentation describes the structure and maintenance of the organizational model. It details that for the "Sales" scenario

attributes such as Division (DIVISION) and Distribution Channel (DISTRCHAN) are assigned to organizational units to define the sales area. Currency (CURRENCY) is also listed as a possible attribute. The link to the Company Code is established as a functional assignment

not a general attribute. (See documentation for Organizational Management in SAP S/4HANA for customer management).

2. SAP Help Portal

SAP S/4HANA

"Setting Up the Organizational Model": This guide explains the process of creating organizational units and assigning attributes using transactions like PPOMACRM. The documentation explicitly shows "Division" as a standard attribute for the sales scenario. It also confirms that while a sales organization must be linked to a company code

this is a different type of assignment than the attributes on the "Attributes" tab.

SAP Billing and Revenue Innovation Management (BRIM) is a solution designed for high-volume, consumption-based business models. Its core processes focus on the entire lifecycle of subscriptions and usage-based services. The "Manage Subscription" process is handled by the Subscription Order Management (SOM) component, which manages contracts and subscriptions. The "Calculate Price and assign Charge" process is the primary function of the SAP Convergent Charging (CC) component, which performs real-time rating and charging of service usage events against a customer's subscription plan. These two processes are fundamental to the BRIM solution's purpose.

A. Manage Material Management: This is a core process of the SAP S/4HANA Materials Management (MM) module, focusing on procurement and inventory, not a primary concentration of the BRIM solution.

C. Manage Sales Order: This refers to the traditional sales process for physical goods, managed by the SAP S/4HANA Sales and Distribution (SD) module, distinct from BRIM's focus on subscription orders.

1. SAP Help Portal

SAP Billing and Revenue Innovation Management

"Solution Overview": This document outlines the key components of the BRIM solution. It explicitly describes Subscription Order Management for managing customer contracts and Convergent Charging for "calculating (rating) and determining the price (charging) of services." This directly supports options B and D.

2. SAP Help Portal

SAP Billing and Revenue Innovation Management

"Subscription Order Management": This section details the business process for managing the complete lifecycle of subscriptions

from creation to modification and cancellation

confirming that "Manage Subscription" is a core BRIM process.

3. SAP Help Portal

SAP Billing and Revenue Innovation Management

"SAP Convergent Charging": This documentation specifies that Convergent Charging's role is to "implement pricing and charging logic" and "calculate charges" for service usage

directly validating the "Calculate Price and assign Charge" process.

In the SAP Billing and Revenue Innovation Management (BRIM) solution, the master data for a customer's service agreement is managed in SAP S/4HANA as a Subscription Contract. When this contract is created or changed, it is distributed to downstream components. The replication process creates a corresponding Provider Contract in both SAP Convergent Invoicing (CI) and SAP Convergent Charging (CC). The Provider Contract in SAP CC contains the specific charging information, such as identifiers for charge plans, which is necessary for the system to rate and charge for service usage. Therefore, the Provider Contract is the object that is created and maintained in SAP Convergent Charging as a result of replication from S/4HANA.

B. Subscription order: This is a transactional document that precedes the contract. It initiates the creation of a contract but is not the master data object replicated for ongoing charging.

C. Partner agreement: This term is not the standard object used for replicating customer charging data from S/4HANA to Convergent Charging in the core BRIM process.

D. Subscription contract: This is the source object in SAP S/4HANA. The object created in SAP Convergent Charging as a result of the replication is the Provider Contract.

1. SAP Help Portal

SAP S/4HANA (2020)

"Integration of Subscription Order Management with Convergent Charging": This official documentation states

"When a subscription contract is created or changed in Subscription Order Management

the contract is distributed to the connected systems. A provider contract is created in SAP Convergent Charging and SAP Convergent Invoicing." This confirms the creation of a Provider Contract in CC.

2. SAP Help Portal

SAP Convergent Charging 2020

"Core Tool > Data Management > Customer Master Data > Provider Contract": The documentation defines the Provider Contract as the central customer master data object in SAP CC. It explicitly mentions that "A provider contract is created in SAP CC when a business partner subscribes to a service or a product proposed by the service provider. The provider contract is sent by a CRM application or another provisioning system connected to SAP CC." In this context

S/4HANA is the provisioning system.