Search Results quarter_num

Overview

AMW_GL_PERIODS_V is a reporting view owned by the APPS schema within the AMW – Internal Controls Manager product family. Its documented purpose is to store and present information about General Ledger periods, exposing the calendar structure, date ranges, and period attributes that Internal Controls Manager relies upon when identifying the accounting periods in scope for control testing, certification, and sign-off activities. The view is registered as VALID and functions strictly as a read-only projection over the General Ledger period definitions; it does not store data of its own. Because AMW operates on a calendar-by-calendar basis, the view deliberately restricts its result set to a single period set name, resolving that name dynamically at runtime. This design means the view behaves as a filtered, AMW-scoped lens on the underlying GL period data rather than a mirror of all calendars defined in the instance. For reporting and integration purposes, the view supplies a stable, product-specific interface that shields consumers from needing to know the AMW calendar profile value or the full structure of the underlying GL views.

Underlying Base Objects

The documented metadata for AMW_GL_PERIODS_V identifies no referenced base objects directly, but the view definition itself names GL_PERIODS_V as its source. GL_PERIODS_V is the standard Oracle General Ledger view over GL_PERIODS and the associated calendar tables, and it supplies all thirteen columns projected by AMW_GL_PERIODS_V without transformation. The governing filter is WHERE PERIOD_SET_NAME = FND_PROFILE.VALUE('AMW_CALENDAR'). This clause restricts output to the accounting calendar assigned to the AMW_CALENDAR profile option at the site, application, or responsibility level in which the query executes. Consequently, two sessions resolving different profile values can legitimately see different rows from the same view, and a session with no AMW_CALENDAR value set will return no rows. Implementers should treat the AMW_CALENDAR profile option as a prerequisite configuration item for any report or concurrent program built on this view, and should be aware that no DDL dependencies beyond GL_PERIODS_V are documented in the ETRM repository.

Key Columns

• PERIOD_NAME – The user-facing period identifier (for example, JAN-24); typically the primary lookup key in AMW reporting.
• PERIOD_SET_NAME – The accounting calendar name; always equal to the AMW_CALENDAR profile value for rows returned by this view.
• START_DATE / END_DATE – The effective date boundaries of the period, used for date-range logic in control testing and evidence collection.
• PERIOD_TYPE / USER_PERIOD_TYPE – The system and user-defined period classifications, such as Month or Quarter.
• PERIOD_YEAR / PERIOD_NUM / QUARTER_NUM – Numeric positioning attributes enabling chronological sorting and fiscal-year aggregation.
• ENTERED_PERIOD_NAME – The period in which an entry is recorded, which may differ from the natural period in adjustment scenarios.
• ADJUSTMENT_PERIOD_FLAG – The flag matching the user's search term; indicates whether the row represents an adjustment period rather than a standard accounting period. This column is central to filtering out or isolating adjustment periods in reconciliation and close-related control reports.
• NUMBER_PER_FISCAL_YEAR – The count of periods in the fiscal year, useful for validation and completeness checks.
• DESCRIPTION – The descriptive text attached to the period definition.

Common Use Cases and Queries

The view is most commonly used in AMW control and certification reporting to enumerate the open or relevant periods for a given calendar, and to distinguish standard periods from adjustment periods. A frequent requirement is to exclude adjustment periods from period-level control counts, since adjustment periods follow different close rules. A representative query is:

SELECT period_name, start_date, end_date, period_year, adjustment_period_flag
FROM   apps.amw_gl_periods_v
WHERE  adjustment_period_flag = 'N'
ORDER BY period_year, period_num;

Conversely, auditors may need to isolate adjustment periods specifically:

SELECT period_name, entered_period_name, period_num
FROM   apps.amw_gl_periods_v
WHERE  adjustment_period_flag = 'Y';

Other common patterns include date-range joins to transactional tables using START_DATE and END_DATE, and lookups that resolve a period name to its fiscal year and quarter for dashboard aggregation. When building such queries, always qualify the view with the APPS schema, confirm that the AMW_CALENDAR profile option is set for the executing responsibility, and account for the possibility of zero rows when the profile is unset.