My Oracle Support Banner

A Revision for a Repository Contract, Resends Deliverable Notification (Doc ID 2865141.1)

Last updated on APRIL 26, 2022

Applies to:

Oracle Procurement Contracts - Version 12.2.9 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.9 version, Deliverables Management

ACTUAL BEHAVIOR
---------------
Find that when creating a revision for a repository contract with deliverables where the notification have already been sent, they are resend again. It is noticed that in the deliverable table when approving a contract revision, all the deliverable are copied with the revision number of the contract but the id that was attached to the original sent notification is not copied.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Using Contract Workbench Admin responsibility, author a repository contract with deliverables.
2. Approve the repository contract.
3. Select the contract and click on create a revision.
4. Make a change not to the deliverable but to parties, contacts.
5. Approve the revision and you will see the notifications sent again.

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!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.