Auto-Trigger Billing Does Not Initiate On Payee Account and Leads to Incorrect Notifications (Doc ID 2338531.1)

Last updated on AUGUST 01, 2023

Applies to:

Symptoms

On : 7.5.0.16.0 version, Rating

ACTUAL BEHAVIOR
-----------------------
Consider below scenario:

Payee Account : 530299872268
Subordinate account : 530299872588
Unit : 3062019935
Bill period = 23rd
Rate 0.03/MB

The user has a payee account and subscription account structure. Payee account is discount sharing owner, and Subscription account is member of it. "shareMORE 1GB" plan was purchased at payee account under /service/telco, which grants 1GB of Data (resource ID: 1002043) and also contains discount object "Shared Data Discount" (Owner).

At subscription level, the user has a data usage product '03MBCanUsg' used for rating, and a non-currency resource ID : 1002049, which gets updated when customer is charged with overages. i.e after consumption of Free shared Data 1002043 available balance.

The user noticed incorrect charge and notifications when a data session requests authorization or re-authorization on the billing day but before billing completes due to auto-trigger billing not performed on the Payee account. Due to this, new sub-balance for Free shared data 1002043 on payee account was not initiated, which is leading to charge on the subscription account. Also , the user had configured fixed threshold notifications when Overage bucket 1002049 value is 1. This is triggering the incorrect notifications to the customer even though they have Free shared balance.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1) on Aug 22 23:57:21, requested 50 MB through PCM_OP_TELCO_AUTHORIZE . Successful
2) on Aug 22 23:57:48 , requested another 50 MB and consumed earlier granted 50 MB through PCM_OP_TCF_AAA_UPDATE_AND_REAUTHORIZE . Successful
3) On Aug 23 00:03:30 i.e on Billing Day ,requested another 50 MB and consumed earlier granted 50 MB through PCM_OP_TCF_AAA_UPDATE_AND_REAUTHORIZE .
This step is not working as expected . Customer was charged for 50 MB instead of deducting from new Free shared bucket 1002043 1 GB.


EXPECTED BEHAVIOR
-----------------------
Issue is seen in step 3. Usage should be deducting from new Free shared bucket 1002043 1 GB instead of charging customer for 50 MB.

Changes

Cause

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