Results for “pqh_document_attributes_f”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PQH_DOCUMENT_ATTRIBUTES_F is a date-tracked ( "_F" ) table in the HR schema owned by the Oracle E-Business Suite, classified under the PQH – Public Sector HR product family. Its documented purpose is to map attributes of a document to known transaction attributes, effectively serving as the attribute-level detail store for documents managed within Public Sector HR flows. Each row associates a specific document (DOCUMENT_ID) with a named tag (TAG_NAME) and a referenced attribute definition (ATTRIBUTE_ID), scoped by an effective date range. Because the entity carries Effective Start and End Dates and holds descriptive attribute assignments rather than defining the master attribute metadata, the heuristic Data Vault classification is satellite-leaning; the master attribute definitions reside in the referenced PQH_ATTRIBUTES table.

Key Information Stored

The table is documented with twelve columns in ETRM 12.2.2. The surrogate primary key is PQH_DOCUMENT_ATTRIBUTES_F_PK, composed of DOCUMENT_ATTRIBUTE_ID, EFFECTIVE_START_DATE, and EFFECTIVE_END_DATE. DOCUMENT_ATTRIBUTE_ID is the system-generated identifier for each attribute assignment row; the two date columns implement the standard EBS date-tracking pattern that allows historical, current, and future versions of an attribute assignment to coexist.

• DOCUMENT_ATTRIBUTE_ID – surrogate identifier; part of the primary key.
• DOCUMENT_ID – the document to which the attribute mapping belongs; part of the UK1 business-key candidate.
• ATTRIBUTE_ID – foreign key to PQH_ATTRIBUTES, pointing to the master attribute definition.
• TAG_NAME – the tag under which the attribute is exposed on the document; part of the UK1 business-key candidate.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE – the validity window for the row; both are part of the primary key.
• OBJECT_VERSION_NUMBER – optimistic locking token maintained by the framework.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE – standard Who columns capturing audit context.

Two unique indexes are documented as business-key candidates: PQH_DOCUMENT_ATTRIBUTES_F_PK (DOCUMENT_ATTRIBUTE_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE) and the UK1 candidate PQH_DOCUMENT_ATTRIBUTES_F_UK1 (DOCUMENT_ID, TAG_NAME, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE). The UK1 candidate gives the pragmatically useful business identity: a given tag on a given document is unique per effective date range.

Common Use Cases and Queries

Typical usage centers on resolving the current attribute set for a document, joining through to the attribute master, and reporting on attribute usage across documents. A standard current-row pattern applies:

• Current attributes for a document: select from PQH_DOCUMENT_ATTRIBUTES_F where DOCUMENT_ID = :doc and sysdate between EFFECTIVE_START_DATE and EFFECTIVE_END_DATE.
• Business-key lookup by tag: filter on DOCUMENT_ID and TAG_NAME to locate a specific attribute assignment and its validity window.
• Attribute master enrichment: join ATTRIBUTE_ID to PQH_ATTRIBUTES to obtain the attribute name, data type, and validation metadata.
• As-of and history reporting: drop the sysdate predicate and order by EFFECTIVE_START_DATE to render the full version history of a document's attributes.
• Data-integrity auditing: detect overlapping effective ranges or orphaned ATTRIBUTE_ID references against PQH_ATTRIBUTES.

Related Objects

• PQH_ATTRIBUTES – referenced via PQH_DOCUMENT_ATTRIBUTES_F.ATTRIBUTE_ID; the FK target supplying attribute definitions.
• PQH_DOCUMENTS (document master) – the parent entity implied by DOCUMENT_ID, providing document headers that these attribute rows detail.
• PQH_ATTRIBUTES_TL / attribute lookup views – used to resolve translatable attribute names for reporting.
• PQH_DOCUMENT_ATTRIBUTES_F_UK1 index – enforces the document-plus-tag business uniqueness used by API and form logic.
• Public Sector HR document APIs and concurrent programs – the consumers that insert, update, and end-date rows in this table when document transactions are processed.