Results for “is_action_enabled”

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

Overview

WSH_TRIP_STOPS_VALIDATIONS is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, residing in the Shipping Execution (WSH) module. Its business purpose is to centralize the validation logic applied to trip stops — the individual stops that a trip or carrier route makes as it performs pickups and deliveries. Trip stops are represented by the WSH_TRIP_STOPS table, and this package enforces the business rules governing sequences, stop status, delivery eligibility, and stop closure. Because it is classified as an "OTHER" API type rather than a public interface, it functions primarily as an internal engine rather than a supported integration point.

The package is registered as VALID in the ETRM metadata, confirming that it compiles and is active. It plays a supporting role in the broader Shipping Execution flow: trip building, delivery assignment, and freight cost calculation all depend on stop-level integrity, and this package supplies the checks that keep stop data consistent.

Key Procedures and Functions

The ETRM metadata documents 13 procedures and functions. Their names indicate the validation domains covered:

• VALIDATE_SEQUENCE_NUMBER — Verifies that a stop's sequence number is valid within its trip.
• VALIDATE_CLOSED_STOP_SEQ — Checks sequencing rules for stops that have already been closed.
• VALIDATE_UNIQUE_SEQUENCE — Confirms that a stop sequence is unique, preventing duplicate ordering.
• CHECK_FOR_NEGATIVE_NUMBER — Rejects negative numeric values where only non-negative values are permitted.
• VALIDATE_STOP_STATUS — Validates that a stop status transition is permitted.
• VALID_DELIVERY_ON_TRIP — Determines whether a given delivery is valid for placement on a trip.
• GET_NEW_SEQUENCE_NUMBER — Returns the next appropriate sequence number for a new stop.
• IS_ACTION_ENABLED — Indicates whether a given stop action is currently enabled.
• GET_DISABLED_LIST — Returns the list of actions that are disabled for a stop context.
• INIT_STOP_ACTIONS_TBL — Initializes the internal table of stop actions used during validation.
• REFRESHSHIPMENTSTYPEFLAG — Refreshes the shipment-type flag associated with transport handling.
• GET_STOP_CLOSE_DATE — Retrieves the effective close date of a stop.
• CHECK_STOP_CLOSE — Confirms whether a stop may be closed given its current state.

No parameter lists are documented in the ETRM metadata, so signatures must be inspected in the database source.

Tables Accessed

The package reads and writes against several core Shipping Execution and order-management tables through APPS synonyms:

• WSH_TRIP_STOPS — The primary subject table; the package validates and updates stop records here.
• WSH_TRIPS — Supplies trip-level context for stop validation.
• WSH_DELIVERY_ASSIGNMENTS, WSH_DELIVERY_DETAILS, WSH_DELIVERY_LEGS, WSH_NEW_DELIVERIES — Used to determine whether a delivery is legitimately tied to a trip and leg.
• MTL_INTERORG_PARAMETERS — Provides inter-organization shipping setup used during validation.
• OE_ORDER_LINES_ALL and PO_REQUISITION_LINES_ALL — Source order and requisition lines underlying outbound and inbound deliveries.
• WSH_SHIPPING_PARAMETERS — Supplies system-level shipping configuration flags.
• PLITBLM — The standard Oracle PL/SQL table-index-by-binary-integer type used for in-memory collections.

Usage Notes

WSH_TRIP_STOPS_VALIDATIONS is referenced by eight other packages, including WSH_TRIP_STOPS_GRP, WSH_TRIP_STOPS_ACTIONS, WSH_TRIPS_ACTIONS, WSH_DELIVERIES_GRP, WSH_DELIVERY_LEGS_ACTIONS, WSH_DELIVERY_LEGS_PVT, WSH_FREIGHT_COSTS_GRP, and WSH_INBOUND_UTIL_PKG. Users searching for "wsh_trip_stops_grp" will find that this package is its principal validation dependency, meaning trip-stop group operations delegate their rule checking here. It is typically invoked indirectly from Shipping Execution forms — trip and stop maintenance windows — as well as from concurrent programs and custom code that manipulate trips, stops, or delivery legs. Because it is an internal "OTHER" classified package, customization should avoid calling it directly where a supported API exists; instead, developers should be aware of it as a dependency when troubleshooting validation errors during trip building, stop sequencing, or stop closure.