Search Results validate_updatetrip

Overview

FTE_TRIPS_PVT is a private (PVT) PL/SQL API package in the Oracle E-Business Suite applications schema (APPS), operating with AUTHID CURRENT_USER. It belongs to the Freight and Transportation Execution (FTE) module and provides the underlying implementation logic for creating, maintaining, validating, and querying freight trips — the groupings of deliveries moved together on a single equipment asset or route. The package is private by classification, meaning it is not intended as a public integration interface; rather, it is consumed internally by FTE table handlers, the public FTE trips API, and related processing logic. As reflected in its header, the package dates to the earliest FTE releases and remains available in both 12.1.1 and 12.2.2, remaining functionally stable across those releases. It encapsulates the FTE trip record type (fte_trip_rec_type), which mirrors the FTE_TRIPS table structure, and exposes a set of documented procedures and functions covering the full trip lifecycle: creation, update, deletion, validation, delivery assignment, and retrieval of descriptive information such as trip names, stop location details, and shipment information.

Key Procedures and Functions

The package exposes sixteen documented procedures and functions. They fall into several logical groups:

• GET_TRIP_NAME — the function/procedure most commonly searched by developers; returns the trip name associated with a given trip identifier, together with a return status. It is the standard utility for translating an internal trip ID into the user-visible trip name.
• Create_Update_Delete_Fte_Trip — a unified wrapper around the create, update, and delete logic. It accepts an action code of 'CREATE', 'UPDATE', or 'DELETE', builds the appropriate PL/SQL record, and dispatches to the corresponding worker procedure.
• CREATE_TRIP and VALIDATE_CREATETRIP — the insert logic and its pre-insert validation rules respectively.
• UPDATE_TRIP and VALIDATE_UPDATETRIP — the modify logic and its accompanying validation.
• DELETE_TRIP and VALIDATE_DELETETRIP — the removal logic and its deletion validation.
• VALIDATE_TRIP — a general trip-level validation routine used across the create, update, and delete operations.
• ASSIGN_DELIVERIES_TO_FTETRIP — associates one or more deliveries with a given FTE trip.
• GET_TRIP_BY_TENDER_NUMBER — retrieves trip information based on an associated tender number.
• GET_FIRST_STOP_LOCATION_INFO and GET_LAST_STOP_LOCATION_INFO — return origin and destination stop details for a trip, useful for routing and reporting.
• GET_TRIP_SEGMENT_NAME — returns the descriptive name for a trip segment.
• GET_SHIPMENT_INFORMATION — returns shipment details associated with a trip.
• GET_TRIP_INFO_FROM_DLVY — retrieves trip information by starting from a delivery reference.

Together these routines cover trip maintenance, delivery-to-trip assignment, and read-only informational lookups. No parameter lists are reproduced here; developers should inspect the package specification in the database directly for exact signatures, noting that output parameters are declared NOCOPY for efficiency.

Tables Accessed

The package reads and writes several core transportation and shipping tables through APPS synonyms:

• FTE_TRIPS and FTE_TRIPS_S — the primary trip entity and its sequence, holding trip identifiers, names, and status.
• FTE_WSH_TRIPS — the FTE-side mapping to WSH trip records, linking FTE trip logic to the Warehouse Management shipping trip model.
• WSH_TRIPS and WSH_TRIP_STOPS — the underlying shipping trip and stop tables from which trip, stop, and location information is derived.
• WSH_DELIVERY_LEGS and WSH_NEW_DELIVERIES — delivery leg and delivery records used when assigning deliveries to trips and when resolving trip information from a delivery.
• MTL_UNITS_OF_MEASURE — the units of measure reference, used for validating or reporting trip measures.
• DBMS_UTILITY and PLITBLM — PL/SQL built-ins used for error stack inspection and message/string table handling.

The mix of FTE and WSH tables reflects the package's role as the FTE-side controller that synchronizes trip definitions with the shipping execution trip records.

Usage Notes

Because FTE_TRIPS_PVT is a private API, it is invoked indirectly rather than called directly by external integrations. Its principal consumers are the FTE table handler layer, the public FTE trip API, FTE freight-related forms (such as trip maintenance and delivery assignment pages), and concurrent programs that process trip creation, tender processing, or trip inquiry. The documented metadata shows the package is referenced by five other packages, consistent with its role as a shared internal implementation block rather than a top-level entry point.

Custom code that must work with FTE trips should generally prefer the public FTE API or the underlying base tables, treating FTE_TRIPS_PVT as an internal dependency that may change without public notice. Where developers do call into it — for example, to reuse GET_TRIP_NAME for name resolution in reporting — they should prepare for standard FND_API error handling, checking the returned status flag and message output. The package remains functional across 12.1.1 and 12.2.2, with the same private classification and procedure set in both releases, so behavior is consistent for organizations upgrading between those versions.