Results for “grade_desc”

32 results




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

Overview

PQH_PTX_HISTORY_V is a reporting view owned by the APPS schema within the Public Sector HR (PQH) product family of Oracle E-Business Suite, documented as VALID in ETRM for releases 12.1.1 and 12.2.2. The view exposes historical position transaction data, presenting the effective-dated snapshot of position definitions as recorded when a Public Sector position transaction was applied. It serves as the read-only history surface for reporting and integration, allowing downstream consumers to reconstruct how a position looked at the point each transaction was executed without directly joining the highly normalized position and transaction base tables.

The view attributes every row to a POSITION_ID and EFFECTIVE_START_DATE pair, and it decorates the raw transaction record with decode-based descriptions for lookup-driven attributes such as transaction status, position type, location, organization, job, availability status, payroll, pay basis, grade, step, and grade rule values. Because these descriptions are derived through HR_GENERAL and PQH_UTILITY decode routines at query time, the view reflects the current lookup meanings against the historical transaction record. The user-search term "work_any_country" is commonly associated with the position transaction history area, since the transaction and history views are frequently queried together when auditing position and deployment attributes across legislation or country contexts.

Underlying Base Objects

The documented referenced base objects are HR_ALL_POSITIONS_F (synonym), HR_ALL_POSITIONS_F_TL (synonym), PER_DEPLOYMENT_FACTORS (synonym), PQH_POSITION_TRANSACTIONS (synonym), HR_GENERAL (package), and PQH_UTILITY (package). The view text confirms these dependencies: position attributes are drawn from the PSF alias, consistent with HR_ALL_POSITIONS_F and its translated name column sourced from HR_ALL_POSITIONS_F_TL, and deployment-level attributes such as SERVICE_MINIMUM, WORK_SCHEDULE, and WORK_DURATION are drawn from the DPF alias, corresponding to PER_DEPLOYMENT_FACTORS.

The historical dimension is anchored by PQH_POSITION_TRANSACTIONS, which records each position transaction and its applied status. HR_GENERAL supplies the DECODE_LOOKUP, DECODE_LOCATION, DECODE_ORGANIZATION, DECODE_JOB, DECODE_GRADE, DECODE_STEP, DECODE_PAYROLL, DECODE_PAY_BASIS, DECODE_AVAILABILITY_STATUS, and DECODE_GRADE_RULE functions, while PQH_UTILITY supplies GET_POS_REC_EED and the DECODE_GRADE_RULE variants returning VALUE, MIN, MID, and MAX. All base tables are referenced through APPS synonyms, so the view must be queried in the APPS context or through a synonym granted to the calling schema.

Key Columns

Common Use Cases and Queries

Typical uses include position history audits, transaction reconciliation against PQH_POSITION_TRANSACTIONS, and integration extracts feeding downstream HR or payroll systems. A representative query follows.

  • SELECT POSITION_ID, EFFECTIVE_START_DATE, NAME, POSITION_TYPE, DATE_EFFECTIVE, FTE FROM APPS.PQH_PTX_HISTORY_V WHERE POSITION_ID = :p_position_id ORDER BY EFFECTIVE_START_DATE;
  • Join to PQH_POSITION_TRANSACTIONS on POSITION_ID and EFFECTIVE_START_DATE to reconcile applied history rows with their source transactions.
  • Filter on EFFECTIVE_START_DATE ranges to reconstruct position state as of a reporting date, accounting for the decode-based descriptions applied at run time.