Presolicitation Notice Data Does Not Default From Associated Solicitation
Last updated on MARCH 08, 2017
Applies to:Oracle Contract Lifecycle Management for Public Sector - Version 12.2.2 and later
Information in this document applies to any platform.
In Oracle Sourcing with Contract Lifecycle Management (CLM), Release 12.2.2, during creation of the presolicitation notice, the data for fields such as Contracting Office's ZIP Code, Classification Code, and Subject do not default from the associated solicitation.
It is expected that the data for these fields will populate from the associated solicitation document.
Steps To Reproduce
The issue can be reproduced at will with the following steps:
1. Log in to Oracle Applications, using the CLM Purchasing responsibility.
2. Navigate to Buyer Work Center > Solicitations tab.
3. Create a new solicitation.
4. Create the presolicitation notice. On the Header: Presolicitation Notice Details (Solicitation XXXXX) page, the fields such as Contracting Office's ZIP Code, Classification Code, and Subject do not show the data which should default from the associated solicitation.
The issue has the following business impact:
Due to this issue, users are having to manually select or specify the values for the presolicitation notice, which may or may not match the data already on the associated solitication and therefore causing potential data integrity issues.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms