Search Results validate_date_active

Overview

OKC_SAV_PVT is a private (PVT-classified) PL/SQL package in the Oracle E-Business Suite Contracts application, owned by the APPS schema. Its name and record structure indicate that it manages the Standard Article Version (SAV) entity — the versioned definitions of standard contract clauses and articles stored in the OKC_STD_ART_VERSIONS base table. The package operates under AUTHID CURRENT_USER and defines a global record type, sav_rec_type, which mirrors the columns of OKC_STD_ART_VERSIONS_B together with the standard WHO columns and a set of DFF attribute columns. This record type is the package's primary data transport mechanism, allowing row data to be passed between the validation, insert, update, and delete routines without the caller having to enumerate every column. As a PVT package, OKC_SAV_PVT is not intended for direct customer invocation; it is the implementation layer beneath the public OKC_SAV API and related Contracts APIs, and it is referenced by two other packages within the module. Its responsibility is to enforce the business rules that govern whether a standard article version may be created, changed, or removed, and to perform the underlying DML against the version tables.

Key Procedures and Functions

The nineteen documented procedures fall into three functional groups: validation, version management, and row-level DML.

• Validators — VALIDATE_ROW is the master validation entry point and typically calls the more granular checks. VALIDATE_SAV_RELEASE confirms that the supplied SAV release value is valid. VALIDATE_DATE_ACTIVE (the object the user searched for) checks the DATE_ACTIVE column of the version row, which controls the effective period during which the standard article version is usable; this is the routine that enforces date-related business rules before a row is accepted. VALIDATE_NO_K_ATTACHED checks that no knowledge or attachment records are linked to the version, preventing deletion or amendment of a version that is still referenced. VALIDATE_LATEST ensures that the row being manipulated is the latest version, and VALIDATE_UPDATABLE determines whether the current version is in a state that permits modification.
• Version and lifecycle functions — CHANGE_VERSION creates or promotes a new version of the standard article, API_COPY duplicates an existing version (including its translated and attribute data), and ADD_LANGUAGE inserts the language-specific rows required for a new installed language.
• DML procedures — INSERT_ROW, UPDATE_ROW, DELETE_ROW, and LOCK_ROW perform the physical insert, update, delete, and row-lock operations against the base table, and QC applies the standard concurrent-program quality-control check at the end of a DML batch.

Tables Accessed

The package's core table is OKC_STD_ART_VERSIONS_B, which holds the base-language version definitions and supplies the DATE_ACTIVE, SAV_RELEASE, and attribute columns seen in sav_rec_type. OKC_STD_ART_VERSIONS_TL holds the translated (language-specific) version descriptions and is populated by ADD_LANGUAGE. OKC_STD_ARTICLES_B provides the parent standard article to which each version belongs, enabling referential validation. FND_LANGUAGES is queried to determine which installed languages require translation rows, and PLITBLM is the standard EBS temporary table used for bulk processing of translated rows. These tables are reached through APPS synonyms.

Usage Notes

Because OKC_SAV_PVT is classified as PVT, it is invoked indirectly. The standard path is through the public Contracts APIs and the Oracle Contracts forms, where a user creating, revising, or end-dating a standard article triggers the public API, which delegates validation and DML to this package. Concurrent programs that bulk-load or copy standard articles also route through API_COPY and CHANGE_VERSION. Custom code should call the supported public API layer (for example OKC_SAV or OKC_API) rather than OKC_SAV_PVT directly, since private package signatures may change between patches and are not covered by Oracle's public API guarantee. In Oracle EBS 12.1.1 and 12.2.2 the behavior is consistent; the 12.2 online-patching model simply means the package file is delivered through the usual ADOP cycle. Developers debugging a DATE_ACTIVE validation failure should trace into VALIDATE_DATE_ACTIVE via VALIDATE_ROW to identify the exact rule that rejected the row.