Results for “name_type”

50+ results




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

Overview

The CSF_MD_RDSEG_NM_ASGNS table, owned by the CSF schema within the Oracle E-Business Suite Field Service module, defines the relationship between road segments and names. It functions as an intersection or association table that maps road segment records to name records, enabling geographic and routing intelligence used by Field Service scheduling, dispatch, and mobile field technician applications.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure identifies this table as a link entity. This classification is a modeling suggestion derived from the fact that the table resolves a many-to-many relationship between two independent business entities — road segments and names — rather than acting as a hub of unique business keys or a satellite of descriptive attributes. The presence of the RD_SEG_NM_ID surrogate key and references to both CSF_MD_RD_SEGS and CSF_MD_NAMES confirms this associative role.

Key Information Stored

The table contains five documented columns in the 12.2.2 schema, with the following principal columns of interest:

  • RD_SEG_NM_ID — The surrogate primary key defined by the constraint CSF_MD_RDSEG_NM_ASGNS_PK. It uniquely identifies each association row and is the object users most commonly reference when searching on the term "rd_seg_nm_id".
  • ROAD_SEGMENT_ID — Foreign key referencing CSF_MD_RD_SEGS. This identifies the road segment participating in the assignment.
  • NAME_ID — Foreign key referencing CSF_MD_NAMES. This identifies the name record (such as a location, route, or geographic designation) assigned to the road segment.
  • NAME_TYPE — A descriptive discriminator column that classifies the nature of the name association, allowing a single road segment to be linked to names of differing semantic types.
  • SECURITY_GROUP_ID — Foreign key referencing FND_SECURITY_GROUPS, enforcing multi-tenant style data segregation through Oracle EBS security group functionality.

The surrogate primary key RD_SEG_NM_ID is a system-generated identifier and is not itself a business key. Business-key candidates are the composite of ROAD_SEGMENT_ID and NAME_ID, potentially qualified by NAME_TYPE, which represent the meaningful real-world combination of segment and name. No separate unique index beyond the primary key is documented in the available metadata.

Common Use Cases and Queries

Typical use cases involve resolving which names are assigned to a given road segment, or conversely identifying all road segments associated with a specific name. Reporting scenarios include route planning, geographic hierarchy reporting, and security-filtered extracts for mobile field engineers.

A common query pattern resolves the lookup by primary key:

  • SELECT rd_seg_nm_id, road_segment_id, name_id, name_type, security_group_id FROM csf.csf_md_rdseg_nm_asgns WHERE rd_seg_nm_id = :p_id;

To retrieve names for a road segment with security filtering:

  • SELECT a.rd_seg_nm_id, a.name_id, a.name_type FROM csf.csf_md_rdseg_nm_asgns a WHERE a.road_segment_id = :seg_id AND a.security_group_id = :sg_id;

Joining to the name master for descriptive output is also frequent, joining NAME_ID to CSF_MD_NAMES to obtain the human-readable name. Because the table is a pure association link, writes are normally performed only through the supported Field Service application logic rather than direct DML.

Related Objects

The following objects are the most significant references and dependencies based on the documented key relationships:

  • CSF_MD_RD_SEGS — Referenced via ROAD_SEGMENT_ID; the parent road segment table.
  • CSF_MD_NAMES — Referenced via NAME_ID; the parent name table holding name master records.
  • FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID; governs data access partitioning.
  • CSF_MD_RDSEG_NM_ASGNS_PK — The primary key constraint enforcing uniqueness on RD_SEG_NM_ID.
  • Field Service dispatch and scheduling APIs — Application-layer consumers that read this assignment data when computing technician routes and service coverage.

Together these dependencies establish CSF_MD_RDSEG_NM_ASGNS as the connective link enabling road segment to name resolution within Oracle EBS Field Service.