Results for “rhx_dp_l_weeks_v”

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

Overview

RHX_DP_L_WEEKS_V is a reporting view shipped within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments under the MRP — Master Scheduling/MRP product family. The object is classified in the ETRM metadata as "Retrofitted," indicating that it was introduced or re-engineered to support a specific downstream reporting or integration requirement rather than being a core transactional object. Its name follows the RHX_DP naming convention associated with Oracle Demand Planning data structures, where the "DP" segment signals a Demand Planning lineage and the "_V" suffix confirms its role as a view rather than a stored table.

Functionally, RHX_DP_L_WEEKS_V exposes a horizontally denormalized, week-grain slice of a planning calendar. It joins calendar identifiers to computed bucket labels, week start and end dates, exception set references, and sequential numbering. Because the view is read-only and derived, it is intended for reporting, extraction, and analytical consumption rather than for transaction processing. In EBS reporting architectures, such views typically feed Discoverer workbooks, BI Publisher extract definitions, or custom SQL used in Demand Planning and Master Scheduling diagnostics.

Underlying Base Objects

The ETRM metadata documents a single referenced base object: RHX_DP_TIMES. The view is defined as a SELECT DISTINCT projection over this times dimension, applying an identity filter (WHERE 1=1) that serves as a placeholder for runtime predicate substitution. No other base tables are documented, and the view carries no additional joins, aggregations, or set operations.

RHX_DP_TIMES contains the physical calendar rows — calendar code, week, month, quarter, year, sequence number, and start/end dates — from which the view derives its output. The key structural difference is that the view synthesizes composite labels (for example, 'W12_M3_Q1_2024') and strips duplicates, presenting a clean dimensional set for downstream consumers. Because the metadata records the view as "Not implemented in this database," it must be validated against the target instance before being referenced in production SQL.

Key Columns

• CALENDAR_CODE — Identifies the planning calendar the bucket belongs to; the primary partitioning key for any query.
• WEEK — The week number within the calendar, used to derive the composite week label exposed by the view.
• START_DATE / END_DATE — The week boundary dates. In the view text these are aliased from RDT.WEEK_START_DATE and RDT.WEEK_END_DATE, providing the temporal window for each bucket.
• EXCEPTION_SET_ID — Foreign reference to the exception set governing how the week is treated during planning runs.
• MONTH — The month number, concatenated with quarter and year to form the second generated label in the select list.
• SEQ_NUM — A sequential ordering value used to sort or rank buckets chronologically.

Note that two columns in the select list are expressions rather than stored attributes: the week label ('W'||WEEK||'_M'||MONTH||'_Q'||QUARTER||'_'||YEAR) and the month label ('M'||MONTH||'_Q'||QUARTER||'_'||YEAR). Consumers should reference these by position or alias.

Common Use Cases and Queries

Typical uses include building time-phased planning reports, aligning demand and supply buckets to a common calendar, and populating extract tables for Demand Planning uploads. A common pattern retrieves all weeks for a given calendar ordered chronologically:

SELECT CALENDAR_CODE, START_DATE, END_DATE, SEQ_NUM
FROM   RHX_DP_L_WEEKS_V
WHERE  CALENDAR_CODE = :p_calendar
ORDER BY SEQ_NUM;

A second pattern isolates a single planning period by date range, useful for period-over-period comparisons:

SELECT CALENDAR_CODE, WEEK, START_DATE, END_DATE
FROM   RHX_DP_L_WEEKS_V
WHERE  START_DATE >= :p_from_date
AND    END_DATE   <= :p_to_date;

Before deploying either query, confirm view availability with a metadata lookup against ALL_VIEWS, since the ETRM record indicates the object is not implemented in every database.