Search Results psb_attribute_values_pvt




Overview

The APPS.PSB_ATTRIBUTE_VALUES_PVT package body is a private (PVT-classified) PL/SQL API within the Oracle E-Business Suite application schema. It belongs to the PSB module, which supports position and budget/position-control functionality used in Oracle Human Resources and Public Sector configurations. Its core business function is to encapsulate the low-level data manipulation logic for attribute value records associated with position assignments. Attribute values in this context represent the flexible, extensible characteristics that are captured against a position assignment — for example, qualifying criteria, coded descriptive attributes, or configuration-specific data elements that vary by implementation.

Because the package is classified as PVT, it is intended as an internal implementation layer rather than a public integration surface. It centralizes the insert, update, delete, locking, and referential-integrity operations for attribute values so that higher-level APIs and forms do not manipulate the underlying base tables directly. This design enforces consistent validation, concurrency handling, and error reporting through the Oracle Application Object Library utilities.

Key Procedures and Functions

The ETRM metadata documents five procedures or functions within this package body. Their names and purposes are as follows:

  • INSERT_ROW — Creates a new attribute value record. It performs the required column defaulting and validation before writing the row, and typically returns or exposes the newly created identifier to the caller.
  • LOCK_ROW — Acquires a row-level lock on an existing attribute value record, implementing optimistic or pessimistic concurrency control so that simultaneous updates do not overwrite one another.
  • UPDATE_ROW — Modifies an existing attribute value record. It applies the changed attribute columns while preserving audit and WHO columns through the standard EBS API conventions.
  • DELETE_ROW — Removes an attribute value record, performing any dependency or integrity checks required before the physical or logical delete is carried out.
  • CHECK_REFERENCES — Validates referential integrity and business rule constraints. It verifies that dependent relationships — such as those to position assignments — remain consistent before a row is inserted, updated, or deleted.

The documentation does not expose individual parameter lists, and no signature detail should be assumed beyond the described purpose.

Tables Accessed

The package body references two base tables through APPS synonyms:

  • PSB_ATTRIBUTE_VALUES — The primary table holding the attribute value rows. All five procedures operate against this table as the principal target of insert, update, delete, lock, and reference-check operations.
  • PSB_POSITION_ASSIGNMENTS — The parent or related table providing the position assignment context to which attribute values are attached. It is consulted for referential validation, ensuring attribute values are tied to a valid assignment.

In addition, the metadata lists dependencies on standard EBS infrastructure packages, including FND_API, FND_MESSAGE, FND_MSG_PUB, and APP_EXCEPTION, which supply the error-handling, message-stack, and API framework behavior used throughout the package.

Usage Notes

PSB_ATTRIBUTE_VALUES_PVT is not referenced by any other database object according to the ETRM metadata, confirming its role as an internal helper rather than a publicly exposed integration point. The metadata also notes it is referenced by five other packages, indicating that sibling or higher-level PSB packages call into this private layer to perform routine attribute value maintenance. It is typically invoked indirectly — through those calling packages, through Oracle Forms–based maintenance screens that delegate to the underlying API, or through concurrent programs that process position assignment data in bulk. Custom code should prefer the documented public APIs of the PSB module; direct invocation of this PVT package is generally reserved for the module's own internal callers and should be treated as subject to change across releases.