Search Results csf_lf_names_pk

Overview

CSF_LF_NAMES is a core reference table in the Oracle E-Business Suite Field Service (CSF) module, holding all name information used by the Location Finder component. The Location Finder provides geospatial and address-resolution services within Field Service, enabling the identification and disambiguation of places, points of interest (POIs), and road segments. Each row in CSF_LF_NAMES represents a discrete name record that can be associated with one or more location entities through the intersection tables CSF_LF_PLACE_NAMES, CSF_LF_POI_NAMES, and CSF_LF_ROADSEGM_NAMES.

In data-vault modeling terms, the FK structure suggests that CSF_LF_NAMES behaves as a hub. Because multiple child tables reference its primary key via NAME_ID, it functions as the central anchor for name-based attributes distributed across satellite-style child tables. This classification is heuristic and should be treated as a modeling suggestion rather than an enforced architectural constraint.

Key Information Stored

The table contains 13 documented columns in the 12.2.2 schema. The most significant are:

• NAME_ID — Surrogate primary key (CSF_LF_NAMES_PK) that uniquely identifies each name record and is referenced by all child intersection tables.
• NAME — The full formatted or raw name string associated with the location entity.
• LANGUAGE_CODE — Language in which the name is expressed, supporting multilingual deployments.
• JUNCTION_NAME — Name used at road junctions or intersections.
• EXIT_NUMBER — Highway or route exit identifier when applicable.
• ROUTE_TYPE — Classification of the route (e.g., highway, street, arterial).
• PREFIX — Directional or qualifier prefix (e.g., North, Old).
• BASE_NAME — Core street or place name without prefix/suffix modifiers.
• STREET_TYPE — Type designator such as Street, Avenue, or Boulevard.
• STREET_TYPE_ATTACHED — Flag indicating whether the street type is attached to the base name.
• STREET_TYPE_BEFORE_BASE — Flag indicating whether the street type precedes the base name.
• SUFFIX — Trailing qualifier (e.g., Jr., Ext).
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, enforcing multi-tenant or organizational data segregation.

The surrogate key is NAME_ID. No separate business-key unique index is documented beyond the primary key, though NAME combined with LANGUAGE_CODE and SECURITY_GROUP_ID often serves as a de facto business identifier in practice.

Common Use Cases and Queries

Typical usage centers on resolving names for places, POIs, and road segments during address validation, routing, and location-based dispatching. A common query joins CSF_LF_NAMES to one of its child tables:

• Retrieving all names for a specific place: SELECT n.NAME FROM CSF_LF_NAMES n, CSF_LF_PLACE_NAMES p WHERE n.NAME_ID = p.NAME_ID AND p.PLACE_ID = :place_id;
• Locating POIs by partial street name: filter on BASE_NAME or NAME using LIKE predicates.
• Reporting on multilingual name coverage by grouping on LANGUAGE_CODE.
• Security-filtered lookups joining to FND_SECURITY_GROUPS on SECURITY_GROUP_ID.

Because the table acts as a hub, reporting layers frequently pre-join it to the three name-intersection tables to produce a unified location naming view.

Related Objects

The following objects have documented relationships with CSF_LF_NAMES:

• CSF_LF_PLACE_NAMES — References NAME_ID; associates name records with places.
• CSF_LF_POI_NAMES — References NAME_ID; associates name records with points of interest.
• CSF_LF_ROADSEGM_NAMES — References NAME_ID; associates name records with road segments.
• FND_SECURITY_GROUPS — Referenced via CSF_LF_NAMES.SECURITY_GROUP_ID; governs row-level access.

These four objects constitute the complete documented dependency surface for CSF_LF_NAMES. Any extension or purge operation on the hub must account for the three child intersection tables to preserve referential integrity.