Results for “msd_sr_booking_data_v”

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

Overview

MSD_SR_BOOKING_DATA_V is an APPS-owned database view in the Oracle E-Business Suite, classified under the MSD – Demand Planning product family. Its documented purpose is to serve as the Source View for Booking Data, exposing order booking information from an Oracle Applications instance so that it can be retrieved and consumed by downstream planning and analytics processes. In the ETRM context, this view functions as a defined staging interface: the Demand Planning engine queries it to collect booking records that are subsequently transformed and loaded into the planning schema. Because the view is defined in the APPS schema and marked VALID, it is treated as a supported integration object rather than an ad hoc query artifact.

The view is relevant to both Oracle EBS 12.1.1 and 12.2.2. The documentation explicitly notes that it "would be applied to an Oracle Applications 11i instance," which reflects its original 11i lineage; the same definition has been carried forward into later releases. The user's search term, sr_original_item_pk, corresponds to the column-position semantics embedded in the view text, where NVL-wrapped primary key values (including item references) are emitted for the source-record columns.

Underlying Base Objects

The documented metadata lists the following referenced base objects: FND_GLOBAL (package), FND_PRODUCT_GROUPS (synonym), HZ_CUST_ACCOUNTS (synonym), HZ_CUST_SITE_USES_ALL (synonym), MSD_APP_INSTANCE_ORGS (synonym), MSD_SETUP_PARAMETERS (synonym), MSD_SR_UTIL (package), MTL_SYSTEM_ITEMS (synonym), OE_ORDER_HEADERS_ALL (synonym), OE_ORDER_LINES_ALL (synonym), RA_SALESREPS_ALL (synonym), and SO_LOOKUPS (synonym).

The core transactional data is drawn from OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL, which supply booking dates, ordered quantities, pricing, promise and schedule ship dates, and item identifiers. MTL_SYSTEM_ITEMS provides the inventory item master, while HZ_CUST_ACCOUNTS and HZ_CUST_SITE_USES_ALL supply customer and site-use context. RA_SALESREPS_ALL provides sales representative information, and SO_LOOKUPS supplies lookup code values. MSD_APP_INSTANCE_ORGS and MSD_SETUP_PARAMETERS control instance and parameter scoping. The MSD_SR_UTIL package is invoked repeatedly for null primary key substitution, unit-of-measure conversion, global amount conversion, and parent-item resolution; FND_GLOBAL and FND_PRODUCT_GROUPS provide session and product-group context.

Key Columns

• Primary key substitution columns — The view emits NVL(..., MSD_SR_UTIL.GET_NULL_PK) and NULL alternating pairs for ship-from organization, inventory item, customer, lookup code, salesrep, and site-use identifiers. These represent the source-record key structure, including the item reference associated with sr_original_item_pk.
• Booking and date columns — BOOKED_DATE, REQUEST_DATE, PROMISE_DATE, and SCHEDULE_SHIP_DATE, each truncated to day precision and defaulted to TO_DATE('1000/01/01','YYYY/MM/DD') when null.
• Extended amount — A computed revenue measure combining UOM conversion, ordered quantity, unit selling price (falling back to unit list price), and global amount conversion keyed to the transactional currency and booking date.
• Quantity — UOM-converted ordered quantity.
• Item and parent-item columns — INVENTORY_ITEM_ID along with a conditional expression that resolves the parent item for ATO configurations, using MSD_SR_UTIL.FIND_PARENT_ITEM controlled by MSD_SETUP_PARAMETERS.PARAMETER_VALUE.

Common Use Cases and Queries

Typical usage centers on extracting booking facts for demand planning loads and for reconciliation of booked versus shipped activity. A minimal projection follows:

SELECT inventory_item_id,
       booked_date,
       ordered_quantity,
       extended_amount
  FROM apps.msd_sr_booking_data_v
 WHERE booked_date >= TRUNC(SYSDATE) - 30;

Analysts may group by item and period to derive booking trends, or join the view to MTL_SYSTEM_ITEMS to resolve item descriptions. Because the view resolves parent items for ATO and option lines, it is also used to aggregate demand at the configured-item level rather than at the option level, which is essential for accurate forecasting. Any query should account for the substituted null-PK sentinel values and the 1000/01/01 default dates when filtering.