Search Results csf_tds_binary_maps_pk

Overview

CSF_TDS_BINARY_MAPS is a table in the CSF (Field Service) product schema of Oracle E-Business Suite, present and valid in both release 12.1.1 and 12.2.2. It stores the digital roadmap definitions used by Oracle Field Service for route calculation. In other words, it holds the binary map metadata that the scheduling and dispatch engine consults when computing optimized travel routes for field service technicians.

The object is documented in the ETRM repository as a TABLE owned by the CSF schema. Its primary key is CSF_TDS_BINARY_MAPS_PK, defined on the BINARY_MAP_ID column. From a Data Vault modeling perspective, the mined foreign key structure suggests a hub-leaning classification: the table's identity is centered on the BINARY_MAP_ID surrogate, while dependent detail columns behave somewhat like satellite attributes.

Key Information Stored

The table contains ten documented columns. The most significant are:

• BINARY_MAP_ID — Surrogate primary key and the object's identity column, enforced by CSF_TDS_BINARY_MAPS_PK.
• NAME — The business name that identifies a particular binary map or roadmap configuration.
• VERSION — Version identifier distinguishing successive releases of the same map definition.
• DRIVING_SIDE — Indicates the driving convention (for example, left-hand or right-hand traffic) applied during route calculation.
• CONFIG — Configuration data governing how the map is interpreted by the routing engine.
• ROADBLOCKS — Stored roadblock information that suppresses or penalizes routes through affected segments.
• CONDITIONS — Travel conditions that influence route weighting and feasibility.
• TIMEINTERVALS — Time-window intervals used when evaluating travel duration and scheduling constraints.
• MAX_AVG_SPEED — The maximum average speed parameter used in travel time estimation.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, providing the multi-org/security partitioning of the map record.

Four unique indexes are documented on the table — SYS_IL0000083081C00005$$, SYS_IL0000083081C00006$$, SYS_IL0000083081C00007$$, and SYS_IL0000083081C00008$$. These index names correspond to LOB or functional index segments over the CONFIG, ROADBLOCKS, CONDITIONS, and TIMEINTERVALS columns, indicating that these are large or structured attribute columns rather than simple business-key candidates.

Common Use Cases and Queries

Typical usage centers on retrieving the active roadmap, inspecting its routing parameters, and joining to the tile detail that makes up the binary map:

• Look up a map by name and version: SELECT binary_map_id, name, version, driving_side, max_avg_speed FROM csf.csf_tds_binary_maps WHERE name = :p_name;
• List all maps available under a security group: SELECT binary_map_id, name FROM csf.csf_tds_binary_maps WHERE security_group_id = :p_group;
• Validate routing parameters before dispatch: SELECT binary_map_id, config, roadblocks, conditions, timeintervals FROM csf.csf_tds_binary_maps WHERE binary_map_id = :p_id;
• Join to the tile detail for map reconstruction: SELECT m.binary_map_id, m.name, t.* FROM csf.csf_tds_binary_maps m JOIN csf.csf_tds_binary_tiles t ON t.binary_map_id = m.binary_map_id;

Reporting use cases include auditing which map versions are deployed across organizations, comparing speed parameters across maps, and tracing the roadmap used for a given scheduling run.

Related Objects

• CSF_TDS_BINARY_TILES — The child table holding the tile segments of each map. Join column: CSF_TDS_BINARY_TILES.BINARY_MAP_ID references CSF_TDS_BINARY_MAPS.BINARY_MAP_ID. This is the primary dependent object.
• FND_SECURITY_GROUPS — Referenced by CSF_TDS_BINARY_MAPS.SECURITY_GROUP_ID; governs row-level access to map records.
• CSF_TDS_BINARY_MAPS_PK — The primary key constraint/index on BINARY_MAP_ID underpinning lookups.
• Field Service scheduling and routing engine components consume this table indirectly through map selection during dispatch processing.

Because the schema is Oracle proprietary and confidential, direct DML against CSF_TDS_BINARY_MAPS should be avoided; changes should flow through supported Field Service configuration and administration paths.