Results for “ghr_pd_classifications_v1”

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

Overview

The GHR_PD_CLASSIFICATIONS_V1 view is a reporting and integration object owned by the APPS schema in Oracle E-Business Suite. It belongs to the GHR - US Federal Human Resources product family, which supports the position management, classification, and staffing requirements specific to U.S. federal agencies. The view exposes position description classification details, providing a stable, versioned access point to the classification data captured against a position description.

As a "V1" view, it forms part of Oracle's versioned view strategy, where a consistent, controlled interface is published for downstream consumers — concurrent programs, Oracle Reports, OAF/Forms pages, BI Publisher extracts, and third-party integration endpoints. Rather than querying base tables directly, report developers and integration architects are expected to reference this view, which insulates them from underlying schema changes while preserving a well-defined column contract. The view is documented as having a VALID status with the owner/schema APPS, confirming it is deployed and available for query in both EBS 12.1.1 and 12.2.2.

Underlying Base Objects

The view is defined over a single documented base object: the synonym GHR_PD_CLASSIFICATIONS (aliased in the view text as PDC). The view is a straightforward projection — it selects columns directly from the base table with no joins, filters, aggregations, or DISTINCT clauses. Its primary transformation is the exposure of the base table's ROWID under the alias ROW_ID, alongside the complete set of classification attributes.

Because the view references the synonym rather than the physical table by name, the underlying object resolves through the APPS synonym to the actual GHR base table. This mirrors the standard Oracle EBS convention of public synonyms layered over APPLSYS/APPS objects, and it means the view inherits the base table's row-level content without additional derivation. No additional referenced base objects are documented in the ETRM metadata.

Key Columns

The view exposes fourteen columns, each projected directly from the base object:

• ROW_ID — The base table ROWID, useful for row identification and for building correlated updates or deletes.
• POSITION_DESCRIPTION_ID — The primary foreign key linking the classification record to its parent position description. This is the column most commonly used to join the view to position description headers and related child entities.
• PD_CLASSIFICATION_ID — The unique identifier for the classification record itself.
• CLASS_GRADE_BY — Indicates the basis or method by which the class/grade determination is made.
• OFFICIAL_TITLE — The official classification title assigned to the position description.
• PAY_PLAN — The pay plan (for example, GS, WG, SES) associated with the classification.
• OCCUPATIONAL_CODE — The occupational series/code identifying the work category.
• GRADE_LEVEL — The grade level assigned to the classification.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN capture WHO-column audit history.
• OBJECT_VERSION_NUMBER — Supports optimistic locking and change detection for integration consumers.

Common Use Cases and Queries

Typical uses include extracting classification data for a given position description, feeding federal classification reports, reconciling pay plan and grade assignments, and integrating classification changes into downstream HR or payroll systems. Because the searched term is position_description_id, the most common access pattern filters or joins on that column.

Sample query retrieving all classifications for a position description:

• SELECT position_description_id, pd_classification_id, official_title, pay_plan, occupational_code, grade_level
• FROM apps.ghr_pd_classifications_v1
• WHERE position_description_id = :p_position_description_id;

A second pattern supports incremental integration by auditing recent changes:

• SELECT pd_classification_id, position_description_id, last_update_date, object_version_number
• FROM apps.ghr_pd_classifications_v1
• WHERE last_update_date >= :p_since_date
• ORDER BY last_update_date;

Because the view performs no filtering, callers must apply their own predicates for effective date, business group, or security context where applicable. Standard APPS schema access grants and any applicable MO/security policies governing the GHR product apply to queries against this view.