Results for “wsh_trip_validations”

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

Overview

WSH_TRIP_VALIDATIONS is an Oracle EBS Logistics (Shipping Execution) validation package owned by the APPS schema. It encapsulates the business rules that govern state transitions on a trip within the Transportation and Shipping Execution module. Its core purpose is to verify that the pre-requisites for a requested action — planning, unplanning, closing, deleting, carrier change, stop arrival or closure, and trip assignment — have been satisfied before the action is permitted to proceed. Each procedure returns an outcome status through a standard x_return_status out parameter so that the calling form, workflow, or API can decide whether to continue, warn, or halt. The package is a documented, API-classified object (classified as OTHER rather than a public business API) and is referenced by thirteen other packages, indicating that it functions as a shared validation service across the Shipping Execution code base in both 12.1.1 and 12.2.2.

Key Procedures and Functions

The package exposes twenty-four documented procedures and functions. The procedures most relevant to trip action control include:

• CHECK_PLAN — Verifies planning pre-requisites: at least two stops are assigned, vehicle or ship method information is present, and stop sequences are valid. It issues warnings if the vehicle is over- or under-filled at any stop and if no delivery is assigned. Planning also triggers recalculation of weight and volume for stops and deliveries when not already specified.
• CHECK_UNPLAN — The procedure returned by the search term "check_unplan". It validates the pre-requisites for unplanning a trip: the trip status must not be CLOSED, and the trip must in fact be planned.
• CHECK_TRIP_CLOSE — Confirms the trip status is OPEN or IN-TRANSIT and, for IN-TRANSIT trips, warns unless the last stop is ARRIVED or CLOSED.
• CHECK_TRIP_DELETE, CHECK_STOP_DELETE, CHECK_STOP_ARRIVE, CHECK_STOP_CLOSE — Validate the corresponding delete, arrival, and closure actions on trips and stops.
• CHECK_CHANGE_CARRIER, CHECK_ASSIGN_TRIP, CHECK_CLOSE, CHECK_INTRANSIT — Validate carrier changes, trip assignment, and close/in-transit related transitions.
• VALIDATE_PLANNED_TRIP, VALIDATE_ARRIVE_AFTER_TRIP, VALIDATE_CONSOL_ALLOWED — Perform cross-cutting checks on planned trips, arrival sequencing, and consolidation eligibility.
• IS_ACTION_ENABLED, GET_DISABLED_LIST, INIT_TRIP_ACTIONS_TBL — Determine which trip actions are permitted for a given trip and initialize the internal action table used by the validation and UI layers.
• GET_TRIP_CALC_WTVOL, HAS_OUTBOUND_DELIVERIES, HAS_INBOUND_DELIVERIES — Utility functions returning calculated trip weight/volume and delivery direction indicators used by the validation logic.

Tables Accessed

WSH_TRIP_VALIDATIONS reads and in limited cases writes the following documented tables, accessed through APPS synonyms:

• WSH_TRIPS — the primary entity being validated; its status and planning flags drive nearly every check.
• WSH_TRIP_STOPS — supplies stop count, stop sequence, and stop status used by CHECK_PLAN, CHECK_TRIP_CLOSE, and stop-level validations.
• WSH_DELIVERY_LEGS and WSH_NEW_DELIVERIES — used to establish which deliveries are attached to the trip and to support inbound/outbound delivery checks.
• WSH_FREIGHT_COSTS — consulted during planning and carrier-related validation because freight cost data is recalculated on planning.
• WSH_SHIPPING_PARAMETERS — provides Shipping Execution profile/setup values that influence whether an action is permitted.
• MTL_SYSTEM_ITEMS — supplies item attributes used in weight/volume and delivery validation.
• DUAL and PLITBLM — used for single-row selection and PL/SQL table management supporting the action table and disabled-list logic.

Usage Notes

WSH_TRIP_VALIDATIONS is normally invoked indirectly rather than called directly by end users. In the Shipping Execution forms (for example the Trip and Stop maintenance and Trip Planning windows), the form's pre-action triggers call the appropriate CHECK_* procedure before executing the underlying action, and use the returned status to enable or disable buttons and to raise warnings. Given that the package is referenced by thirteen other packages, it is also a common dependency of workflow activities, concurrent programs, and other Shipping Execution packages that need a consistent enforcement point for trip state rules. Customizations and extensions that manipulate trips programmatically should call the matching validation routine before performing the action, and should honor both error and warning outcomes returned through x_return_status; bypassing these checks risks corrupting trip status, stop sequences, and freight cost data. Because the object is classified as OTHER rather than a committed public API, its signature should be treated as internal and subject to change between releases.