Search Results oks_sll_pvt




Overview

OKS_SLL_PVT is an internal (private) PL/SQL package body in the APPS schema belonging to the Oracle E-Business Suite Service Contracts (OKS) module. Its "PVT" API classification indicates that it is not a public, externally supported interface; instead it functions as a helper layer that supports the Service Contracts stream-level functionality, most likely within the Service Line / subscription-style line processing area of the Contracts and Service Contracts (OKC/OKS) stack. The package provides low-level data manipulation and validation logic for stream levels, wrapping the underlying stream-level base entity with controlled insert, update, delete, lock, and copy operations.

The package is currently VALID in 12.1.1 and 12.2.2. It depends on several standard EBS foundation and OKC utilities, including FND_API, FND_GLOBAL, FND_MSG_PUB, APP_EXCEPTIONS, OKC_API, OKC_P_UTIL, and OKS_SLL_PVT itself. This dependency profile confirms that OKS_SLL_PVT follows the standard EBS API conventions: use of FND_MSG_PUB for error message handling, FND_GLOBAL for session context (user, login, application), APP_EXCEPTIONS and FND_API for exception signalling and return-status management, and OKC core utilities for contract-related processing. It is not referenced by any database object, meaning it is called only from other PL/SQL code and not exposed through database-level objects or views.

Key Procedures and Functions

The ETRM metadata documents 18 procedures/functions. The named procedures shown are QC, CHANGE_VERSION, API_COPY, INSERT_ROW, LOCK_ROW, UPDATE_ROW, DELETE_ROW, and VALIDATE_ROW. Their documented purposes are as follows:

  • QC — Quality-control/consistency checking routine, used to validate that a stream-level row satisfies structural and business prerequisites before further processing.
  • CHANGE_VERSION — Manages the versioning of stream-level records, supporting changes to the entity's version identifier as part of contract or line revision handling.
  • API_COPY — Copies stream-level data, typically used when duplicating a service line, template, or contract structure.
  • INSERT_ROW — Creates a new stream-level record.
  • LOCK_ROW — Acquires a lock on an existing stream-level row prior to update or delete, preventing concurrent modification.
  • UPDATE_ROW — Modifies an existing stream-level record.
  • DELETE_ROW — Removes a stream-level record.
  • VALIDATE_ROW — Validates a stream-level record prior to persistence, enforcing required attributes and business rules.

These procedures follow the standard EBS "API_COPY / INSERT_ROW / LOCK_ROW / UPDATE_ROW / DELETE_ROW / VALIDATE_ROW" pattern seen in the OKC/OKS entity infrastructure. Parameter lists are not documented in the ETRM excerpt and must not be assumed; callers should inspect the package specification in the target environment.

Tables Accessed

The package references two documented tables through APPS synonyms:

  • OKS_STREAM_LEVELS_B — The base table storing stream-level data. OKS_SLL_PVT performs its primary insert, update, delete, lock, and version-change operations against this table.
  • PLITBLM — The standard Oracle PL/SQL internal table type used in the STANDARD package; appears as a referenced object through normal PL/SQL compilation.

The metadata also lists OKS_STREAM_LEVELS_V (the view) among dependencies, consistent with read access for validation and query purposes. Together, the _B table and _V view form the stream-level entity, and this package is the private DML layer that maintains them.

Usage Notes

Because OKS_SLL_PVT is a PVT (private) package and is not referenced by any database object, it is not intended for direct invocation by customers or customizations. It is called internally by other Service Contracts packages — the metadata indicates it is referenced by 5 other packages — most often during service line processing, stream-level creation, copying of service structures, and version changes.

Typical invocation paths include Service Contracts forms and concurrent programs that manage service lines and subscriptions, as well as the public OKS/OKC APIs that internally route stream-level DML to this private package. Oracle support generally recommends that custom code call the corresponding public OKS APIs rather than OKS_SLL_PVT, because the private interface is subject to change without notice.

Standard EBS API behaviour applies: return status is communicated via FND_API conventions, errors through FND_MSG_PUB, and session context through FND_GLOBAL. Any debugging or extension of stream-level behaviour should be performed in a supported environment and validated against the package specification for the exact release.