PRODUCT_NOT_FOUND When The Service Is Cancelled And New Service Created With Same MSISDN
(Doc ID 2742347.1)
Last updated on DECEMBER 06, 2022
Applies to:
Oracle Communications BRM - Elastic Charging Engine - Version 11.3.0.9.0 and laterInformation in this document applies to any platform.
Symptoms
An account having service with MSISDN.This service is cancelled and new service is created for the same account and with same MSISDN. Only the service POID is different.
After this activity, there is a active service but the rating is failing with error PRODUCT_NOT_FOUND.
It is real-time data scenario, so there is no backdated CDR concept. It is only real-time usage which suppose to work with the new service.
Steps to Reproduce this issue
+++++++++++++++++++
1. Created a charge offer CO1 of telephony service, which charges $1/min
2. Created another charge offer CO2 of telephony service, which charges $2/min
3. Created an account with CO1, with service login name for puid and did usage for 30 minutes through sdk
4. Initial balance in ece is 0. Now balance is updated with $30
5. Then moved the pvt to next day and cancelled the telephony service
6. Then appended the puid with some random number as follows
publicIdentifier = [005810080_111222, 005810080]
purchasedChargeOffers = [
PurchasedChargeOffering:
, id=33448561
, status=CANCELLED
7. Then purchased the charge offer CO2 to the same account with different puid and later updated the puid to same number as previous one using the opcode PCM_OP_CUST_UPDATE_SERVICES
publicIdentifier = [005810080]
PurchasedChargeOffering:
, id=33453537
, status=ACTIVE
,
usageValidity=Interval{start=2015-01-02T00:00-08:00[PST8PDT],end=+292278994-08-17T07:12:55.807Z}
,
purchaseValidity=Interval{start=2015-01-02T00:00-08:00[PST8PDT],
end=+292278994-08-17T07:12:55.807Z}
, usageValidityRule=null
, packageReference=null
, instantiatedTime=null
, effectiveTime=1420221600000
ChargeOffering{
, id='ed51a6f9-9c5d-4675-af29-dae9f725ad87
, name=VOICE_CO1
, externalId=33454499
, validityInterval=Interval{start=1970-01-01T00:00Z ,end=+292278994-08-17T07:12:55.807Z}, assignedTo='TelcoGsmTelephony
8. Then sent a terminate request for next day and the rating failed
Cause
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
Symptoms |
Cause |
Solution |
References |