Results for “date_ineffective”

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

Overview

FA_ADD_WARRANTIES is an Oracle E-Business Suite table owned by the FA schema and delivered under the OFA (Assets) product module. It stores warranty information associated with fixed assets, linking each warranty definition to the specific asset to which it applies and capturing the effective date range over which that warranty relationship is active. The table resides in the core Fixed Assets data model and is populated during asset additions processing and subsequent warranty maintenance.

Under a heuristic Data Vault classification derived from its foreign key structure, FA_ADD_WARRANTIES is best modeled as a link entity. It does not hold a self-contained descriptive business key of its own; instead it resolves the many-to-many relationship between warranty definitions and assets, with DATE_EFFECTIVE and DATE_INEFFECTIVE providing the effectivity semantics typical of a link with temporal attributes. This classification is a modeling suggestion only and should be validated against the actual column semantics and population logic used in a given implementation.

Key Information Stored

The documented physical schema in ETRM 12.2.2 contains nine columns. The most significant columns fall into three groups:

• WARRANTY_ID — identifies the warranty definition. This column participates in the composite primary key and forms the foreign key reference to FA_WARRANTIES.
• ASSET_ID — identifies the fixed asset to which the warranty applies. It is part of the composite primary key and references FA_ADDITIONS_B.
• DATE_EFFECTIVE — the date from which the warranty association becomes effective for the asset; the third component of the composite primary key.
• DATE_INEFFECTIVE — the date on which the warranty association ceases to apply, supporting historical tracking of warranty coverage.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN — standard Oracle EBS WHO columns that capture audit and concurrency information for each row.

The primary key is defined by the constraint FA_ADD_WARRANTIES_PK over (WARRANTY_ID, ASSET_ID, DATE_EFFECTIVE). A unique index, FA_ADD_WARRANTIES_U1, covers the same three columns and serves as the business-key candidate that enforces one active warranty-to-asset association per effective date. There is no single-column surrogate key; the composite key itself performs that role.

Common Use Cases and Queries

Typical applications of this table include asset warranty reporting, audit of warranty coverage periods, and reconciliation between warranty definitions and the assets they cover. A common join pattern retrieves the asset number alongside the warranty description:

• SELECT w.warranty_id, a.asset_number, w.date_effective, w.date_ineffective FROM fa.fa_add_warranties w JOIN fa.fa_additions_b a ON a.asset_id = w.asset_id JOIN fa.fa_warranties fw ON fw.warranty_id = w.warranty_id;
• Filtering on SYSDATE BETWEEN DATE_EFFECTIVE AND NVL(DATE_INEFFECTIVE, SYSDATE) yields currently active warranties for an asset.
• Reporting on expiring coverage uses DATE_INEFFECTIVE as the driver column, grouped by ASSET_ID.

Because the table is a pure link with attribute-level effectivity, extracts for downstream maintenance or insurance systems frequently select by ASSET_ID and resolve warranty attributes from FA_WARRANTIES rather than storing descriptive text here.

Related Objects

• FA_WARRANTIES — the warranty master table; joined on FA_ADD_WARRANTIES.WARRANTY_ID = FA_WARRANTIES.WARRANTY_ID.
• FA_ADDITIONS_B — the asset additions base table; joined on FA_ADD_WARRANTIES.ASSET_ID = FA_ADDITIONS_B.ASSET_ID.
• FA_ADD_WARRANTIES_PK — the primary key constraint enforcing uniqueness of (WARRANTY_ID, ASSET_ID, DATE_EFFECTIVE).
• FA_ADD_WARRANTIES_U1 — the unique index backing the business-key candidate.
• Asset inquiry and warranty maintenance forms within the OFA module depend on this table for coverage display.