Search Results create_trip

Overview

FTE_WSH_TRIPS_PVT is a private (PVT-classified) PL/SQL package in the APPS schema of Oracle E-Business Suite that underpins the integration between Oracle Transportation Management and Oracle Shipping Execution at the trip level. The package header declares AUTHID CURRENT_USER, indicating that its SQL statements execute with the privileges of the calling schema rather than the package owner, which is a common convention for internal API layers that are always invoked from trusted server-side code. Its header carries the version identifier $Header: FTEFWTHS.pls 115.7 2002/12/03, confirming that the file has been stable since the early FTE release line.

The central construct in the package specification is the record type fte_wsh_trip_rec_type, which mirrors the FTE_WSH_TRIPS table definition. Every column in that record—such as FTE_TRIP_ID, WSH_TRIP_ID, SEQUENCE_NUMBER, the standard WHO audit columns, and fifteen descriptive flexfield attributes—defaults to the corresponding FND_API.G_MISS_* sentinel. This is characteristic of the FND_API-based API pattern: callers populate only the attributes they wish to change, and the private procedures interpret the G_MISS markers as "leave unchanged" rather than as nulls, enabling partial updates of the trip association.

Key Procedures and Functions

The package exposes seven procedures that together form a complete lifecycle API for the FTE-to-WSH trip mapping. In line with the PVT classification, none of these are documented as supported public APIs; they are intended for consumption by higher-level wrapper packages.

• VALIDATE_TRIP — performs business-rule and data-integrity checks on a single trip record before it is committed, ensuring referential and value constraints are satisfied.
• CREATE_TRIP — inserts a new row into the trip association table using the supplied fte_wsh_trip_rec_type instance.
• UPDATE_TRIP — the procedure surfaced by the user's "update_trip" search; it modifies existing trip association data, honoring G_MISS semantics so that unchanged attributes are not overwritten.
• VALIDATE_TRIP_FOR_DELETE — verifies that a trip may be safely removed, checking for dependencies that would otherwise leave orphaned references.
• DELETE_TRIP — removes the trip association row once validation succeeds.
• VALIDATE_TRIP_WRAPPER — a convenience wrapper around VALIDATE_TRIP, typically used when validation is required independently of a subsequent DML operation.
• CREATE_UPDATE_TRIP_WRAPPER — consolidates create and update logic, allowing a caller to submit a trip record without first determining whether it already exists.

Tables Accessed

The package operates against four tables, accessed through APPS synonyms: FTE_TRIPS and FTE_WSH_TRIPS hold the FTE-side trip definition and its link to the corresponding shipping trip; WSH_TRIPS is the Shipping Execution trip header; and WSH_TRIP_STOPS stores the individual stop lines within a trip. The FTE_WSH_TRIPS table is the primary target of the create, update, and delete operations, while the remaining tables supply validation context—confirming that the referenced WSH trip exists and that its stops are consistent before a mapping is written or removed.

Usage Notes

Because FTE_WSH_TRIPS_PVT is a private package referenced by two other packages, it is never invoked directly from Oracle Forms or concurrent programs. In a 12.1.1 or 12.2.2 environment, it is called from the FTE integration layer—most commonly when a transportation plan is confirmed or modified in Oracle Transportation Management and the resulting trip data must be reflected in Oracle Shipping Execution. Custom code should not call UPDATE_TRIP or its siblings directly; the supported entry points are the public wrapper packages, which enforce the correct sequence of validation, DML, and error handling. All procedures should be invoked within the caller's transaction, as the package does not perform independent commits.