Search Results delete_contract_grpngs

Overview

OKC_CONTRACT_GROUP_PUB is the public (PUB-classified) PL/SQL API for managing contract groups within the Oracle Contracts (OKC) module of Oracle E-Business Suite. A contract group provides a way to logically associate multiple contracts—through group headers and group-member (contract-to-group) relationships—supporting categorization, grouping, and query-driven retrieval of contracts for reporting and administrative purposes. The package is owned by APPS and exposes a set of published entry points that other application modules and custom extensions are permitted to call, isolating callers from the underlying private implementation contained in OKC_CONTRACT_GROUP_PVT and related packages.

The header identifies the source revision and the use of shared subtype definitions, including cgpv_rec_type and cgcv_rec_type (contract-group header and contract-group/contract records) plus their table counterparts and the query-key table type qry_k_tbl. These records carry the data payload that the public procedures accept and return, ensuring that both header and member information are validated and persisted consistently as a unit.

Key Procedures and Functions

The package documents thirty procedures and functions. The primary data-manipulation entry points are:

• CREATE_CTR_GROUP and UPDATE_CTR_GROUP — the procedures most directly associated with the search term update_ctr_group. CREATE_CTR_GROUP creates a new contract-group header together with its associated group members; UPDATE_CTR_GROUP modifies an existing group header and its member rows. Both follow the standard OKC API signature conventions: an API version, an initialization flag, the standard return-status/message-count/message-data OUT parameters, an IN record or table for input, and OUT copies reflecting the processed data.
• VALIDATE_CTR_GROUP — performs validation of a proposed contract group without persisting changes.
• CREATE_CONTRACT_GROUP, UPDATE_CONTRACT_GROUP, DELETE_CONTRACT_GROUP, LOCK_CONTRACT_GROUP, VALIDATE_CONTRACT_GROUP — the full create/update/delete/lock/validate lifecycle for contract-group header records.
• CREATE_CONTRACT_GRPNGS, UPDATE_CONTRACT_GRPNGS, DELETE_CONTRACT_GRPNGS, LOCK_CONTRACT_GRPNGS, VALIDATE_CONTRACT_GRPNGS — the parallel lifecycle for contract-group member associations (group-to-contract linkages).
• VALIDATE_NAME, VALIDATE_PUBLIC_YN, VALIDATE_SHORT_DESCRIPTION, VALIDATE_RECORD — granular validation routines for individual attributes such as the group name, the public flag, and the short description, plus a combined record validator.
• SET_SEARCH_STRING — prepares or normalizes a search string used when querying contracts belonging to groups.
• GET_QUERIED_CONTRACTS — returns the set of contracts matching a supplied group query, supporting selection-screen and reporting use cases.
• ADD_LANGUAGE — the standard multilingual (MLS) routine that propagates translated rows into the base tables, a common companion procedure in APPS APIs.

Tables Accessed

According to the documented metadata, the package references the table via the APPS synonym PLITBLM. PLITBLM is the translation (MLS) table used for maintaining language-specific text, which is consistent with the presence of the ADD_LANGUAGE procedure; translated names and descriptions for contract groups are stored and maintained through this table. Contract-group header and member data are persisted through the corresponding OKC base tables (for example, the OKC_CONTRACT_GROUPS structures) accessed by the underlying private package; validation reads reference data to confirm that supplied group names, public flags, and short descriptions satisfy business rules before insert, update, or lock operations proceed.

Usage Notes

OKC_CONTRACT_GROUP_PUB is intended to be invoked by Oracle Contracts forms, concurrent programs, and approved custom code rather than called directly from ad hoc scripts. Callers should pass a valid p_api_version, honor the p_init_msg_list flag, and always inspect x_return_status, x_msg_count, and x_msg_data to detect failures—the package declares G_EXCEPTION_HALT_VALIDATION and standard error tokens for unexpected conditions. Validation procedures should be called before create or update to surface attribute errors early. Because the package participates in the standard OKC API messaging model, callers in EBS 12.1.1 and 12.2.2 can rely on consistent error handling and MLS behavior across releases.