Search Results per_ri_mng_cfg_pkg




Overview
Explore in AI Chat

Overview

The APPS.PER_RI_MNG_CFG_PKG package body is a configuration-management utility within the Oracle E-Business Suite "RI" (Regulatory/Information) framework, most closely associated with the Oracle HRMS person/assignment "RI" configuration infrastructure introduced in Release 12. It provides the application programming interface layer through which Oracle EBS forms, concurrent programs, and internal APIs manage the lifecycle of RI configuration definitions—the metadata records that describe how RI configurations and their associated locations are defined, stored, and propagated across the enterprise. The package is classified as an "OTHER" API, meaning it is intended primarily for internal use by Oracle application code rather than as a formally published, customer-facing public API. Its status is VALID in the APPS schema, confirming that the compiled body is present and syntactically consistent with its specification. Because it depends on the RI configuration API and information API packages, it acts as a thin orchestration layer that delegates persistence work to the underlying entity APIs while exposing simplified operations for deletion and duplication of configuration records.

Key Procedures and Functions

The ETRM metadata documents two procedures on this package body:

  • DELETE_CONFIGURATION — Removes an RI configuration definition and its related configuration data from the repository. It is the packaged entry point used when a configuration is no longer required and must be purged, including the associated configuration information records.
  • DUPLICATE_CONFIGURATION — Creates a copy of an existing RI configuration so that it can be reused, modified, or seeded as the basis for a new configuration. This supports rapid setup of similar configurations without manual re-entry of every attribute.

Neither procedure is documented with an explicit parameter list in the ETRM metadata, and no parameter signatures are asserted here. In typical usage, the identification of the configuration to act upon is passed from the calling form or program through the package's interface, with the actual row-level manipulation performed by the referenced configuration APIs.

Tables Accessed

The package references the following documented base tables (through APPS synonyms):

  • PER_RI_CONFIG_INFORMATION — Stores the configuration information records that define an RI configuration's content and attributes. The package reads these rows during duplication and removes them during deletion.
  • PER_RI_CONFIG_LOCATIONS — Stores the locations associated with an RI configuration. It is accessed when configuration location data must be copied or removed alongside the parent configuration.

Dependency metadata also shows indirect access to PER_RI_CONFIGURATIONS_VL, PER_RI_CONFIGURATION_API, PER_RI_CONFIG_INFORMATION_API, and PER_RI_CONFIG_LOCATION_API, indicating that the package relies on the validation view and the entity APIs for the actual insert, update, and delete operations, rather than performing direct DML in every case. The body additionally depends on the SYS.STANDARD package supplied by the database.

Usage Notes

PER_RI_MNG_CFG_PKG is not referenced by any other database object and is not a published customer API, so it is normally invoked indirectly. It is most commonly called from Oracle EBS Forms or concurrent programs within the Oracle HRMS/RI configuration setup flows, where an administrator chooses to delete or duplicate an RI configuration from a configuration maintenance window. The form or program passes the selected configuration identifier to DELETE_CONFIGURATION or DUPLICATE_CONFIGURATION, and the package coordinates the corresponding API calls against the underlying configuration, information, and location entities. Customizations should avoid calling this package directly where a supported public API exists, since its interface is subject to change across patch levels; any direct invocation should be confined to controlled extensions and tested against both 12.1.1 and 12.2.2, where the RI configuration data model is unchanged.