SAP CC allowance counters

[AravindVijayaraghavan]

Hi Team,

I would like to know in a scenario where we need to store values for multiple periods (for e.g. monthly counters) using allowances, what would be the recommended way of handling this? Manage multiple counters within a single allowance or create separate allowances by having less counters per allowance.

Regards,

Aravind

[Eric_F · Accepted solution]

Hello,

my previous answer is still valid. It is better to have a counter validity period close to the allowance validity period (even for shared allowances). 

In your case, it means that you will have a shared allowance for the current month and another one for the month before. The older allowances are removed by the allowance purge scheduler . 

Just keep in mind to maintain the number of shared allowing in track in order to keep a good level of performances. See the SAP note 2478958 - Impact of the Master Data on the SAP CC Performance 

Best regards,

Eric F.

[AravindVijayaraghavan · Accepted solution]

Thanks Eric. Will refer the SAP note and keep the recommended values in mind.

[Eric_F]

Hello,

if you have a set of counters which have a validity period, the recommendation is to manage these counter inside an allowance which has the same validity period. 

Just take care to manage properly the purge of the expired allowance in order to avoid to keep too many useless data in memory.

Best regards,

Eric F.

[AravindVijayaraghavan]

Hi Eric,
Thanks for the reply.

Sorry, I forgot to mention this, but I was talking about using shared allowances in which we need to accumulate usages for each month and reset at the end of a common cycle. We would also need to read the accumulated counter values at the end of the period which may be quarterly/half-yearly/yearly.  In this case, would you rather manage 12 allowances (or maintain allowance per quarter) or have a single shared allowance with counters for each month?