Search Results closing_time

Overview

FTE_LOAD_HEADERS_V is a reporting view within the Oracle E-Business Suite Transportation Execution (FTE) module. It exposes load header information — the top-level shipment or transportation load record — in a denormalized, presentation-ready format suitable for operational reporting, integration extracts, and dashboards. In the context of the searched term "load_number," this view surfaces the LOAD_NUMBER column, which is the human-readable business identifier for a load (as opposed to the internal LOAD_ID primary key). Load numbers are the value transportation planners, carriers, and customer service personnel reference when tracking a shipment, and they are the key returned by this view whenever a user searches for a specific load.

The view flattens a wide set of header, party, geography, and measurement attributes into a single row per load, so consumers do not need to join the many underlying detail tables themselves. Note that the ETRM metadata records this object as "Not implemented in this database," meaning the view is documented but may not exist in every environment or release; validation with ALL_VIEWS / ALL_OBJECTS is advisable before use.

Underlying Base Objects

The ETRM metadata for this view does not document explicit base objects, and the supplied metadata records no referenced base tables. Based on the FTE data model and the column list, the view is defined over the core load header table (FTE_LOAD_HEADERS) with supporting lookups and descriptive tables that resolve codes to their descriptions. Columns such as LANE_NAME and SCHEDULE_NAME indicate joins to lane and schedule definitions (for example FTE_LANES and FTE_SCHEDULES), while STATUS_DESC and BOOKING_TYPE_DESC indicate joins to lookup or code tables that translate the STATUS_CODE and BOOKING_TYPE_CODE values. The view also references party and address information, suggesting joins to recipient, shipper, and consignee source structures.

Key Columns

• LOAD_ID / LOAD_NUMBER / DESCRIPTION — The internal identifier, the searchable business load number, and a free-text description of the load.
• PARENT_LOAD_ID — Self-referencing link for consolidated or master-vs-child load relationships.
• RECIPIENT_ID / RECIPIENT_NAME — The party receiving the load; the internal ID and its resolved name.
• LANE_ID / LANE_NAME, SCHEDULE_ID / SCHEDULE_NAME — The routing lane and schedule assigned to the load, with descriptive names.
• BOOKING_TYPE_CODE / BOOKING_TYPE_DESC, STATUS_CODE / STATUS_DESC, BOOKING_NUMBER — Booking classification, current load status, and the associated booking reference.
• EST_DATE_OF_DEPARTURE / EST_DATE_OF_ARRIVAL — Estimated departure and arrival timestamps, formatted as 'DD-MM-YYYY HH24:MI:SS'. CLOSING_TIME captures the cutoff.
• ORDER_NUMBER / SHIPPER_REFERENCE_NUMBER — Cross-references back to source sales orders and shipper references.
• TOTAL_WEIGHT / WEIGHT_UOM, TOTAL_VOLUME / VOLUME_UOM — Aggregated weight and volume measures; the view adds literal qualifiers 'TOTWEIGHT' and 'VOLUME' as TOTAL_WEIGHT_QUALIFIER and TOTAL_VOLUME_QUALIFIER.
• TEMPERATURE_FROM / TEMPERATURE_TO / TEMP_UOM — Temperature-control range for reefer or specialized loads.
• WAYBILL / TRADE COLUMNS — HOUSE_WAYBILL_NUMBER, MASTER_WAYBILL_NUMBER, EXPORT_LICENSE_NUMBER, COUNTRY_OF_ORIGIN_CODE/DESC, PORT_OF_LOADING_CODE/DESC, PORT_OF_DISCHARGE_CODE/DESC, and EID_FLAG for trade and customs visibility.
• Party/address blocks — SHIPPER_*, CONSIGNEE_*, WHO_*, WHD_*, NOTIFYA_*, and NOTIFYB_* name, address, town, state, country, postal code, and phone attributes printed on transportation documents.
• Flags and classifications — SERVICE_REQUIRED_FLAG, TRANSPORT_DETAILS_FLAG, SERVICE_TYPE, MOVEMENT_TYPE, and HANDLING_INFORMATION.

Common Use Cases and Queries

The most frequent search is by load number to retrieve a full load summary. A typical query joins the view back to the load header for detail or filters by status for operational dashboards:

• Load lookup by number: SELECT load_number, status_desc, lane_name, shipper_name, consignee_name, est_date_of_departure FROM fte_load_headers_v WHERE load_number = :p_load_number;
• Open loads by status: filter on STATUS_DESC or STATUS_CODE for active loads, ordering by EST_DATE_OF_DEPARTURE.
• Weight/volume reporting: aggregate TOTAL_WEIGHT and TOTAL_VOLUME by LANE_NAME or booking type.
• Customs and waybill extracts: select PORT_OF_LOADING_DESC, PORT_OF_DISCHARGE_DESC, MASTER_WAYBILL_NUMBER, and export license columns for trade documentation.
• Document generation: use the SHIPPER_*, CONSIGNEE_*, and NOTIFY* address blocks to print bills of lading and arrival notices.

Because the view embeds TO_CHAR formatting on the date columns, developers importing into external systems should account for the fixed 'DD-MM-YYYY HH24:MI:SS' string format, or select the underlying header dates directly for type-safe date handling.