Results for “msd_booking_data_orig_cs_v”

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

Overview

The MSD_BOOKING_DATA_ORIG_CS_V view is an APPS-owned, VALID database object within the Oracle EBS 12.1.1 / 12.2.2 environment, delivered as part of the MSD - Demand Planning product family. Its stated purpose is to support product substitution in booking data. In practice, the view presents booking transaction records from MSD_BOOKING_DATA alongside denormalized level-value surrogate keys resolved from MSD_LEVEL_VALUES. It emits a fixed set of dimension level identifiers (PRD, GEO, ORG, REP, CHN, TIME) so that downstream demand planning, substitution logic, and integration processes can consume booking data through a stable interface without directly joining the level hierarchy tables.

Because the object is a view rather than a table, it holds no data of its own; it is a reporting and integration surface layered over the base MSD tables. This design isolates consumers from the physical structure of MSD_BOOKING_DATA and centralizes the level-resolution logic used for product substitution scenarios.

Underlying Base Objects

The documented dependent objects are two synonyms owned within the APPS context:

• MSD_BOOKING_DATA (SYNONYM) — the primary source of booking rows, supplying dates, quantities, amounts, audit columns, and the surrogate key references (SR_INV_ORG_PK, SR_ORIGINAL_ITEM_PK, SR_SALES_CHANNEL_PK, SR_SALES_REP_PK, SR_SHIP_TO_LOC_PK, and SR_PARENT_ITEM_PK).
• MSD_LEVEL_VALUES (SYNONYM) — the level-hierarchy lookup table, aliased six times (ORG_PK, ITEM_PK, SALES_CHANNEL_PK, SALES_REP_PK, SHIP_TO_LOC_PK, PARENT_ITEM_PK) to resolve each surrogate key to its corresponding LEVEL_PK.

Joins are performed on INSTANCE and the appropriate SR_LEVEL_PK pairing, with each alias constrained to a specific LEVEL_ID. The PARENT_ITEM_PK join is an outer join, so bookings without an associated parent item are still returned, with NULL parent values.

Key Columns

The view exposes both hard-coded dimension constants and resolved values:

• Level ID constants: PRD_LEVEL_ID (1), GEO_LEVEL_ID (11), ORG_LEVEL_ID (7), REP_LEVEL_ID (18), CHN_LEVEL_ID (27), TIME_LEVEL_ID (9). UD1_LEVEL_ID and UD2_LEVEL_ID are NULL.
• Resolved value keys: PRD_LEVEL_VALUE_PK, GEO_LEVEL_VALUE_PK, ORG_LEVEL_VALUE_PK, REP_LEVEL_VALUE_PK, CHN_LEVEL_VALUE_PK.
• Product substitution columns: PRD_PARENT_LEVEL_ID (DECODE returning 1 when a parent item exists, else NULL) and PRD_PARENT_LEVEL_VALUE_PK. These are central to the substitution use case referenced by the user search term prd_parent_level_id.
• Measures and dates: BOOKED_DATE, REQUESTED_DATE, PROMISED_DATE, SCHEDULED_DATE, AMOUNT, and QTY_ORDERED.
• Audit/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 scenarios include retrieving bookings with their resolved product parent for substitution analysis, and filtering bookings by organization or ship-to location. Because PRD_PARENT_LEVEL_ID is derived, a query such as the following identifies bookings eligible for parent-based substitution:

• SELECT prd_level_value_pk, prd_parent_level_value_pk, qty_ordered, booked_date FROM msd_booking_data_orig_cs_v WHERE prd_parent_level_id IS NOT NULL;
• SELECT org_level_value_pk, SUM(qty_ordered) FROM msd_booking_data_orig_cs_v GROUP BY org_level_value_pk;
• SELECT * FROM msd_booking_data_orig_cs_v WHERE booked_date BETWEEN :start_date AND :end_date;

These queries reinforce the view's role as a convenient, substitution-aware read interface over MSD booking data.