Search Results amw_calendar

Overview

APPS.AMW_GL_PERIODS_V is an Oracle E-Business Suite (EBS) reporting view owned by the Applications (APPS) schema and associated with the Enterprise Tax and Reporting Management (ETRM) product family, historically delivered under the AMW module. The view exposes General Ledger accounting period definitions, but restricts the result set to a single accounting calendar identified at runtime by the AMW_CALENDAR profile option. Its defining characteristic is the filter predicate PERIOD_SET_NAME = FND_PROFILE.Value('AMW_CALENDAR'), which causes the view to return only the periods belonging to the accounting calendar configured for the AMW/ETRM application context in the current session.

This behavior is significant for reporting and integration. Rather than requiring every consumer of period data to resolve the profile option and re-apply the same filter, the view centralizes the calendar-selection logic. In EBS 12.1.1 and 12.2.2 this pattern is common for ETRM objects: the profile option AMW_CALENDAR acts as the authoritative designation of which GL period set the tax and reporting components should use, and AMW_GL_PERIODS_V is the sanctioned access path to those periods.

Underlying Base Objects

Per the documented metadata, the view is defined solely over GL_PERIODS_V, itself a GL view over the GL_PERIODS and GL_PERIOD_SETS base tables. No other base objects are documented. Because the definition reads FROM GL_PERIODS_V WHERE PERIOD_SET_NAME = FND_PROFILE.Value('AMW_CALENDAR'), every column available in GL_PERIODS_V is projected outward unchanged; the view adds no joins, expressions, or aggregations of its own. The relationship is therefore a strict filtering projection: AMW_GL_PERIODS_V = GL_PERIODS_V restricted to the calendar named by the AMW_CALENDAR profile option. If the profile option resolves to NULL or to a period set name that does not exist, the view returns no rows.

Key Columns

• PERIOD_NAME — The accounting period identifier (for example, JAN-24) within the selected calendar.
• PERIOD_SET_NAME — The accounting calendar / period set name; in this view it always equals the AMW_CALENDAR profile value.
• START_DATE and END_DATE — The first and last calendar dates spanned by the period, used for date-range logic in tax and reporting extracts.
• PERIOD_TYPE and USER_PERIOD_TYPE — The system and user-defined period type classifications that drive period generation rules.
• PERIOD_YEAR, PERIOD_NUM, QUARTER_NUM — The fiscal year, sequential period number within the year, and quarter number, supporting chronological sequencing and period-over-period comparisons.
• ENTERED_PERIOD_NAME — The corresponding entered (as opposed to adjusted) period, relevant to adjustment-period handling.
• ADJUSTMENT_PERIOD_FLAG — Indicates whether the row represents an adjustment period.
• NUMBER_PER_FISCAL_YEAR — The count of periods defined in the fiscal year.
• DESCRIPTION — Free-form description of the period.

Common Use Cases and Queries

The view is typically used to validate whether a transaction or reporting date falls within an open or defined AMW period, to drive period-selection lists in concurrent programs, and to align ETRM extracts with the GL calendar. Because the profile option is resolved at query time, the same SQL returns different calendars depending on the session's AMW_CALENDAR setting.

Listing all periods in the configured calendar:

SELECT period_name, start_date, end_date, period_year, period_num
FROM   apps.amw_gl_periods_v
ORDER  BY period_year, period_num;

Identifying the period containing a given date:

SELECT period_name, period_year, quarter_num
FROM   apps.amw_gl_periods_v
WHERE  :p_date BETWEEN start_date AND end_date;

Excluding adjustment periods:

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

To confirm which calendar is in effect, compare the returned PERIOD_SET_NAME values against SELECT fnd_profile.value('AMW_CALENDAR') FROM dual. If no rows are returned, the profile option should be verified at the site, application, or responsibility level before the view is used as a source for ETRM period data.