Search Results hri_bpl_conc_log




Overview
Explore in AI Chat

Overview

APPS.HRI_BPL_CONC_LOG is a valid PL/SQL package body in the Oracle E-Business Suite APPLSYS/APPS schema. It belongs to the HRI (Human Resources Intelligence) product family — the Oracle HRMS Intelligence / Daily Business Intelligence (DBI) subsystem used for HR analytics and collection processing. In EBS 12.1.1 and 12.2.2, this package serves as the logging and message-management utility for the concurrent/data-collection layer of the HRI BPL (Business Process Library) stack. Its principal business function is to record, format, and persist process log entries, informational messages, and start/end telemetry for HRI collection programs as they execute under the concurrent manager.

The package is classified as OTHER in ETRM and exposes no public user-facing API. It is a supporting infrastructure unit, invoked primarily by sibling HRI collection packages (notably HRI_BPL_CONC_ADMIN and others in the BPL_CONC family) rather than by forms or end users directly.

Key Procedures and Functions

The package body exposes ten documented subprograms, each serving a discrete logging role:

  • GET_LAST_COLLECT_TO_DATE — Returns the last recorded collection "to date," enabling incremental HRI collection runs to resume from the prior checkpoint.
  • DELETE_PROCESS_LOG — Removes obsolete process log rows, supporting log maintenance and housekeeping of historical concurrent-run entries.
  • OUTPUT — Writes formatted log or informational lines to the concurrent manager output file via FND_FILE.
  • DBG — Conditional debug tracing, emitted only when the appropriate FND_PROFILE debug flag is enabled.
  • RECORD_PROCESS_START — Marks the beginning of a process run, capturing start context for later reporting.
  • LOG_PROCESS_INFO — Buffers a general informational message for the current process.
  • FLUSH_PROCESS_INFO — Persists buffered messages to the log tables, producing the durable written record.
  • LOG_PROCESS_END — Records completion of a process run, closing out the log entry.
  • OBSOLETED_MESSAGE — Emits a standard notice when an obsolete or unsupported code path or message is encountered.

Most of these subprograms resolve messages and formatting through FND_MESSAGE, FND_DATE, FND_FILE, and HR_UTILITY — consistent with the documented dependency list.

Tables Accessed

The package references several tables through APPS synonyms:

  • HRI_ADM_MSG_LOG — The primary message log table where process messages, timestamps, and status codes are persisted.
  • HRI_ADM_MSG_LOG_S — The sequence used to generate unique identifiers for entries in the message log.
  • HRI_ADM_MTHD_ACTIONS — Method-action metadata consulted to associate logged messages with method invocations.
  • DUAL — Used for single-row utility selects and date/format conversions.
  • PLITBLM — An Oracle-supplied internal table for PL/SQL compilation and debugging infrastructure.

Supporting calls to BIS_COLLECTION_UTILITIES, HRI_BPL_PARAMETER, and HRI_OPL_MULTI_THREAD indicate the package participates in the broader collection-framework messaging cycle.

Usage Notes

HRI_BPL_CONC_LOG is not referenced by any database object itself, confirming it is entirely an inline-invoked utility package. It is normally called from sibling HRI BPL packages (referenced by 15 other packages according to ETRM) — including HRI_BPL_CONC_ADMIN — during execution of HRI concurrent collection programs. Typical invocation patterns include HRMS Data Collection, DBI/EBS Analytics concurrent programs, and any custom program requiring HRI-standard logging. Developers integrating with the HRI collection stack should call RECORD_PROCESS_START, LOG_PROCESS_INFO, FLUSH_PROCESS_INFO, and LOG_PROCESS_END in sequence to produce complete, consistent log records visible to administrators. It should not be invoked directly by Oracle Forms.