Describing Shared Allowances

Objective

After completing this lesson, you will be able to describe Shared Allowances.

Business Example: Shared Allowances

Subscription Product BSU_CLOUD_SEL_ALLO includes a Payment in Advance model, which offers a prepaid scenario with a discount for the payment type. Customers can pay 100 Euro, 500 Euro, or 1,000 Euro in advance and get a bonus of 10%, 20%, or 25%. The amount paid in advance is in Convergent Charging (CC), calculated with an allowance counter.

Shared Allowances

The image explains that a shared allowance can be used across independent contracts with the same shared ID, managed via the Manage Sharing Groups app (F4432), and cannot be rerated. It also provides an industry example of sharing a payment in advance between different provider contracts in Convergent Charging.
The image outlines a three-step process for configuring subscription products in Fiori Launchpad: creating sharing and allowance groups, and performing cross-catalog mapping. Each step involves accessing specific apps and assigning groups to subscription orders and allowance products.
A flowchart illustrates the process of creating and managing shared allowances in SAP S/4HANA Service and Convergent Charging, detailing steps from creating a sharing group to consuming shared allowances across different subscription and provider contracts. Key components include subscription orders, contracts, and shared allowance assignments. The steps are explained in the following text.

Product Design for Shared Allowance – follow these eight steps:

  1. Sharing group creation. Create a sharing group as customer master data, for example, for Headquarter 02, if all allowances should be shared in this group.
  2. Create a subscription product with an allowance as a contributor product with Cross-Catalog Mapping (CCM) assignment of shared objects.

    A. Set Shared Objects = YES.

    B. Assign a Shared ID as a Parameter.

    The charge plan in Convergent Charging (CC) is a sharing charge plan.

  3. (Optional). Create a subscription product with an allowance as a consumption product of the shared allowance. The consumption product leaves out the shared allowance creation.

    It's also possible to create and consume with the contributor product runtime.

  4. Create a subscription order and a subscription contract as a contributor for the shared allowance in Sales Order Management (SOM).
  5. The shared allowance is created in SAP Convergent Charging.

    The shared allowance ID is a concatenation of the sharing group assigned in the subscription order and a created shared ID. In our process example, it's shared ID A123.

  6. Create a second subscription order, and assign the shared ID in this subscription order.
  7. A provider contract in SAP Convergent Charging is as a consumer provider contract is for the shared allowance.
  8. Consumption of all assigned provider contracts reduces the shared allowance.

Comparison of Scenarios

 Sharing ContractsShared Allowances
Shared ObjectsFocus is more on counters.

Focus is more on allowances.

Currently, Allowances can only count downwards.

CouplingTight Coupling during product modeling between sharing and shared product.Loose Coupling via Sharing ID, Assignment of Sharing Group ID during order/quotation creation.
Account Split / B2BIn SAP Convergent Charging, the subscriber account for sharing and shared contracts must be unique. In Subscription Order Management, different contract partners (payers) are allowed. They're merged artificially to the same subscriber account ID in SAP Convergent Charging (account merge).Account Split is supported as the allowance is only coupled via the share ID. The contracts are completely independent.
ReratingRerating is supported.Support of Rerating not available yet.

Learning

SAP FacebookSAP YoutubeSAP LinkedIn