Search Results validate_short_description




Overview

OKC_CONTRACT_GROUP_PUB is the public PL/SQL API package for the Contract Groups entity within Oracle Contract Lifecycle Management (formerly Oracle Contracts Core). Contract Groups provide a categorization mechanism that allows users to organize contracts into logical groupings — for example by business line, counterparty class, or internal ownership — and to apply group-level access rules such as public or private visibility. The package body, delivered under the APPS schema with a header reference to OKCPCGPB.pls (version 120.0, dated 2005), encapsulates the business logic and persistence operations for creating, maintaining, validating, and deleting these groups, and exposes them to forms, concurrent programs, and custom extensions through a stable public interface. Internally it relies on the Oracle Tool Kit record and table types (cgpv_rec_type and cgpv_tbl_t) and on the standard WHO columns (created_by, creation_date, last_updated_by, last_update_date, last_update_login) to maintain audit integrity. Helper routines such as migrate_cgpv map attribute and descriptive columns from one record payload to another, which is typical of the multi-language (NLS/MLS) row handling used throughout the ETRM module.

Key Procedures and Functions

The package exposes more than 30 documented entry points, grouped functionally as follows:

Tables Accessed

Per the ETRM metadata, the only table referenced through an APPS synonym is PLITBLM, the Tool Kit persistent table historically used by Oracle Forms to stage record-list data. Business data itself is written to the Contract Groups base and translation tables (OKC_CONTRACT_GROUPS and its MLS counterpart), with the WHO columns populated by the API and validation delegated to the validator functions described above. The package is referenced by 11 other packages, indicating that it acts as a foundational dependency for higher-level contract APIs.

Usage Notes

This package is invoked primarily from the Contract Groups setup and maintenance forms in the Contracts workbench, from concurrent programs that bulk-load or migrate group definitions, and from custom code that needs to create or validate a group without direct table DML. In Oracle EBS 12.1.1 and 12.2.2 the recommended pattern is to call VALIDATE_* first, obtain the resulting record type, then call CREATE_* or UPDATE_*, supplying the object_version_number for optimistic locking. The l_debug variable and the AFLOG_ENABLED profile option enable diagnostic logging. Direct inserts or updates against the underlying Contract Groups tables should be avoided, since they bypass the validation and locking logic implemented here.