Search Results okc_ubl_pvt




Overview
Explore in AI Chat

Overview

OKC_UBL_PVT is the private implementation package body for the Oracle E-Business Suite Contracts (OKC) module, dedicated to the management of User Bins (UBL). In Oracle Contracts, a "user bin" is a named, reusable container of well-defined business values — typically statuses, classifications, group codes, or lookup categories — that a customer defines to control how contract terms, conditions, and supporting data are grouped and selected during authoring. The package encapsulates the low-level DML, concurrency control, and validation logic required to create, copy, maintain, and delete these bins in a controlled and auditable manner.

Consistent with Oracle's layered PL/SQL design, OKC_UBL_PVT is the private counterpart of a public API. The public interface of the OKC Contracts family (notably OKC_API) exposes supported calls to forms, concurrent programs, and external integrations, while OKC_UBL_PVT supplies the internal procedures that the public layer invokes. Because the package is marked "PVT" and referenced by two other packages, it is a shared internal utility rather than an entry point intended for direct customer use.

Key Procedures and Functions

The documented API surface comprises thirteen procedures and functions. The principal row-level operations provide the standard CRUD model used throughout Oracle's private packages:

  • QC — quality control; performs the internal consistency and referential checks applied before and after a bin record is persisted.
  • CHANGE_VERSION — manages the object version attribute, supporting optimistic locking and change-tracking across revisions of a bin.
  • API_COPY — copies an existing user bin to a new bin, enabling reuse and template-style duplication of bin definitions.
  • INSERT_ROW — inserts a new user bin record and its descriptive attributes.
  • LOCK_ROW — acquires a row-level lock for concurrency control during update or delete operations.
  • UPDATE_ROW — modifies existing bin data while preserving version and audit information.
  • DELETE_ROW — removes a user bin record once dependent references permit.
  • VALIDATE_ROW — applies business rules to the row (required values, valid combinations, and profile-driven defaults) before the write proceeds.

Remaining documented procedures follow the same naming family and support the surrounding maintenance and validation flow. Together these routines implement the bin lifecycle from validation through copy, update, and deletion.

Tables Accessed

The package resolves its base objects through APPS synonyms. The documented tables are:

  • OKC_USER_BINS — the primary persistent store for user bin definitions. All insert, update, delete, lock, and copy operations for bins ultimately read from and write to this table.
  • PLITBLM — an Oracle general-purpose PL/SQL index-by table type used internally as an in-memory structure. It is referenced as a type rather than as a business table, and supports the package's collection-based processing.

The package additionally depends on the standard utility packages FND_API and FND_GLOBAL (message and error handling, environment context), FND_PROFILE (profile option access), APP_EXCEPTIONS (error propagation), OKC_API and OKC_P_UTIL (Contracts business logic and common utilities), and STANDARD, the base PL/SQL package. Notably, the ETRM dependency extract states that OKC_UBL_PVT is not referenced by any database object, while other package metadata records that it is invoked by two other packages within the OKC family.

Usage Notes

OKC_UBL_PVT is an internal implementation layer and is not invoked directly from Oracle Contracts forms, concurrent programs, or customer-written code. It is called by the public Contracts API and by the two dependent OKC packages that manage user bin administration. Developers extending contract defaulting or bin configuration should use the supported public Contracts API rather than calling OKC_UBL_PVT procedures directly, so that validation, versioning, and audit behaviour remain intact across EBS 12.1.1 and 12.2.2 environments.