Search Results pji_utils




Overview
Explore in AI Chat

Overview

APPS.PJI_UTILS is a utility package body within the Oracle EBS Projects Intelligence (PJI) product family. It provides a shared library of low-level helper routines that other PJI packages, concurrent programs, and reporting components invoke for common infrastructure tasks: retrieving and persisting system parameters, resolving schema and tablespace names, managing currency conversion functions, writing to log and output files, and formatting monetary values. Its classification in the ETRM metadata is OTHER, indicating that it is not a public business API in the sense of an interface table handler, but rather an internal support package. The package reports a status of VALID and resides in the APPS schema, which means it is compiled against APPS synonyms and is callable from any PL/SQL unit running with the standard EBS APPS credentials.

The package is heavily depended upon: ETRM documentation records that it is referenced by 44 other packages. This makes PJI_UTILS one of the foundational components of the PJI subsystem rather than an end-user-facing artifact.

Key Procedures and Functions

The documented interface contains 39 procedures and functions. Grouped by purpose, they are as follows.

Tables Accessed

PJI_UTILS reads and writes through APPS synonyms. Configuration and system state are held in PJI_SYSTEM_PARAMETERS, PJI_SYSTEM_SETTINGS, PJI_SYSTEM_CONFIG_HIST, and PJI_ORG_EXTR_INFO. Debug and event traces are written to PJI_SYSTEM_DEBUG_MSG, PJI_SYSTEM_DEBUG_MSG_S, and PA_PJI_PROJ_EVENTS_LOG. Currency operations draw on FND_CURRENCIES, GL_DAILY_CONVERSION_TYPES, and the GL_CURRENCY_API referenced in the package dependencies. Project and organization context comes from PA_IMPLEMENTATIONS_ALL, PA_OBJECT_RELATIONSHIPS, PA_PROJ_ELEMENT_VERSIONS, PA_RBS_PRJ_ASSIGNMENTS, HR_ALL_ORGANIZATION_UNITS_VL, and GL_PERIOD_STATUSES. Installation and profile information is obtained from FND_ORACLE_USERID, FND_PROFILE_OPTIONS, FND_PROFILE_OPTION_VALUES, and the FND_PROFILE dependency. Lookup values are resolved through PJI_LOOKUPS, and calendar context through PJI_TIME_CAL_PERIOD_V and PJI_TIME_ENT_PERIOD_V. Dynamic object metadata is inspected via ALL_TABLES and ALL_INDEXES.

Usage Notes

Because PJI_UTILS is not referenced by any database object and is itself referenced by 44 packages, it is typically invoked from within other PL/SQL units rather than directly from Oracle Forms or concurrent program definitions. Standard usage patterns include calling GET_PARAMETER at the start of a processing routine, invoking WRITE2LOG between processing steps for traceability, and using the currency helpers before performing any amount conversion. Developers extending PJI functionality should call these utilities rather than reimplementing equivalents, since the package centralizes the profile and setup lookups that govern correct behavior across multi-organization and multi-currency implementations. The dependency on UTL_FILE and FND_FILE indicates that WRITE2OUT and WRITE2LOG require the concurrent program context or an appropriately configured database directory; invoking them outside that context may result in runtime errors. No parameter lists are documented in the ETRM metadata, so callers should inspect the package specification in the target environment before reuse.