[Home] [Help] [Dependency Information]
Object Name: | CSF_LF_ROADSEGM_POSTS_NA |
---|---|
Object Type: | TABLE |
Owner: | CSF |
Subobject Name: | |
Status: | VALID |
DEFINITION
Intersection table since one Roadsegment can contains multiple Postal Codes (e.g. roadsegment on postcode boundary --> left / right different Postal Code), and one Postal Code will be shared by multiple RoadSegments.
EXAMPLE
MISCELLANEOUS
Tablespace: | APPS_TS_TX_DATA |
---|---|
PCT Free: | 10 |
PCT Used: |
Name | Datatype | Length | Mandatory | Comments |
---|---|---|---|---|
ROADSEGMENT_POSTCODE_ID | NUMBER | (30) | Yes | Surrogate key used for primary unique identifiers |
POSTCODE_SIDE | VARCHAR2 | (1) | Post Code exits on Left (L), Right (R) or Both (B) sides | |
ROADSEGMENT_ID | NUMBER | (30) | Yes | Permanent identifier for RoadSegment (=GDF3.0 Edge ID) |
POSTAL_CODE_ID | NUMBER | (30) | Yes | Primary key for the Postal Code table |
SECURITY_GROUP_ID | NUMBER | Identifier used for running in hosted mode. |
Cut, paste (and edit) the following text to query this object:
SELECT ROADSEGMENT_POSTCODE_ID
, POSTCODE_SIDE
, ROADSEGMENT_ID
, POSTAL_CODE_ID
, SECURITY_GROUP_ID
FROM CSF.CSF_LF_ROADSEGM_POSTS_NA;
CSF.CSF_LF_ROADSEGM_POSTS_NA does not reference any database object
CSF.CSF_LF_ROADSEGM_POSTS_NA is referenced by following:
|
|
|