Search Results pqh_accommodations_f




Overview

PQH_ACCOMMODATIONS_F is a datetracked ("_F" denoting the effective-dated table) transactional table owned by the HR schema and delivered as part of the Public Sector HR (PQH) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. The table stores descriptive and operational information about accommodations—physical or residential units used by public sector agencies for housing, assignment, or facility administration—that are maintained as part of an agency's accommodation inventory. It is not part of Oracle Human Resources core (PER) datetracking, but follows the same effective-dating conventions, allowing multiple historical versions of each accommodation record to coexist.

Based strictly on the heuristic Data Vault classification mined from the FK structure provided in the ETRM metadata, this object is classified as standalone. In Data Vault modeling terms, this suggests the table behaves primarily as a reference or descriptive entity (nearest to a hub or a hub-plus-satellite combination) with no documented foreign key dependencies to other transactional children. Analysts should treat it as a master-level repository rather than a link table in any downstream dimensional model.

Key Information Stored

The table contains 99 documented physical columns. The most significant are:

Common Use Cases and Queries

Typical reporting scenarios include accommodation inventory listing, capacity analysis, and rental valuation. A standard current-row query is:

  • Current inventory: SELECT ACCOMMODATION_ID, ACCOMMODATION_NAME, ACCOMMODATION_TYPE, RENTAL_VALUE FROM HR.PQH_ACCOMMODATIONS_F WHERE TRUNC(SYSDATE) BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE;
  • Historical versions of a unit: SELECT * FROM HR.PQH_ACCOMMODATIONS_F WHERE ACCOMMODATION_ID = :id ORDER BY EFFECTIVE_START_DATE;
  • Capacity summary by business group: aggregate MAIN_ROOMS and FAMILY_SIZE grouped by BUSINESS_GROUP_ID.
  • Accessibility reporting: filter on SUITABILITY_DISABLED = 'Y'.

Because the table is DateTracked, all queries must constrain on effective dates unless the intent is a full-history report.

Related Objects