Search Results fte_trips_s

Overview

APPS.FTE_TRIPS_PVT is the private implementation package body behind the Oracle E-Business Suite Freight and Transportation Execution (FTE) trip functionality. In Oracle EBS 12.1.1 and 12.2.2, the FTE module extends Oracle Shipping Execution (WSH) to support transportation planning, tender and carrier assignment, trip building, and freight cost processing. The _PVT suffix follows the standard EBS naming convention for a private package body: the corresponding public specification, FTE_TRIPS_S, exposes a stable interface, while FTE_TRIPS_PVT contains the actual PL/SQL logic, internal validation routines, and direct Data Manipulation Language (DML) against the underlying WSH and FTE tables.

The object resides in the APPS schema and is documented with a VALID status in the ETRM metadata set for release 12.2.2. Its API classification is PVT, confirming that it is intended for internal use by the FTE_TRIPS_S wrapper and other FTE packages rather than for direct invocation from custom code.

Key Procedures and Functions

The package body exposes sixteen documented procedures and functions, organized around a create/update/delete lifecycle with paired validation logic and a set of query helpers:

• GET_TRIP_NAME — Derives or generates the display name for a trip record.
• CREATE_UPDATE_DELETE_FTE_TRIP — The umbrella entry point that dispatches a trip operation to the appropriate create, update, or delete handler.
• CREATE_TRIP / VALIDATE_CREATETRIP — Creates a new FTE trip; the validate counterpart enforces business rules before the insert.
• UPDATE_TRIP / VALIDATE_UPDATETRIP — Modifies an existing trip; validation precedes the update.
• DELETE_TRIP / VALIDATE_DELETETRIP — Removes a trip; validation confirms the record is eligible for deletion.
• VALIDATE_TRIP — A general-purpose trip validation routine.
• ASSIGN_DELIVERIES_TO_FTETRIP — Associates delivery legs to an FTE trip.
• GET_TRIP_BY_TENDER_NUMBER — Retrieves a trip using the carrier tender number as the search key.
• GET_LAST_STOP_LOCATION_INFO / GET_FIRST_STOP_LOCATION_INFO — Return the origin and destination stop details for a trip itinerary.
• GET_TRIP_SEGMENT_NAME — Returns the name of a trip segment.
• GET_SHIPMENT_INFORMATION — Retrieves shipment-level detail associated with a trip.
• GET_TRIP_INFO_FROM_DLVY — Resolves trip information starting from a delivery reference.

Tables Accessed

The package reads and writes core Shipping Execution and FTE tables through APPS synonyms. FTE_TRIPS and FTE_TRIPS_S hold the FTE trip header and its translated/secure attributes. FTE_WSH_TRIPS links FTE trips to WSH trip records. WSH_TRIPS, WSH_TRIP_STOPS, WSH_DELIVERY_LEGS, and WSH_NEW_DELIVERIES supply the WSH trip, stop, and delivery-leg structures that FTE depends on. MTL_UNITS_OF_MEASURE is referenced for unit-of-measure validation. DBMS_UTILITY and PLITBLM are utility references used for internal processing. The dependency listing also shows calls to FND_API, FND_GLOBAL, FND_MESSAGE, and FND_MSG_PUB for the standard EBS API, message, and error-stack infrastructure, and to WSH_UTIL_CORE, WSH_DEBUG_SV, and WSH_WV_UTILS for WSH utility and debug services.

Usage Notes

FTE_TRIPS_PVT is a private body and should not be called directly from customer extensions. Application logic reaches it through FTE_TRIPS_S, which is in turn invoked by FTE transportation forms, concurrent programs, and other FTE packages. The metadata confirms that the package body is referenced by five other database objects, reflecting its role as a shared internal engine. Because it performs direct DML and relies on FND_MSG_PUB for error handling, any custom integration should invoke the public FTE_TRIPS_S specification rather than this package. Version compatibility is maintained across 12.1.1 and 12.2.2, with identical dependency profile in the documented ETRM metadata.