Pipeline Does Not See Object Cache Type to Avoid Loading Prepaid Accounts
(Doc ID 1489037.1)
Last updated on MARCH 21, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 7.3.0]
Information in this document applies to any platform.
Selective Account Loading feature is missing.
Accounts were created without specifying a /config/business_profile (default is Postpaid), so PCM_OP_CUST_CHANGE_BUSINESS_PROFILE() is called to assign a “prepaid” business profile. After configure the account, started the Pipeline and process an EDR for this “Prepaid” account to see if the Pipeline is loading the account in the memory cache.
When marking this account as a “Prepaid”, the purpose is to prevent Pipeline loading the account data in the memory cache; but in the dmp file, this account was in memory and with a PIN_FLD_OBJECT_CACHE_TYPE (set to 0, convergent) different from the data in the database (set to 1, prepaid).
- ISC_ObjectCacheTypeOutputSplitter iScript is not configured
- No TIMOS on the system
The purpose for this is not to load the information for all the prepaid accounts in the Pipeline memory cache, but the result shows it still loads accounts in cache.
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