Search Results oke_kcopy_pkg




Overview
Explore in AI Chat

Overview

OKE_KCOPY_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM (E-Business Suite Technical Reference Manual) as an "OTHER" API rather than a formally published public interface. Its name and dependency graph place it squarely within the Oracle Contracts (OKE/OKC) family of modules, where the OKE prefix designates the Contracts Core / Project Contracts schema and the OKC prefix designates the shared Contracts Intelligence and contract-authoring objects. The "KCOPY" fragment indicates the package's role: copying contract header, line, and article structures from a source contract to a target contract. In practice, this supports business scenarios in which a user duplicates an existing contract — for example, to create a renewed agreement, a template-based contract, or a versioned derivative — by replicating the underlying contract header, line, article, party-role, process, and user-attribute rows across the Contracts tables. The package is recorded as VALID in the ETRM metadata for both 12.1.1 and 12.2.2, and it is referenced by no other packages, which confirms it is invoked directly rather than as a subordinate library routine.

Key Procedures and Functions

The documented interface exposes a single procedure:

  • COPY_CONTRACT — the package's sole documented programmable unit. Its purpose is to perform the contract-copy operation: taking a source contract identifier together with the target context supplied by the caller, and inserting the corresponding header, line, article, role, process, billing-method, and user-attribute records into the destination contract. Because the ETRM metadata does not publish a parameter list, callers should not assume a signature; the procedure should be treated as an internal API whose exact argument set must be confirmed against the 12.1.1/12.2.2 package specification in the target instance before any custom invocation.

Internally, the package builds on several other Contracts APIs, notably OKC_CIM_PVT (Contract Items Maintenance), OKC_CONTRACT_ITEM_PUB (the public contract-item interface), and OKE_API (the general Contracts Core API). These dependencies indicate that COPY_CONTRACT does not manipulate contract tables in isolation but delegates part of its work to the standard contract-item creation routines. In addition to the built-in STANDARD package, these are the only objects referenced by OKE_KCOPY_PKG.

Tables Accessed

The documented tables touched by the package span both the shared OKC contract tables and OKE-specific extension tables. On the shared side, the package reads and writes OKC_K_HEADERS_ALL_B (contract headers), OKC_K_LINES_B (contract lines), OKC_K_ITEMS (contract line items), OKC_K_ARTICLES_B (contract terms and conditions articles), OKC_K_PARTY_ROLES_B (party roles associated with the contract), and OKC_K_PROCESSES (contract processes such as signatures and approvals). On the OKE-specific side, it accesses OKE_K_HEADERS and OKE_K_LINES (the Contracts Core header and line extensions), OKE_K_TYPES_B (contract type definitions), OKE_K_BILLING_METHODS (billing method assignments), and OKE_K_USER_ATTRIBUTES (descriptive flexfield values). All references are made through APPS synonyms, consistent with EBS standards. The table set confirms that copying a contract is not limited to a single header row: article text, party roles, processes, billing methods, and user attributes are all migrated as part of the same operation.

Usage Notes

Because OKE_KCOPY_PKG is classified as OTHER and is referenced by no other packages, it is best regarded as an internal utility rather than a supported public API. It is most commonly reached indirectly through the Contract Authoring / Contracts Core forms when a user runs a copy or duplicate action against an existing contract, and potentially through concurrent or custom programs that need to reproduce a contract's full structure. Custom code that calls OKE_KCOPY_PKG.COPY_CONTRACT should be treated cautiously: the procedure's signature is not published in the ETRM, behavior is version-dependent, and the package relies on OKC_CIM_PVT and OKC_CONTRACT_ITEM_PUB, whose own validation and security rules must be satisfied by the calling context. Oracle customers should prefer supported APIs such as OKC_CONTRACT_ITEM_PUB where an equivalent function exists, and should re-verify the procedure declaration against the live 12.1.1 or 12.2.2 instance before compiling dependent code.