In SAP Subscription Order Management, a subscription order represents a binding agreement with a customer. To be valid and processable, it must contain certain fundamental attributes. These include the specific Subscription product (A) being ordered, the Contract Start Date (D) which defines the beginning of the service and billing period, and the Bill-to party (E), which is the business partner responsible for payment. Without these three core pieces of information—what is being sold, when it starts, and who pays for it—a legally and systemically valid subscription contract cannot be established or processed for billing.

B. Payment term: This is typically derived automatically from the master data of the Bill-to or Payer business partner and is not a mandatory manual entry on the order itself.

C. Service recipient: This partner function is not mandatory. If a separate service recipient is not specified, the system defaults to using the sold-to party.

1. SAP Help Portal

SAP S/4HANA

Subscription Order Management

"Creating Subscription Orders": The official documentation outlines the creation process

stating that users must "add one or more products to your order" (confirming A) and maintain item details where the "contract start date and the contract end date" are key fields (confirming D). The determination of business partners

including the essential Bill-to party for invoicing

is also a prerequisite (confirming E).

2. SAP Learning Hub

Course BR235 - SAP Billing and Revenue Innovation Management - Subscription Order Management

Unit 2: Subscription Order: This courseware details the structure of a subscription order. It emphasizes that each order item must contain a product and that contract time-slice data

including the start date

is mandatory for defining the subscription term. It also clarifies the role of mandatory partner functions

where the Bill-to party is essential for the downstream billing process.

The Order Monitor in SAP Subscription Order Management provides an end-to-end view of the distribution status of subscription documents and their items. It is used to validate two primary distribution flows. First, it tracks the replication of the master data agreement, the subscription contract, to both SAP S/4HANA FI-CA (as a provider contract) and to SAP Convergent Charging for rating purposes. Second, it monitors the distribution of individual order items, such as one-off charges, to SAP S/4HANA Convergent Invoicing, where they are processed for immediate or subsequent billing. This ensures that all components of a customer's order are successfully provisioned in the relevant backend systems.

B: The subscription contract is distributed to SAP Convergent Charging for rating, not the preceding sales order document itself.

C: This option is incomplete. The Order Monitor tracks the distribution of contract data to both FI-CA and SAP Convergent Charging.

1. SAP S/4HANA 2020 Help Portal

Subscription Order Management

"Monitoring Subscription Documents": This official documentation states

"You use the order and contract distribution monitor to monitor the distribution of subscription orders... to the follow-up processes and systems

such as the creation of provider contracts in SAP S/4HANA and the distribution of these contracts to SAP Convergent Charging." This directly supports option D.

2. SAP S/4HANA 2020 Help Portal

Subscription Order Management

"Processing of One-Off Charges": The documentation details that one-off items in a subscription order are transferred to Convergent Invoicing. The Order Monitor tracks the status of all items

including these. It states

"The system creates a billable item for the one-off charge in Convergent Invoicing." This supports option A.

3. SAP Learning Hub

Course BR235 (SAP Billing and Revenue Innovation Management - Subscription Order Management)

Unit 6: "Monitoring and Troubleshooting". This courseware explains that the Order Monitor (Transaction FKKSOMOMON) is the central tool for checking the status of order items being sent to Convergent Invoicing and the resulting contract being sent to FI-CA and Convergent Charging.

In the integration between SAP S/4HANA Subscription Order Management (SON) and SAP Convergent Charging (CC), the complex pricing logic resides entirely within SAP CC. During the creation of a subscription order in S/4HANA, the system needs to reference this pricing logic. It does so by making real-time calls to SAP CC to fetch and display a list of available Charge Plans. Similarly, Mapping Tables, which are detailed components of the pricing logic within a charge plan, are also managed exclusively in CC. These objects are only displayed for selection or informational purposes in the S/4HANA UI but are not replicated or stored in the S/4HANA database.

B. Technical Resource: This is transactional data managed within the subscription contract in S/4HANA and is replicated to the provider contract in SAP CC.

C. Product: This is a core master data object created in S/4HANA and actively replicated to SAP CC as a chargeable item class.

1. SAP Help Portal for SAP S/4HANA 2020

"Subscription Order Management -> Integration with SAP Convergent Charging": This documentation details the integration architecture

explaining that pricing and charging models are designed in SAP CC. It describes how

during order capture in S/4HANA

a remote lookup is performed to display the charge plans available in the CC catalog for selection. This confirms the "display only" nature of Charge Plans.

2. SAP Help Portal for SAP S/4HANA 2020

"Product Master Data in Subscription Order Management -> Replicating Products to External Systems": This section explicitly states that products created in S/4HANA are replicated to SAP Convergent Charging as chargeable items

which invalidates option C.

3. SAP Help Portal for SAP Convergent Charging 5.0

"Application Help -> Core Tool -> Designing the Pricing Logic -> Charge Plan": This source defines a Charge Plan and its components

including Mapping Tables

as the fundamental building blocks of pricing logic configured within the CC Core Tool. This establishes them as CC-native objects

not S/4HANA data.

A Solution Quotation, upon acceptance by the customer, is typically converted into a Solution Order. The Solution Order then functions as an orchestrator, automatically creating the relevant follow-up documents in the corresponding SAP components based on the item categories within the quotation. For items representing a one-time sale of goods, a Sales Order (A) is created. For items representing recurring, usage-based, or subscription services, a Subscription Contract (B) is generated in SAP Subscription Billing. For items related to long-term or recurring services, a Service Contract (D) is created in the service management component. These documents represent the fulfillment and billing processes for the different components of the overall solution.

C. Sales Contract: This is a long-term outline agreement. The standard follow-up for a one-time sales item in a Solution Order is a transactional Sales Order, not a Sales Contract.

E. Solution Contract: This is not a standard, distinct document type created as a follow-up in Solution Order Management. The Solution Order itself is the orchestrating object for other specific contracts.

1. SAP S/4HANA Cloud Help Portal

"Manage Solution Orders": "Based on the items you enter in a solution order

the system automatically creates the relevant follow-up documents in the corresponding components. These can be sales orders

service orders

service contracts

and subscription contracts." This confirms that Sales Orders

Service Contracts

and Subscription Contracts are primary follow-up objects.

2. SAP Best Practices Explorer

Scope Item "Solution Order Management (1B9)" for SAP S/4HANA: The process overview and process flow diagrams for this scope item explicitly show the creation of Sales Orders

Service Contracts

and Subscription Contracts as the key follow-up documents orchestrated by the Solution Order

which originates from a Solution Quotation.

3. SAP Learning Hub

Course BR235 "SAP Billing and Revenue Innovation Management - Solution Order": Unit 2

"Solution Order

" details the process where a Solution Order creates follow-up documents. It specifies that sales items lead to sales orders

subscription items lead to subscription contracts

and service contract items lead to service contracts.

In the context of SAP BRIM, the Advanced Variant Configurator (AVC) is used to model complex, configurable subscription products. Dependencies (C) are the fundamental building blocks used to define the logic and relationships between product characteristics (e.g., preconditions, selection conditions, procedures). They are essential for modeling the structure of any configurable product. Variant conditions (A) are a specific feature used to determine the price of the product based on the options selected by the customer. This is critical in SAP BRIM for calculating recurring and one-time charges for subscription contracts. While BRF+ can also be used, dependencies are the primary and foundational mechanism for modeling.

B. BRF+: While AVC can integrate with BRF+ for very complex rules, dependencies are the more fundamental and standard feature for modeling the core configuration logic.

D. Service-Level Agreement: An SLA is a business contract defining service performance levels; it is not a technical feature within the Advanced Variant Configurator used for product modeling.

1. SAP Help Portal

SAP S/4HANA 2022

"Dependencies": "Dependencies describe the interdependencies between characteristics and characteristic values. They are used to control the configuration process and to make sure that the configuration is complete and consistent." This confirms dependencies are the core modeling tool.

2. SAP Help Portal

SAP S/4HANA 2022

"Variant Pricing in Sales Documents with Advanced Variant Configuration": "You can use variant conditions to define surcharges and discounts for a variant of a configurable material... When you configure the material in the sales document

the system uses the variant conditions to calculate the final price." This confirms the role of variant conditions in modeling the commercial aspect of the product.

3. SAP Help Portal

SAP S/4HANA 2022

"Products in Subscription Order Management": "You can use configurable products to offer your customers a product with different features (for example

different bandwidths for an internet contract). The product configuration is based on the Advanced Variant Configuration (AVC) engine." This establishes the link between BRIM (Subscription Order Management) and AVC.