Results for “msd_booking_data_cs_v”

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

Overview

MSD_BOOKING_DATA_CS_V is a database view owned by the APPS schema within the MSD — Demand Planning product of Oracle E-Business Suite. Its documented purpose is to provide Booking Data to the Express Upload process, and it is implemented through the Custom Data Stream Module. This view therefore acts as a staging and interface layer that presents booking records in a denormalized, dimension-resolved format suitable for bulk loading and consumption by Express Upload routines rather than for direct transactional maintenance.

The view is registered as VALID in the ETRM 12.2.2 metadata, which confirms it is a supported, non-invalidated object in a running 12.2.2 instance. Because the object name carries the CS suffix, the view is understood to belong to the Custom Data Stream family of MSD interfaces, whose members are designed to flatten hierarchical level values into explicit, hard-coded level identifiers. This design enables the Express Upload engine to interpret each row without additional lookups at load time.

Underlying Base Objects

The documented base objects referenced by MSD_BOOKING_DATA_CS_V are two synonyms: MSD_BOOKING_DATA and MSD_LEVEL_VALUES. MSD_BOOKING_DATA is the fact-like source holding the booking transaction records, including booked, requested, promised, and scheduled dates along with ordered amounts and quantities. MSD_LEVEL_VALUES is the level-instance mapping table that resolves surrogate level keys to the levels used by the MSD data model.

The view joins MSD_BOOKING_DATA to MSD_LEVEL_VALUES six times, each aliased to a distinct dimension: ORG_PK, ITEM_PK, SALES_CHANNEL_PK, SALES_REP_PK, SHIP_TO_LOC_PK, and PARENT_ITEM_PK. Each join matches on INSTANCE and the corresponding SR_LEVEL_PK column and is further constrained by a fixed LEVEL_ID. The parent item join is an outer join, so bookings without an associated parent item are retained with null parent attributes.

Key Columns

The view exposes a set of level identifier and level value pairs that describe each booking across the MSD dimensions:

• PRD_LEVEL_ID and PRD_LEVEL_VALUE — product level (1) and the resolved item level value.
• GEO_LEVEL_ID and GEO_LEVEL_VALUE_PK — geography level (11) and the ship-to location value.
• ORG_LEVEL_ID and ORG_LEVEL_VALUE_PK — organization level (7) and the inventory organization value.
• REP_LEVEL_ID and REP_LEVEL_VALUE_PK — sales representative level (18) and its value.
• CHN_LEVEL_ID and CHN_LEVEL_VALUE_PK — sales channel level (27) and its value.
• UD1_LEVEL_ID, UD1_LEVEL_VALUE_PK, UD2_LEVEL_ID, UD2_LEVEL_VALUE_PK — user-defined levels, returned as NULL in this implementation.
• PRD_PARENT_LEVEL_ID and PRD_PARENT_LEVEL_VALUE_PK — parent product level, derived via DECODE and populated only when a parent item exists.
• TIME_LEVEL_ID — time level (9), with BOOKED_DATE, REQUESTED_DATE, PROMISED_DATE, and SCHEDULED_DATE supplying the temporal detail.
• AMOUNT and QTY_ORDERED — the booked monetary and quantity measures.
• Audit and refresh columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_REFRESH_NUM, CREATED_BY_REFRESH_NUM, and ACTION_CODE.

Common Use Cases and Queries

Typical use is to feed the Express Upload process with booking demand spread across product, geography, organization, representative, channel, and time. Demand planners and integration developers may also query the view directly for diagnostics.

• Verify data availability for an upload cycle by counting rows per booking date.
• Aggregate ordered quantity and amount by organization and item.
• Inspect bookings lacking a parent item, using the outer-join behavior.
• Track refresh activity through LAST_REFRESH_NUM and ACTION_CODE.

Example query:

SELECT PRD_LEVEL_VALUE, ORG_LEVEL_VALUE_PK, SUM(QTY_ORDERED) TOTAL_QTY, SUM(AMOUNT) TOTAL_AMT FROM APPS.MSD_BOOKING_DATA_CS_V WHERE BOOKED_DATE >= :p_from_date GROUP BY PRD_LEVEL_VALUE, ORG_LEVEL_VALUE_PK ORDER BY TOTAL_AMT DESC;

A second query to isolate records without a parent item:

SELECT PRD_LEVEL_VALUE, BOOKED_DATE, QTY_ORDERED FROM APPS.MSD_BOOKING_DATA_CS_V WHERE PRD_PARENT_LEVEL_VALUE_PK IS NULL;