Search Results oks_insert_row_upg




Overview
Explore in AI Chat

Overview

OKS_BRS_PVT is a private PL/SQL package in the APPS schema that encapsulates the core business logic for Oracle Service Contracts (OKS) billing rate schedules. The suffix PVT designates the package as a private API layer, meaning it is not intended for direct invocation by external or customer-written code. Instead, it functions as the engine behind the public billing rate schedule API, providing the primitive row-level operations, validation, versioning, and locking behavior that the public layer exposes to callers. In Oracle EBS 12.1.1 and 12.2.2, this package is central to the creation and maintenance of billing rate schedules, which define how service contract coverage is priced and invoiced across a contract period.

The package follows the standard Oracle Application Object Library (AOL) API architecture: a specification paired with a package body, reliance on FND_API and OKC_API utilities, and a set of insert, update, delete, and validation entry points consistent with other EBS private APIs.

Key Procedures and Functions

The ETRM metadata documents twenty procedures and functions within OKS_BRS_PVT. The principal documented operations are:

  • QC — Quality control routine, typically invoked to verify that the package environment is correctly initialized before the API is used.
  • INSERT_ROW — Creates a new billing rate schedule row in the underlying base table.
  • UPDATE_ROW — Modifies attributes of an existing billing rate schedule row.
  • DELETE_ROW — Removes a billing rate schedule row.
  • LOCK_ROW — Acquires a row-level lock to enforce concurrency control during update or delete operations.
  • VALIDATE_ROW — Performs business-rule validation on the row attributes prior to persistence.
  • CHANGE_VERSION — Handles version control semantics required when a schedule is modified under the EBS versioning model.
  • CREATE_VERSION — Creates a new version of an existing billing rate schedule.
  • RESTORE_VERSION — Reinstates a previously defined version of a billing rate schedule.
  • API_COPY — Copies billing rate schedule data, commonly used when duplicating a schedule during contract copy or template operations.

Together these procedures implement the complete lifecycle of a billing rate schedule row: validation, insertion, update, locking, version management, and deletion.

Tables Accessed

The package references the following tables through APPS synonyms:

  • OKS_BILLRATE_SCHEDULES — The primary base table holding billing rate schedule records. INSERT_ROW, UPDATE_ROW, DELETE_ROW, and LOCK_ROW operate against this table.
  • OKS_BILLRATE_SCHEDULES_H — The history (audit) table maintained for versioning. CREATE_VERSION, RESTORE_VERSION, and CHANGE_VERSION write to this table to preserve prior row states.
  • PLITBLM — The standard EBS PL/SQL index-by table used for bulk DML and message handling within AOL-style APIs.

The metadata also lists OKS_BILLRATE_SCHEDULES_V, the view counterpart, referenced through the dependency chain. These tables collectively store pricing, billing, and schedule detail consumed by downstream service contract billing processes.

Usage Notes

OKS_BRS_PVT is a private package and should not be called directly from custom code. It is invoked indirectly through the public billing rate schedule API. The ETRM dependency report explicitly shows OKS_BRS_PVT referenced by OKS_COVERAGES_PVT and by the upgrade routine OKS_INSERT_ROW_UPG, which explains why a search for "oks_insert_row_upg" surfaces this package. That upgrade script calls OKS_BRS_PVT to migrate or seed billing rate schedule rows during patch and upgrade operations.

Typical invocation paths include Service Contracts forms that manage coverage and billing schedules, concurrent programs performing contract pricing or renewal, and the OKS upgrade utilities. Custom integrators requiring billing rate schedule maintenance should use the public OKS API wrappers, which enforce the FND_API savepoint, message, and validation conventions that OKS_BRS_PVT assumes are already in place. Direct calls bypassing the public layer risk inconsistent versioning and circumvent standard validation, so the package should be treated strictly as an internal implementation detail of the Service Contracts billing rate schedule API stack.