Search Results mrp_bucket_type

Overview

The APPS.ICX_MRP_FORECAST_DATES_V view presents forecast demand records sourced from Oracle's Material Requirements Planning (MRP) and Master Production Scheduling (MPS) forecast data. It is a reporting-oriented view within the iProcurement/ICX schema family that exposes forecast lines already decoded with their lookup meanings, allowing consumers to read human-readable descriptions of bucket types and origination types without performing additional joins to the lookup tables. Because the view joins organization, item, and lookup descriptors into a single flattened result set, it is well suited for ad hoc reporting, dashboard queries, and integration extracts that must reconcile forecast data across organizations and planning designators.

The view is defined over the forecast dates base object (MRP_FORECAST_DATES) and enriches it with descriptive attributes sourced from MFG_LOOKUPS, MTL_ITEM_FLEXFIELDS, and MTL_PARAMETERS. The search term mrp_bucket_type is directly relevant here: the view resolves the BUCKET_TYPE lookup code against the MFG_LOOKUPS lookup type value MRP_BUCKET_TYPE, exposing the decoded meaning as BUCKET_TYPE_DESC.

Underlying Base Objects

The documented base objects referenced by this view are:

• MRP_FORECAST_DATES (accessed via synonym) — the primary source of forecast rows, providing forecast dates, quantities, confidence, and sources.
• MFG_LOOKUPS (view) — joined twice: once as L1 for the ORIGINATION_TYPE lookup type MRP_FORECAST_ORIG, and once as L2 for the BUCKET_TYPE lookup type MRP_BUCKET_TYPE.
• MTL_ITEM_FLEXFIELDS (view) — joined on ORGANIZATION_ID and END_ITEM_ID to return the concatenated item number for the end item.
• MTL_PARAMETERS (accessed via synonym) — joined on SOURCE_ORGANIZATION_ID to return the source organization code.

All three secondary relationships are outer joins (indicated by the (+) operator), so forecast rows are preserved even when no matching item, organization, or source organization descriptor exists. The lookup joins on BUCKET_TYPE and ORIGINATION_TYPE are standard equijoins and therefore require valid lookup codes to return a row.

Key Columns

• TRANSACTION_ID, INVENTORY_ITEM_ID, ORGANIZATION_ID — identify the forecast line and the owning item/organization context.
• FORECAST_DESIGNATOR, SOURCE_FORECAST_DESIGNATOR — the forecast name and any originating designator.
• BUCKET_TYPE / BUCKET_TYPE_DESC — the raw lookup code and its decoded meaning from lookup type MRP_BUCKET_TYPE, central to the user's search.
• FORECAST_DATE, RATE_END_DATE — the date range over which the forecast quantity applies.
• CURRENT_FORECAST_QUANTITY, ORIGINAL_FORECAST_QUANTITY, CONFIDENCE_PERCENTAGE — quantitative forecast measures.
• ORIGINATION_TYPE / ORIGINATION_TYPE_DESC — decoded origin from lookup type MRP_FORECAST_ORIG.
• CUSTOMER_ID, SHIP_ID, BILL_ID — demand source references for customer-driven forecasts.
• SOURCE_ORGANIZATION_ID, ORGANIZATION_CODE — the supplying organization and its code.
• END_ITEM_ID, END_ITEM_SEGMENT, ITEM_SEGMENTS — the end item and its flexfield item number.
• END_PLANNING_BOM_PERCENT, DEMAND_CLASS — planning and classification attributes.

Common Use Cases and Queries

A frequent scenario is reporting forecast quantities grouped by decoded bucket type, which directly answers queries phrased around mrp_bucket_type:

• Summarizing forecast demand per organization, designator, and bucket type description.
• Filtering forecast lines to a specific date window or confidence threshold for planning reviews.
• Auditing which lookup meaning is attached to each bucket and origination type.
• Extracting item-level forecast data joined to item flexfield descriptions for integration.

Sample query:

SELECT organization_id, forecast_designator, bucket_type, bucket_type_desc, forecast_date, current_forecast_quantity FROM apps.icx_mrp_forecast_dates_v WHERE bucket_type = :p_bucket AND forecast_date BETWEEN :p_start AND :p_end ORDER BY organization_id, forecast_date;

Because MFG_LOOKUPS, MTL_ITEM_FLEXFIELDS, and MTL_PARAMETERS are joined, callers should expect the item and organization descriptors to be null when the outer-join conditions are unmet, and should still apply the appropriate organization security or planning context in their predicates for accurate results.