Search Results fa_conventions




Overview
Explore in AI Chat

Overview

FA_CONVENTIONS is a reference configuration table in the Oracle Assets (OFA) module, owned by the FA schema. It stores the detailed prorate convention definitions that govern how depreciation is calculated for the period in which an asset is placed in service or retired. In Oracle EBS, a prorate convention determines whether depreciation is charged for a full period, a partial period, or no period at all, based on the transaction date relative to period boundaries. This table supplies the date logic that drives that determination.

The object is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2. Its 9-column physical schema has been cataloged in ETRM 12.2.2. The heuristic Data Vault classification mined from the FK structure is satellite-leaning: the table primarily holds descriptive, time-versioned attributes attached to a parent convention type, rather than acting as an independent transaction hub. From a modeling perspective, it may be treated as a satellite of FA_CONVENTION_TYPES.

Key Information Stored

The table's content is deliberately narrow: it holds the effective-dated rules for each prorate convention. Its most significant columns are:

  • PRORATE_CONVENTION_CODE — the business identifier for the convention (e.g., the code users select when defining a book or asset category). It forms part of the primary key.
  • START_DATE — the effective-from date for a given version of the convention definition. Combined with the code, it forms the primary key and allows conventions to change over time without losing history.
  • END_DATE — the effective-to date, closing out the version. It also participates in the unique index, so no two versions of the same convention can overlap in date range.
  • PRORATE_DATE — the rule that maps a transaction date to the depreciation proration behavior; this is the operative column that drives how much depreciation is taken in the acquisition or retirement period.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN track who inserted and last modified each row and when.

The documented primary key, FA_CONVENTIONS_PK, is the composite (PRORATE_CONVENTION_CODE, START_DATE). The business-key candidate is exposed through the unique index FA_CONVENTIONS_U1, defined as (PRORATE_CONVENTION_CODE, START_DATE, END_DATE). There is no single surrogate column in the documented schema; the composite key serves that purpose.

Common Use Cases and Queries

Typical usage centers on verifying which conventions exist, which are currently effective, and what proration behavior they apply. A common query retrieves currently active conventions:

  • SELECT prorate_convention_code, start_date, end_date, prorate_date FROM fa_conventions WHERE TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, TRUNC(SYSDATE));

A second pattern joins the convention to its type to present a complete reference list for a configuration report:

  • SELECT c.prorate_convention_code, c.prorate_date, t.convention_type FROM fa_conventions c, fa_convention_types t WHERE c.prorate_convention_code = t.prorate_convention_code;

Reporting use cases include auditing set-up books whose default convention has been end-dated, validating that an asset category points to an active convention, and reconciling depreciation discrepancies traced to a proration rule change. Because the table is small and configuration-oriented, it is typically joined rather than queried standalone.

Related Objects

The documented foreign key defines the principal relationship: FA_CONVENTIONS.PRORATE_CONVENTION_CODE references FA_CONVENTION_TYPES, making the convention type the parent of this detail table. Related objects that consume the convention code include the asset category and book assignment tables in the OFA module, which reference the convention when defining depreciation terms. The primary key FA_CONVENTIONS_PK and unique index FA_CONVENTIONS_U1 enforce integrity for any dependent table joining on PRORATE_CONVENTION_CODE. Application logic driven by this table surfaces primarily through the Assets depreciation programs, which read the PRORATE_DATE rule when calculating period depreciation, and through the Oracle Assets setup forms where convention definitions are maintained.