Search Results check_job

Overview

APPS.HRI_BPL_SETUP_DIAGNOSTIC is a diagnostic utility package in Oracle E-Business Suite (12.1.1 / 12.2.2) that validates the configuration and setup integrity of Oracle Advanced Benefits (OAB) and related Human Resources components. Its name derives from "HRI" (Human Resources Intelligence), "BPL" (Benefit Plan Logic layer), and "SETUP_DIAGNOSTIC," accurately reflecting its purpose: to inspect the state of profile options, Fast Formula definitions, database triggers, DBI (DataBase Item) tables, job and geography flexfield configurations, and benefit buckets, then report whether each element is correctly configured and, where problems exist, present an impact message and a documentation link.

The package does not process business transactions. Instead, it supports administrators and implementers during implementation, patching, and troubleshooting by surfacing misconfigurations that would otherwise cause benefit calculations or eligibility processing to fail silently. It is classified as an "OTHER" API, meaning it is a support/administrative utility rather than a public integration interface.

Key Procedures and Functions

• CHECK_PROFILE_OPTION — Inspects a named profile option within a functional area, returning the resolved user profile name and value together with an impact flag, message, and documentation URL.
• CHECK_FAST_FORMULA — Evaluates a Fast Formula by name and type within a functional area, returning a table of formula records containing business group, status, and impact messaging.
• CHECK_TRIGGERS — Verifies whether a specified database trigger has been generated, is enabled, and is in a valid state, along with impact details.
• CHECK_DBI_TABLES — Confirms the existence and status of DBI tables required by OAB, reporting impact and remediation links.
• CHECK_JOB — Diagnoses the Job flexfield structure, indicating whether job families and job functions are defined through its output modes.
• CHECK_GEOGRAPHY — Validates geography-related setup used by benefits eligibility and eligibility determination.
• CHECK_BUCKETS — Verifies the configuration of benefits buckets employed in balance and accumulation processing.
• PPLT_OBJ_FAREA_TAB — A referenced table/collection construct mapping diagnostic objects to their functional areas.
• GET_PRODUCT_NAME — Returns the product name associated with a diagnostic target, used to label results.
• IS_TOKEN_EXIST — The function the user searched for; it reports whether a given diagnostic token (identifier) exists in the diagnostic configuration, enabling callers to conditionally execute or display checks.

Tables Accessed

• FF_FORMULAS_F — Provides Fast Formula definitions validated by CHECK_FAST_FORMULA.
• FND_LOOKUP_VALUES — Supplies lookup configuration used to interpret profile and setup values.
• PAY_TRIGGER_EVENTS — Confirms registered payroll/benefits trigger events.
• PER_PERIODS_OF_SERVICE — Supports period-of-service validation for eligibility checks.
• HR_ORGANIZATION_INFORMATION — Retrieves organization-level setup attributes.
• BIS_DIMENSIONS — Confirms DBI dimension definitions backing DBI tables.
• HRI_ADM_DGNSTC_SETUP and HRI_ADM_DGNSTC_SBSCRB — Store diagnostic setup configuration and subscriptions that drive which checks execute.
• PLITBLM — PL/SQL table utility used to manage in-memory collections of results.
• USER_OBJECTS — Verifies existence and validity of database objects referenced by the diagnostics.

Usage Notes

HRI_BPL_SETUP_DIAGNOSTIC is typically invoked from the Oracle Advanced Benefits setup diagnostic concurrent program, from the OAB administrative responsibility, or from custom validation scripts run during implementation and post-patch verification. It is also referenced by three other packages within the applications schema, which call its procedures to aggregate diagnostic results. Because its procedures return status and impact information rather than raising exceptions, callers should inspect the OUT parameters and the returned tables, including the documentation URL, to determine whether corrective action is required. The IS_TOKEN_EXIST function is commonly used to guard execution of individual checks when a diagnostic token is not configured for the current environment.