Search Results curr_flag

Overview

The MSC_PLAN_BUCKETS table is a core data object within the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) module. It serves as the foundational repository for time-phased bucket definitions used specifically by the Planner Workbench Horizontal Plan. This table is critical for the application's time-series planning logic, as it stores the chronological sequence of planning periods (buckets) against which supply, demand, and net requirements are projected and analyzed for a given plan and organization. The integrity of the Horizontal Plan's graphical and tabular displays depends directly on the accurate population of this table during the plan launch process.

Key Information Stored

The table's primary key uniquely identifies a bucket for a specific plan and organization, ensuring no duplicate time periods exist for the same planning context. The key columns are PLAN_ID, SR_INSTANCE_ID, ORGANIZATION_ID, BUCKET_INDEX, and CURR_FLAG. The PLAN_ID links to the master planning definition, while SR_INSTANCE_ID and ORGANIZATION_ID identify the specific inventory organization being planned. The BUCKET_INDEX is a sequential integer defining the order of the time bucket. Although not listed in the provided metadata, based on its described purpose, the table would also contain columns for the bucket's start date (BUCKET_DATE) and potentially its type (e.g., daily, weekly). The CURR_FLAG is a common Oracle EBS construct, typically used to mark the current or most relevant record in a historical set.

Common Use Cases and Queries

The primary use case is supporting the Planner Workbench interface, where queries against this table structure the horizontal time axis. It is also essential for custom reports that need to align planning data with the official planning calendar. A common analytical query involves joining this table to requirement and supply snapshots (like MSC_NET_RESULTS) to aggregate data by the defined planning periods. For instance, to retrieve the bucket schedule for a specific plan, a query would be: SELECT bucket_index, bucket_date FROM msc_plan_buckets WHERE plan_id = :p_plan_id AND organization_id = :p_org_id AND sr_instance_id = :p_instance_id ORDER BY bucket_index;. Troubleshooting plan data display issues often involves verifying that this table is populated correctly for the affected plan and organization.

Related Objects

As documented in the foreign key metadata, MSC_PLAN_BUCKETS has a direct and essential relationship with the MSC_PLAN_ORGANIZATIONS table. This foreign key enforces referential integrity, ensuring that a bucket record cannot exist without a corresponding organization defined within the plan. The join is performed on three key columns: PLAN_ID, ORGANIZATION_ID, and SR_INSTANCE_ID. This relationship underscores that bucket definitions are scoped at the plan-organization level. The table is also a likely parent to numerous planning snapshot tables (e.g., MSC_SUPPLIES, MSC_DEMANDS, MSC_NET_RESULTS) which use the composite key of PLAN_ID, ORGANIZATION_ID, SR_INSTANCE_ID, and BUCKET_DATE or BUCKET_INDEX to associate transactional data with a specific planning time period.