Results for “fa_locations”

50+ results




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

Overview

FA_LOCATIONS is the Oracle Assets (OFA) master table that stores location flexfield segment value combinations. Each row represents a valid, uniquely identifiable location that can be assigned to an asset, a distribution line, a mass transaction, or a maintenance schedule. Physically, the table resides in the FA schema and is documented in ETRM 12.2.2 with 31 columns. Because it serves as the reference point for a wide range of child tables across Assets, and is also referenced by non-FA schemas such as CSI and CUN, the table functions as a central reference hub. Under the heuristic Data Vault classification mined from the foreign key structure, FA_LOCATIONS is classified as hub-leaning — a modeling suggestion in which LOCATION_ID acts as the durable business key that links many dependent satellites and links.

Key Information Stored

The table's surrogate primary key is LOCATION_ID, enforced by FA_LOCATIONS_PK and also exposed through the unique index FA_LOCATIONS_U1, which makes it the business-key candidate. The descriptive identity of each location is captured in the location flexfield segments SEGMENT1 through SEGMENT7, whose concatenated values form the user-visible location name. Control columns include SUMMARY_FLAG, which distinguishes summary (parent/rollup) locations from detail locations, and ENABLED_FLAG, which governs whether a location is selectable in transaction and inquiry windows. Effective dating is handled by START_DATE_ACTIVE and END_DATE_ACTIVE, allowing historical locations to be retained while preventing new assignments after deactivation.

Standard EBS audit columns are present: LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. The table also carries a flexible attribute set — ATTRIBUTE_CATEGORY_CODE and ATTRIBUTE1 through ATTRIBUTE15 — used for descriptive flexfield (DFF) data and client-specific extensions. The segment and attribute columns together provide the mechanism by which customers model their own location hierarchies without schema changes.

Common Use Cases and Queries

Typical reporting retrieves active locations for asset assignment, validates location references before mass transactions, and reconciles distribution defaults against valid locations. A representative query joining locations to the distribution defaults:

  • List enabled detail locations: SELECT LOCATION_ID, SEGMENT1, SEGMENT2, SEGMENT3 FROM FA.FA_LOCATIONS WHERE ENABLED_FLAG = 'Y' AND SUMMARY_FLAG = 'N';
  • Join locations to distribution defaults: SELECT d.LOCATION_ID, l.SEGMENT1 FROM FA.FA_DISTRIBUTION_DEFAULTS d, FA.FA_LOCATIONS l WHERE d.LOCATION_ID = l.LOCATION_ID;
  • Trace mass transfers: join FA_MASS_TRANSFERS.FROM_LOCATION_ID and TO_LOCATION_ID back to FA_LOCATIONS.LOCATION_ID.

Because the table is referenced by both FA and non-FA modules, it is also used to verify cross-module consistency, for example reconciling instances stored in CSI against their Assets locations.

Related Objects

The table is referenced by a large set of dependent objects. The most significant, with their join columns, include:

Together these relationships confirm the table's role as the shared location hub for Oracle Assets and its adjacent modules.