SAP CC Allowance Debit Priority

[bkurti]

Hi CC team,

we have the following business scenario:

The customer can have one or more valid buckets (allowances) at the same time with the same validity start and end date. When a consumption request to debit the allowance is sent we must debit the allowances according to the order they were created.

For example:

chargeableItem-> price = 40

Allowance1 -> counter 800

Allowance2 -> counter 200

This chargeable request should debit only the counter of the first allowance in this case, and debit the second only when there is not enough credit on the first one. Even the "Sorting" Tab is maintained to sort the allowances based on the unique identifier it seems that when we send a chargeableItem via the chargeableItemCharge WS both allowances counters are depleted and we have the following situation:

Allowance1 -> counter 760

Allowance2 -> counter 160

How can we debit allowances according to a specific priority we have defined?

Thanks in advance!

Best regards,

Malbora

[bkurti]

The issue has been resolved.

[chetan_099]

Hello Malbora,

Would you be able tell what cause this issue? I have not experienced this error but what we have used was single allowance counter. Would like to understand this was resolved. thanks.

[bkurti]

hi Chetan,

it was a small mapping mistake in the allowance logic. I was not sending the updated value back to the charge, so the event sender was sending the same event to all other valid allowances by debiting them all. When the updated property value is equal to 0, nothing will be depleted from the other allowances counters.

Or then you have the second solution mentioned by Francois below, which does the same thing, but avoids sending the event to the other allowances when the updated property is equal to 0, so probably from the performance perspective is better as the other allowances are not checked anymore.

Best regards,

Malbora

[francois_thimon · Accepted solution]

Hi Malbora,

It seems that you're looking for the option named "Stop sending when the monitored property is lower than or equal to 0".
It's described in Core tool's guide, in the page about the "Allowance event sender" operator:
https://help.sap.com/docs/Convergent_Charging/c7120011d1c244168dc1f945a06f1350/c183cc88f0ac462d98c38...

The monitored property can either be a counter of the allowance itself (i.e., the bucket), or it can be an input property (e.g., the fee you need to debit).
For your current use case, you should consequently be able to use that, in order to debit allowances one by one, until you've collected the target amount.

Can you try that, and let us know if you need more guidance?

Best regards.

François
SAP Convergent Charging Support

[francois_thimon]

Hi Malbora,

There was an issue with my browser because, when I sent my reply, I hadn't seen the conversation with Chetan.
Anyway, thank you very much for your feedback and, yes, for future implementations, you'll probably be better off using the standard feature available in Core tool.
Feel free to ask for more guidance if needed.

Best regards.

François
SAP Convergent Charging Support

[bkurti]

Hi Francois,

thank you very much for your answer.

I have already resolved the issue. There was a small mapping mistake in the property value returned back from the allowance logic, that i had not noticed. As long as the updated remaining amount to be paid is equal to 0, the next allowance is not debited anymore, so everything works fine now.

The option you mention would also be a second possible solution. I was just curious why the first one was not working, but it was a mistake on my side 🙂

Kind regards,

Malbora