Search Results oks_ibint_pub




Overview
Explore in AI Chat

Overview

OKS_COD_PVT is a private PL/SQL package belonging to the Oracle Service (OKS) module of Oracle E-Business Suite, delivered under the APPS schema. The suffix PVT denotes a private API package: it provides the internal, low-level data manipulation and validation logic that supports the public service contracts APIs and other integration packages. The package is primarily concerned with the order details and change-order (COD) data structures used within the Service Contracts foundation tables, exposing controlled insert, update, delete, and validation routines against the OKS_K_ORDER_DETAILS entity.

In the Oracle EBS 12.1.1 and 12.2.2 releases this package is certified VALID and forms part of the dependency chain beneath several higher-level PL/SQL APIs, including OKS_IBINT_PUB, OKS_OMINT_PUB, OKS_ORDER_DETAILS_PUB, OKS_ORDER_DETAILS_PVT, OKS_COVERAGES_PVT, OKS_EXTWAR_UTIL_PVT, and OKS_INTEGRATION_UTIL_PUB. It in turn depends on the generic FND_API and OKC_API utility packages, the standard SYS.STANDARD package, and the OKS_K_ORDER_DETAILS table and its view.

Key Procedures and Functions

The ETRM metadata documents eighteen procedures and functions within OKS_COD_PVT, of which the following are identified by name. Descriptions are limited to documented purpose; parameter signatures are intentionally omitted.

  • API_COPY — Copies an existing order-detail or change-order record, supporting duplication scenarios in service contract processing.
  • CHANGE_VERSION — Advances the version of a record, consistent with the Oracle EBS API versioning convention used for contract changes.
  • QC — A quick-check routine used to verify the existence or validity of a record before further processing.
  • INSERT_ROW — Inserts a new row into the underlying order-details structure, performing the standard WHO-column and validation handling expected of an EBS private API.
  • UPDATE_ROW — Updates an existing row, applying the same validation and concurrency conventions as INSERT_ROW.
  • DELETE_ROW — Removes a row, typically a logical delete consistent with EBS data-retention practice.
  • LOCK_ROW — Acquires a row-level lock to support optimistic concurrency control during multi-step transactions.
  • VALIDATE_ROW — Performs entity-level validation of the attributes before insert, update, or delete proceeds.

The remaining ten procedures and functions are not individually itemised in the available metadata; they support the above routines and the overall order-detail change lifecycle.

Tables Accessed

The documented tables referenced through APPS synonyms are:

  • OKS_K_ORDER_DETAILS — The core order-detail entity table holding the change-order and order-line detail records this package manipulates. It is the principal read/write target of INSERT_ROW, UPDATE_ROW, DELETE_ROW, LOCK_ROW, and VALIDATE_ROW.
  • OKS_K_ORDER_DETAILS_V — The validating view over the same entity, used during validation and quick-check processing.
  • PLITBLM — The standard Oracle EBS PL/SQL index-by table type used as the in-memory collection structure passed into and out of the private API routines.

These tables supply the persistence layer for order-detail changes triggered by higher-level integration flows such as Installed Base and Order Management interfaces.

Usage Notes

OKS_COD_PVT is a private package and is not intended for direct invocation from forms, concurrent programs, or customer extensions. It is invoked indirectly by its referencing public and private APIs — notably OKS_IBINT_PUB and OKS_ORDER_DETAILS_PVT — which call OKS_COD_PVT during order-detail creation, modification, and change-order processing.

Because it depends on FND_API and OKC_API, callers must respect standard EBS API conventions, including initialisation of the API context and handling of the returned x_return_status and message-stack outputs. Customisations that bypass this package in favour of direct DML against OKS_K_ORDER_DETAILS risk corrupting the validation and concurrency logic maintained here. When troubleshooting order-detail or change-order issues in 12.1.1 or 12.2.2, this package is best inspected after first examining the calling public API in the dependency chain.