Search Results create_configuration




Overview
Explore in AI Chat

Overview

APPS.PER_RI_CONFIGURATION_API is a public Oracle E-Business Suite API package that governs the definition and lifecycle of "RI configurations" — the configuration records used by the Oracle HRMS regulatory/legislative framework to control which information types, validations, and reporting behaviors apply to a business group under a given legislation. The package body header (pecnfapi.pkb) is a shipped, non-customized Oracle component, evidenced by the noship version flag in the source identifier, and it follows the standard HRMS API conventions: a p_validate Boolean that defaults to FALSE, an hr_api.userenv_lang default for language, mandatory p_effective_date handling, and an out-bound p_object_version_number used for optimistic locking. In Oracle EBS 12.1.1 and 12.2.2 this package is the supported programmatic entry point for creating, maintaining, and removing configuration rows, ensuring that the underlying base and translation tables remain consistent and that the developer key is generated through the appropriate HRMS insert layer rather than by direct DML.

Key Procedures and Functions

The documented API exposes three procedures, all of which operate on the configuration entity as a whole:

  • CREATE_CONFIGURATION — Establishes a new configuration record. It accepts the configuration code, type, status, name, and description, together with a language code and effective date, and returns the object version number assigned to the new row. The implementation truncates date inputs to remove time components and issues a savepoint named after the procedure, allowing a caller-invoked validation mode to roll back cleanly.
  • UPDATE_CONFIGURATION — The procedure associated with the search term "update_configuration". It modifies the attributes of an existing configuration, including its status, name, description, and translated text, using the supplied object version number to detect concurrent modification. It is the routine invoked when a configuration must be re-pointed at a different type, retired, or renamed.
  • DELETE_CONFIGURATION — Removes a configuration row (and its associated translation data) subject to the same object version number check, preventing deletion of records that have been altered since the caller last read them.

Tables Accessed

The package reads and writes three documented tables through APPS synonyms:

  • PER_RI_CONFIGURATIONS_TL — the translation (language) table holding the configuration name and description per language. The package variables g_business_group_id and g_legislation_code are declared specifically for validating translation content against the owning business group and legislation.
  • HR_LOCATIONS_ALL — the base HRMS locations table, whose OBJECT_VERSION_NUMBER column supplies the %TYPE anchor for the version-number variable used in the API signature, and which participates in the row-level locking convention shared by HRMS APIs.
  • HR_LOCATIONS_ALL_TL — the corresponding translation table, referenced in the same framework context. These HR_LOCATIONS tables are the canonical HRMS reference for the object version and multilingual patterns that PER_RI_CONFIGURATION_API reuses.

Usage Notes

PER_RI_CONFIGURATION_API is normally invoked indirectly rather than by ad hoc SQL. HRMS configuration and legislation setup forms, and the concurrent programs that seed configuration data during installation or legislative patching, call these procedures so that validation, translation, and developer-key generation all occur through supported code paths. Four other packages reference this API, making it a dependency within the HRMS configuration layer; direct DML against PER_RI_CONFIGURATIONS_TL is therefore unsupported. Custom extensions should call CREATE_CONFIGURATION, UPDATE_CONFIGURATION, or DELETE_CONFIGURATION with p_validate => TRUE first, inspect the returned object version number, and only then commit. Callers must always supply an effective date and retain the latest object version number between the read and the update or delete, since the API relies on it for optimistic locking across 12.1.1 and 12.2.2.