Search Results fte_location_parameters_u2

Overview

FTE.FTE_LOCATION_PARAMETERS is a transactional configuration table within the Oracle E-Business Suite Transportation Management (FTE) schema. It stores facility definitions and the operational parameters that govern how each facility may participate in consolidation, deconsolidation, and cross-docking activity. In Oracle EBS 12.1.1 and 12.2.2, this table supplies the master facility attributes consumed by the Transportation Planning engine when evaluating shipment consolidation opportunities and cross-dock execution.

Under a heuristic Data Vault classification derived from foreign key structure, this object is satellite-leaning. It extends a facility business key with descriptive and operational attributes rather than acting as a pure hub or a link between multiple hubs, which is consistent with its role as an attribute-bearing satellite around the facility entity.

The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. Its FND Design Data reference is FTE.FTE_LOCATION_PARAMETERS. In the documented 12.2.2 physical schema the table carries 92 columns.

Key Information Stored

The surrogate primary key is FACILITY_ID, enforced by the FTE_LOCATION_PARAMETERS_PK constraint. Two further unique indexes function as business-key candidates: FTE_LOCATION_PARAMETERS_U1 on FACILITY_ID and FTE_LOCATION_PARAMETERS_U2 on LOCATION_ID, while FTE_LOCATION_PARAMETERS_U3 uniquely constrains FACILITY_CODE. These three unique constraints make FACILITY_CODE and LOCATION_ID the practical business identifiers used by external references.

• FACILITY_ID — numeric primary key of the table.
• FACILITY_CODE — unique facility identifier, VARCHAR2(60).
• LOCATION_ID — foreign key to WSH_LOCATIONS.wsh_location_id, linking the facility to a physical location.
• DESCRIPTION — optional user description, VARCHAR2(250).
• CONSOLIDATION_ALLOWED / DECONSOLIDATION_ALLOWED / CROSSDOCKING_ALLOWED — Yes/No flags gating each major activity type.
• PARCEL_LTL_CONSOLIDATION, PARCEL_TL_CONSOLIDATION, LTL_TL_CONSOLIDATION, LTL_LTL_CONSOLIDATION — permitted mode-to-mode consolidation combinations.
• LTL_PARCEL_DECONSOLIDATION, TL_PARCEL_DECONSOLIDATION, TL_LTL_DECONSOLIDATION, LTL_LTL_DECONSOLIDATION — permitted deconsolidation combinations.
• PARCEL_INBOUND_CROSSDOCKING, LTL_INBOUND_CROSSDOCKING, TL_INBOUND_CROSSDOCKING and their outbound counterparts — mode-specific cross-dock permissions.
• STORAGE_FACILITY, CARRIER_DROP_TRAILER_ALLOWED, CARRIER_OWNED_HAUL — operational facility characteristics.
• NUM_DOCKS, NUM_SHIPPING_DOCKS, NUM_RECEIVING_DOCKS, NUM_PARKING_SPOTS — dock and parking capacity attributes.
• HANDLING_CAPACITY, DOCK_HANDLING_RATE, HANDLING_UNIT — throughput and capacity measures.
• EFFECTIVE_DATE_FROM / EFFECTIVE_DATE_TO — date-range control over parameter validity.
• FACILITY_CONTACT_ID — foreign key to HZ_PARTIES identifying the facility contact.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard EBS descriptive flexfield columns.

Common Use Cases and Queries

Planners and logistics analysts query this table to determine which facilities permit consolidation or cross-docking before committing a load plan. A typical lookup resolves a facility by business code:

• SELECT facility_id, facility_code, description FROM fte.fte_location_parameters WHERE facility_code = :code;
• SELECT facility_code, consolidation_allowed, crossdocking_allowed FROM fte.fte_location_parameters WHERE consolidation_allowed = 'Y' AND effective_date_to IS NULL;
• Joining to WSH_LOCATIONS to obtain address and site detail for reporting.
• Filtering by mode-specific flags to identify facilities capable of LTL-to-TL consolidation.
• Reviewing effective-dated rows to audit parameter changes over time.

Related Objects

• WSH_LOCATIONS — referenced via LOCATION_ID (FTE_LOCATION_PARAMETERS.LOCATION_ID → WSH_LOCATIONS.WSH_LOCATION_ID).
• HZ_PARTIES — referenced via FACILITY_CONTACT_ID for the facility contact.
• Transportation planning and consolidation engine logic in the FTE schema that consumes these Yes/No flags.
• Cross-dock and load-building programs that validate facility permissions before execution.
• Standard EBS flexfield and audit infrastructure that reads ATTRIBUTE1–15 and the WHO columns.