Search Results pv_enty_attr_validations_pk

Overview

PV_ENTY_ATTR_VALIDATIONS is a Partner Management (PV) module table within the Oracle E-Business Suite 12.1.1 and 12.2.2 data model. The table stores column-level validation records for entity attributes defined in the Partner Management entity model. Entity attributes in PV describe configurable partner attributes — such as qualification criteria, tier definitions, and classification values — and this table governs whether a submitted attribute value conforms to the validation rules configured for that attribute.

Because it holds validation metadata rather than transactional partner data, the table functions as a reference and control entity within the PV schema. The ETRM metadata classifies it heuristically as hub-leaning in Data Vault terms. This classification applies only to the table's identifier structure: the primary key VALIDATION_ID is a single, stable, non-derived surrogate identifier, which matches the characteristic of a Data Vault hub. The descriptive columns (validation date, note, and auditor columns) are better modeled as a satellite attached to that hub. This is a modeling suggestion, not a functional attribute of the Oracle schema.

Key Information Stored

The table has a documented column count of 11. The most significant columns and their roles are:

• VALIDATION_ID — Surrogate primary key defined by constraint PV_ENTY_ATTR_VALIDATIONS_PK. A unique index, PV_ENTY_ATTR_VALIDATIONS_U1, is also defined on this column, making it both the physical key and the documented business-key candidate.
• VALIDATED_BY_RESOURCE_ID — Identifier of the resource or user who performed or is associated with the validation.
• VALIDATION_DOCUMENT_ID — Reference to the document against which the validation was carried out or recorded.
• VALIDATION_DATE — Date on which the validation occurred; used for ordering and age analysis.
• VALIDATION_NOTE — Free-text note capturing the outcome, exception, or commentary for the validation.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS WHO columns recording audit history and the login context of the last change.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the EBS framework to detect concurrent updates.

Surrogate key and business key are the same column here. No alternate unique business key (for example, a composite of validated-by, document, and date) is documented, so uniqueness of validation events is enforced only at the VALIDATION_ID level.

Common Use Cases and Queries

Typical usage centers on auditing which entity attribute values were validated, by whom, and when. A representative query joins validation records to the validated values:

• Validation audit report: select VALIDATION_ID, VALIDATED_BY_RESOURCE_ID, VALIDATION_DOCUMENT_ID, VALIDATION_DATE, and VALIDATION_NOTE, filtered by a date range.
• Linkage query joining PV_ENTY_ATTR_VALUES to PV_ENTY_ATTR_VALIDATIONS on VALIDATION_ID = VALIDATION_ID to retrieve values that carry a validation outcome.
• Exception reporting: retrieve rows where VALIDATION_NOTE is non-null and VALIDATION_DATE is older than a threshold, to flag stale or failed validations.
• Concurrency and integrity monitoring: confirm OBJECT_VERSION_NUMBER consistency and check for orphaned value rows using an outer join from PV_ENTY_ATTR_VALUES to this table.

Because VALIDATION_ID is uniquely indexed, predicate-driven lookups by that column return single rows and are the preferred access path for application and custom reporting SQL.

Related Objects

The documented relationship data identifies one direct dependency:

• PV_ENTY_ATTR_VALUES — The referencing table. Column PV_ENTY_ATTR_VALUES.VALIDATION_ID is a foreign key to PV_ENTY_ATTR_VALIDATIONS.VALIDATION_ID, making this the primary child of the validation table.
• PV_ENTY_ATTR_VALIDATIONS_PK — Primary key constraint on VALIDATION_ID.
• PV_ENTY_ATTR_VALIDATIONS_U1 — Unique index on VALIDATION_ID supporting key-based retrieval.
• Other PV entity attribute objects — Attribute definitions and value sets in the PV entity model supply the context in which VALIDATED_BY_RESOURCE_ID and VALIDATION_DOCUMENT_ID are meaningful.

Any deletion or renumbering of cells in this table must respect the foreign key from PV_ENTY_ATTR_VALUES to avoid orphaning validated attribute values.