Collections Actions Did Not Get Populated In UNIFIED_COLL_ACTION_IF_VIEW
(Doc ID 1920041.1)
Last updated on OCTOBER 10, 2018
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 7.5.0]
Information in this document applies to any platform.
On Oracle Communications Billing and Revenue Management(BRM) Applications, it was observed that the Collections actions did not get populated in UNIFIED_COLL_ACTION_IF_VIEW on a multi-schema setup.
The setup contains a BRM 7.5 PS8 and PS9 multischema environment integrates with Siebel via AIA.
In an end-to-end testing, below are what have been found:
-- When collections ran in primary schema, COLL_ACTION_IF_VIEW got populated with all the data, but UNIFIED_COLL_ACTION_IF_VIEW did not get populated with any data.
-- When collections ran in secondary schema, UNIFIED_COLL_ACTION_IF_VIEW got populated with all the data, but COLL_ACTION_IF_VIEW did not get populated with any data.
AIA always checked data in UNIFIED_COLL_ACTION_IF_VIEW to send the collections info to Siebel CRM. That is, AIA only picked the collections actions data populated in UNIFIED_COLL_ACTION_IF_VIEW. But for collection actions generated in primary schema, the data was populated in COLL_ACTION_IF_VIEW, hence when accounts in primary schema entered collections, AIA could not send the actions data to CRM.
How to resolve this issue?
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