Results for “bkt_end_date”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

MSC_PLAN_BUCKETS is a table in the MSC schema (Advanced Supply Chain Planning) within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the bucket date definitions used by the Planner Workbench Horizontal Plan, providing the time-bucketing framework against which planned supply, demand, and projected on-hand quantities are aggregated and displayed to planners. Each row represents a single time bucket for a given plan, organization, and source instance, defining that bucket's start date, end date, and duration.

From a dimensional modeling perspective, the table's foreign key structure is satellite-leaning. It references MSC_PLAN_ORGANIZATIONS and carries descriptive bucket attributes (dates, duration, type) that contextualize the parent plan/organization combination. The ETRM metadata classifies it heuristically as satellite-leaning, meaning it is best understood as an attribute-bearing table attached to a plan-organization hub rather than as an independent transactional hub or a pure many-to-many link.

Key Information Stored

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

• PLAN_ID — Identifies the Advanced Supply Chain plan the buckets belong to.
• ORGANIZATION_ID — The inventory organization whose buckets are defined.
• SR_INSTANCE_ID — Source instance identifier, supporting multi-source or multi-instance planning.
• BUCKET_INDEX — Ordinal position of the bucket within the plan horizon (e.g., bucket 1, 2, 3 …).
• CURR_FLAG — Flag indicating whether the bucket row is the current active definition.
• BKT_START_DATE — The starting date of the bucket.
• BKT_END_DATE — The ending date of the bucket.
• DAYS_IN_BKT — Number of days covered by the bucket.
• BUCKET_TYPE — Classification of the bucket (for example, day, week, or period granularity).
• LAST_UPDATE_DATE, CREATION_DATE, CREATED_BY, LAST_UPDATED_BY — Standard audit columns for change tracking.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — Concurrent program context that last created or refreshed the row.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — The standard EBS descriptive flexfield (DFF) columns.

The composite primary key is defined by MSC_PLAN_BUCKETS_PK over (CURR_FLAG, PLAN_ID, ORGANIZATION_ID, BUCKET_INDEX, SR_INSTANCE_ID). The unique index MSC_PLAN_BUCKETS_U1 covers the same business-key columns (PLAN_ID, ORGANIZATION_ID, SR_INSTANCE_ID, BUCKET_INDEX, CURR_FLAG) in a slightly different order, confirming that this combination—not a generated surrogate—is the true business key. No single-column surrogate key is documented; the primary key is composite and business-meaningful.

Common Use Cases and Queries

Typical uses include building horizontal plan reports, resolving bucket index positions to calendar dates for a given plan horizon, and validating that bucket definitions align with planning calendar settings. A common query joins buckets to plan organizations to retrieve the date range for a specific plan and organization:

• Retrieve all buckets for a plan and organization: SELECT BUCKET_INDEX, BKT_START_DATE, BKT_END_DATE, DAYS_IN_BKT, BUCKET_TYPE FROM MSC.MSC_PLAN_BUCKETS WHERE PLAN_ID = :plan_id AND ORGANIZATION_ID = :org_id AND CURR_FLAG = 'Y' ORDER BY BUCKET_INDEX;
• Join to the parent organization row: SELECT b.BUCKET_INDEX, b.BKT_START_DATE, b.BKT_END_DATE FROM MSC.MSC_PLAN_BUCKETS b, MSC.MSC_PLAN_ORGANIZATIONS o WHERE b.PLAN_ID = o.PLAN_ID AND b.ORGANIZATION_ID = o.ORGANIZATION_ID AND b.SR_INSTANCE_ID = o.SR_INSTANCE_ID;
• Determine the bucket that contains a given date: filter on BKT_START_DATE <= :as_of_date AND BKT_END_DATE >= :as_of_date.

Reporting scenarios include horizon-length analysis, bucket granularity audits before running a plan, and reconciliation of planner-facing date labels against the underlying supply/demand time fences.

Related Objects

The most significant related objects are:

• MSC_PLAN_ORGANIZATIONS — Referenced by the foreign key on PLAN_ID, ORGANIZATION_ID, and SR_INSTANCE_ID; the parent plan-organization definition.
• MSC_PLANS — Plan-level attributes that contextualize PLAN_ID.
• MSC_PLAN_ENTRIES / MSC_SUPPLIES and MSC_DEMANDS — Fact-style tables whose quantities are aggregated into the horizontal plan using bucket dates.
• MSC_PLAN_BUCKETS_PK / MSC_PLAN_BUCKETS_U1 — The composite primary key and unique index enforcing bucket uniqueness.
• Planner Workbench Horizontal Plan concurrent programs — The processes (reflected in REQUEST_ID/PROGRAM_ID) that populate and refresh bucket rows.

These relationships establish MSC_PLAN_BUCKETS as the date-dimension underpinning for horizontal plan visualization in Advanced Supply Chain Planning.