Results for “per_ri_config_products”

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

Overview

APPS.PER_RI_CONFIG_RESPON_PKG is a PL/SQL package belonging to the Oracle Human Resources (PER) product family in Oracle E-Business Suite. The package name combines the "PER" application prefix with "RI_CONFIG_RESPON," indicating that its purpose is to manage the configuration association between responsibilities and the Oracle HRMS regulatory/reporting infrastructure that consumes territory-specific configuration data. In EBS releases 12.1.1 and 12.2.2, the Human Resources module uses a set of "RI" (Reporting Infrastructure) package families to control how legislative and country-specific data is presented and processed depending on the user's responsibility, business group, and territory.

The package is declared with AUTHID CURRENT_USER, meaning its procedures execute with the privileges of the invoking schema rather than the defining schema. This is significant in EBS because it allows the package to participate in invoker-rights security models and to be callable within the security context of an application user, which is essential for responsibility-scoped configuration, since the responsibility being configured is itself a security construct. The header carries a 2005-era revision marker ($Header: perriconresp.pkh 120.0), indicating the package is an established, stable component of the HR shared infrastructure rather than a frequently revised object.

Key Procedures and Functions

The package exposes a single documented procedure: LOAD_CONFIGURATION. Based on the documented metadata, this procedure is responsible for establishing or refreshing the configuration row that links a given responsibility to its applicable territory/regulatory configuration. It is the sole entry point into the package's functionality, and per the referenced metadata it operates against the PER_RI_CONFIG_RESPONSIBILITY table, which acts as the persistence layer for the mapping it establishes.

No parameter list is reproduced here because the ETRM metadata documents only the procedure name and purpose. The procedure and the package body are not documented as being referenced by any other package (Referenced by: 0 other packages), which indicates that LOAD_CONFIGURATION is invoked directly by configuration tooling or administrative entry points rather than through a chain of internal API calls.

Tables Accessed

The single documented table accessed by this package is PER_RI_CONFIG_RESPONSIBILITY, reached through an APPS synonym. This table stores the responsibility-level configuration records consumed by the HRMS reporting infrastructure. LOAD_CONFIGURATION reads from and/or writes to this table in order to create, update, or reconcile the association between a responsibility and its configuration context. In practice, the table serves as the lookup that the HRMS runtime uses to determine which territory or reporting configuration applies when a user enters a given responsibility. Because this table embodies responsibility-scoped configuration, writes to it affect the behavior of every session that subsequently signs in under the configured responsibility.

Usage Notes

LOAD_CONFIGURATION is best understood as a setup-time or administration-time procedure rather than a runtime transactional API. It is typically invoked when implementing or reconfiguring Oracle HRMS regulatory/reporting features, such as when onboarding a new legal entity, adding a responsibility for a new territory, or correcting a mismapped responsibility during an upgrade or post-clone refresh. Because it writes configuration used across the HRMS reporting stack, it should be executed only by administrators with a clear understanding of the target responsibility, and preferably outside peak usage windows.

As an invoker-rights (AUTHID CURRENT_USER) package with no dependent packages, it is commonly called from custom setup scripts, ad hoc SQL*Plus sessions, or migration scripts rather than from an Oracle Forms UI or a standard concurrent program. Given that ETRM lists no referencing packages, implementers should treat it as a direct-call utility and confirm behavior in a test environment before executing it against production data.