Modification Signed Date On Header Not Corresponding W/ SF30 And Action History When Doc Fails To Merge (Doc ID 2208910.1)

Last updated on DECEMBER 01, 2016

Applies to:

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

Symptoms

On : 12.2.2 version, Modifications

The modification Signed Date that displays on the Modification Header should correspond with the date of obligation. The SF30 and the Action History should reflect this date as well. Currently, if a document fails to merge or is held up in the system for any other reason such as FPDS, there is a discrepancy between the header and the SF30 and the Action History. There are legal ramifications for the CO signature/date and there financial ramifications for the date of obligation - these items need to be in sync.

Steps to reproduce the issue:
      
1. Login the instance with federal user
2. Go to CLM Purchasing super user role
3. Create an award
4. Modify that award and submit that award with co officer sign >  enabled.
5. Login as CO and approve the modification.
6. View the modified PDF.

Changes

 

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