Search Results working_day




Overview
Explore in AI Chat

Overview

APPS.MSD_TIME_V is a reporting view in Oracle E-Business Suite that exposes the contents of the MSD_TIME table in a stable, presentation-ready form. It belongs to the ETRM (Enterprise Territory and Resource Management) schema owned by APPS. The view flattens the hierarchical calendar structure into a single denormalized row per day, carrying the full context of the year, quarter, month, and week that contains that day. Because it is defined over the MSD_TIME synonym, it presents the identical time-dimension data used by ETRM scheduling and territory engines, but with a deterministic ordering and a null-handling refinement on the working-day indicator.

The searched term "working_day" maps directly to the view's WORKING_DAY column. The view re-expresses this column through NVL(WORKING_DAY, 'YES'), so consumers always receive an explicit working-day value rather than a null. This makes the view the preferred read interface for any logic that must decide whether a given day is a business day.

Underlying Base Objects

The view is defined exclusively over MSD_TIME, documented as a SYNONYM. Its text is an inline view that selects from MSD_TIME, ordering by CALENDAR_CODE and DAY, and then projects an outer query that adds ROWNUM and the NVL-normalized working-day value. The two-tier structure is significant: the inner query imposes ordering, and the outer query assigns a sequential row number, giving each day a stable ordinal within its calendar. No other base objects are referenced in the documented definition, so the view inherits MSD_TIME's grain — one row per calendar day per calendar code.

Key Columns

Common Use Cases and Queries

The view is typically used to drive date filtering, working-day calculations, and calendar-key lookups when joining ETRM fact data to a time dimension. A common pattern retrieves only working days within a month boundaries:

  • Filtering business days: SELECT DAY, DAY_DESCRIPTION FROM APPS.MSD_TIME_V WHERE CALENDAR_CODE = :code AND WORKING_DAY = 'YES' AND DAY BETWEEN :start AND :end ORDER BY DAY;
  • Resolving a day to its month and quarter keys for aggregation: select MONTH, QUARTER, YEAR for a given DAY and calendar.
  • Populating a time-dimension lookup in downstream reporting, using ROWNUM to generate surrogate sequence values.
  • Cross-checking calendar coverage, e.g. counting days per WORKING_DAY flag per month.

All practical use of this view should filter by CALENDAR_CODE to avoid mixing rows across calendars, since the inner query orders by calendar code and day but does not restrict the result set.