Results for “rep_level_value_pk”

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

Overview

MSD_CS_PLANNING_BOOKING_V is a reporting view owned by the APPS schema in the Oracle E-Business Suite environment, and it belongs to the MSD - Demand Planning product family, which is the Demand Planning module within the Oracle Advanced Supply Chain Planning (ASCP) or Enterprise Planning suite. The view is documented as VALID in ETRM metadata for EBS 12.1.1 and 12.2.2 and carries a description of "Standalone Patch for QA115," indicating it was introduced or modified through a targeted patch rather than through a major release rollup. Functionally, the view presents booking data organized across the standard demand planning dimension hierarchies: product, geography, organization, sales representative, sales channel, and two user-defined dimensions, along with the time dimension. It exists to provide a stable, read-optimized projection of booking facts keyed by surrogate level identifiers and their associated primary-key values, which is characteristic of the Planning Server (MSD) data model used to feed demand planning engines and BI reporting layers. For the user who searched on "org_level_value_pk," this view is directly relevant because ORG_LEVEL_VALUE_PK is one of the principal columns exposed, carrying the organization dimension key value used to slice booking amounts and quantities.

Underlying Base Objects

According to the documented view text, MSD_CS_PLANNING_BOOKING_V is defined over a single referenced base object, MSD_BOOKING_DATA_CS_V, itself a view within the MSD schema family. The defining query is a simple projection: it selects PRD_LEVEL_ID, PRD_LEVEL_VALUE_PK, GEO_LEVEL_ID, GEO_LEVEL_VALUE_PK, ORG_LEVEL_ID, ORG_LEVEL_VALUE_PK, REP_LEVEL_ID, REP_LEVEL_VALUE_PK, CHN_LEVEL_ID, CHN_LEVEL_VALUE_PK, UD1_LEVEL_ID, UD1_LEVEL_VALUE_PK, UD2_LEVEL_ID, UD2_LEVEL_VALUE_PK, TIME_LEVEL_ID, BOOKED_DATE, AMOUNT, and QUANTITY from that base view. Because the base object is a view rather than a physical table, the true lineage continues down to the MSD booking fact and dimension tables beneath MSD_BOOKING_DATA_CS_V; however, the ETRM metadata documents only the immediate reference. The relationship is therefore one-to-one at the row level: no join, filter, or aggregation is applied in MSD_CS_PLANNING_BOOKING_V, making it a pass-through reporting facade that standardizes column exposure for downstream consumers. Note that the documented column list also includes END_DATE, while the view text shows BOOKED_DATE; the column listing may reflect a later revision of the view definition.

Key Columns

The view exposes paired identifier columns for each planning dimension, where the *_LEVEL_ID column identifies which hierarchy level is being referenced and the *_LEVEL_VALUE_PK column holds the surrogate primary key of the specific dimension member at that level. For the organization dimension, ORG_LEVEL_ID and ORG_LEVEL_VALUE_PK serve this purpose, allowing a query to determine both the level and the specific organization member associated with a booking record. Parallel pairs exist for product (PRD), geography (GEO), sales representative (REP), sales channel (CHN), and the two user-defined dimensions (UD1, UD2). TIME_LEVEL_ID and BOOKED_DATE anchor the booking in time. AMOUNT and QUANTITY provide the numeric measures. One documented inconsistency should be noted: the columns listing shows CHN_LEVL_VALUE_PK (a typographical variant) whereas the view text correctly shows CHN_LEVEL_VALUE_PK, and the listing includes END_DATE in addition to BOOKED_DATE. The ten level-identifier columns are typically resolved against MSD level metadata tables to retrieve level names and dimensionality.

Common Use Cases and Queries

• Organization-level booking analysis. Filter or group by ORG_LEVEL_VALUE_PK to aggregate bookings for a particular organization hierarchy member:
  SELECT ORG_LEVEL_VALUE_PK, SUM(AMOUNT), SUM(QUANTITY) FROM APPS.MSD_CS_PLANNING_BOOKING_V GROUP BY ORG_LEVEL_VALUE_PK;
• Level discovery. Inspect ORG_LEVEL_ID alongside ORG_LEVEL_VALUE_PK to determine which organization hierarchy level a booking row references before joining to dimension tables.
• Cross-dimensional reporting. Combine product, geography, and organization keys for multi-dimensional booking reports consumed by BI Publisher or custom concurrent programs.
• Time-series booking trends. Use BOOKED_DATE with TIME_LEVEL_ID to trend AMOUNT and QUANTITY over planning periods.
• Downstream integration. Because it is a pass-through over MSD_BOOKING_DATA_CS_V, the view provides a controlled interface for external planning extracts while insulating consumers from changes to the base view.