Search Results per_ri_config_defaults




Overview
Explore in AI Chat

Overview

The PER_RI_CONFIG_DEFAULTS table is a core configuration table within the Oracle E-Business Suite Human Resources (PER) module. Its primary role is to support the Rapid Implementation (RI) and Organization Structures Configuration processes. Specifically, it stores predefined default values for parameters required when calling the PL/SQL APIs that populate the HR_PUMP_BATCH_LINES table, which is the central staging table for the HR Data Pump. This table is essential for automating and standardizing the bulk data loading of organizational structures, ensuring consistency and reducing manual entry during implementation or migration projects.

Key Information Stored

The table's structure is defined by a composite primary key consisting of API_MODULE_NAME and PARAMETER_NAME. This design associates default values with specific parameters of defined API modules. While the full column list is not detailed in the provided metadata, the key columns and their logical purpose are:

  • API_MODULE_NAME: Identifies the specific PL/SQL API module (e.g., a procedure for loading a particular entity like jobs or positions) that requires parameter defaults.
  • PARAMETER_NAME: Specifies the name of the parameter within the identified API module for which a default value is provided.
  • PARAMETER_VALUE (inferred): Although not explicitly listed, the table's purpose indicates a column storing the actual default value to be passed for the corresponding parameter.

This configuration allows the system to automatically apply standardized values—such as effective dates, batch names, or data pump operation codes—during data load operations.

Common Use Cases and Queries

The primary use case is during the execution of the Organization Structures Configuration or other RI processes. When the HR Data Pump APIs are invoked, they can reference this table to obtain necessary parameter defaults, streamlining the insertion of records into HR_PUMP_BATCH_LINES. Administrators may query this table to audit or modify configuration defaults. A typical query would examine the defaults for a specific API module:

SELECT parameter_name, parameter_value
FROM hr.per_ri_config_defaults
WHERE api_module_name = 'HR_EXM_API.INSERT_ROW'
ORDER BY parameter_name;

Another common pattern is joining with the HR_API_MODULES table to get a more descriptive view of the associated modules:

SELECT ham.module_name, ham.product_code, prcd.parameter_name, prcd.parameter_value
FROM hr.per_ri_config_defaults prcd
JOIN hr.hr_api_modules ham ON ham.api_module_name = prcd.api_module_name
WHERE ham.product_code = 'PER'
ORDER BY ham.module_name, prcd.parameter_name;

Related Objects

PER_RI_CONFIG_DEFAULTS has defined relationships with other key HR objects, as per the provided foreign key metadata:

  • HR_API_MODULES: The table has a foreign key relationship where PER_RI_CONFIG_DEFAULTS.API_MODULE_NAME references HR_API_MODULES.API_MODULE_NAME. This ensures that default values are only configured for valid, registered API modules within the system.
  • HR_PUMP_BATCH_LINES: While no direct foreign key is listed, the table's stated purpose is to supply defaults for APIs that insert rows into this central Data Pump staging table, making it a critical upstream dependency.

The table is intrinsically linked to the HR Data Pump architecture and the suite of PL/SQL APIs used for loading organizational data, serving as a configuration hub for these processes.