Search Results pji_mt_buckets




Overview
Explore in AI Chat

Overview

PJI_MT_BUCKETS is a table in the PJI (Project Intelligence) schema of Oracle E-Business Suite, belonging to the obsolete PJI - Project Intelligence product module. The table stores information about bucket values for different measures used in project reporting and analytics. In Oracle EBS 12.1.1 and 12.2.2, Project Intelligence provided multidimensional reporting capabilities for project data, and bucket definitions were essential for organizing numeric ranges into meaningful analytical groupings.

Each row in PJI_MT_BUCKETS defines a discrete bucket within a named bucket set. A bucket set is identified by BUCKET_SET_CODE, and the buckets within it are bound by FROM_VALUE and TO_VALUE ranges. This structure allows project measures — such as cost, revenue, effort, or utilization — to be classified into ranges for aggregation, exception reporting, and graphical presentation. The table is documented as VALID but belongs to a legacy module that has been superseded by later Oracle Analytics and EBS reporting frameworks.

From a Data Vault modeling perspective, the mined FK structure is standalone, meaning no foreign key relationships were detected. Heuristically, the table behaves most like a reference satellite (or lookup satellite) whose parent hub or link key is composite (BUCKET_SET_CODE, NAME). Because the metadata does not expose an FK to a parent bucket-set table within the documented schema, this classification is a modeling suggestion rather than a documented fact.

Key Information Stored

The table contains 12 documented columns. The most significant are:

  • BUCKET_SET_CODE — the identifier of the bucket set to which the row belongs. Together with NAME, it forms the primary key.
  • NAME — the bucket name or label within the set.
  • SEQ — the sequencing order of the bucket within its set, controlling display ordering.
  • FROM_VALUE — the lower boundary of the bucket range.
  • TO_VALUE — the upper boundary of the bucket range.
  • DEFAULT_FLAG — indicates whether the bucket is the default for the set or is used as a catch-all for values outside defined ranges.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY — audit columns for the most recent change.
  • CREATION_DATE, CREATED_BY — audit columns for initial creation.
  • LAST_UPDATE_LOGIN — the login session associated with the last update.
  • ZD_EDITION_NAME — the editioning column supporting EBS 12.2 online patching (Edition-Based Redefinition).

The surrogate primary key is PJI_MT_BUCKETS_PK, defined across (BUCKET_SET_CODE, NAME). The unique index PJI_MT_BUCKETS_U1 spans (BUCKET_SET_CODE, NAME, ZD_EDITION_NAME), refining the business-key candidate to include the editioning column. This composite structure confirms that a bucket is uniquely identified by its set and name, with ZD_EDITION_NAME distinguishing runtime editions.

Common Use Cases and Queries

Bucket definitions are primarily consumed during report execution to classify measure values. A typical query retrieves all buckets for a set in display order:

  • SELECT bucket_set_code, name, seq, from_value, to_value, default_flag FROM pji_mt_buckets WHERE bucket_set_code = :set_code ORDER BY seq;
  • Identify the default bucket: SELECT name FROM pji_mt_buckets WHERE bucket_set_code = :set_code AND default_flag = 'Y';
  • Validate non-overlapping ranges by comparing FROM_VALUE/TO_VALUE across SEQ-ordered rows within a set.

Reporting scenarios include profitability banding (e.g., margin buckets), effort ranges for utilization analysis, and exception dashboards that flag projects falling outside expected thresholds. Because the module is obsolete, most environments read this table only when maintaining or migrating legacy Project Intelligence configurations.

Related Objects

The documented metadata reports no foreign keys (standalone classification), so dependent objects are inferred from the PJI schema and standard EBS patterns rather than FK evidence:

  • PJI_MT_BUCKET_SETS (or similarly named bucket-set table) — likely parent referenced by BUCKET_SET_CODE.
  • Additional PJI_MT_* measure tables that reference bucket sets for metric classification.
  • Project Intelligence reporting views and concurrent programs within the PJI module that consume BUCKET_SET_CODE and NAME.
  • EBS audit columns (CREATED_BY, LAST_UPDATED_BY) resolve to FND_USER.

Because the FK structure is undocumented, administrators should confirm actual dependencies through the data dictionary (USER_CONSTRAINTS, USER_DEPENDENCIES) before modifying configurations in a live 12.1.1 or 12.2.2 instance.