Search Results get_pji_index_tspace

Overview

PJI_UTILS is a utility package in the Oracle E-Business Suite Projects (PJI) module, owned by the APPS schema and classified as an OTHER API. It provides the shared low-level infrastructure used throughout the Project Intelligence (PJI) schema collection: retrieval and persistence of system parameters and setup settings, resolution of schema and tablespace names, currency and rate lookups, amount spreading, output routing, and diagnostic logging. The package is not an end-user-facing interface; it is a foundational library invoked internally by other PJI packages. The documented metadata records that PJI_UTILS is referenced by 44 other packages, confirming its role as a common dependency across the PJI subsystem.

Key Procedures and Functions

The 39 documented routines fall into several functional groups.

• Parameter management: GET_PARAMETER and SET_PARAMETER read and write PJI parameter values held in PJI_SYSTEM_PARAMETERS; SET_PARAMETER does not commit. GET_SETUP_PARAMETER returns setup parameter values from PJI_SYSTEM_SETTINGS, accepting a parameter name that corresponds to a table column name, with date columns converted to 'YYYY/MM/DD'.
• Schema name resolution: GET_APPS_SCHEMA_NAME, GET_PA_SCHEMA_NAME, and GET_PJI_SCHEMA_NAME return the Oracle schema names of the APPS, PA, and PJI users.
• Environment and session handling: GET_PJI_DATA_TSPACE and GET_PJI_INDEX_TSPACE return the data and index tablespaces for PJI; SET_OUTPUT_DEST, SET_CURR_FUNCTION, RESET_CURR_FUNCTION, and RESET_SSWA_SESSION_CACHE manage output routing, current function context, and the SSWA session cache.
• Currency and rate accessors: GET_GLOBAL_RATE_PRIMARY, GET_MAU_PRIMARY, and GET_GLOBAL_PRIMARY_CURRENCY expose primary currency and rate configuration; SPREAD_AMOUNT performs monetary spreading.
• Date and logging utilities: GET_EXTRACTION_START_DATE returns the extraction start date, while WRITE2LOG, WRITE2OUT, and WRITE2SSWALOG write diagnostic output to the log, the output destination, and the SSWA log respectively.

Tables Accessed

PJI_UTILS reads and writes a defined set of APPS-synonym tables. Parameter and setup storage relies on PJI_SYSTEM_CONFIG_HIST and PJI_SYSTEM_DEBUG_MSG tables (PJI_SYSTEM_DEBUG_MSG and its sibling), which support configuration history and debug messaging. Currency and conversion logic draws on FND_CURRENCIES, GL_DAILY_CONVERSION_TYPES, and GL_PERIOD_STATUSES. Schema and implementation context is resolved through FND_ORACLE_USERID, FND_PROFILE_OPTIONS, FND_PROFILE_OPTION_VALUES, PA_IMPLEMENTATIONS_ALL, and PA_OBJECT_RELATIONSHIPS. Project event and element data are consulted via PA_PJI_PROJ_EVENTS_LOG, PA_PROJ_ELEMENT_VERSIONS, and PA_RBS_PRJ_ASSIGNMENTS. Additional organization-level information is sourced from PJI_ORG_EXTR_INFO.

Usage Notes

PJI_UTILS is invoked programmatically rather than through a dedicated form or concurrent program. Other PJI packages call its functions—for example, GET_SETUP_PARAMETER—to obtain configuration and environment values before performing their own processing. Because SET_PARAMETER intentionally omits a commit, callers must manage transaction boundaries themselves. Diagnostic routines such as WRITE2LOG and WRITE2SSWALOG are used throughout PJI execution paths for tracing and troubleshooting. Custom code extending PJI functionality should treat this package as an internal utility layer and observe the same conventions regarding parameter naming, commit handling, and output routing.