on 2022 Mar 03 3:03 PM
Hello,
in general it should be possible to include a usage forecast in the billing forecast of Subscription Billing, as described here: https://help.sap.com/viewer/987aec876092428f88162e438acf80d6/2022-01-26/en-US/0d86630af3c5408e842c37...
It seems, that this only works if the usage is requested from an external system and not if the usage was entered manually e.g. via Fiori App "Usage"?
I tested it out by myself and
1. Created a backdated subscription based on a rate plan that includes (among others) usage based charges
2. Published some usage manually in the Fiori app for the last months
3. Performed a change on the subscription to trigger the creation of a new billing forecast
4. Requested the billing forecast via API call.
The resulting billing forecast only shows the recurring fees and the usage based fees have amount 0.00€ - see:
My question is now if it is not possible to get a usage forecast based on manually entered usage data?
Thanks and kind regards,
Fabio
Request clarification before answering.
Dear Fabio,
the scenario described by you is not supported for manually processing through user interfaces. The usages entered manually via Fiori App "Usage" are not considered during forecast generation. The usages can be created only by the action from the outside upon receiving Usage Forecast Request Event from Subscription Billing. Usage creation is achieved by sending POST request containing usages on /usage-records/$batch endpoint. Usually, this request is sent automatically by external system but can be sent also manually. For more details about the request, you can look on UsageRecord API documentation. In addition, be aware that while sending usages via endpoint, the used atomicityGroup must match the sequenceNumber from Usage Forecast Request Event.
Let us know if there is any further question from your side.
Best regards,
Peter
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
9 | |
3 | |
2 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.