Search Results pji_insert_events_log

Overview

PJI_SETUP_PKG is the administrative setup package for the Oracle EBS Project Intelligence (PJI) application. PJI provides project performance analytics, dashboards, and reporting overlays that draw on data from Oracle Projects, Oracle General Ledger, and related subledgers. The package encapsulates the configuration layer that governs how those analytics are generated: organizational structure selection, period and as-of-date defaults for the various PJI report families, cycle definitions, and summarization rules.

Business users interact with this configuration indirectly through the Project Intelligence setup forms, where an administrator defines system-wide defaults. The package translates those form entries into persisted settings in PJI_SYSTEM_SETTINGS and validates referenced master data, such as organization structures, org structure versions, budget types, and bucket ranges. It also maintains subsidiary setup tables for multi-tenant (MT) operations and provides a logging entry point used for diagnostic and audit tracing.

Key Procedures and Functions

• PJI_SYS_SETTINGS_UPDATE_ROW — The principal update routine that writes the system-wide PJI settings row. It accepts the full set of configuration values, including default period type, as-of date, and cycle for each report family (PRJPIP, PRJBAB, RESUTL, RESAVL, RESPLN, PRJHLT, PRJACT, PRJPRF, PRJCST), period flags, conversion/book-to-bill/DSO/dormant-backlog day counts, budget, forecast, and report options, rolling-week counts, and performance configuration flags.
• PJI_MT_BSR_INSERT_ROW — Inserts a row for the Balance Sheet Reporting (BSR) analytical area within the multi-tenant setup framework.
• PJI_MT_PIP_UPDATE_ROW — Maintains the setup row for the Project Information Portal (PIP) analytical area.
• PJI_MT_DLS_UPDATE_ROW — Maintains the setup row for the Deliverables (DLS) analytical area.
• PJI_MT_RES_AVL_DUR_UPDATE_ROW — Maintains the setup row governing resource availability duration analysis.
• PJI_MT_AVL_UPDATE_ROW — Maintains the general availability setup row for multi-tenant operation.
• PJI_VALIDATE_BUCKET_RANGES — Validates the bucket definitions held in PJI_MT_BUCKETS, ensuring that ranges used for aging and duration analysis are contiguous and internally consistent.
• PJI_INSERT_EVENTS_LOG — Writes an entry to the PJI events log, providing a traceable record of setup activity and errors. This is the routine most frequently referenced by users searching for PJI event logging behavior.
• CHECK_ORG_STRUCTURE — Validates that the organization structure supplied as a setup parameter exists and is eligible for use by PJI.
• CHECK_ORG_STRUCTURE_VERSION — Validates the specified version of an organization structure against the configured structure.
• CHECK_BUDGET_TYPE — Validates budget type values passed into setup processing against the budget type master data.
• DERIVE_SUMMARIZATION_FLAGS — Derives the appropriate summarization flags from the configured settings so that PJI analytics aggregate data at the intended level.

Tables Accessed

• PJI_SYSTEM_SETTINGS — The primary configuration store; read and updated by PJI_SYS_SETTINGS_UPDATE_ROW and referenced by the validation and derivation routines.
• PJI_MT_BUCKETS — Holds bucket definitions for aging and duration analysis; read by PJI_VALIDATE_BUCKET_RANGES.
• PER_ORGANIZATION_STRUCTURES — Source of valid organization structures; queried by CHECK_ORG_STRUCTURE.
• PER_ORG_STRUCTURE_VERSIONS — Source of valid structure versions; queried by CHECK_ORG_STRUCTURE_VERSION.
• PA_BUDGET_TYPES — Budget type master data; queried by CHECK_BUDGET_TYPE.
• DUAL — Used for singleton lookups and expression evaluation within PL/SQL logic.

Usage Notes

PJI_SETUP_PKG is most commonly invoked from the Project Intelligence setup forms when an administrator saves system settings, and from concurrent programs or initialization routines that establish or refresh PJI configuration. Because the package is not a public integration API, custom code should invoke it only where a supported form or concurrent process already does so. Direct calls to PJI_INSERT_EVENTS_LOG are appropriate when a custom process needs to record PJI setup activity in the same diagnostic log. Calls should always supply the organization structure and version values consistently, since validation failures raise errors rather than silently defaulting.