My Oracle Support Banner

CLM - Enhancement for BSO Web Service And PDS Inbound Flows To Allow Supplier Change (Novation) (Doc ID 2925105.1)

Last updated on MARCH 26, 2024

Applies to:

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

Symptoms

ACTUAL BEHAVIOR
Unable to perform Supplier Change (Novation) via BSO Web service and PDS Inbound. Business requires the ability to handle Novations via BSO Web service API Call and PDS Inbound.

EXPECTED BEHAVIOR
 BSO (Business Service Object) Web Service and PDS (Procurement Data Standard) Inbound should have the ability to support the Supplier Change (Novation) with the following conditions.

 1. Allow only if old supplier and new supplier differ.

 2. Allow only if supplier is active & not put on hold in the system

 3. Allow only if document type is Award

 4. Don't allow if the document is an IDV (Indefinite Delivery Vehicle) or the document is an Order referring to IDV

 5. Check the existence of downstream documents, such as receipts and invoices. If they exist, Supplier change not supported through BSO.

 6. Allow only if a relevant site for the changed supplier provided.

 7. If the new Supplier is not a SAM (System for Award Management) supplier, ensure that CCR (Central Contractor Registration) exception reason provided.

 8. If the Supplier change causes any change in Project or Task or Accounts, do not allow.

 9. If Bilateral indicator is enabled: Ensure that acceptance due date, supplier contact person and number of prints are entered.



 

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.