My Oracle Support Banner

Modification Sync Not Working When Non Standard Clauses Are Present (Doc ID 2404551.1)

Last updated on MAY 29, 2018

Applies to:

Oracle Contract Lifecycle Management for Public Sector - Version 12.2 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.6 version, Requisition

ACTUAL BEHAVIOR
---------------


When working with concurrent modifications, if one modification adds a Non-Standard Clause the system is not assigning an Operating Unit to the non-standard clause

so once the modification is signed and conformed the other concurrent mods receive an error when trying to synch.

Steps to replicate :
----------------------
1. Create several concurrent modifications from the same IDV
2. In one of the concurrent mods add a non-standard clause. Type some text into the text editor and then save the non-standard clause
3. Submit the modification for signature
4. Once signed and conformed go back to the draft concurrent mods and try to update one
5. System notifies user there are changes to synch. Accept the changes and receive the following error

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.webui.OAWebBeanHelper.processRequest(OAWebBeanHelper.java:659)
  at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processRequest(OAWebBeanContainerHelper.java:283)
  at oracle.apps.fnd.framework.webui.beans.layout.OAStackLayoutBean.processRequest(Unknown Source)
  at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:1058)
 

Changes

 

Cause

To view full details, 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 a vibrant support community of peers and Oracle experts.