Search Results day_bucket

Overview

The APPS.MSC_VERTICAL_PLAN_SC package body is a server-side PL/SQL component in Oracle E-Business Suite Advanced Supply Chain Planning (ASCP), part of the MSC (Manufacturing Supply Chain) schema. Its header comment identifies the source file as MSCVERPB.pls, last updated at version 115.15 in 2004, indicating a long-stable interface that carries into both EBS 12.1.1 and 12.2.2. The package's core purpose is to convert time-phased planning activity from the MSC vertical plan view into bucketed quantities organized by calendar period. This is the mechanism behind weekly, monthly, and other period-bucketed displays of supply, demand, and projected available balance in the planning workbench. The suffix "_SC" denotes a supply chain planning utility rather than a public open interface API; ETRM classifies the package as API classification OTHER, meaning it is a supporting internal routine rather than a documented integration entry point.

Key Procedures and Functions

• POPULATE_BUCKETED_QUANTITY — The central documented routine and the object most relevant to the "week_bucket" search. It aggregates planning rows into date-bucketed quantities and returns a concatenated quantity string, a matching period-name string, and a period count. Internally it declares a cursor over the MSC_VERTICAL_PLAN_V view that groups quantity_rate by new_due_date, organization, and item, and it uses an associative array of bucket start dates together with a parallel array of per-bucket quantities. Bucket boundaries are derived from the calendar date tables rather than computed inline, which is why the same procedure can produce day, week, or period buckets depending on the bucket type requested.
• GET_EXCEPTION_GROUP — Resolves the exception grouping associated with a planning exception, allowing the calling form or report to present exceptions under their defined group classification.
• FLUSH_MULTI_RETURN — Handles the emission of multi-value return buffers, flushing accumulated string or numeric results back to the caller. This pattern exists because PL/SQL output parameters passed through certain EBS form and Java integration layers must be assembled and returned in a controlled sequence.

The package also contains private helper logic, including an add_to_plan routine that appends a quantity to the current bucket, and cursor-level filtering by plan, instance, organization, and item.

Tables Accessed

• MSC_CALENDAR_DATES, MSC_CAL_WEEK_START_DATES, MSC_PERIOD_START_DATES — Supply the start dates that define bucket boundaries. MSC_CAL_WEEK_START_DATES is directly responsible for week-level bucketing.
• MSC_PLANS — Identifies the plan and its calendar/period configuration.
• MSC_FORM_QUERY — Stores the query definition used by the planning form to request a bucketed result set.
• MSC_TRADING_PARTNERS — Resolves partner information for supply chain plan rows.
• PLITBLM — The standard EBS PL/SQL table (index-by table) used for passing array values between forms and the database.

Usage Notes

MSC_VERTICAL_PLAN_SC is not documented as being referenced by any other package, so it is invoked directly rather than through a dependency chain. Typical invocation is from the ASCP planning workbench when a user selects a bucketed view such as weekly, from concurrent planning reports that require period-summarized output, and from custom extensions that need the same bucket calculation used by the standard vertical plan display. Because it reads the MSC_VERTICAL_PLAN_V view and returns delimited strings, callers should expect plan/instance/organization/item context to be supplied on every call and should treat the returned period strings as presentation-ready rather than as raw dates.