Search Results pv_enty_attr_validations_u1

Overview

PV.PV_ENTY_ATTR_VALIDATIONS is a transactional table in the Oracle EBS Process Manufacturing (OPM) product family, owned by the PV schema. Its documented purpose is to store the validations associated with records in PV_ENTY_ATTRS, meaning it holds evidence of quality, compliance, or approval checks applied to entity attribute values in the ETRM (Enterprise Trade and Risk Management) / Process Manufacturing data model. The table resides in the APPS_TS_TX_DATA tablespace with PCT Free 10, and its unique index PV_ENTY_ATTR_VALIDATIONS_U1 resides in APPS_TS_TX_IDX.

From a Data Vault modeling perspective, the heuristic classification for this table is hub-leaning. It is anchored by a single-column surrogate primary key (VALIDATION_ID), carries standard Who columns, an OBJECT_VERSION_NUMBER for optimistic locking, and only a small number of descriptive attributes. This structure suggests it behaves as a hub for validation events, with dependent transactional detail (the validated attribute values) held in downstream tables. Its status is VALID, and no database objects are referenced by it, confirming it is a foundational record rather than a join or lookup table.

Key Information Stored

The table exposes 11 documented columns. The most significant are:

• VALIDATION_ID (NUMBER) — Surrogate primary key, defined by constraint PV_ENTY_ATTR_VALIDATIONS_PK and uniquely indexed via PV_ENTY_ATTR_VALIDATIONS_U1. This is also the business-key candidate identified in the unique index.
• VALIDATED_BY_RESOURCE_ID (NUMBER) — Identifies the resource (person, equipment, or system) that performed the validation.
• VALIDATION_DOCUMENT_ID (NUMBER) — References the supporting document for the validation, such as a certificate of analysis or inspection record.
• VALIDATION_NOTE (VARCHAR2, 240) — Free-text note describing the outcome or context of the validation.
• VALIDATION_DATE (DATE) — The date on which the validation was recorded.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN (DATE/NUMBER) — Standard Who columns providing audit trail and concurrency context.
• OBJECT_VERSION_NUMBER (NUMBER) — Standard Who column used for optimistic locking during concurrent updates.

The distinction between the surrogate key (VALIDATION_ID) and any natural business key is important: only VALIDATION_ID is enforced unique, so lookup by resource or document must be treated as non-unique filtering.

Common Use Cases and Queries

Typical uses include audit reporting, compliance traceability, and lineage reconciliation between validation events and the attribute values they qualify. Because the table is referenced by PV_ENTY_ATTR_VALUES through the VALIDATION_ID foreign key, analysts commonly join these two objects to reproduce the full validation-to-value chain. A representative query follows:

• Validation history by resource: SELECT v.VALIDATION_ID, v.VALIDATION_DATE, v.VALIDATION_NOTE FROM PV.PV_ENTY_ATTR_VALIDATIONS v WHERE v.VALIDATED_BY_RESOURCE_ID = :resource_id ORDER BY v.VALIDATION_DATE DESC;
• Validation-to-value linkage: SELECT a.VALIDATION_ID, a.ATTRIBUTE_VALUE, v.VALIDATION_DATE FROM PV.PV_ENTY_ATTR_VALUES a JOIN PV.PV_ENTY_ATTR_VALIDATIONS v ON a.VALIDATION_ID = v.VALIDATION_ID;
• Concurrency-safe update: reference OBJECT_VERSION_NUMBER in the WHERE clause of UPDATE statements to prevent lost updates under the EBS optimistic locking framework.

Related Objects

• PV_ENTY_ATTR_VALUES — References PV_ENTY_ATTR_VALIDATIONS via VALIDATION_ID (foreign key), carrying the individual validated values.
• PV_ENTY_ATTR_VALIDATIONS# — Documented dependent object (the hash/compile artifact referenced by this table).
• PV_ENTY_ATTRS — The parent attribute definition table whose validations are stored here, per the documented purpose statement.
• PV_ENTY_ATTR_VALIDATIONS_PK — Primary key constraint on VALIDATION_ID.
• PV_ENTY_ATTR_VALIDATIONS_U1 — Unique index on VALIDATION_ID in APPS_TS_TX_IDX.