Search Results okc_rep_contract_text_idx_pvt

Overview

The APPS.OKC_REP_CONTRACT_TEXT_IDX_PVT package is a private (PVT) PL/SQL package within the Oracle E-Business Suite Contracts (OKC) module. Its business function is to gather and assemble metadata that describes Repository contracts and their versions, primarily for use by Oracle Text indexing operations. Oracle Text maintains full-text search indexes over contract content and clauses; the metadata collected by this package helps drive the indexing and searchable representation of contract records stored in the Repository.

The package header is declared AUTHID DEFINER, meaning its procedures execute with the privileges of the package owner (APPS) rather than the calling user. This is consistent with the Oracle EBS security model for private packages, where application schema privileges are encapsulated and not exposed directly to end users. The header comment block notes a source control revision dated 2005 and flags the script as noship, indicating it is a private internal dependency not intended for direct customer invocation.

Although its documented procedures are named OKC_REP_CON_MD and OKC_REP_VER_MD, the internal comment blocks refer to the API name okc_rep_ver_md for both, reflecting a copy-and-paste signature in the original source rather than two distinct public APIs. The package is classified as PVT, reinforcing that it is not part of the supported public contracts API surface.

Key Procedures and Functions

The ETRM metadata documents two procedures:

• OKC_REP_CON_MD — Collects metadata for a Repository contract. Its purpose is to populate a metadata payload describing the contract record identified by its ROWID, writing the result into the supplied CLOB. This is the procedure the user's search term "okc_rep_con_md" maps to, and it is the primary entry point of interest.
• OKC_REP_VER_MD — Collects metadata for Repository contract versions. It operates on the version representation of a contract, again identified by ROWID and writing metadata into a CLOB.

Both procedures accept a required row identifier (ROWID) and a required IN OUT NOCOPY CLOB parameter that receives the metadata. The NOCOPY hint avoids unnecessary duplication of potentially large CLOB data, which is important given that contract text can be substantial. Per the documentation, parameter lists should be treated as documented; no additional or substituted parameters should be assumed.

Tables Accessed

The documented dependency list references two underlying objects via APPS synonyms: DBMS_LOB and PLITBLM.

• DBMS_LOB is the Oracle-supplied built-in package for large object manipulation. Its use confirms that the procedures assemble and append metadata into CLOB structures, consistent with the IN OUT NOCOPY CLOB parameter.
• PLITBLM is a standard Oracle EBS internal package used for PL/SQL tables of large objects / text handling utilities. Its presence indicates that intermediate metadata may be staged in PL/SQL table structures before being written to the CLOB.

The documented metadata does not enumerate the OKC Repository tables read by these procedures. In practice, package logic of this nature queries the contract header, version, and text tables under the OKC schema to derive indexable content, but the ETRM excerpt only confirms the two referenced objects above. Any additional table dependencies should be verified directly against the package body.

Usage Notes

Because the package is classified as Private and carries the noship designation, it is not intended for direct invocation by customers or custom code. Instead, it is typically called internally by Oracle Text or Repository metadata generation routines whenever contract text must be indexed or refreshed. The procedures are invoked with a ROWID identifying the specific contract or version row, and they return metadata through the CLOB parameter rather than as a return value.

Typical invocation contexts include Oracle Text index synchronization jobs, contract repository maintenance flows, and any internal process that regenerates searchable metadata for contracts. The package is referenced by zero other packages per the documented dependency report, indicating it sits at a leaf of the dependency tree and is called directly by index-related framework code rather than by other PL/SQL packages.

Developers investigating the "okc_rep_con_md" search term should understand that this private procedure is an internal implementation detail of the contract text indexing feature. Direct calls from custom code are unsupported and should be avoided; supported extension points for contract indexing should be used instead. Any diagnostic activity should focus on tracing calls from the indexing framework into these procedures.