Results for “api_module_name”

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

Overview

PER_RI_CONFIG_DEFAULTS is a configuration table owned by the HR schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the PER (Human Resources) product family and supports the Organization Structures configuration framework. The table stores the default values for parameters that must be supplied to PL/SQL API calls responsible for inserting rows into the datapump batch lines table, HR_PUMP_BATCH_LINES. Because these APIs drive the population of batch line records used during organization structure setup and data loading, PER_RI_CONFIG_DEFAULTS acts as a central repository of pre-seeded defaults that callers can reference rather than hard-coding values at each invocation.

From a Data Vault modeling perspective, the documented foreign key structure suggests a satellite-leaning classification. The table carries descriptive attributes (default values, audit columns) attached to a composite business key rather than acting as an independent hub or an associating link. The mined classification should be treated as a modeling suggestion rather than an enforced design.

Key Information Stored

The table contains eight documented columns. The most significant are:

• API_MODULE_NAME — Identifies the API module that owns the parameter, forming part of the composite primary key and acting as a foreign key to HR_API_MODULES.API_MODULE_NAME.
• PARAMETER_NAME — The name of the parameter for which a default is supplied; together with API_MODULE_NAME it constitutes the composite primary key.
• PARAMETER_DEFAULT_VALUE — The actual default value applied when the corresponding API is invoked without an explicit value for that parameter.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns tracking the most recent modification.
• CREATED_BY, CREATION_DATE — Standard WHO audit columns capturing record creation.

The primary key is composite, defined on (API_MODULE_NAME, PARAMETER_NAME). Because this composite key is the only documented unique identifier, both columns serve jointly as the business-key candidate; there is no separate surrogate key column. The audit columns are descriptive attributes required by EBS multi-user conventions.

Common Use Cases and Queries

The primary use case is resolving default parameter values before invoking the Organization Structures datapump APIs. Application logic, concurrent programs, or custom extensions can query this table to retrieve the default value for a given API and parameter, then pass it into the API call that inserts rows into HR_PUMP_BATCH_LINES. Typical query patterns include:

• Retrieving the default value for a specific module and parameter: SELECT PARAMETER_DEFAULT_VALUE FROM PER_RI_CONFIG_DEFAULTS WHERE API_MODULE_NAME = :module AND PARAMETER_NAME = :param;
• Listing all defaults configured for a given API module: SELECT PARAMETER_NAME, PARAMETER_DEFAULT_VALUE FROM PER_RI_CONFIG_DEFAULTS WHERE API_MODULE_NAME = :module ORDER BY PARAMETER_NAME;
• Auditing configuration changes by filtering on LAST_UPDATE_DATE to identify recently modified defaults.
• Reporting all parameters that lack a configured default, useful when validating that every required datapump API parameter has a value.

Because the table is small and configuration-oriented, reporting is typically limited to setup validation and troubleshooting of datapump loads rather than high-volume transactional reporting.

Related Objects

The most significant relationships are:

• HR_API_MODULES — Referenced through PER_RI_CONFIG_DEFAULTS.API_MODULE_NAME. This is the documented foreign key relationship and the primary parent object for module resolution.
• HR_PUMP_BATCH_LINES — The datapump batch lines table populated by the APIs whose parameters this table parameterizes. It is the downstream consumer of the configuration values.
• PER_RI_CONFIG_DEFAULTS primary key — The composite (API_MODULE_NAME, PARAMETER_NAME) index that enforces uniqueness and supports lookup queries.

Together these objects form the metadata backbone supporting the Organization Structures configuration process, with PER_RI_CONFIG_DEFAULTS supplying reusable defaults to the datapump insertion logic that ultimately writes to HR_PUMP_BATCH_LINES.