Results for “check_assign_trip”

18 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.WSH_TRIP_VALIDATIONS package body encapsulates the business-rule validation layer for trip management within Oracle E-Business Suite's Warehouse Management (WSH) module. In both Release 12.1.1 and 12.2.2, a "trip" represents a logical grouping of deliveries assigned to a single carrier and vehicle movement, forming the unit against which freight costs, stops, and delivery legs are managed. Before any change in trip state — planning, unplanning, carrier reassignment, stop arrival, trip closure, or deletion — the system must confirm that the action is permissible given the current status of the trip and its dependent deliveries.

WSH_TRIP_VALIDATIONS centralizes these checks so that the UI (Trip Planning and Carrier forms), the public WSH_TRIPS_PVT and WSH_TRIP_STOPS_PVT APIs, and concurrent processes all enforce identical rules. The package is classified as API type OTHER and references a broad set of WSH, FND, and MTL objects, reflecting its role as a cross-cutting validation utility rather than a standalone business API.

Key Procedures and Functions

The ETRM metadata documents 24 procedures and functions. The principal entries are:

Tables Accessed

Via APPS synonyms, the package reads and writes: WSH_TRIPS (trip header and status), WSH_TRIP_STOPS (stop sequencing), WSH_DELIVERY_LEGS (leg-to-trip association), WSH_NEW_DELIVERIES (delivery status and assignment), WSH_FREIGHT_COSTS (freight charge records affecting closure/deletion), WSH_SHIPPING_PARAMETERS (profile-driven behavior), MTL_SYSTEM_ITEMS (item attributes for weight/volume), and DUAL/PLITBLM for single-row queries and PL/SQL index-by table support. It also depends on FND_API, FND_MESSAGE, FND_DATE, and the WSH_DEBUG_SV/WSH_DEBUG_INTERFACE utilities for error handling and diagnostics.

Usage Notes

WSH_TRIP_VALIDATIONS is not intended as a public integration API. It is invoked internally by WSH_TRIPS_PVT, WSH_TRIP_STOPS_PVT, WSH_DELIVERY_VALIDATIONS, and the Trip Planning forms to render action buttons as enabled or disabled and to enforce rules server-side. The presence of INIT_TRIP_ACTIONS_TBL and IS_ACTION_ENABLED indicates a pattern where the form first populates an action table and then queries it to drive UI state. Customizations should call the public WSH_TRIPS_PVT APIs rather than this package directly; because it is referenced by 13 other packages but references no external callers, it functions strictly as an internal validation service. Any modification risks widespread side effects across trip, stop, and delivery processing.