My Oracle Support Banner

R12: OKE: Article Text Does Not Get Copied To Contract Header Articles Section (Doc ID 2374452.1)

Last updated on SEPTEMBER 05, 2024

Applies to:

Oracle Project Contracts - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

OKE- Project Contracts: Article Text does not get copied to Contract header
articles section when a standard FAR / DFAR article is selected from the
standard Oracle clause repository.

Loaded the Contracts Standard Clause library with vendor provided FAR and
DFAR clauses. The text provided through xml files by the vendor are used to
process and load into article text clob data in Oracle articles standard
tables using 'Import Clause' program.

The text appears on the Clause library, but it does not get copied to a
contract header when chosen to add to the list of articles on contract.
This is due to being over 4000 characters. Note that it works for clauses
with shorter text length.

When the article text is manually copied from the library, the form accepts
and saves the text.

The clause text is also successfully added using the API
'OKC_TERMS_MIGRATE_GRP.Add_Standard_Clause'.

But none of the above are workarounds as article text should be automatically
populated when chosen from the library on a contract.

Receive xml files from the vendor which are parsed and loaded into Oracle
interface tables.

 



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.