My Oracle Support Banner

SNR is not Generated for Policy Counters in Member Bundles When Added to Discount Sharing Group (Doc ID 2893033.1)

Last updated on NOVEMBER 28, 2023

Applies to:

Oracle Communications BRM - Elastic Charging Engine - Version and later
Information in this document applies to any platform.


When an account is added to discount sharing group (DSG) and policy counter in member bundles is changed, Status-Notification-Request (SNR) is not generated.
SNR is generated for policy counter changes before adding to group. If the account with the same bundle is not added to group, SNR is generated successfully for policy counter changes.

SNR should be generated when the policy counter is updated to -1

The issue can be reproduced at will with the following steps:
1. Plan:
  a. Grants Data of 20MB (Resource: DA)
  b. Grants a policy counter with value -2 which is InAllowance (Resource: DAPCS)
  c. When data is fully consumed (i.e DA=0), Policy counter (DAPCS) is updated to -1 which is OutOfAllowanace.
2. Owner Account (Login: 202205100060068) and discount sharing group is created.
3. Member account (Login: 202205100060268) and owner balance is fully consumed.
4. Initiate update request with RSU = 100MB (Session ID: GPRS_1653313902, request number: 1)
    Active reservation of full 20MB is done on DA and 80MB is reserved on a different resource POUA)
5. Update request with USU = 100MB is sent (Session ID: GPRS_1653313902, request number: 2)
    DA balance 20MB is fully consumed and DAPCS (policy counter) is updated to -1
    But SNR is not generated.




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.