Search Results pji_system_parameters_u1

Overview

PJI.PJI_SYSTEM_PARAMETERS is a configuration table in the Oracle Projects Intelligence (PJI) module of Oracle E-Business Suite, documented as VALID in both 12.1.1 and 12.2.2. The table stores the parameters and default values that govern the behavior of a specific Oracle Projects Intelligence installation. Rather than holding transactional project data, it functions as a control repository: each row names a summarization parameter and supplies the value that the summarization engine, reporting layer, or extraction process reads at runtime. The object resides in the APPS_TS_INTERFACE tablespace with a PCT Free of 10, a storage profile typical of interface and staging objects rather than high-volume base tables.

From a data modeling perspective, the metadata carries no foreign key relationships to or from other objects, and the heuristic Data Vault classification is standalone. Under that model, the table is best treated as a standalone reference or configuration hub rather than a link or satellite, since it holds no foreign keys and participates in no declared referential integrity. Its role is that of a lookup source for parameter names and their assigned values.

Key Information Stored

The documented physical schema is deliberately narrow, comprising only two columns:

• NAME (VARCHAR2, 60, mandatory) — the summarization parameter name. This is the business key of the table and the column underpinning the unique index PJI_SYSTEM_PARAMETERS_U1. It is also documented as the primary key via PJI_SYSTEM_PARAMETERS_PK, making NAME the natural identifier for each configuration row.
• VALUE (VARCHAR2, 240) — the summarization parameter value associated with the corresponding NAME. Values are stored as character strings regardless of their logical type, so numeric thresholds, dates, flags, and text settings are all persisted in this single column and must be interpreted by the consuming process.

There is no documented surrogate system-generated key. The uniqueness constraint PJI_SYSTEM_PARAMETERS_U1 on NAME confirms that the business-key candidate and the physical primary key coincide, so each parameter name appears exactly once and can be used directly as a stable join predicate. Because only two columns are documented, no audit columns, effective dates, or organizational identifiers are present in the published schema.

Common Use Cases and Queries

The table is most frequently accessed to read, audit, or compare configuration values across environments. A standard retrieval of all parameters uses the query pattern published in the ETRM documentation:

• SELECT NAME, VALUE FROM PJI.PJI_SYSTEM_PARAMETERS; — full listing of the installation's summarization parameters.
• Point lookups by parameter name, exploiting the unique index on NAME, are the most efficient access path: SELECT VALUE FROM PJI.PJI_SYSTEM_PARAMETERS WHERE NAME = :param_name;
• Pattern searches support administrative review of parameter families, for example filtering on NAME LIKE 'PJI%' to isolate module-specific settings.
• Environment comparison queries join the table to itself across database links or staging copies on NAME to highlight VALUE differences between a development, test, and production instance.
• Reporting and diagnostic scripts extract VALUE and apply datatype conversion functions to validate that stored strings match the expected numeric or date formats.

Because the table is small and read-oriented, it is well suited to being cached or referenced directly in concurrent program logic and BI Publisher data models, provided that consumers cast the VARCHAR2 VALUE column appropriately.

Related Objects

The documented dependency section states that PJI.PJI_SYSTEM_PARAMETERS does not reference any database object, while it is referenced by the APPS synonym PJI_SYSTEM_PARAMETERS. This means the relationship surface is intentionally minimal and no foreign key joins are documented.

• APPS.PJI_SYSTEM_PARAMETERS — the synonym through which application code and concurrent programs address the table.
• PJI_SYSTEM_PARAMETERS_PK (NAME) — the primary key constraint enforcing row uniqueness.
• PJI_SYSTEM_PARAMETERS_U1 (NAME) — the unique index on the NAME column in APPS_TS_INTERFACE, the primary access path for parameter lookups.

Beyond these documented entries, related PJI summarization and collection objects consume the parameter values at runtime, but no explicit referential links are published in the ETRM metadata. Any join between PJI_SYSTEM_PARAMETERS and other PJI or Projects tables must therefore be constructed on the NAME column by convention rather than enforced by the database.