Search Results okc_scc_pvt




Overview
Explore in AI Chat

Overview

OKC_SCC_PVT is a private PL/SQL package in the APPS schema that encapsulates the core data-manipulation and validation logic for Oracle E-Business Suite section content records. Within the Oracle Contracts (OKC) module, "SCC" denotes Section Content Control, and the package serves as the private persistence layer behind the public sections interfaces. It is functionally subordinate to OKC_SECTIONS_PUB and OKC_SECTIONS_PVT, which expose the contract sections and article content model to callers, while OKC_SCC_PVT performs the low-level row operations, locking, validation, and version handling against the underlying section content tables. The package is classified as PVT, meaning it is intended for internal use by the Contracts application and is not part of the supported public API surface. This distinction matters when planning customizations or extensions: Oracle supports the public sections APIs, but direct invocation of OKC_SCC_PVT bypasses the documented entry points and the consistency checks performed at that layer.

Key Procedures and Functions

The ETRM documentation lists twelve program units, of which seven core procedures are named. INSERT_ROW creates a new section content record, establishing the base row for content associated with a contract section or standard article. LOCK_ROW obtains the row-level lock required before an update or delete proceeds, protecting the record from concurrent modification and supporting the DML sequencing required by the Contracts model. UPDATE_ROW applies changes to an existing section content record. DELETE_ROW removes a section content row, typically as part of section restructuring or contract revision. VALIDATE_ROW applies business-rule and referential validation before the row is committed. CREATE_VERSION and RESTORE_VERSION implement the historical versioning mechanism for section content, generating a versioned snapshot of the current record and reinstating a previously captured version respectively. Consistent with the PVT classification, all of these units operate on the internal content model and are expected to be called within the transaction context established by the higher-level public packages.

Tables Accessed

Documented references include OKC_SECTION_CONTENTS and its view OKC_SECTION_CONTENTS_V, which are the primary targets of the insert, update, and delete operations. OKC_SECTIONS_B and OKC_SECTIONS_BH hold the base and history records for contract sections, linking content rows to their owning section and providing the historical context for versioning. OKC_SECTION_CONTENTS_H stores history for section content, supporting the CREATE_VERSION and RESTORE_VERSION routines. OKC_K_ARTICLES_B and OKC_K_LINES_B represent contract articles and lines, tying section content to the contract's article and line structure. OKC_STD_ARTICLES_B supplies the standard article definitions from which contract article content is derived. PLITBLM appears as a standard Oracle PL/SQL internal table for handling arrays of identifiers during bulk processing. The package also references FND_API and OKC_API for shared APIs and error-handling conventions, and STANDARD for the PL/SQL standard package.

Usage Notes

OKC_SCC_PVT is not typically invoked directly from forms, concurrent programs, or custom code. It is referenced by OKC_COPY_CONTRACT_PVT, OKC_K_ARTICLE_PVT, OKC_SECTIONS_PUB, OKC_SECTIONS_PVT, and OKS_RENCPY_PVT, and is referenced by five packages in total. These callers cover contract copy, article maintenance, sections public API, sections private API, and service renewal copy operations. Customizations should therefore target the public sections APIs and the supported Contracts interfaces rather than this package directly. When troubleshooting section content errors, defects, or unexpected version behavior, OKC_SCC_PVT is the correct object to inspect, since the row-level operations, locking, and validation logic for the section content model are concentrated here. The package is valid in both Oracle EBS 12.1.1 and 12.2.2, and its dependency footprint on OKC_SECTION_CONTENTS, OKC_SECTIONS_B, and the history tables should be confirmed after any patch or upgrade that changes the Contracts schema.