Search Results hr_standard

Overview

HR_ADE_ADI_DATA_SETUP is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema that supports the Application Data Model / ADI (Application Data Installer) setup and metadata maintenance used during Oracle HRMS implementations. Its primary business function is to provision, register, and maintain the metadata descriptors that describe HRMS data objects and their associated interface columns, together with the ad-hoc query definitions used by the ADI data setup tooling. The package operates as an internal setup utility rather than as an end-user business API; it is invoked by the HRMS ADI installation and configuration flows to persist descriptive metadata that downstream loader and integrator processes consume.

The package is classified as OTHER in the ETRM metadata and is not referenced by any other package, confirming it sits at the outer edge of the HRMS dependency graph. The shipped header ($Header: peadeset.pkb 120.3 2008/04/29) indicates a long-stable code line present in both EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

Three procedures are documented for this package. No parameter lists are published in the metadata, and none are asserted here.

• CREATE_METADATA — Creates the metadata rows that describe HRMS ADI objects and their column-level definitions. This is the core registration routine that populates the descriptor tables required before any interface or integrator can consume a given HRMS data object.
• CREATE_STANDALONE_QUERY — Defines and persists a standalone (ad-hoc) query definition within the ADI setup framework. Standalone queries allow implementers to expose custom data extractions without authoring a full integrator.
• MAINTAIN_STANDALONE_QUERY — Performs ongoing maintenance of existing standalone query definitions, including updates and removal, keeping the stored query metadata synchronized with the current configuration.

The package body also contains private helper procedures, notably set_new_session_flag, which detects whether the NEW SESSION cloning functionality is installed by probing BNE_INTEGRATORS_B.NEW_SESSION_FLAG via FND_INSTALLATION.GET_APP_INFO for the owning schema, and, when present, dynamically updates the integrator row to enable session cloning. This helper illustrates the package's role in coordinating HRMS ADI setup with the broader BNE integrator framework.

Tables Accessed

The documented tables accessed through APPS synonyms are:

• BNE_INTERFACE_COLS_B — Stores interface column definitions for integrators; read and written to register the columns associated with HRMS data objects.
• FND_ORACLE_USERID — Resolves Oracle schema and user information used to validate object ownership and set up metadata correctly.
• HR_ADI_OBJECT_CODE_S — The HR ADI object code key-flex or lookup table that maps HRMS objects to their codes; central to CREATE_METADATA.
• ALL_TAB_COLUMNS — Data dictionary view used to test for the existence of specific columns (for example, verifying NEW_SESSION_FLAG on BNE_INTEGRATORS_B) before issuing dynamic SQL.
• DUAL — Used for single-row evaluations and cursor tests.
• USER_SYNONYMS — Consulted to validate synonym existence for the APPS schema objects referenced during setup.

Usage Notes

HR_ADE_ADI_DATA_SETUP is an internal setup and metadata-maintenance package rather than a runtime business API. It is typically invoked during HRMS ADI implementation and configuration, or when new HRMS data objects and standalone queries must be registered or altered. Because it is not referenced by any other package, it is called directly from the relevant HRMS ADI setup forms, concurrent programs, or from custom installation scripts rather than through the standard HRMS API call chain.

Developers working with the package in 12.1.1 and 12.2.2 should note that its dynamic SQL path depends on the runtime presence of the NEW_SESSION_FLAG column; the package degrades gracefully when that feature is absent, defaulting the cloning indicator to 'N'. As with most ADI-era utilities, changes should be executed with the same privileges and schema context under which the original setup flows run to preserve metadata integrity.