Validation Of Native Account ID On Customer Contact
(Doc ID 2294077.1)
Last updated on MARCH 07, 2019
Applies to:Oracle Utilities Customer Care and Billing - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
**Disclaimer:** This KM article may include the following abbreviations:
CCB/CC&B - Oracle Utilities Customer Care and Billing
OUAF/FW - Oracle Utilities Framework
ER - Enhancement Request
On : 18.104.22.168.0 version, CI - Customer Information
This is an Enhancement Request for validation of Native Account ID on Customer Contact
Prior to CC&B Service Pack 2 one recorded the Account & Premise as characteristics on the Customer Contact. In adopting Service Pack 2 they have chosen to record the account in the native ‘Account’ field on the Customer Contact, which forces validation of the Person & Account, and will not let the contact be recorded without the Person being linked to the Account. I belive the native Premise field does the same - the 3 entities have to be set up on the V.
As per business model one receive contact from Persons about an Account where they are not the bill payer. We are using the Person Account Relationship link in CC&B only for bill payers or people who are authorised to discuss the account (as a form of security control for sharing customer information). The contact we receive will not always be from people who are authorised to discuss the account, so we do not want to link them to the Account. The issue we have is that we cannot log the Customer Contact without linking them. We would also like to use the native field to enjoy other benefits in CC&B (e.g. the account history and communication history zones).
Would Oracle consider a Feature Configuration item to remove this validation, so Account and Premise IDs do not have to be linked to the Persons on the Contact?
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