Search Results csf_lf_place_names




Overview
Explore in AI Chat

Overview

CSF_LF_PLACE_NAMES is a table in the CSF (Field Service) product schema of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. Its documented purpose is to define the relationship between a Place and a Name. In the Field Service data model, "Places" represent physical or logical service locations (such as a customer site, an installed-at address, or a service delivery point), while "Names" represent the parties or entities associated with those locations. CSF_LF_PLACE_NAMES therefore acts as an associative structure that records which names are linked to which places, and in what capacity, through the NAME_TYPE column.

The ETRM metadata assigns a heuristic Data Vault classification of link. This is a modeling suggestion: the table resolves a many-to-many association between two hub-like entities, CSF_LF_PLACES and CSF_LF_NAMES, and carries the surrogate key PLACE_NAME_ID plus descriptive attributes of the relationship itself (notably NAME_TYPE). Practically, this table is queried whenever Field Service needs to resolve the identity of the party or contact attached to a given service location, or conversely, to find all locations associated with a given name.

Key Information Stored

The documented physical schema in 12.2.2 contains five columns. The most significant are listed below.

  • PLACE_NAME_ID — The surrogate primary key, enforced through constraint CSF_LF_PLACE_NAMES_PK. It uniquely identifies each place-to-name association row and is the column that dependent objects and child tables reference.
  • PLACE_ID — Foreign key to CSF_LF_PLACES. Identifies the Place side of the relationship. This is a principal business-key candidate because it is half of the natural association between a place and a name.
  • NAME_ID — Foreign key to CSF_LF_NAMES. Identifies the Name (party, contact, or entity) side of the relationship. Along with PLACE_ID, it forms the other half of the natural business key.
  • NAME_TYPE — A descriptive attribute that qualifies the role or category of the name as associated with the place. The column is central to interpreting an association row: the same place may be linked to multiple names distinguished only by this value.
  • SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS. Supports Oracle's multi-org / data security model by segregating rows according to the security group under which they were created, restricting visibility per operating unit or responsibility.

The combination of PLACE_ID and NAME_ID (potentially with NAME_TYPE) is the principal business-key candidate; PLACE_NAME_ID remains the surrogate primary key used for physical joins.

Common Use Cases and Queries

Typical usage resolves the names associated with a service location, or the places associated with a given name.

  • Retrieving all names for a place: SELECT pn.PLACE_NAME_ID, pn.NAME_ID, pn.NAME_TYPE FROM CSF_LF_PLACE_NAMES pn WHERE pn.PLACE_ID = :place_id;
  • Resolving the place(s) for a name: SELECT pn.PLACE_ID, pn.NAME_TYPE FROM CSF_LF_PLACE_NAMES pn WHERE pn.NAME_ID = :name_id;
  • Joining to the name master for descriptive output: SELECT n.* FROM CSF_LF_PLACE_NAMES pn, CSF_LF_NAMES n WHERE pn.NAME_ID = n.NAME_ID AND pn.PLACE_ID = :place_id;
  • Filtering by security context in multi-org deployments using SECURITY_GROUP_ID.
  • Reporting on the count of names per place, or the distribution of NAME_TYPE values, for data-quality and Field Service configuration audits.

Related Objects

The following objects are most significant in relation to this table, based on the documented foreign-key structure.

  • CSF_LF_PLACES — Referenced via CSF_LF_PLACE_NAMES.PLACE_ID; the parent of the place side of the association.
  • CSF_LF_NAMES — Referenced via CSF_LF_PLACE_NAMES.NAME_ID; the parent of the name side of the association.
  • FND_SECURITY_GROUPS — Referenced via CSF_LF_PLACE_NAMES.SECURITY_GROUP_ID; governs row-level security.
  • CSF_LF_PLACE_NAMES_PK — The primary key constraint on PLACE_NAME_ID.

Together these objects form the Field Service place-name resolution layer, and any dependent view or concurrent program that reports on place-to-name associations will join through PLACE_ID and NAME_ID as documented above.