The Relationship Between A Contact And Its Primary Household Is Being Saved On The Account Field
(Doc ID 2520769.1)
Last updated on OCTOBER 30, 2019
Applies to:Oracle Fusion Sales Cloud Service - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
The implementation is primarily optimized for B2B flows where Household is not typically used.
Household is expected to be used in B2C flows in which case Account will not be used. The Household DCL field can be exposed instead of the Account DCL field. It holds the Household Name and drilling down opens the desired record.
Household information if applicable for B2B implementation, is expected to be captured as part of relationship subtab.
To see the contact - household association, instead of adding household in Contact profile subtab, add a contact - household relationship so that it becomes visible in the Relationships subtab of contact. To do this, navigate to relationships subtab of the contact and then add a new relationship by searching for the household with which the contact needs to be associated.
While testing the household module:
a) Start the process for Creating a household
b) Search for a Primary Contact
c) Create a new contact from that page
d) Assign that contact as the primary contact for a household
e) Save and close the record
f) Navigate to the contact
The household is incorrectly saved in the "Account" field of the Contact. After drilling down on the household, it opens the Account details page, and after clicking on the profile tab for that "Account", an application error and a null pointer exception occur.
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