Search Results fte_location_parameters_pk

Overview

FTE_LOCATION_PARAMETERS is a table owned by the FTE schema within the Oracle E-Business Suite Transportation Execution module. It stores Facility definitions and their associated operational parameters, serving as the master configuration repository for how each facility behaves in transportation planning, consolidation, crossdocking, and load-building activities. Within Oracle EBS 12.1.1 and 12.2.2, this table underpins the facility-level rules consumed by Transportation Execution and integration with Oracle Transportation Management (OTM) planning and execution flows.

In Data Vault terms, the FK structure classifies FTE_LOCATION_PARAMETERS as satellite-leaning, meaning it is a descriptive, attribute-bearing structure that enriches a core hub of facility identities rather than representing a pure relationship link. Each row elaborates a single facility with operational parameters, suggesting it functions best as a satellite keyed to a facility hub. The FTE_LOCATION_PARAMETERS_PK primary key is defined on FACILITY_ID, uniquely and authoritatively identifying each facility row.

Key Information Stored

The table holds 92 documented columns. The most operationally significant are summarized below.

• FACILITY_ID — Surrogate primary key (FTE_LOCATION_PARAMETERS_PK); the definitive identifier for each facility record.
• FACILITY_CODE — Business-key candidate; unique per FTE_LOCATION_PARAMETERS_U3, used for human-readable identification and integration matching.
• LOCATION_ID — Business-key candidate; unique per FTE_LOCATION_PARAMETERS_U2, linking the facility to its location reference.
• DESCRIPTION — Free-text descriptive name for the facility.
• CONSOLIDATION_ALLOWED / DECONSOLIDATION_ALLOWED / CROSSDOCKING_ALLOWED — Core flags governing whether freight may be consolidated, deconsolidated, or crossdocked at the facility.
• PARCEL_LTL_CONSOLIDATION, LTL_TL_CONSOLIDATION, PARCEL_TL_CONSOLIDATION (and related mode-pair flags) — Granular controls for allowed consolidation and deconsolidation transitions between parcel, LTL, and TL modes.
• PARCEL_INBOUND_CROSSDOCKING, LTL_INBOUND_CROSSDOCKING, TL_INBOUND_CROSSDOCKING and their outbound counterparts — Inbound/outbound crossdock eligibility by mode.
• STORAGE_FACILITY / CARRIER_DROP_TRAILER_ALLOWED / CARRIER_OWNED_HAUL — Physical and carrier-handling attributes of the site.
• NUM_DOCKS, NUM_SHIPPING_DOCKS, NUM_RECEIVING_DOCKS, NUM_PARKING_SPOTS — Capacity metrics for dock and yard planning.
• HANDLING_CAPACITY, DOCK_HANDLING_RATE, HANDLING_UNIT, HANDLING_CAPACITY_TYPE — Throughput and handling-rate parameters.
• WEIGHT_UOM, VOLUME_UOM, TIME_UOM, DIMENSIONAL_UOM — Units of measure governing facility data interpretation.
• FLOW_THROUGH_TIME, LOADING_TIME, UNLOADING_TIME, FLOW_THROUGH_TIME_UOM — Timing parameters for planning.
• MAXIMUM_VEHICLE_HEIGHT, MAXIMUM_VEHICLE_WIDTH, MAXIMUM_VEHICLE_LENGTH — Physical access constraints.
• EFFECTIVE_DATE_FROM / EFFECTIVE_DATE_TO — Temporal validity of the parameter set.
• FACILITY_CONTACT_ID — Foreign key to HZ_PARTIES identifying the facility contact.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Standard EBS extensibility (flexfield) columns for customer-defined data.

Common Use Cases and Queries

Typical scenarios include configuring consolidation and crossdocking rules per facility, driving load-building decisions in Transportation Execution, and reporting on facility capacity and throughput. A common lookup pattern is to resolve a facility by its unique business code:

• SELECT facility_id, description, consolidation_allowed, crossdocking_allowed FROM fte_location_parameters WHERE facility_code = :p_code;
• SELECT facility_id, description FROM fte_location_parameters WHERE location_id = :p_location_id;
• SELECT facility_code, num_docks, handling_capacity, dock_handling_rate FROM fte_location_parameters WHERE storage_facility = 'Y';
• SELECT facility_code, flow_through_time, loading_time, unloading_time, time_uom FROM fte_location_parameters WHERE effective_date_to IS NULL OR effective_date_to >= SYSDATE;
• SELECT facility_code, parcel_ltl_consolidation, ltl_tl_consolidation, parcel_inbound_crossdocking FROM fte_location_parameters;

These queries support facility master data validation, planning parameter extracts, and integration with external planning engines. Reporting on carrier drop-trailer permissions and mode-specific crossdocking eligibility is common for network design analysis.

Related Objects

• HZ_PARTIES — Referenced via FTE_LOCATION_PARAMETERS.FACILITY_CONTACT_ID, providing the facility contact party record.
• FTE_LOCATION_PARAMETERS_PK — Primary key constraint on FACILITY_ID enforcing uniqueness.
• FTE_LOCATION_PARAMETERS_U1 — Unique index on FACILITY_ID.
• FTE_LOCATION_PARAMETERS_U2 — Unique index on LOCATION_ID.
• FTE_LOCATION_PARAMETERS_U3 — Unique index on FACILITY_CODE, supporting business-key lookups.

Additional dependencies in the Transportation Execution module are implied by shared FTE facility and location terminology, and the table participates in EBS standard audit columns (CREATED_BY, LAST_UPDATED_BY, PROGRAM_ID, REQUEST_ID) that integrate with the concurrent program and audit framework.