Search Results pqh_document_attributes_f_pk




Overview
Explore in AI Chat

Overview

The PQH_DOCUMENT_ATTRIBUTES_F table is a core data object within the Oracle E-Business Suite Public Sector Human Resources (PQH) module. It functions as a mapping table, establishing and maintaining the relationships between document attributes and known transaction attributes. Its primary role is to enable the structured association of specific data points (attributes) from documents with corresponding attributes defined within the HRMS transaction framework. This mapping is crucial for automating data validation, routing, and processing workflows in public sector personnel actions, where supporting documentation must be explicitly linked to transactional data. As a date-effective table (indicated by the _F suffix and the EFFECTIVE_START_DATE and EFFECTIVE_END_DATE columns), it supports the tracking of historical changes to these attribute mappings over time, allowing for accurate auditing and retroactive reporting.

Key Information Stored

The table's structure is designed to enforce unique mappings and maintain historical integrity. The primary identifier is the DOCUMENT_ATTRIBUTE_ID, which uniquely identifies each mapping record. The EFFECTIVE_START_DATE and EFFECTIVE_END_DATE columns define the period for which the mapping is active, a standard pattern for date-tracked entities in HRMS. A unique key constraint ensures that for a given DOCUMENT_ID, each TAG_NAME is unique, preventing duplicate attribute assignments to the same document. The ATTRIBUTE_ID is a foreign key that links directly to the PQH_ATTRIBUTES table, pointing to the specific transaction attribute definition. In summary, the key columns are:

  • DOCUMENT_ATTRIBUTE_ID: Primary surrogate key for the mapping record.
  • DOCUMENT_ID: Identifier for the associated document.
  • TAG_NAME: The specific attribute tag or name from the document being mapped.
  • ATTRIBUTE_ID: Foreign key to PQH_ATTRIBUTES, linking to the transactional attribute.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE: Defines the date range of the mapping's validity.

Common Use Cases and Queries

A primary use case is generating reports that show all active attribute mappings for a specific document type or transaction, which is essential for compliance audits. Support personnel may query this table to troubleshoot why document data is not populating a transaction correctly, verifying the mapping is active and correct. A common SQL pattern retrieves all current mappings for a document: SELECT tag_name, attribute_id FROM pqh_document_attributes_f WHERE document_id = :doc_id AND SYSDATE BETWEEN effective_start_date AND NVL(effective_end_date, SYSDATE); Another frequent operation is joining to PQH_ATTRIBUTES to get the descriptive name of the mapped transaction attribute for a report: SELECT pda.tag_name, pa.attribute_name FROM pqh_document_attributes_f pda, pqh_attributes pa WHERE pda.attribute_id = pa.attribute_id AND pda.document_id = :doc_id; These queries are foundational for ensuring the integrity of document-driven transaction processes.

Related Objects

The table has direct dependencies within the PQH product schema. Its most critical relationship is with the PQH_ATTRIBUTES table, enforced by a foreign key on the ATTRIBUTE_ID column. This table holds the master definition of transaction attributes that document tags are mapped to. The table is also intrinsically linked to the document management infrastructure within EBS, likely referenced by the document entity identified by DOCUMENT_ID. The two defined constraints, PQH_DOCUMENT_ATTRIBUTES_F_PK (primary key) and PQH_DOCUMENT_ATTRIBUTES_F_UK (unique key), are essential related database objects that maintain data integrity. Custom APIs, workflows, and validation engines within the Public Sector HR module will reference this mapping table to process document data accurately.