Search Results pji_system_settings_pk

Overview

PJI_SYSTEM_SETTINGS is a configuration table in the PJI (Project Intelligence) product family of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It stores the installation-level parameters that govern how Oracle Projects Intelligence reports, dashboards, and analytical engines interpret Projects data. Rather than holding transactional project records, the table centralizes defaults such as period types, as-of dates, currency treatment, budget and forecast conversion rules, and feature enablement flags. Typically a single row, or a very small number of rows, defines the active configuration for the installation, making the table a mandatory reference point for nearly every Project Intelligence query that resolves reporting periods or currency conversions.

From a dimensional modeling perspective, the metadata's heuristic Data Vault classification is standalone. In Data Vault terms this suggests the table behaves as an independent hub-like structure rather than a link or satellite dependent on a parent business key. Its grain is defined by the surrogate SETTING_ID, and it does not act as an associative entity between other hubs.

Key Information Stored

The documented physical schema contains 75 columns. The most operationally significant include:

• SETTING_ID — the surrogate primary key, enforced by the constraint PJI_SYSTEM_SETTINGS_PK.
• ORGANIZATION_STRUCTURE_ID and ORG_STRUCTURE_VERSION_ID — foreign keys that anchor the configuration to a specific organization hierarchy and hierarchy version in Oracle HRMS.
• DFLT_*_PERIOD_TYPE, DFLT_*_AS_OF_DATE, DFLT_*_CYCLE_ID — repeating families of default period, as-of date, and cycle settings for report templates including PRJPIP, PRJBAB, RESUTL, RESAVL, RESPLN, PRJHLT, PRJACT, PRJPRF, and PRJCST.
• PA_PERIOD_FLAG and GL_PERIOD_FLAG — control whether Oracle Projects (PA) periods or General Ledger periods drive the reporting calendar.
• CONVERSION_RATIO_DAYS, BOOK_TO_BILL_DAYS, DSO_DAYS, DORMANT_BACKLOG_DAYS — global thresholds used in Project Intelligence metrics.
• REPORT_COST_TYPE, COST_BUDGET_TYPE_CODE, REVENUE_BUDGET_TYPE_CODE, COST_FORECAST_TYPE_CODE, REVENUE_FORECAST_TYPE_CODE — define which budget, forecast, and cost classifications feed reporting.
• ROLLING_WEEKS and the CONFIG_*_FLAG columns — control rolling-window horizons and enablement of Project Performance, Cost, Profit, and Utilization dashboards.

The unique index PJI_SYSTEM_SETTINGS_U1 spans SETTING_ID and ZD_EDITION_NAME. The inclusion of ZD_EDITION_NAME indicates support for Oracle's edition-based redefinition (EBR) model, meaning the same SETTING_ID can exist once per edition, and any business-key lookup must account for the active edition rather than relying on SETTING_ID alone.

Common Use Cases and Queries

The primary use case is configuration discovery: determining which period type, currency flag, or budget type code an installation is using before running any Project Intelligence report. A typical pattern retrieves the single active configuration row:

• Configuration lookup: SELECT setting_id, pa_period_flag, gl_period_flag, report_cost_type FROM pji.pji_system_settings WHERE zd_edition_name = 'SET1';
• Currency analysis: querying PRJ_CURR_FLAG, PROJFUNC_CURR_FLAG, TXN_CURR_FLAG, GLOBAL_CURR1_FLAG, and GLOBAL_CURR2_FLAG to determine how project, functional, transactional, and global currencies are handled.
• Period defaults: joining the DFLT_*_PERIOD_TYPE and DFLT_*_CYCLE_ID columns to PA period and cycle definitions to validate reporting calendars.
• Dashboard enablement: reading CONFIG_PROJ_PERF_FLAG, CONFIG_COST_FLAG, CONFIG_PROFIT_FLAG, and CONFIG_UTIL_FLAG to drive conditional display logic.

Related Objects

The documented foreign keys tie this configuration to Oracle HRMS organization structures:

• PER_ORGANIZATION_STRUCTURES — joined on PJI_SYSTEM_SETTINGS.ORGANIZATION_STRUCTURE_ID.
• PER_ORG_STRUCTURE_VERSIONS — joined on PJI_SYSTEM_SETTINGS.ORG_STRUCTURE_VERSION_ID.

Beyond these, Project Intelligence reporting extracts and the PA (Oracle Projects) budget, forecast, cost, and revenue tables depend on the conversion rules and type codes defined here. Oracle Projects period definitions in PA_PERIODS and GL period tables in GL_PERIODS are referenced conceptually by the PA_PERIOD_FLAG and GL_PERIOD_FLAG settings, while PA budgeting and forecasting tables consume the COST/REVENUE_BUDGET_TYPE_CODE and FORECAST_TYPE_CODE values. The ZD_EDITION_NAME column also links the table to Oracle's editioning infrastructure, which must be respected in any join or lookup against this configuration.