Search Results pji_system_settings_u1

Overview

PJI.PJI_SYSTEM_SETTINGS is a configuration table within the Oracle Projects Intelligence (PJI) schema. It stores the parameters and defaults that define the configuration of an Oracle Projects Intelligence installation under Oracle E-Business Suite 12.1.1 and 12.2.2. The table resides in the APPS_TS_SEED tablespace, consistent with its role as a seed/reference data object rather than a high-volume transactional table. Its status is documented as VALID, and its FND Design Data reference is PJI.PJI_SYSTEM_SETTINGS.

The table is classified heuristically as standalone under a Data Vault modeling suggestion. This means it does not naturally decompose into a classic hub, link, or satellite pattern; rather, it behaves as a single-row, wide configuration record keyed by a surrogate identifier. Practically, it functions as the central control record from which the Projects Intelligence reporting engine reads default period types, as-of dates, and cycle identifiers for each configured reporting profile.

Key Information Stored

The primary key of the table is PJI_SYSTEM_SETTINGS_PK, defined on the SETTING_ID column (NUMBER(15)), which serves as the surrogate identifier for the setting. A unique index, PJI_SYSTEM_SETTINGS_U1, is defined on the composite of SETTING_ID and ZD_EDITION_NAME; this index represents the business-key candidate for the record, with ZD_EDITION_NAME supporting edition-based versioning. The table contains 75 documented columns in total.

The most significant columns fall into distinct groups:

• Organization context: ORGANIZATION_STRUCTURE_ID identifies the organization hierarchy used for reporting, and ORG_STRUCTURE_VERSION_ID identifies the specific version of that hierarchy.
• Reporting defaults per profile: Each Projects Intelligence report has a triplet of period type, as-of date, and cycle ID, including DFLT_PRJPIP_PERIOD_TYPE, DFLT_PRJPIP_AS_OF_DATE, DFLT_PRJPIP_CYCLE_ID; corresponding triplets exist for PRJBAB, RESUTL, RESAVL, RESPLN, PRJHLT, PRJACT, PRJPRF, and PRJCST.
• Calendar and period controls: PA_PERIOD_FLAG and GL_PERIOD_FLAG govern period source selection, while CURR_REP_PA_PERIOD, CURR_REP_GL_PERIOD, and CURR_REP_ENT_PERIOD hold current reporting period values.
• Metric configuration: CONVERSION_RATIO_DAYS, BOOK_TO_BILL_DAYS, DSO_DAYS, and DORMANT_BACKLOG_DAYS drive calculation thresholds for key project performance metrics.
• Budget, forecast, and currency flags: COST_BUDGET_TYPE_CODE, REVENUE_BUDGET_TYPE_CODE, their conversion rules, forecast type codes, and currency indicators such as PRJ_CURR_FLAG, PROJFUNC_CURR_FLAG, and TXN_CURR_FLAG.
• Audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Administrators and developers query this table to inspect or validate the current Projects Intelligence configuration. A typical pattern retrieves all defaults for active editions:

SELECT SETTING_ID,
       ORGANIZATION_STRUCTURE_ID,
       ORG_STRUCTURE_VERSION_ID,
       DFLT_PRJPIP_PERIOD_TYPE,
       DFLT_PRJPIP_AS_OF_DATE,
       CURR_REP_PA_PERIOD,
       CURR_REP_GL_PERIOD
  FROM PJI.PJI_SYSTEM_SETTINGS
 WHERE ZD_EDITION_NAME = :edition;

Common scenarios include diagnosing discrepancies in reported project profitability caused by mismatched as-of dates, confirming which organization hierarchy version is active for reporting, and auditing metric thresholds such as DSO or dormant backlog days. Because the table drives default period and cycle selection, it is also queried during reconciliation between PA and GL reporting periods.

Related Objects

Two documented foreign keys anchor this table to the organization model:

• ORGANIZATION_STRUCTURE_ID references PER_ORGANIZATION_STRUCTURES, defining the reporting hierarchy.
• ORG_STRUCTURE_VERSION_ID references PER_ORG_STRUCTURE_VERSIONS, pinning the hierarchy version.

Additional dependent objects include the PJI reporting views and concurrent programs that read the DFLT_* triplet values (such as the Projects Intelligence performance, cost, and profitability reports), the Oracle Projects (PA) tables supplying period and cycle context, and the currency-related setup objects referenced by the various currency flags. Because the table is standalone with only organization-model foreign keys, most runtime dependencies are expressed through application logic rather than database constraints.