Results for “msd_booking_data_v”

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

Overview

MSD_BOOKING_DATA_V is a view owned by the APPS schema within the MSD (Demand Planning) product family of Oracle E-Business Suite, and is documented for both the 12.1.1 and 12.2.2 releases. It exposes booking data — the recorded demand for items against a given organization, sales channel, sales representative, and ship-to location — as it is stored in the planning server. The defining characteristic of the view is that it is not restricted by a demand plan. Because booking data resides in a plan-independent fact structure, the view can be queried directly whenever a planning server instance serves a single demand plan. Where multiple demand plans share one planning server, this view (or the underlying fact table) remains the appropriate access path precisely because it carries no plan filter. The view is therefore used for reporting, data extraction, and integration of historical and forward-looking bookings into downstream planning, analytics, and custom EBS reports.

Underlying Base Objects

The documented view metadata identifies two referenced objects, both exposed as synonyms: MSD_BOOKING_DATA and MSD_LEVEL_VALUES. MSD_BOOKING_DATA is the fact table holding the measures and date attributes of each booking record, together with surrogate keys (SR_INV_ORG_PK, SR_ITEM_PK, SR_SALES_CHANNEL_PK, SR_SALES_REP_PK, SR_SHIP_TO_LOC_PK) and an INSTANCE column that identifies the planning server instance.

MSD_LEVEL_VALUES is the level-member dimension table. The view joins it five times — once for each dimension of the booking fact — to resolve surrogate keys into level values. Each join is constrained both by INSTANCE and by a fixed LEVEL_ID, confirming the level-member semantics: level 7 for inventory organization, 1 for item, 27 for sales channel, 18 for sales representative, and 11 for ship-to location. This join pattern is what allows the view to present readable dimension values alongside their primary keys.

Key Columns

The view returns paired value/key columns for each dimension:

• INV_ORG / INV_ORG_PK — inventory organization level value and its primary key (derived from ORG_PK, LEVEL_ID 7).
• ITEM / ITEM_PK — item level value and primary key (LEVEL_ID 1).
• SALES_CHANNEL / SALES_CHANNEL_PK — sales channel level value and primary key (LEVEL_ID 27).
• SALES_REP / SALES_REP_PK — sales representative level value and primary key (LEVEL_ID 18).
• SHIP_TO_LOC / SHIP_TO_LOC_PK — ship-to location level value and primary key (LEVEL_ID 11).
• USER_DEFINED1 / USER_DEFINED2 — user-defined attributes passed through from the fact table; the corresponding _PK columns are returned as NULL.
• BOOKED_DATE, REQUESTED_DATE, PROMISED_DATE, SCHEDULED_DATE — the booking, request, promise, and schedule dates for each record.
• AMOUNT — the monetary booking amount.
• QTY_ORDERED — the ordered quantity. This is the column most commonly referenced and the term matching the user's search; it is the primary demand quantity carried by the booking fact.

Common Use Cases and Queries

Typical scenarios include extracting booking history for demand analytics, feeding booking quantities into custom forecast reconciliation reports, and surfacing plan-independent booking totals by organization, item, or channel.

• Total ordered quantity by item: SELECT ITEM, SUM(QTY_ORDERED) FROM APPS.MSD_BOOKING_DATA_V GROUP BY ITEM;
• Bookings within a date range: SELECT INV_ORG, ITEM, SALES_CHANNEL, BOOKED_DATE, QTY_ORDERED, AMOUNT FROM APPS.MSD_BOOKING_DATA_V WHERE BOOKED_DATE BETWEEN :start_date AND :end_date;
• Bookings by ship-to location and sales representative: SELECT SHIP_TO_LOC, SALES_REP, SUM(AMOUNT) FROM APPS.MSD_BOOKING_DATA_V GROUP BY SHIP_TO_LOC, SALES_REP;

Because the view applies no demand plan predicate, queries return all booking data available to the planning server instance, which is the intended behavior for plan-independent reporting.