Search Results month_end_date

Overview

GMP_SR_MFG_TIME_V is a view owned by the APPS schema within the Oracle E-Business Suite Process Manufacturing (GMP) module, specifically associated with Process Planning. As documented in the ETRM metadata for release 12.2.2, the object carries a VALID status, meaning Oracle maintains it as part of the shipped application dictionary. Its name and column set indicate that it is intended to expose manufacturing calendar time dimensions — years, quarters, months, weeks, and days — for use in planning, scheduling, and reporting contexts.

The presence of the QUARTER_START_DATE column, and the search term "quarter_start_date" that surfaced this object, confirms the view is designed to supply calendar-bucketed date attributes. Because it is defined as a view rather than a table, consumers interact with it through standard SQL and through Oracle EBS reporting tools such as Oracle Reports, BI Publisher, and Discoverer without touching physical storage directly.

Underlying Base Objects

The documented view text defines the object strictly over SYS.DUAL:

SELECT NULL CALENDAR_CODE, TO_NUMBER(NULL) SEQ_NUM, NULL YEAR, ...
FROM SYS.DUAL
WHERE 1 <> 1

The predicate WHERE 1 <> 1 is always false, so the view never returns rows. This is a deliberate "stub" construct. Its columns are defined with explicit TO_NUMBER(NULL) and TO_DATE(NULL) casts, which fixes each column's datatype so that dependent objects, reports, and integration interfaces can be compiled and validated against a stable structure even when no calendar data is populated. In practice, customization teams typically replace this stub with a real query against the GMP calendar tables (such as the manufacturing calendar definitions that hold year, quarter, month, week, and day hierarchies) so that the same column contract returns live time-dimension rows.

Key Columns

• CALENDAR_CODE — Identifies the manufacturing calendar to which the row belongs.
• SEQ_NUM — Numeric ordering key used to sequence time periods.
• YEAR, YEAR_DESCRIPTION, YEAR_START_DATE, YEAR_END_DATE — The highest-level period grouping and its bounds.
• QUARTER, QUARTER_DESCRIPTION, QUARTER_START_DATE, QUARTER_END_DATE — Quarterly bucketing; QUARTER_START_DATE is the column most relevant to fiscal-quarter reporting and is the attribute most commonly searched for.
• MONTH, MONTH_DESCRIPTION, MONTH_START_DATE, MONTH_END_DATE — Monthly period attributes.
• WEEK, WEEK_DESCRIPTION, WEEK_START_DATE, WEEK_END_DATE — Weekly period attributes, common in production scheduling.
• DAY, DAY_DESCRIPTION — The lowest-granularity period attributes.

All date-typed columns are cast with TO_DATE(NULL), and numeric columns with TO_NUMBER(NULL), ensuring consistent datatypes across the view's column contract.

Common Use Cases and Queries

The view is typically consumed by planning reports that need to aggregate manufacturing activity by quarter, month, or week, and by integrations that require a normalized calendar dimension. A representative query retrieving quarterly boundaries might be:

SELECT calendar_code,
       quarter,
       quarter_start_date,
       quarter_end_date
FROM   apps.gmp_sr_mfg_time_v
WHERE  quarter_start_date IS NOT NULL
ORDER  BY calendar_code, quarter_start_date;

Because the shipped definition is a no-row stub, running this query against an un-customized instance returns zero rows. This behaviour is expected and serves as validation that the object resolves. Once the application's calendar data is wired into the view (or a site-specific replacement view is created), the same query returns real fiscal-period rows suitable for period-over-period reporting, forecasting, and schedule alignment in Process Planning.