Search Results lock_section_content

Overview

OKC_SECTIONS_PVT is a private PL/SQL package in the Oracle E-Business Suite Contracts (OKC) module, owned by APPS and classified as a PVT (private) API. It provides the internal programmatic interface for managing contract sections and their associated content, forming part of the core Contracts Intelligence / Contract Terms and Conditions authoring infrastructure. The package is responsible for the lifecycle management of section records, encompassing creation, modification, deletion, locking, and validation of both section headers and section content rows. The source header identifies the file as OKCCSCNS.pls, with a version stamp dated 2005 and marked "noship," confirming its role as an internal, non-shipped component invoked by public APIs rather than directly by external integrations.

Sections are the structural building blocks of a contract document; each section may contain one or more content records that hold the actual textual or structured terms. OKC_SECTIONS_PVT encapsulates the business logic that governs how those sections and their content are persisted, ensuring that validation, locking, and concurrency rules are applied consistently. Because it is classified as private, it is not intended to be called directly by customer extensions; the corresponding public API surface in the OKC module delegates to this package.

Key Procedures and Functions

The package exposes twenty-one documented procedures spanning section and content management. The principal section-level operations are:

• CREATE_SECTION — Inserts a new section record, available in both single-record and table (bulk) overloads.
• UPDATE_SECTION — Modifies an existing section record; the searched procedure. Provided in single-record and bulk table overloads.
• DELETE_SECTION — Removes a section record from the contract structure.
• LOCK_SECTION — Acquires a lock on the section record to prevent concurrent modification.
• VALIDATE_SECTION — Applies business validation rules to section data prior to persistence.

The content-level operations mirror these, operating on section content rows:

• CREATE_SECTION_CONTENT — Creates content entries belonging to a section.
• UPDATE_SECTION_CONTENT — Modifies existing content records.
• DELETE_SECTION_CONTENT — Removes content records.
• LOCK_SECTION_CONTENT — Locks content rows for concurrency control.
• VALIDATE_SECTION_CONTENT — Validates content data against defined rules.

Additionally, ADD_LANGUAGE supports multilingual content by creating translated section records. Both CREATE_SECTION and UPDATE_SECTION are defined with p_api_version, p_init_msg_list, x_return_status, x_msg_count, and x_msg_data standard API parameters. The type definitions scnv_rec_type, scnv_tbl_type, sccv_rec_type, and sccv_tbl_type are subtyped from OKC_SCN_PVT and OKC_SCC_PVT respectively, indicating that section and content records are passed as structured record or table parameters, consistent with the Oracle PL/SQL API design standard.

Tables Accessed

The documented table accessed by this package is OKC_SECTIONS_B, the base table storing contract section definitions. Through APPS synonyms the package reads and writes this table to persist the outcomes of create, update, and delete operations, to retrieve records for locking and validation, and to maintain the section hierarchy and descriptive attributes. Content-related procedures operate against the implicit content structures referenced via the OKC_SCC_PVT subtype, though OKC_SECTIONS_B is the primary documented base table. All access is performed through standard APPS synonyms, maintaining the EBS schema isolation model.

Usage Notes

Because OKC_SECTIONS_PVT is classified as a private API, it is not documented for direct invocation by customers or third-party integrations. It is typically called from within the OKC Contracts forms and from other OKC packages — the metadata notes that it is referenced by one other package. The standard usage pattern is for a public API or form-level handler to prepare the section or content record structures (scnv_rec_type, sccv_rec_type) and delegate the actual DML, validation, and locking to this package. Callers must honor the concurrent-programming contract: invoke LOCK_SECTION before UPDATE_SECTION when concurrent edits are possible, and always inspect x_return_status rather than relying on exceptions, since the procedures communicate errors through the standard message stack (x_msg_count, x_msg_data). In Oracle EBS 12.1.1 and 12.2.2, this package behaves consistently; the 12.2 online patching model does not alter its internal logic, but adopters should avoid direct calls and instead use the supported public API layer so that patches to this private package do not break custom code. The ADD_LANGUAGE procedure should be invoked only through the multilingual flows supported by the Contracts application.