Search Results entered_period_name

Overview

The view BIM_DIMV_PERIODS is a Marketing Intelligence (BIM) database object that exposes the accounting periods defined in the Oracle General Ledger GL_PERIODS table for a single, user-selected accounting calendar. It is a dimension-style, read-only view whose purpose is to provide BI and CRM reporting components with a clean, filtered list of periods belonging to the calendar an implementation has designated as its reporting calendar.

The critical characteristic of the view is that it deliberately excludes adjustment periods. Its defining predicate is WHERE ADJUSTMENT_PERIOD_FLAG = 'N', meaning that only standard (non-adjustment) periods are surfaced to consumers. This makes the view the appropriate source for period-to-date analytics, trend reporting, and any comparison that should reflect the ordinary accounting flow rather than closing or audit adjustment periods.

The view is scoped to PERIOD_SET_NAME = JTF_BIS_UTIL.PROFILEVALUE('CRMBIS:PERIOD_SET_NAME'), so it dynamically resolves the calendar through the CRM/BIS profile option at query time. This design allows one deployment of the view to serve a specific enabled calendar without hard-coding the period set name.

Underlying Base Objects

The view is defined solely over the General Ledger base table GL_PERIODS. The ETRM metadata records no other referenced base objects, and the view text confirms that all projected columns trace back to GL_PERIODS. There are therefore no joins, aggregations, or lookups in the definition. The ETRM documentation notes the object is "Not implemented in this database," indicating that in the documented environment the view was not present; the definition itself is captured for reference. The only external dependency is the JTF_BIS_UTIL.PROFILEVALUE function call used to resolve the CRMBIS:PERIOD_SET_NAME profile, which supplies the calendar filter value at runtime.

Key Columns

• PERIOD_SET_NAME — The accounting calendar (period set) the row belongs to; filtered to the profile-driven calendar.
• PERIOD_NAME — The period identifier, e.g., a month name.
• PERIOD_TYPE — The classification of the period within the calendar, such as month, quarter, or year.
• PERIOD_NUM — The ordinal position of the period within its year.
• QUARTER_NUM — The fiscal quarter to which the period belongs.
• PERIOD_YEAR — The fiscal year of the period.
• START_DATE / END_DATE — The effective date boundaries of the period.
• ENTERED_PERIOD_NAME — The period name used when the period is referenced for data entry.
• DESCRIPTION — Descriptive text associated with the period.
• ADJUSTMENT_PERIOD_FLAG — The flag indicating whether the period is an adjustment period. Because the view filters on 'N', this column always returns N.

Common Use Cases and Queries

The view is typically used to populate period selection lists, date-keyed dimensions, and reporting prompts within Marketing Intelligence, ensuring that adjustment periods never appear as selectable reporting buckets. A typical projection follows the view's own column list:

• Listing all standard periods for the designated calendar:
  SELECT PERIOD_NAME, PERIOD_TYPE, PERIOD_YEAR, START_DATE, END_DATE FROM BIM_DIMV_PERIODS ORDER BY START_DATE;
• Restricting to a specific fiscal year:
  SELECT PERIOD_NAME, QUARTER_NUM FROM BIM_DIMV_PERIODS WHERE PERIOD_YEAR = 2013;
• Determining the current period by date:
  SELECT PERIOD_NAME FROM BIM_DIMV_PERIODS WHERE TRUNC(SYSDATE) BETWEEN START_DATE AND END_DATE;

Because the view resolves its calendar through the CRMBIS:PERIOD_SET_NAME profile, any change to that profile setting alters which periods the view returns. This behavior is important when troubleshooting reports that appear to reference the wrong calendar, and any analysis of the adjustment_period_flag column should note that the view will only ever return 'N' values by design.