Results for “fa_location_id”

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

Overview

CSI_A_LOCATIONS is a table within the CSI (Install Base) product schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to hold the mapping between an asset location and an HZ (Trading Community Architecture) location, effectively serving as the association layer that connects installed base asset location records to the corresponding party or HR location definitions. In EBS, this table acts as the bridge that allows asset location data captured in the Install Base to resolve to a canonical location entity used across Oracle's applications.

ETRM classifies this object heuristically as a link table under Data Vault modeling conventions. This classification is a modeling suggestion rather than a strictly enforced property: the table carries a surrogate primary key plus multiple foreign key references to dimension-like tables, which is characteristic of a relationship (link) artifact connecting two or more entities. The presence of both a unique business-key index and foreign key columns to FA_LOCATIONS and HR_LOCATIONS_ALL reinforces this interpretation.

Key Information Stored

The table is documented with 13 columns. The most important include:

• ASSET_LOCATION_ID — the surrogate primary key, defined by the constraint CSI_A_LOCATIONS_PK and also carried by the unique index CSI_A_LOCATIONS_U01. This is the technical identifier for each mapping row.
• FA_LOCATION_ID — foreign key to FA_LOCATIONS, anchoring the asset-side location used by Fixed Assets.
• LOCATION_ID — foreign key to HR_LOCATIONS_ALL. Documented twice in the FK list, this column holds the HR location identifier.
• LOCATION_TABLE — discriminator that, together with LOCATION_ID, forms the unique business-key candidate CSI_A_LOCATIONS_U02 (LOCATION_TABLE, LOCATION_ID). It indicates which location source the LOCATION_ID refers to.
• ACTIVE_START_DATE / ACTIVE_END_DATE — effective-dating columns that scope when a mapping is valid, enabling historical tracking of asset-to-location relationships.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, providing multi-tenant / operating unit style data segregation.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the ORM framework to detect concurrent updates.
• Standard audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

The distinction between the surrogate key (ASSET_LOCATION_ID) and the natural business-key candidates (ASSET_LOCATION_ID captured in U01, and the composite LOCATION_TABLE + LOCATION_ID in U02) is important when writing joins that must remain stable across environments.

Common Use Cases and Queries

The principal use case is resolving an installed base asset location to its HZ or HR location for reporting, party-relationship analysis, or integration with Fixed Assets. A typical query joins CSI_A_LOCATIONS to HR_LOCATIONS_ALL on LOCATION_ID and to FA_LOCATIONS on FA_LOCATION_ID:

• Locating all active mappings effective on a given date: filter ACTIVE_START_DATE <= :p_date and (ACTIVE_END_DATE IS NULL OR ACTIVE_END_DATE >= :p_date).
• Reporting by security group: constrain on SECURITY_GROUP_ID to respect data access rules.
• Reconciling Fixed Assets locations against Install Base asset locations where the FA_LOCATION_ID does not resolve to an active row.
• Driving downstream interface loads — for example, CSI_I_ASSET_TXN_TEMP and OKL_LINES_INTERFACE both reference ASSET_LOCATION_ID, so extracts commonly select ASSET_LOCATION_ID for these consumers.

Because the table is effective-dated, reports should always apply the date-range predicates rather than assuming one current row per asset.

Related Objects

• FA_LOCATIONS — referenced via CSI_A_LOCATIONS.FA_LOCATION_ID.
• HR_LOCATIONS_ALL — referenced via CSI_A_LOCATIONS.LOCATION_ID (documented twice, indicating possible dual relationships).
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID.
• CSI_I_ASSET_TXN_TEMP — references CSI_A_LOCATIONS.ASSET_LOCATION_ID.
• OKL_LINES_INTERFACE — references CSI_A_LOCATIONS.ASSET_LOCATION_ID.
• CSI_A_LOCATIONS_PK / _U01 / _U02 — the primary and unique indexes defining identity and business keys.

Together these objects confirm CSI_A_LOCATIONS as the connective link between Install Base asset locations, Fixed Assets locations, HR locations, and interfaced transaction data.