Search Results trip_action




Overview

The APPS.WSH_TRIPS_PUB package is the public Trip Application Program Interface (API) within the Oracle E-Business Suite Oracle Transportation/Shipping Execution module (product code WSH). Its documented purpose is to expose a controlled, supported interface through which external and internal callers may create trips, update existing trips, and perform various business actions on trips without directly manipulating the underlying base tables. The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking schema, and it is classified in ETRM as a public (PUB) API, indicating it is intended for direct invocation by customer and partner code. The header identifies the package as an active, supported component (@rep:compatibility S) scoped to the WSH_TRIP business entity. In 12.1.1 and 12.2.2 the package forms part of the Shipping Execution trip management layer, abstracting the validation, defaulting, and persistence logic associated with trip records so that callers need not replicate that logic themselves.

Key Procedures and Functions

The ETRM metadata documents two public subprograms in this package, plus the package-level record type that accompanies them.

  • CREATE_UPDATE_TRIP — The primary transactional entry point. It handles both the creation of new trips and the update of existing ones in a single, consolidated call, distinguishing the operation based on the identifying attributes supplied in the trip record. On creation, it applies defaults and validations and inserts a new trip; on update, it validates and persists changes to an existing trip.
  • TRIP_ACTION — This is the procedure associated with the user's search term "trip_action". It performs business actions on an existing trip, such as the state or workflow transitions that a trip can undergo (for example, confirming, closing, or otherwise advancing a trip through its lifecycle). This procedure is the documented mechanism for acting on a trip after it exists, rather than modifying its descriptive attributes.
  • Trip_Pub_Rec_Type — A PL/SQL record type that serves as the common input/output structure for the API. It carries the trip identifier and name, sequencing information (ARRIVE_AFTER_TRIP_ID, ARRIVE_AFTER_TRIP_NAME), vehicle attributes, carrier and ship method details, routing information, and the standard ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTEn descriptive flexfield columns. Fields not supplied default to the standard FND_API.G_MISS_* sentinel values.

Tables Accessed

The documented table reference for this package is PLITBLM, accessed through an APPS synonym. PLITBLM is the standard Oracle Applications table used for temporary storage of batch records (commonly associated with interface/batch processing utilities). In the context of this API it supports the bulk handling of trip records passed into the API routines. Writes to the base trip table (WSH_TRIPS) and its related detail tables occur indirectly through the API's internal processing rather than being listed as direct documented references for this package.

Usage Notes

WSH_TRIPS_PUB is typically invoked from custom PL/SQL, wrapper packages, or integration code that needs to programmatically manage trips. Because it is a public API with @rep:scope public, it is the supported alternative to direct DML against the trip tables. The metadata records that the package is referenced by four other packages, indicating it is relied upon within the Shipping Execution stack as well as by customer extensions. Callers should populate a Trip_Pub_Rec_Type record, leave unspecified fields at their G_MISS defaults, and invoke CREATE_UPDATE_TRIP for inserts/updates or TRIP_ACTION to drive lifecycle transitions. Standard FND_API-style error and message handling should be expected, and callers should not implement their own validation of trip attributes.