Describing Account Splitting

Objectives

After completing this lesson, you will be able to:
  • Illustrate the Account Splitting process
  • Use Account Splitting customizing

The Account Splitting Process

Introduction

The image explains the concept of Account Splitting in SAP Convergent Charging, detailing its functionality, business example, and features, including workload optimization and mapping table creation. It also mentions Account Merge as the opposite transaction.

In SAP Convergent Charging, the number of contracts for a dedicated subscriber account (business partner) is limited due to performance reasons. To get rid of this limitation, the new concept of alternative subscriber accounts is introduced when distributing the provider contract to SAP Convergent Charging to optimize workload distribution among SAP Convergent Charging raters. Each single provider contract in SAP Convergent Charging can now manage their own independent alternative subscriber accounts in SAP Convergent Charging.

Definition Shared SAP CC Tables – Agreement Tables

  • As a consequence, agreement tables are introduced as a new variant of SAP Convergent Charging tables. Agreement tables are mapping or range tables that are shared between multiple objects with a specific relation.
  • This relation can be a subscriber account identifier, so that all provider contracts with different alternative subscriber accounts belonging to one specific subscriber account can share the same table. Or, alternatively, the relation can be a master agreement ID, so that all provider contracts with reference to this master agreement can use the same agreement table.

As of SAP S/4HANA 1909, agreement tables are introduced as new variants of SAP Convergent Charging tables. Agreement tables are mapping or range tables, which are shared between multiple objects with a specific relation. This relation can be either:

  • A subscriber account identifier, so that all provider contracts with different alternative subscriber accounts belonging to one specific subscriber account can share the same table.
  • Or the relation can be a master agreement ID, so that all provider contracts with reference to this master agreement can use the same agreement table.

Account Split: Definition Shared SAP Convergent Charging Tables

  • As a consequence of account split, agreement tables are introduced as new variant of SAP Convergent Charging tables. Agreement tables are mapping or range tables that are shared between multiple objects with a specific relation.
  • This relation can be either a subscriber account identifier, so that all provider contacts with different alternative subscriber accounts belonging to one specific subscriber account can share the same table.
  • Or the relation can be a master agreement ID, so that all provider contracts with reference to this master agreement can use the same agreement table.
  • Manage SAP Convergent Charging tables using the application Manage Mapping/Range Table.
  • Create an agreement table for a specific business partner. The mapping table is created as the agreement table.
  • Search for SAP Convergent Charging tables (searching with a subscriber account finds agreement and subscriber tables; searching without subscriber account finds catalog tables and agreement tables for master agreements).
  • Use SAP Convergent Charging tables in Subscription Orders / Solution Quotations.
  • Assign catalog or agreement tables for the specific partner to subscription items.
  • Create a redefined SAP Convergent Charging table in a subscription order depending on the scenario (account split) as a subscriber or as an agreement table.
  • Use SAP Convergent Charging tables in the Master Agreement.
  • Create a redefined SAP Convergent Charging agreement table in a master agreement.

Features Account Split and Shared SAP Convergent Charging Tables with 1909

  • Identify Account Split.
  • Offer the customer the flexibility to define whether a mapping/range table is created as an agreement table (Customizing + BAdI).
  • Determine account split relevance during subscription order / solution quotation creation.
  • Pass account split information to subscription contracts, FI-CA provider contract and SAP Convergent Charging.
  • Manage SAP Convergent Charging tables via the application Manage Mapping/Range Table.
  • Create an agreement table for a specific business partner; the mapping table is created as an agreement table.
  • Search for SAP Convergent Charging tables (searching with a subscriber account finds agreement and subscriber tables; searching without a subscriber account finds catalog tables and agreement tables for master agreements).
  • Use SAP Convergent Charging Tables in Subscription Orders / Solution Quotations.
  • Assign catalog or agreement tables for the specific partner to subscription items.
  • Create a redefined SAP Convergent Charging table in a subscription order depending on the scenario (account split) as subscriber or as agreement table.
  • Use SAP Convergent Charging Tables in the Master Agreement.
  • Create a redefined SAP Convergent Charging agreement table in a master agreement.

As of SAP S/4HANA 2020, agreements tables are not used for contract specific redefined tables, because 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 number of agreement tables, which has a negative impact on the performance in SAP Convergent Charging. Therefore, SAP Convergent Charging 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.

Agreement tables can still be used as assigned tables, so that you can create one agreement table for a business partner, which can be used for all related alternative subscriber accounts.

This diagram illustrates the process of creating and replicating master data for a business partner with 10 subscription contracts, detailing the flow from Subscription Order Management (SOM) to Financial Contract Accounting (FI-CA) and Convergent Charging via web services. It shows the creation of contract accounts, provider contracts, and subscriber accounts.

Process Steps in Account Splitting

Account splitting is a performance optimization method for the rating of B2B business partner with a high volume of subscription contracts and a high volume of usage.

Preparation: Create a subscription order with a split in the subscription order item category. Alternatively, a BAdI can be implemented with customer-defined rules for splitting.

  1. Provider contract creation concatenates an additional field alternative subscriber account that consists of a business partner number and a Provider Contracts number.
  2. The Web Service interface to Convergent Charging creates an own subscriber account for each provider contract with an alternative Subscriber Account Number.
  3. Create 10 Subscriber Accounts with alternative Subscriber Account Numbers via the FI-CA Joint Master Data Distribution.
  4. Subscriber accounts are distributed to different raters for performance optimization in parallel processing.
The diagram illustrates the process of creating and replicating master data, starting from the creation of a Business Partner and Subscription Order in SOM, followed by the replication of data to Convergent Charging, involving Subscriber Accounts and Mapping Tables. Key steps include determining aSUAC, replicating aSUAC, and managing mapping tables through ODI.

Process Steps for Subscriber Mapping Table in Account Splitting

  1. Redefining a table in the order or quotation will always create a subscriber-specific table.
  2. Replicate Subscriber 4711 and create MT_4711. This table is created for the business partner (= subscriber account), as it is already the case if no aSUAC is in the game.
  3. A Subscription Contract is created, which is using the mapping table.
  4. A new ODI step is introduced before the contract is distributed to SAP CC. In this ODI step, the existing subscriber table will be deleted and recreated with the same ID using the aSUAC as subscriber account. Deletion is necessary, since the table IDs (even the subscriber table IDs) are unique within an SAP Convergent Charging system. In a change order, when the aSUAC is already known, you can create the subscriber table directly for the aSUAC.
  5. The Provider Contract is replicated to CC pointing to the subscriber-mapping table of the aSUAC.
The image illustrates the process of creating and managing a subscription order for account splitting, including the identification of the order, assignment of optional mapping tables, and creation of the subscription contract, with screenshots of relevant software interfaces. Key elements include the FI-CA contract, alternative subscriber account, CC provider contract, and mapping tables.

Account Splitting Customizing

The image shows instructions for maintaining custom logic via BAdI in SAP, with a screenshot of subscription-specific item category customization options. It highlights the Split column and provides details on the enhancement spot, BAdI definition, and sample class.
The image shows the SAP configuration path for the BAdI Determine Split for Subscriber Account in SAP CC (CRMS4_SOM_BADI_CC_ACC_SPLIT) and provides a brief description and example of its use in determining the indicator for subscriber account split in SAP Convergent Charging.

Log in to track your progress & complete quizzes

Learning

SAP FacebookSAP YoutubeSAP LinkedIn