Search Results csf_lf_blocks

Overview

CSF_LF_BLOCKS is a table in the CSF (Field Service) product schema within Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented description states that it "defines the available address range for a segment." In practical terms, the table stores the discrete address-number blocks associated with a road segment, supplying the low and high address bounds and the numbering scheme or format that governs how addresses are assigned and validated along each side of a street segment. This makes it a foundational reference object for address validation and location-based service coverage in Field Service deployments where geographic addressing is required.

The table's documented physical schema in ETRM 12.2.2 lists the owner as CSF with twelve columns. Its primary key is CSF_LF_BLOCKS_PK, defined on BLOCK_ID, which is a system-generated surrogate identifier rather than a user-facing business key. Foreign key relationships show that CSF_LF_BLOCKS references CSF_LF_ROADSEGMENTS via ROADSEGMENT_ID and FND_SECURITY_GROUPS via SECURITY_GROUP_ID. The mined Data Vault classification is heuristic and satellite-leaning: the table behaves as a satellite attached to the CSF_LF_ROADSEGMENTS hub, carrying descriptive address-range attributes rather than acting as an independent hub or a pure link.

Key Information Stored

The most consequential columns fall into three groups: identity, address-range definition, and partitioning/ownership metadata.

• BLOCK_ID — Surrogate primary key (CSF_LF_BLOCKS_PK). No documented business-key unique index exists beyond this; candidates such as the road segment plus address range would be inferred, not documented.
• ROADSEGMENT_ID — Foreign key to CSF_LF_ROADSEGMENTS, tying each address block to its parent street segment.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, enforcing Multi-Org / security-group partitioning.
• START_LEFT_ADDRESS and END_LEFT_ADDRESS — The numeric range bounds for the left side of the segment.
• START_RIGHT_ADDRESS and END_RIGHT_ADDRESS — The corresponding range bounds for the right side.
• LEFT_ADDRESS_SCHEME and RIGHT_ADDRESS_SCHEME — The numbering scheme applied per side (for example, odd/even conventions).
• LEFT_ADDRESS_FORMAT and RIGHT_ADDRESS_FORMAT — The display or parsing format for addresses on each side.
• ADDRESS_TYPE — Classifies the block, distinguishing address categories within the segment.

Together these columns let the application resolve whether a given street number falls within a valid, serviceable range on the correct side of a road segment.

Common Use Cases and Queries

Typical uses include validating a customer address against known serviceable ranges, reporting coverage by street segment, and reconciling address data loaded from external geographic sources. Because SECURITY_GROUP_ID is present, queries should generally be restricted to the appropriate security group.

• Retrieve all blocks for a segment: SELECT block_id, start_left_address, end_left_address, start_right_address, end_right_address FROM csf.csf_lf_blocks WHERE roadsegment_id = :seg_id;
• Validate a left-side address: SELECT COUNT(*) FROM csf.csf_lf_blocks WHERE roadsegment_id = :seg_id AND :addr BETWEEN start_left_address AND end_left_address;
• Security-scoped reporting: join to CSF_LF_ROADSEGMENTS to present segment names alongside their address ranges, filtered by SECURITY_GROUP_ID.
• Data-quality checks for overlapping or inverted ranges (START greater than END).

Related Objects

The following objects are most significant relative to CSF_LF_BLOCKS, based on the documented foreign-key relationships:

• CSF_LF_ROADSEGMENTS — Parent table; joined on CSF_LF_BLOCKS.ROADSEGMENT_ID = CSF_LF_ROADSEGMENTS.ROADSEGMENT_ID.
• FND_SECURITY_GROUPS — Referenced on SECURITY_GROUP_ID for security partitioning.
• CSF_LF_BLOCKS_PK — The primary-key constraint used for unique access by BLOCK_ID.
• Address-validation and location modules within Field Service that consume block ranges by way of the road-segment relationship, rather than referencing CSF_LF_BLOCKS directly.

Any downstream reporting or integration should traverse the documented ROADSEGMENT_ID and SECURITY_GROUP_ID relationships to remain consistent with the ETRM-documented schema.