Results for “period_close_date”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FAFV_ACCT_PRDS is a read-only Oracle E-Business Suite view owned by the APPS schema and registered against the Oracle Assets (OFA) product. It is classified in ETRM as a retrofitted object, indicating it exists primarily to preserve backward compatibility with earlier forms, reports, or custom extensions that referenced the FA_ACCT_PRDS naming convention from legacy Assets releases. The view functions as a thin projection layer that surfaces accounting period attributes drawn from the depreciation calendar maintained in Oracle Assets.

Because the view declaration terminates with WITH READ ONLY, it cannot be used for DML. Its role is strictly that of a reporting and integration surface, allowing external tools, custom concurrent programs, and ad hoc SQL to retrieve period definitions — including the period close date — without querying the underlying table directly. For users searching on period_close_date, this view is the standard access point within the Assets data model, exposing both the depreciation period close date and the corresponding calendar period close date side by side.

Underlying Base Objects

ETRM documents a single referenced base object for this view: FA_DEPRN_PERIODS, accessed through a synonym in the APPS schema. The view text selects from FA_DEPRN_PERIODS without joins, filters, or aggregation, and applies WITH READ ONLY as the only constraint. FA_DEPRN_PERIODS is the core Assets table that stores one row for each accounting period per depreciation book, recording when each period opens and closes together with its calendar-year and period-number positioning. Because the relationship is a direct one-to-one projection, every row and column available in the view mirrors a corresponding row in the base table, subject only to the column list projected by the view definition. The documented column list includes PERIOD_NUMBER in the metadata header, while the view text lists PERIOD_NUM; consumers should confirm the actual column name in their environment with DESC APPS.FAFV_ACCT_PRDS.

Key Columns

• PERIOD_NAME — The accounting period identifier, such as JAN-24, in the format defined by the Assets calendar.
• PERIOD_COUNTER — The internal numeric key for the period; used in joins to FA_DEPRN_PERIODS and other Assets tables.
• FISCAL_YEAR — The fiscal year to which the period belongs.
• PERIOD_NUM / PERIOD_NUMBER — The ordinal position of the period within the fiscal year.
• PERIOD_OPEN_DATE — The date on which the depreciation period becomes open for transaction entry.
• PERIOD_CLOSE_DATE — The depreciation period close date; the primary column of interest for users searching this term, and the date after which the period is normally closed to further depreciation activity.
• CALENDAR_PERIOD_OPEN_DATE — The corresponding open date in the general ledger calendar, which may differ from the depreciation period open date.
• CALENDAR_PERIOD_CLOSE_DATE — The corresponding general ledger calendar close date.
• BOOK_TYPE_CODE — The depreciation book that the period row belongs to, distinguishing rows when multiple books share the same calendar and period names.

Common Use Cases and Queries

A frequent requirement is to determine the close date of the current or most recent depreciation period for a specific book. The following query returns the latest closed period for a given BOOK_TYPE_CODE:

• SELECT period_name, fiscal_year, period_close_date FROM apps.fafv_acct_prds WHERE book_type_code = 'CORP' AND period_close_date <= SYSDATE ORDER BY period_close_date DESC;

To compare the depreciation close date against the GL calendar close date — useful when diagnosing reconciliation differences between Assets and the general ledger — the view exposes both values on the same row:

• SELECT period_name, period_close_date, calendar_period_close_date FROM apps.fafv_acct_prds WHERE book_type_code = 'CORP' AND fiscal_year = 2024;

Custom reports and interfaces that need to validate whether a transaction falls within an open period also use this view to build period-validity lookups keyed on PERIOD_NAME and BOOK_TYPE_CODE. Because the view is read only and unindexed beyond the base table's own indexes, queries should filter by BOOK_TYPE_CODE, FISCAL_YEAR, or PERIOD_COUNTER to keep execution efficient. Avoiding direct references to FA_DEPRN_PERIODS in custom code and using this view instead improves forward compatibility with Oracle Assets upgrades.