Search Results shipment_receipt

Overview

APPS.MSC_CUST_BUCKET_V is a reporting and integration view in the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) schema. It presents supply-and-demand plan entries in a pivoted, planning-bucket form, exposing a single quantity measure distributed across a fixed set of named demand and supply categories. Each of the categories — sales forecast, order forecast, supply commit, historical sales, sell-through forecast, negotiated capacity, safety stock, allocated on-hand, unallocated on-hand, and others — is materialized as an individual column, and the value returned is conditioned on the value of the publisher_order_type discriminator on the underlying row.

The view is primarily consumed by downstream planning publishers and by customers or suppliers that receive published plan data through the MSC collaborative planning framework. Its central purpose is to normalize the direction and ownership of a plan entry: quantities owned by the current planning company are reported from primary_quantity, while quantities belonging to a trading partner are reported from tp_quantity, the trading-partner quantity. This makes MSC_CUST_BUCKET_V the natural source for any report that must reconcile internal versus partner-supplied plan figures.

Underlying Base Objects

The view is defined over the documented base objects MSC_SUP_DEM_ENTRIES_UI_V (a view), and it references the packages FND_GLOBAL and MSC_X_UTIL. MSC_SUP_DEM_ENTRIES_UI_V supplies the supply/demand entry rows that carry publisher_order_type, publisher_id, customer_id, supplier_id, primary_quantity, and tp_quantity. FND_GLOBAL is used to resolve the runtime application context — most notably the company identifier retrieved through SYS_CONTEXT('MSC','COMPANY_ID'), which drives the ownership branch in each DECODE expression. MSC_X_UTIL supplies supporting planning utility logic used elsewhere in the planning schema. Because the view resolves the company from the session context, its output is security-context dependent and reflects the planning company of the active session.

Key Columns

• sales_forecast — populated when publisher_order_type = 1; the entry is classified as a sales forecast.
• order_forecast — populated when publisher_order_type = 2.
• supply_commit — populated when publisher_order_type = 3.
• historical_sales — populated when publisher_order_type = 4.
• sell_through_forecast — populated when publisher_order_type = 5.
• negotiated_capacity — populated when publisher_order_type = 6.
• safety_stock — populated when publisher_order_type = 7.
• allocated_onhand — populated when publisher_order_type = 9.
• unallocated_onhand — populated when publisher_order_type = 10.
• tp_quantity — the trading-partner quantity. When the publishing entity is not the current company and the row identifies a partner relationship, the measure is drawn from tp_quantity rather than primary_quantity.
• primary_quantity — the quantity when the publisher is the current planning company.

In every category column, rows whose publisher_order_type does not match the column's category return zero, so the view behaves as a sparse matrix keyed by plan entry.

Common Use Cases and Queries

Typical uses include published forecast reconciliation between an OEM and its suppliers, safety-stock and on-hand reporting for partner collaboration, and bucket-level analysis of forecasts by customer or supplier. A representative query aggregating sales and order forecasts follows:

• SELECT sales_forecast, order_forecast, supply_commit, tp_quantity FROM apps.msc_cust_bucket_v WHERE sales_forecast > 0 OR order_forecast > 0;
• SELECT SUM(sales_forecast) total_sf, SUM(tp_quantity) total_tp FROM apps.msc_cust_bucket_v;

Because quantities depend on the MSC company context and on the trading-partner branch, queries should be executed within the appropriate planning responsibility so that SYS_CONTEXT('MSC','COMPANY_ID') resolves correctly and partner versus internal quantities are attributed accurately.