Results for “okc_contract_pub”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
OKC_CONTRACT_PUB is the public-API package body for Oracle E-Business Suite's Contracts Core (OKC) module, delivered under the APPS schema and classified as a PUB-layer API. It exposes a procedural, transaction-oriented interface that other Oracle EBS modules and customer extensions use to create, maintain, validate, lock, and delete contract data without directly manipulating the underlying OKC base tables. In Oracle EBS 12.1.1 and 12.2.2, this package is the supported entry point for contract header, line, governance, and contract-process operations, shielding callers from the internal structures managed by OKC_CONTRACT_PVT and the various private (PVT) helper packages. The package body is validated as VALID in the ETRM metadata and is a central integration object within the Contracts family.
Key Procedures and Functions
The ETRM metadata documents 65 procedures and functions. The prominent public routines follow a consistent CRUD-plus-lifecycle pattern across four business entities:
- Contract header operations: CREATE_CONTRACT_HEADER, UPDATE_CONTRACT_HEADER, DELETE_CONTRACT_HEADER, LOCK_CONTRACT_HEADER, and VALIDATE_CONTRACT_HEADER.
- Contract line operations: CREATE_CONTRACT_LINE, UPDATE_CONTRACT_LINE, DELETE_CONTRACT_LINE, LOCK_CONTRACT_LINE, and VALIDATE_CONTRACT_LINE.
- Governance operations: CREATE_GOVERNANCE, UPDATE_GOVERNANCE, DELETE_GOVERNANCE, LOCK_GOVERNANCE, and VALIDATE_GOVERNANCE.
- Contract process operations: CREATE_CONTRACT_PROCESS, UPDATE_CONTRACT_PROCESS, DELETE_CONTRACT_PROCESS, LOCK_CONTRACT_PROCESS, and VALIDATE_CONTRACT_PROCESS.
The CREATE routines instantiate records, UPDATE routines modify existing ones, DELETE routines remove them, LOCK routines acquire the necessary concurrency control for subsequent changes, and VALIDATE routines apply business rules and return validation status. The remaining documented procedures extend this same pattern to related contract sub-entities. Parameter lists are intentionally not restated here; callers should reference the package specification for exact signatures.
Tables Accessed
The documented table reference for this package body is PLITBLM, accessed through an APPS synonym. In addition, the package's dependency list shows it relies on the contract views OKC_K_HEADERS_V, OKC_K_LINES_V, and OKC_STATUSES_V, plus the public synonym OKC_CONTRACT_PUB and the internal OKC private packages (OKC_CONTRACT_PVT, OKC_CAC_PVT, OKC_CHR_PVT, OKC_CLE_PVT, OKC_CPS_PVT, OKC_CVM_PVT, OKC_GVE_PVT). These views expose header, line, and status information that the API reads when validating and processing contract records. All underlying base-table writes are generally delegated to the private packages, keeping the public layer thin and consistent.
Usage Notes
OKC_CONTRACT_PUB is typically invoked from Contracts forms, concurrent programs, and custom PL/SQL that need to manipulate contracts through a supported interface. The ETRM metadata records that it is referenced by 68 other packages, confirming its role as a foundational API. Callers benefit from its dependency on FND_API for standard return-status conventions, and should honor the expected sequence of LOCK, CREATE/UPDATE, VALIDATE, and commit operations. Because the package is owned by APPS and is not itself referenced by any database object, extensions should call it rather than the private PVT packages, ensuring upgrade-safe behavior across EBS 12.1.1 and 12.2.2.