Search Results delivered_to

Overview

FTE_LOAD_SCHEDULES_V is a reporting and integration view within the Oracle E-Business Suite Transportation Execution (FTE) module. It exposes header-level information about load schedules — the pre-defined, recurring transportation movements that FTE uses to generate loads and trips across a planner's network. The view presents a denormalized, presentation-ready projection of load schedule data, joining schedule attributes with carrier, lane, mode of transport, and document-level details so that downstream reports and interfaces do not need to reconstruct those relationships themselves. Because it flattens operational identifiers (LOAD_ID, LOAD_SCHEDULE_ID, LANE_ID, CARRIER_ID) alongside human-readable names (LOAD_SCHEDULE_NAME, LANE_NAME, CARRIER_NAME), it is well suited for both user-facing inquiries and outbound integration extracts. Note that the ETRM metadata records this view as "Not implemented in this database" and lists no documented referenced base objects, so its availability depends on the specific FTE patch level and configuration in a given environment.

Underlying Base Objects

Per the documented view text, FTE_LOAD_SCHEDULES_V is defined over a single base table, FTE_LOAD_SCHEDULES. All non-derived columns in the view map directly to columns on that table. The only transformations applied in the SELECT are explicit TO_CHAR conversions that format the date-time columns DEPARTURE_DATE, ARRIVAL_DATE, DELIVERY_DATE, RECEIPT_DATE, and SHIP_DATE using the 'DD-MM-YYYY HH24:MI:SS' mask. This means the view returns date values as formatted character strings rather than native DATE datatypes — an important consideration for any query that performs date arithmetic or range filtering at the database level. EST_DEPARTURE_DATE and EST_ARRIVAL_DATE are surfaced without this masking. The ETRM documentation lists no additional base objects, so the view is a straightforward single-table projection with no documented joins to lane, carrier, or stop master tables, despite the presence of denormalized name columns such as LANE_NAME and CARRIER_NAME, which are stored on the schedule record itself.

Key Columns

• LOAD_SCHEDULE_ID — Primary identifier for the load schedule. This is the column most commonly used for lookups and joins, and it matches the "load_schedule_id" search term that surfaces this object.
• LOAD_ID — Identifier of the load instance associated with or generated from the schedule.
• LOAD_SCHEDULE_NAME / ORIGINAL_SCHEDULE_ID — Display name and the source schedule reference for derived or template schedules.
• LANE_ID / LANE_NAME, CARRIER_ID / CARRIER_NAME, MODE_OF_TRANSPORTATION — Routing and carrier context for the schedule.
• DEPARTURE_DATE / ARRIVAL_DATE — Planned movement timestamps, returned as formatted strings, alongside plain-date EST_DEPARTURE_DATE and EST_ARRIVAL_DATE.
• PORT_OF_LOADING / PORT_OF_DISCHARGE, VESSEL, VESSEL_TYPE, VOYAGE, EQUIPMENT_TYPE, SERVICE_TYPE — Ocean and equipment attributes supporting international and charter movements.
• STATUS_CODE, SEQUENCE_NUMBER, EID_FLAG, FREQUENCY — Operational state, ordering within a multi-leg schedule, external interface indicator, and recurrence frequency.
• WHO_* / WHD_* — Warehouse origin and destination address and contact details.
• WORKFLOW_NAME / WORKFLOW_PROCESS — Workflow configuration tied to the schedule.
• FOB, FREIGHT_TERMS, PRICE, CURRENCY, QUOTATION_NUMBER, BOOKING_NUMBER, CARRIER_TRACKING_NUMBER — Commercial and booking terms.
• CARRIER_REMARKS, CONSIGNEE_NOTES, CARRIER_NOTES, POD_SENT, POR_SENT, DELIVERED_TO, RECEIVED_BY — Execution and proof-of-delivery tracking.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE.

Common Use Cases and Queries

Typical uses include operational dashboarding of recurring schedules, reconciliation of load generation against schedule definitions, and outbound extracts feeding carrier booking or visibility platforms. Because the date columns are pre-formatted strings, filters should be applied against the underlying base table when precise date logic is required.

Retrieve all attributes for a known schedule:

SELECT * FROM FTE_LOAD_SCHEDULES_V WHERE LOAD_SCHEDULE_ID = :p_schedule_id;

List active schedules by carrier and lane for a reporting period:

SELECT LOAD_SCHEDULE_NAME, CARRIER_NAME, LANE_NAME, MODE_OF_TRANSPORTATION, DEPARTURE_DATE, STATUS_CODE FROM FTE_LOAD_SCHEDULES_V WHERE CARRIER_ID = :p_carrier AND STATUS_CODE = 'ACTIVE' ORDER BY LOAD_SCHEDULE_NAME;

Reconcile commercial terms for schedules tied to a quotation:

SELECT LOAD_SCHEDULE_ID, QUOTATION_NUMBER, FOB_CODE, FREIGHT_TERMS_CODE, PRICE, CURRENCY FROM FTE_LOAD_SCHEDULES_V WHERE QUOTATION_NUMBER IS NOT NULL;

For date-sensitive analysis, query FTE_LOAD_SCHEDULES directly and apply native date predicates, or convert the formatted strings explicitly in the calling report.