[Home] [Help] [Dependency Information]
Object Name: | CSF_LF_ROADSEGM_NAMES |
---|---|
Object Type: | TABLE |
Owner: | CSF |
FND Design Data: | CSF.CSF_LF_ROADSEGM_NAMES |
Subobject Name: | |
Status: | VALID |
DEFINITION
Intersection table since one roadsegment can have multiple names (e.g. E34 and A12) and one name can be used by multiple roadsegments.
EXAMPLE
MISCELLANEOUS
Some roadsegments do not have a name in reality (so called 'Valid Unnamed'). For these roadsegment no entry exist in the Roadsegment Name table.
Tablespace: | APPS_TS_MEDIA |
---|---|
PCT Free: | 10 |
PCT Used: |
Name | Datatype | Length | Mandatory | Comments |
---|---|---|---|---|
ROADSEGMENT_NAME_ID | NUMBER | (30) | Yes | Unique identifier for RoadSegment Name table |
NAME_TYPE | VARCHAR2 | (1) | Yes | Indication if RoadSegment's Name represents Official, Alternate, Stale or Vanity Name' |
ROADSEGMENT_ID | NUMBER | (30) | Yes | Permanent identifier for RoadSegment (=GDF3.0 Edge ID) |
NAME_ID | NUMBER | (30) | Yes | Unique key for Name |
SECURITY_GROUP_ID | NUMBER | Identifier used for running in hosted mode. |
Cut, paste (and edit) the following text to query this object:
SELECT ROADSEGMENT_NAME_ID
, NAME_TYPE
, ROADSEGMENT_ID
, NAME_ID
, SECURITY_GROUP_ID
FROM CSF.CSF_LF_ROADSEGM_NAMES;
CSF.CSF_LF_ROADSEGM_NAMES does not reference any database object
CSF.CSF_LF_ROADSEGM_NAMES is referenced by following:
|
|
|