Search Results g_exception_halt_processing

Overview

OKC_STD_ARTICLE_PUB is the public PL/SQL API package for managing standard articles within the Oracle E-Business Suite Contracts (OKC) module. Standard articles are reusable, pre-authored clause or section texts that serve as the building blocks of contract terms and conditions. They are assembled into contract templates and, ultimately, into executable contracts managed by the OKC schema family. The package provides the canonical programmatic entry points for creating, maintaining, versioning, validating, and deleting standard article definitions and their associated versions and incomplete states.

The package body is implemented in the OKCPSAEB.pls source file and is classified as a PUB (public) API. It exposes 83 documented procedures and functions, reflecting the full lifecycle of standard article maintenance, including multi-language support. Because it is a public API rather than an internal helper, it is the supported interface through which forms, concurrent programs, and custom extensions should manipulate standard article data. The package also contains internal migration routines, such as migrate_saev and migrate_sacv, used to transform legacy article records into the current data structures, populating attributes, name, subject code, and the SFWT flag.

Key Procedures and Functions

The documented API surface is organized around article master records, versions, and incomplete definitions:

• CREATE_STD_ARTICLE / UPDATE_STD_ARTICLE / DELETE_STD_ARTICLE — Insert, modify, and remove a standard article master record.
• LOCK_STD_ARTICLE — Obtains a locking handle on a standard article to prevent concurrent modification during an update cycle.
• VALIDATE_STD_ARTICLE — Performs the full set of business-rule validations prior to persistence.
• CREATE_STD_ART_VERSION / UPDATE_STD_ART_VERSION / DELETE_STD_ART_VERSION / VALIDATE_STD_ART_VERSION — Manage the versioned content of a standard article, including save, update, deletion, and validation of version rows.
• LOCK_STD_ART_VERSION — Locks a specific article version for serialized maintenance.
• CREATE_STD_ART_INCMPT — Creates an incomplete (work-in-progress) article definition, allowing partial authoring before final validation and commit.
• VALIDATE_NAME — Confirms uniqueness and correctness of the article name.
• VALIDATE_NO_K_ATTACHED — Verifies that no contract article references the standard article before a destructive operation.
• VALIDATE_SAV_RELEASE — Validates release status governing whether a version may be modified.
• VALIDATE_DATE_ACTIVE — Checks the active date range of the article or version.
• VALIDATE_UPDATABLE — Determines whether the target record may be changed in its current state.
• VALIDATE_LATEST — Confirms that the version under maintenance is the latest version.
• VALIDATE_SHORT_DESCRIPTION — Checks the short description field for completeness and constrained values.
• ADD_LANGUAGE — Installs translated article data for supported languages.

Tables Accessed

The package reads and writes the following documented tables through APPS synonyms:

• OKC_ARTICLE_VERSIONS — Stores the versioned content of each standard article, including version numbering and active date ranges. This is the principal DML target for the version-oriented APIs.
• OKC_K_ARTICLES_B — The base table holding contract article records. Referenced by VALIDATE_NO_K_ATTACHED to ensure an article is not in use before deletion.
• PLITBLM — The PL/SQL character table type (a PL/SQL TABLE OF VARCHAR2), used in bulk processing of article identifiers, names, or language arrays rather than as a persistent database object.

Usage Notes

OKC_STD_ARTICLE_PUB is normally invoked indirectly through the Oracle Contracts standard article maintenance forms and related concurrent programs, which call the CREATE, UPDATE, LOCK, and VALIDATE APIs in sequence, wrapping calls in the appropriate locking and validation order. The user search term g_exception_halt_processing refers to a global application-level flag commonly checked in Oracle Forms for exception handling, not a member of this package. Because the metadata lists zero inbound package references, custom code should treat these APIs as the supported extension point: callers should invoke validation and locking routines before DML, respect the LOCK/UPDATE/UNLOCK pattern, and rely on the incomplete-article APIs when authoring long content incrementally. Multi-language deployments should route translated content through ADD_LANGUAGE.