Search Results csf_lf_poi_names




Overview

CSF_LF_POI_NAMES is a table owned by the CSF schema within the Oracle E-Business Suite Field Service module. Its documented purpose is to define the relationship between POI (Point of Interest) records and Name records. In the context of Oracle EBS 12.1.1 and 12.2.2, this table functions as an intersection or association entity that links a point-of-interest definition to a named entity, such as a customer, contact, or location descriptor. It holds five documented columns and is classified as VALID in the data dictionary, confirming it is an active, supported object rather than a deprecated artifact.

From a heuristic Data Vault modeling perspective, the mined foreign key structure suggests this object is best classified as a link table. Its purpose is to resolve a many-to-many or qualified relationship between two principal entities — CSF_LF_POIS and CSF_LF_NAMES — rather than to store descriptive attributes about a single business entity. The presence of a surrogate primary key and multiple foreign keys pointing outward to independent parent tables reinforces this interpretation.

Key Information Stored

The table contains five documented columns. The most significant are described below.

  • POI_NAME_ID — The surrogate primary key, enforced by the constraint CSF_LF_POI_NAMES_PK. This value uniquely identifies each row in the association table and has no intrinsic business meaning; it exists to provide a stable technical identifier.
  • POI_ID — A foreign key referencing CSF_LF_POIS. This column anchors the row to a specific Point of Interest record and is one half of the business relationship being modeled.
  • NAME_ID — A foreign key referencing CSF_LF_NAMES. This column anchors the row to a specific name record and forms the other half of the relationship.
  • NAME_TYPE — A qualifier column that distinguishes the role or category of the associated name. Because a single POI may be linked to multiple names in different capacities, this column provides semantic context for each association.
  • SECURITY_GROUP_ID — A foreign key referencing FND_SECURITY_GROUPS. This column supports Oracle's multi-organization and data security architecture, ensuring that rows are partitioned and visible only to authorized security groups.

The business-key candidate is the composite of POI_ID, NAME_ID, and NAME_TYPE, which together define a unique association between a point of interest and a named entity within a given security group. The surrogate POI_NAME_ID is not a business key.

Common Use Cases and Queries

Typical scenarios include resolving which names are associated with a given Point of Interest, and conversely, which Points of Interest reference a given name. Reporting on name associations by type is common in Field Service scheduling and dispatch analysis.

  • Retrieving all names linked to a POI:
    SELECT pn.POI_NAME_ID, pn.NAME_ID, pn.NAME_TYPE FROM CSF_LF_POI_NAMES pn WHERE pn.POI_ID = :poi_id;
  • Finding all POIs associated with a specific name:
    SELECT pn.POI_ID, pn.NAME_TYPE FROM CSF_LF_POI_NAMES pn WHERE pn.NAME_ID = :name_id;
  • Joining to parent tables to produce a readable report:
    SELECT p.POI_ID, n.NAME, pn.NAME_TYPE FROM CSF_LF_POI_NAMES pn, CSF_LF_POIS p, CSF_LF_NAMES n WHERE pn.POI_ID = p.POI_ID AND pn.NAME_ID = n.NAME_ID;
  • Filtering by security group for multi-org environments:
    SELECT * FROM CSF_LF_POI_NAMES WHERE SECURITY_GROUP_ID = :org_id;

Related Objects

The following objects are most directly related through documented foreign key and primary key relationships.

  • CSF_LF_POIS — Parent table joined via CSF_LF_POI_NAMES.POI_ID = CSF_LF_POIS.POI_ID.
  • CSF_LF_NAMES — Parent table joined via CSF_LF_POI_NAMES.NAME_ID = CSF_LF_NAMES.NAME_ID.
  • FND_SECURITY_GROUPS — Security parent joined via CSF_LF_POI_NAMES.SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID, governing row-level access.
  • CSF_LF_POI_NAMES_PK — The primary key constraint enforcing uniqueness on POI_NAME_ID.

These relationships make CSF_LF_POI_NAMES a central junction in Field Service data retrieval, particularly when Points of Interest must be resolved to named parties or locations for scheduling, territory assignment, and service reporting.