Search Results pqh_documents_f




Overview
Explore in AI Chat

Overview

PQH_DOCUMENTS_F is an Oracle EBS table owned by the HR schema and delivered under the PQH (Public Sector HR) product family. It is a document management table used primarily for self-service PDF print functionality, allowing Oracle EBS to record, store, and retrieve document definitions that can be rendered to PDF and presented to end users through employee or manager self-service. In Release 12.1.1 and 12.2.2, the table is reported as VALID and exposes 18 documented columns in the physical schema of ETRM 12.2.2.

The object is an effective-dated (date-tracked) table: business attributes are versioned using EFFECTIVE_START_DATE and EFFECTIVE_END_DATE, and the composite primary key PQH_DOCUMENTS_F_PK is composed of DOCUMENT_ID, EFFECTIVE_START_DATE, and EFFECTIVE_END_DATE. A second unique index, PQH_DOCUMENTS_F_UK, is defined on SHORT_NAME, providing a human-readable business identifier for each document. From a heuristic Data Vault modeling perspective, the table's classification is standalone, i.e., neither a pure hub, link, nor satellite has been mined from the FK structure. A reasonable suggestion is to treat DOCUMENT_ID as a hub-like business key candidate, with the effective-dated descriptive columns modeled as satellite attributes. Because the classification is heuristic rather than authoritative, it should be confirmed against the actual data model before use.

Key Information Stored

The columns most relevant to developers, report writers, and integrators are:

  • DOCUMENT_ID — The surrogate identifier portion of the composite primary key; the primary handle for retrieving a document record.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — The date-effective range that controls which version of the document definition is in force at a given time.
  • SHORT_NAME — Business-key candidate defined by PQH_DOCUMENTS_F_UK; the unique, user-meaningful reference for a document.
  • DOCUMENT_NAME — The descriptive, display-oriented name shown to users.
  • FILE_ID — The pointer to the underlying file/template stored in the document repository; the link between the row and its actual PDF source.
  • ENABLE_FLAG — Enables or disables the document for self-service use.
  • FORMULA_ID — Associates the document with a formula, allowing conditional or calculated document logic.
  • DOCUMENT_CATEGORY — Classifies the document for filtering and reporting.
  • LOB_CODE — Line-of-business code, used for organizational scoping.
  • LANGUAGE, TERRITORY — Localization and regionalization attributes for multilingual and multiterritory deployments.
  • OBJECT_VERSION_NUMBER — Optimistic locking column used by the EBS framework.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns.

Common Use Cases and Queries

Typical queries resolve the currently effective version of a document by its short name, honoring the date-effective window:

  • Retrieve active documents for self-service: SELECT * FROM hr.pqh_documents_f WHERE enable_flag = 'Y' AND SYSDATE BETWEEN effective_start_date AND effective_end_date;
  • Resolve a document by business key: filter on short_name and the current effective range.
  • Report available PDF print definitions by category: SELECT document_id, short_name, document_name, document_category FROM hr.pqh_documents_f WHERE document_category = :p_category AND SYSDATE BETWEEN effective_start_date AND effective_end_date;

Reporting patterns frequently join on file_id to locate stored content and use language/territory for localized output. Always constrain on the effective dates to avoid returning superseded versions of a document.

Related Objects

The metadata classifies this object as standalone, so no enforced foreign keys are documented for PQH_DOCUMENTS_F. Functional relationships typically involve:

  • The file/document repository underlying the FILE_ID reference, joined on the file identifier.
  • The formula infrastructure referenced by FORMULA_ID.
  • Self-service PDF print setup and concurrent programs that consume SHORT_NAME and DOCUMENT_ID.
  • Standard HR audit/WHO columns linked to the application user via CREATED_BY and LAST_UPDATED_BY.

Because FK relationships are not mined in the supplied metadata, joins should be verified against the actual HR schema before being used in production SQL.