Search Results copy_contacts

Overview

OKC_REP_CONTRACT_PROCESS_PVT is an internal PL/SQL package in the APPS schema that serves as the core contract lifecycle processing engine for Oracle E-Business Suite's Enterprise Contracts (formerly Oracle Contracts) module — the repository-based contract authoring and management feature set. It is classified as a PVT package, meaning it is private implementation code intended for consumption by the public API surface rather than for direct customer invocation. In both EBS 12.1.1 and 12.2.2, this package underpins the actions that users perform on a contract through the Contracts workbench and related Forms-based contract windows: submitting a contract for approval, versioning, copying, deleting, signing, and terminating. Because it orchestrates so many discrete operations against the OKC tables, it acts as a central transaction coordinator, delegating validation, workflow, and document management to OKC_API, OKC_MANAGE_DELIVERABLES_GRP, and related packages.

Key Procedures and Functions

The ETRM documentation identifies 27 documented procedures and functions. They group naturally into several functional families.

• Approval and signing: SUBMIT_CONTRACT_FOR_APPROVAL initiates the approval workflow for a contract; SIGN_CONTRACT and ESIGN_CONTRACT record execution of a contract, with the latter supporting electronic signature scenarios.
• Versioning and copying: COPY_CONTRACT_DETAILS, COPY_CONTACTS, COPY_PARTIES, COPY_RISKS, and COPY_ACL replicate the various component areas of an existing contract, while VERSION_CONTRACT_DETAILS creates the new version record set used when a contract is revised.
• Deletion: DELETE_CONTRACT, DELETE_CONTACTS, DELETE_PARTIES, DELETE_RISKS, DELETE_RELATED_CONTRACTS, DELETE_ACL, DELETE_STATUS_HISTORY, DELETE_APPROVAL_HISTORY, and DELETE_BOOKMARKS remove the corresponding child data, ensuring referential integrity when a contract or its elements are removed.
• Lifecycle and locking: LOCK_CONTRACT_HEADER obtains a lock on the contract header row to serialize concurrent updates; TERMINATE_CONTRACT ends the contract's active life.

The metadata does not enumerate parameter lists; those must be obtained from the package specification.

Tables Accessed

The package operates against a focused set of contract repository tables, reached through APPS synonyms. OKC_REP_CONTRACTS_ALL is the primary contract header table that the majority of procedures read and update. OKC_CONTRACT_RISKS stores contract risk assignments manipulated by COPY_RISKS and DELETE_RISKS, and OKC_REP_BOOKMARKS holds user bookmarks managed by DELETE_BOOKMARKS. OKC_REP_CONTACT_ROLES_TL provides the translatable contact role definitions used by the contact copy and delete routines. Several non-contract tables are referenced for supporting infrastructure: the FND_DOCUMENT_SEQUENCES family (FND_DOC_SEQUENCES, FND_DOC_SEQUENCE_ASSIGNMENTS, FND_DOC_SEQUENCE_CATEGORIES) supplies document numbering, while FND_GRANTS, FND_MENUS, FND_OBJECTS, EGO_DATA_LEVEL_B, and EGO_EXTFWK_S relate to function security, menu access, and extensibility/data-level security checks. HR_ALL_ORGANIZATION_UNITS and HR_ORGANIZATION_INFORMATION resolve organization context for the contract.

Usage Notes

OKC_REP_CONTRACT_PROCESS_PVT is a private package and should not be called directly from custom code. It is invoked indirectly through the public contract APIs, and the dependency metadata confirms it is referenced by OKC_REP_EXP_NTF_PVT and OKC_REP_UTIL_PVT within ETRM. In practice it is triggered by user actions in the Contracts authoring Forms and by concurrent programs such as approval and versioning processes. Developers extending contracts should call the supported public API layers (for example OKC_API) rather than this package; direct invocation risks bypassing validation, security, and workflow logic that the package assumes is already applied by its callers.