Error Oracle.Apps.Imc.Ocong.Root.Server.Imcrootamimpl.Getpartynamefromid When Add New Contact

(Doc ID 1428352.1)

Last updated on JULY 12, 2017

Applies to:

Oracle Trading Community - Version: 12.1.3 and later   [Release: 12.1 and later ]
Information in this document applies to any platform.

Symptoms

After upgrading from 11i to R12.1.3, when a user is adding a new contact to an organization the DQM rules checks to see if a person or contact already exists that matches.

If users select the option Use Existing Person, the following error is received:

Error
You have encountered an unexpected error. Please contact the System Administrator for assistance.

Exception Details.
oracle.apps.fnd.framework.OAException: java.lang.NullPointerException
at oracle.apps.fnd.framework.OAException.wrapperException(OAException.java:912)
at oracle.apps.fnd.framework.OAException.wrapperException(OAException.java:886)
at oracle.apps.fnd.framework.OAException.wrapperInvocationTargetException(OAException.java:1009)
at oracle.apps.fnd.framework.server.OAUtility.invokeMethod(OAUtility.java:211)
at oracle.apps.fnd.framework.server.OAUtility.invokeMethod(OAUtility.java:153)
....
....
## Detail 0 ##
java.lang.NullPointerException
at oracle.apps.imc.ocong.root.server.ImcRootAMImpl.getPartyNameFromId(ImcRootAMImpl.java:142)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at oracle.apps.fnd.framework.server.OAUtility.invokeMethod(OAUtility.java:190)
at oracle.apps.fnd.framework.server.OAUtility.invokeMethod(OAUtility.java:153)
at oracle.apps.fnd.framework.server.OAApplicationModuleImpl.invokeMethod(OAApplicationModuleImpl.java:762)
at oracle.apps.imc.ocong.party.person.webui.ImcContactProfilePageCO.processRequest(ImcContactProfilePageCO.java:100)
...
...

The issue only happens when Option 2: Use Existing Person is selected.
The contact is added successfully but the error message leads the user to think it was not created.

Steps to reproduce:
-Customers Online Superuser, N: Home tab : Customers sub-tab
-Query a customer
-Click on Relationship > Contact
-Select a relationship type and click on Create button
-Enter a contact name that already exists.
-The Warning: Possible Matching Persons appears with 2 options:
   Option 1: Create new person
   Option 2: Use Existing Person
-Select Option 2: Use Existing Person. The error appears.

Changes

The issue is due to a custom personalization.

The following personalization has been done at the Responsibility level on the Create/Update Contact page in OCO:

-Navigate to Contacts page in OCO.
-Select a contact and click on Update button
-Click on Personalize Page link at the top right.
-Click on Personalize pencil for Message Text Input: First Name
-Under Personalization Properties, Read Only is set as follows:
Responsibility: Customers Online CS User_RTS
SPEL = ${oa.zzCusContactRoleVO1.ReadOnly}
Result / Source = ${oa.zzCusContactRoleVO1.ReadOnly} / Responsibility

This is a customization as oa.zzCusContactRoleVO1.ReadOnly is a customization.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms