Search Results per_ri_configurations_pk




Overview
Explore in AI Chat

Overview

PER_RI_CONFIGURATIONS is a Human Resources (PER) module table in the HR schema of Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. It stores information about configurations created by users, including the configuration name, description, and status. In the context of Oracle iRecruitment and related recruitment intelligence functionality, this table acts as the master header for a configuration definition, where each row represents a distinct configuration that drives downstream behavior such as the locations, translations, and associated setup rows tied to that configuration.

Under the heuristic Data Vault classification mined from its foreign key structure, PER_RI_CONFIGURATIONS is characterized as hub-leaning. This suggests it functions as a central reference entity — a business concept hub — around which dependent tables such as translations and location mappings are organized as satellites or links. In practical terms, the table serves as the canonical anchor for the CONFIGURATION_CODE business key.

Key Information Stored

The table contains 10 documented columns. The most significant are listed below.

  • CONFIGURATION_CODE — The primary key column and the business identifier for each configuration. It is the value propagated to dependent tables and is the join anchor across the object family.
  • CONFIGURATION_TYPE — Describes the category or nature of the configuration, distinguishing different configuration behaviors defined within setup.
  • CONFIGURATION_STATUS — Holds the status of the configuration, indicating whether it is active, inactive, or otherwise in a defined lifecycle state. This is critical for filtering only the currently effective configuration.
  • OBJECT_VERSION_NUMBER — The standard EBS optimistic locking column, incremented on each update to prevent concurrent modification conflicts.
  • ZD_EDITION_NAME — The editioning column introduced with EBS 12.2 online patching. It is part of the unique index PER_RI_CONFIGURATIONS_PK (CONFIGURATION_CODE, ZD_EDITION_NAME) and scopes rows to a specific edition.
  • Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE record who created and last changed each configuration and when.

Note that CONFIGURATION_CODE alone is the declared primary key in earlier documentation, while the documented physical schema for 12.2.2 defines the unique index as the composite (CONFIGURATION_CODE, ZD_EDITION_NAME). The descriptor text (name and description) is not held on this base table; it is stored on the translation table PER_RI_CONFIGURATIONS_TL.

Common Use Cases and Queries

Typical reporting and validation scenarios revolve around listing active configurations and resolving their translated names.

  • Listing all active configurations: SELECT configuration_code, configuration_type, configuration_status FROM hr.per_ri_configurations WHERE configuration_status = 'ACTIVE';
  • Resolving name and description via the translation table: SELECT c.configuration_code, t.name, t.description FROM hr.per_ri_configurations c, hr.per_ri_configurations_tl t WHERE c.configuration_code = t.configuration_code AND t.language = USERENV('LANG');
  • Auditing change history for a specific configuration using LAST_UPDATED_BY and LAST_UPDATE_DATE.
  • Locating configurations mapped to specific locations via PER_RI_CONFIG_LOCATIONS for site-driven recruitment setup.

Related Objects

The following objects reference or depend on PER_RI_CONFIGURATIONS, joined on CONFIGURATION_CODE.

  • PER_RI_CONFIGURATIONS_TL — Translation table holding the language-specific name and description; joined on CONFIGURATION_CODE.
  • PER_RI_CONFIG_LOCATIONS — Stores location mappings for a configuration; joined on CONFIGURATION_CODE.

These two dependent tables form the documented relationship footprint. Reporting should always join PER_RI_CONFIGURATIONS_TL for human-readable descriptors, since the base table carries only the configuration code, type, and status rather than the display name.