Results for “to_date_placed_in_service”

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

Overview

The FA_MAINT_SCHEDULE_HDR table, owned by the FA schema within the Oracle E-Business Suite Assets (OFA) module, stores the header information for maintenance scheduling requests submitted against fixed assets. It acts as the control record that defines the scope and parameters of a maintenance-related request, capturing the qualifying criteria (book, asset number range, service date range, category, and location) together with the currency and the concurrent request that ultimately executed the process. Because it governs request-level metadata rather than individual asset attributes, it functions as a request definition table that other processes and reports consume to reconstruct what was scheduled, for which population of assets, and under which operating parameters.

From a modeling perspective, the ETRM metadata's heuristic Data Vault classification for this object is link. This suggestion is consistent with the table's structure: it carries a surrogate identifier plus a set of foreign keys referencing independent business entities (book, assets, category, location, currency, and concurrent request), making it a natural association record between those hubs rather than a pure descriptive satellite.

Key Information Stored

The documented physical schema contains 19 columns, of which the following are the most significant:

• SCHEDULE_ID — the primary key (FA_MAINT_SCHEDULE_HDR_PK). It is also the sole unique index documented as FA_MAINT_SCHEDULE_HDR_U1, so it is the only documented business-key candidate; no separate natural key is exposed in the metadata.
• BOOK_TYPE_CODE — the depreciation book under which the request applies, referencing FA_BOOK_CONTROLS.
• FROM_ASSET_NUMBER and TO_ASSET_NUMBER — the inclusive asset number range bounding the request, both referencing FA_ADDITIONS_B.
• FROM_DATE_PLACED_IN_SERVICE and TO_DATE_PLACED_IN_SERVICE — the range of placed-in-service dates used to qualify the asset population.
• START_DATE and END_DATE — the effective window of the maintenance schedule request.
• CATEGORY_ID — the asset category qualifier, referencing FA_CATEGORIES_B.
• LOCATION_ID — the location qualifier, referencing FA_LOCATIONS.
• ASSET_KEY_ID — the asset key identifier associated with the selection.
• CURRENCY_CODE — the reporting currency used in the request, referencing FND_CURRENCIES.
• CONCURRENT_REQUEST_ID — the concurrent request that processed the schedule, referencing FND_CONCURRENT_REQUESTS.
• STATUS — the processing or submission state of the request.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, and LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical scenarios include auditing maintenance scheduling activity, reconciling which concurrent request produced a given schedule, and reporting the qualifying parameters under which asset maintenance work was requested.

Listing recent schedule requests by book and status:

• SELECT schedule_id, book_type_code, from_asset_number, to_asset_number, status, start_date, end_date FROM fa.fa_maint_schedule_hdr WHERE book_type_code = :book AND status = :status ORDER BY creation_date DESC;

Joining to the concurrent request to trace execution:

• SELECT h.schedule_id, r.request_id, r.phase_code, r.status_code FROM fa.fa_maint_schedule_hdr h, fnd_concurrent_requests r WHERE h.concurrent_request_id = r.request_id;

Resolving descriptive attributes for reporting:

• SELECT h.schedule_id, b.book_type_code, c.category_name, l.location_name, h.currency_code FROM fa.fa_maint_schedule_hdr h, fa_book_controls b, fa_categories_b c, fa_locations l WHERE h.book_type_code = b.book_type_code AND h.category_id = c.category_id AND h.location_id = l.location_id;

Related Objects

• FA_BOOK_CONTROLS — joined on BOOK_TYPE_CODE; supplies book-level depreciation and calendar context.
• FA_ADDITIONS_B — joined on FROM_ASSET_NUMBER and TO_ASSET_NUMBER; defines the asset range and descriptive attributes.
• FA_CATEGORIES_B — joined on CATEGORY_ID; provides asset category definition.
• FA_LOCATIONS — joined on LOCATION_ID; supplies the physical location of qualifying assets.
• FND_CURRENCIES — joined on CURRENCY_CODE; resolves currency descriptions.
• FND_CONCURRENT_REQUESTS — joined on CONCURRENT_REQUEST_ID; links the schedule to its executing concurrent process.

No child tables, views, or public APIs for FA_MAINT_SCHEDULE_HDR are documented in the supplied ETRM metadata; the relationships above are those evidenced by the foreign keys and primary key constraints.