Search Results pqh_corps_fileres_v




Overview
Explore in AI Chat

Overview

PQH_CORPS_FILERES_V is a database view owned by the APPS schema in Oracle E-Business Suite, registered under the PQH — Public Sector HR product family. Its documented description is simply "Corp filere view." In practice, the view exposes a filtered, decoded projection of Corps (Corps of Engineers / public sector position classification) extra-information records where the information type equals "FILERE." The name FILERE is an internal abbreviation for "file reference," referring to a classification file reference — that is, the specific file, standard, or reference document associated with a Corps definition entry.

Unlike transactional tables, this view carries no data of its own. It is a read-only presentation layer that sanitizes and reshapes data stored in PQH_CORPS_EXTRA_INFO so that downstream reporting, forms, or integration logic can consume the classification file reference without re-implementing the decode rules. In the Oracle EBS reporting model, such views are frequently used as the source for concurrent program reports, Oracle Discoverer/BI Publisher data models, and custom PL/SQL lookups. The FILERE_NAME column is surfaced as a human-readable label, distinguishing this view from the raw base data where only a coded value is held.

Underlying Base Objects

The ETRM metadata documents three referenced base objects:

  • PQH_CORPS_EXTRA_INFO (SYNONYM) — the only table referenced in the view's FROM clause, which is the actual store for Corps extra information records.
  • HR_GENERAL (PACKAGE) — referenced indirectly through the call HR_GENERAL.DECODE_SHARED_TYPE, which converts a shared-type code into a display value.
  • FND_NUMBER (PACKAGE) — referenced through FND_NUMBER.CANONICAL_TO_NUMBER, which converts the canonical number representation stored in INFORMATION4 into a numeric value.

The single-table FROM clause, restricted by INFORMATION_TYPE = 'FILERE', means the view behaves as a narrow slice over a generic key-value style extra-information table. The two package calls are invoked at runtime and are therefore dependencies that must be valid for the view to return correctly decoded output. The synonym for PQH_CORPS_EXTRA_INFO resolves to its underlying table in the same schema.

Key Columns

  • CORPS_DEFINITION_ID — identifier of the parent Corps definition record to which the extra information belongs; the primary join key back to the Corps definition entity.
  • CORPS_EXTRA_INFO_ID — unique identifier of the extra-information row itself, useful for point lookups and auditing.
  • OBJECT_VERSION_NUMBER — optimistic locking / concurrency version stamp carried through from the base row.
  • INFORMATION_TYPE — always 'FILERE' because the view is filtered on this value; retained for report clarity and consistency with the base structure.
  • FILERE_NAME — the decoded, human-readable name of the file reference, produced by HR_GENERAL.DECODE_SHARED_TYPE applied to the canonical number of INFORMATION4.
  • FILERE_CD — the raw INFORMATION4 value, i.e., the canonical or coded file-reference value before decoding.

Common Use Cases and Queries

The most common scenario is retrieving the classification file reference associated with a Corps definition for display on a report or form, avoiding the need to re-code the shared-type decode logic. A basic lookup by definition is shown below.

SELECT corps_definition_id, corps_extra_info_id, filere_name, filere_cd FROM apps.pqh_corps_fileres_v WHERE corps_definition_id = :p_definition_id;

To list all file references with their descriptive names, ordered for readability:

SELECT filere_cd, filere_name FROM apps.pqh_corps_fileres_v ORDER BY filere_name;

A validation query that tests whether the decode produced a value — that is, whether the shared-type lookup resolved successfully — is useful when diagnosing missing configuration:

SELECT corps_extra_info_id, filere_cd, filere_name FROM apps.pqh_corps_fileres_v WHERE filere_name IS NULL AND filere_cd IS NOT NULL;

Because the view is read-only and filtered, INSERT/UPDATE/DELETE statements are not supported; changes must be applied to PQH_CORPS_EXTRA_INFO directly. Reports and integrations should treat FILERE_NAME as the presentation value and FILERE_CD as the stable key when persisting references across systems.

Oracle Proprietary, Confidential Information — Legal Notices apply.