Welcome to our blog series about new features in SAP Subscription Billing, and if you're already following our blogs, welcome back!
This week we'd like to share with you a couple of features that were recently released: one-time charges based on quantities, and usage aggregation across rating periods. Let’s take a look at these features in more detail:
You can now define one-time charges based on the quantity of a product purchased. To do this, you use subscription parameters in subscription items when you configure your pricing model with pricing schemes.
Accordingly, in the Business Configuration API the following endpoint has been updated to support the data source subscription for rate elements of the type onetime: /config/Global/Metric/v1 (GET and PUT).
Find out more about this feature in our blog One-Time Charges Based on Quantities.
When you define your pricing model with pricing schemes, you can now configure aggregations for usage-based charges. Within one billing cycle, this allows you to aggregate usage data across multiple rating periods to determine the price for the billing cycle.
Find out how this feature works with a real-life use case in our blog Configure Aggregations for Usage-Based Charges.
The Manage Aggregation Catalog app is now available on the SAP Subscription Billing launchpad to support the configuration of aggregations for usage-based charges:
To support aggregations across rating periods within a billing cycle, new standard fields have been introduced: billingCycleStart, billingCycleEnd, ratingPeriodStart, ratingPeriodEnd, and subscriptionStart
Note: Standard fields are usually predefined when a new tenant is created. For existing tenants, we recommend that you create them manually.
In the Rate Plan Simulation API, the field subscriptionStart has also been added to the endpoint /simulations (POST) to support this feature.
That’s all on our latest features. Thank you for reading today’s blog post! ☁️
To make sure you don’t miss the next feature articles, follow the tag SAP Subscription Billing. And in the meantime, you can find out more about our solution in the information section below.
Also: Please like this post if you found it useful, and don’t hesitate to leave us your feedback in the comment section.
In case of questions, feel free to ask them in our Q&A section using the tag SAP Subscription Billing.
Stay tuned and take care!
Katherine
This week we'd like to share with you a couple of features that were recently released: one-time charges based on quantities, and usage aggregation across rating periods. Let’s take a look at these features in more detail:
One-Time Charges Based on Quantities
You can now define one-time charges based on the quantity of a product purchased. To do this, you use subscription parameters in subscription items when you configure your pricing model with pricing schemes.
Accordingly, in the Business Configuration API the following endpoint has been updated to support the data source subscription for rate elements of the type onetime: /config/Global/Metric/v1 (GET and PUT).
Find out more about this feature in our blog One-Time Charges Based on Quantities.
Usage Aggregation Across Multiple Rating Periods
When you define your pricing model with pricing schemes, you can now configure aggregations for usage-based charges. Within one billing cycle, this allows you to aggregate usage data across multiple rating periods to determine the price for the billing cycle.
Find out how this feature works with a real-life use case in our blog Configure Aggregations for Usage-Based Charges.
The Manage Aggregation Catalog app is now available on the SAP Subscription Billing launchpad to support the configuration of aggregations for usage-based charges:
New app Manage Aggregation Catalog
To support aggregations across rating periods within a billing cycle, new standard fields have been introduced: billingCycleStart, billingCycleEnd, ratingPeriodStart, ratingPeriodEnd, and subscriptionStart
Note: Standard fields are usually predefined when a new tenant is created. For existing tenants, we recommend that you create them manually.
In the Rate Plan Simulation API, the field subscriptionStart has also been added to the endpoint /simulations (POST) to support this feature.
That’s all on our latest features. Thank you for reading today’s blog post! ☁️
To make sure you don’t miss the next feature articles, follow the tag SAP Subscription Billing. And in the meantime, you can find out more about our solution in the information section below.
Also: Please like this post if you found it useful, and don’t hesitate to leave us your feedback in the comment section.
In case of questions, feel free to ask them in our Q&A section using the tag SAP Subscription Billing.
Stay tuned and take care!
Katherine
More Information About SAP Subscription Billing
- SAP Managed Tags:
