Search Results bis_bucket_vl




Overview

HRI_BPL_SETUP_DIAGNOSTIC is an Oracle EBS diagnostics package body owned by the APPS schema. Its purpose is to validate the configuration and setup of the Oracle Human Resources Intelligence (HRBI/HR Analytics) and Daily Business Intelligence (DBI) reporting stack. The package examines the foundational metadata that DBI/HRI relies upon — bucket definitions, dimensional hierarchies, flexfield mappings, Fast Formula definitions, trigger registrations, and administrative subscription settings — and reports whether each element is correctly configured for reporting to function. It surfaces its findings through FND_MESSAGE and the diagnostic framework tables, notably HRI_ADM_DGNSTC_SETUP and HRI_ADM_DGNSTC_SBSCRB.

Key Procedures and Functions

The package exposes ten documented procedures and functions, each targeting a distinct area of setup verification:

  • CHECK_PROFILE_OPTION — Validates that required profile options (read via FND_PROFILE and FND_PROFILE_OPTIONS_VL) are set to expected values for the reporting configuration.
  • CHECK_FAST_FORMULA — Confirms that the Fast Formulas referenced by the reporting layer exist and are valid, drawing on FF_FORMULAS_F.
  • CHECK_TRIGGERS — Verifies that the database triggers required to capture HR transactional events are present, using PAY_TRIGGER_EVENTS and USER_OBJECTS.
  • CHECK_DBI_TABLES — Checks the existence and state of the DBI summary and staging tables that drive reporting.
  • CHECK_JOB — Validates job-related setup against HRI_OPL_JOBH and associated organization data.
  • CHECK_GEOGRAPHY — Assesses geography and organization hierarchy setup, referencing HR_ORGANIZATION_INFORMATION.
  • CHECK_BUCKETS — Examines bucket definitions in BIS_BUCKET_VL to confirm that reporting buckets are defined and enabled. This is the routine most directly associated with the user search term "bis_bucket_vl".
  • PPLT_OBJ_FAREA_TAB — Supports internal diagnostic processing, likely populating a PL/SQL table (PLITBLM) of object/functional-area results.
  • GET_PRODUCT_NAME — Resolves the product or application name associated with a diagnostic check for output formatting.
  • IS_TOKEN_EXIST — Performs a token-existence test used by the diagnostic framework to determine whether a given configuration token or parameter is present.

Tables Accessed

The package reads a broad set of setup and metadata tables through APPS synonyms. BIS_BUCKET_VL supplies bucket definitions and translations; BIS_DIMENSIONS and BIS_FLEX_MAPPINGS_V provide dimensional and key flexfield mapping metadata used by CHECK_DBI_TABLES and the bucket/dimension checks. FF_FORMULAS_F backs the Fast Formula validation. FND_LOOKUP_VALUES, FND_ID_FLEX_SEGMENTS_VL, FND_ID_FLEX_STRUCTURES_VL, FND_DESCR_FLEX_CONTEXTS_VL, and FND_DESCR_FLEX_COL_USAGE_VL are consulted to confirm that descriptive and key flexfield structures and segments are configured correctly. HR_ORGANIZATION_INFORMATION supports geography checks, PER_PERIODS_OF_SERVICE and PAY_TRIGGER_EVENTS support trigger and event validation, and HRI_ADM_DGNSTC_SETUP and HRI_ADM_DGNSTC_SBSCRB store or retrieve diagnostic setup and subscription records. PLITBLM and USER_OBJECTS serve internal processing and object-existence checks respectively.

Usage Notes

HRI_BPL_SETUP_DIAGNOSTIC is not an end-user API; it is invoked by the Oracle HRMS/DBI diagnostics framework, typically triggered from the "Diagnostics" or "Setup Diagnostics" administrative function within the EBS application or via the related concurrent process. It is referenced by three other packages, including HRI_BPL_DATA_SETUP_DGNSTC, which likely delegate specific setup checks to this routine. It does not reference or modify transactional HR data directly and produces no database object that is referenced elsewhere. Administrators generally run it when diagnosing missing DBI/HRI report content, bucket display problems (the bis_bucket_vl scenario), or incorrectly registered triggers. No public API parameters are documented here; callers should treat the procedures as internal diagnostic entry points rather than supported integration interfaces.