Search Results per_ri_config_information_api




Overview

APPS.PER_RI_CONFIG_INFORMATION_API is a public Oracle HRMS (HCM) Application Programming Interface shipped under the per product and owned by the APPS schema. Per its ETRM header, the package "contains APIs that maintain enterprise structure configuration information," and it is exposed with the display name Enterprise Structure Configuration. Its declared purpose is to create and maintain the configuration information that drives setup of the HRMS application, specifically the Workstructures components such as Organizations, Jobs, and Positions. The package is declared AUTHID CURRENT_USER and its header carries an RCS identifier of pecniapi.pkh 120.5, dated 2006, indicating a long-stable interface carried forward into the 12.1.1 and 12.2.2 releases.

Because configuration information governs which flexfield structures and sequencing are used by Workstructures descriptive flexfields, this API is the programmatic entry point for establishing the foundation rows that HCM enterprise structure setup depends upon. It is licensed for use with Oracle Human Resources.

Key Procedures and Functions

ETRM documents three public procedures within the package. All three follow the standard Oracle HRMS API conventions, including validation-only execution and error reporting through the standard HRMS error handling mechanism.

  • CREATE_CONFIG_INFORMATION — Creates a Configuration Information record. Documented parameters include p_validate (when true, validation alone is performed and the database remains unchanged; when false and all validation checks pass, the database is modified), p_configuration_code (unique short name of the configuration), p_config_information_category (the context value that determines which descriptive flexfield structure is used with the descriptive flexfield segments), p_config_sequence (a sequence number used to order the displayed data in the UI), and the descriptive flexfield segments p_config_information1 and p_config_information2. Documented prerequisites are NONE. On success, configuration data to set up HCM Workstructures setup data is created; on failure, the configuration setup data is not created and an error is raised.
  • UPDATE_CONFIG_INFORMATION — Modifies existing enterprise structure configuration information, allowing the configuration code, context category, display sequence, and descriptive flexfield segment values to be maintained after initial creation.
  • DELETE_CONFIG_INFORMATION — Removes a configuration information record that is no longer required for the HRMS Workstructures setup.

Tables Accessed

The documented data access for this package resolves through APPS synonyms to the following objects:

  • HR_LOCATIONS_ALL and HR_LOCATIONS_ALL_TL — the base and translated location tables, which form part of the Workstructures enterprise structure data that configuration information governs.
  • PER_RI_WORKBENCH_ITEMS_TL — the translated workbench item definitions used by the HRMS configuration workbench, which is the primary consumer of configuration information records.
  • Descriptive flexfield segment storage associated with the p_config_information_category context, which the API populates based on the caller-supplied context value.

Usage Notes

This package is typically invoked from the HRMS Configuration Workbench and related enterprise structure setup forms rather than being called directly in day-to-day processing. Custom code should call the procedures only within a controlled setup context, always passing p_validate = TRUE first to confirm that validation passes without modifying the database, then re-invoking with p_validate = FALSE to commit the change. Callers must supply a unique configuration code and a valid descriptive flexfield context value; the API performs all descriptive flexfield validation on the caller's behalf. ETRM records that the package is referenced by three other packages, confirming its role as a dependency for higher-level HCM setup code. Because the interface is licensed for Oracle Human Resources, use should be restricted to HCM enterprise structure configuration scenarios such as Organizations, Jobs, and Positions.