Results for “is_valid_consol”
16 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
WSH_FTE_COMP_CONSTRAINT_GRP is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema, classified under the FTE (Freight and Transportation Execution) subsystem of Oracle Shipping Execution. In ETRM terms it is flagged as an API classification of GRP (group), signalling that it acts as an aggregation or coordination layer rather than as a standalone transactional API. Its role is to evaluate and enforce compatibility constraints on the grouping of delivery assignments, delivery legs, trips, and trip stops that are being consolidated into a single freight or transportation execution unit. In effect, the package answers the business question: may these candidate shipments be legally grouped together under the same trip or consolidation context? It is used in the broader constraint-validation framework that governs trip building and freight consolidation, ensuring that capacity, compatibility, and configuration rules are honoured before the shipping transaction commits. The package body carries a VALID status in ETRM 12.1.1 and 12.2.2 and is not referenced by any other database object, indicating it is invoked as a top-level validation entry point.
Key Procedures and Functions
Two documented procedures are exposed by this package:
- VALIDATE_CONSTRAINT — the principal validation routine. It is invoked to test whether a proposed grouping of deliveries, legs, trips, or stop combinations satisfies the active constraint definitions. It coordinates calls to subordinate logic and returns constraint-evaluation results through the standard EBS message stack. It relies on FND_API, FND_MESSAGE, and FND_MSG_PUB for error and message handling, and on WSH_DEBUG_SV for debugging output.
- IS_VALID_CONSOL — a supporting check that determines whether a given consolidation context is valid. It is typically called by VALIDATE_CONSTRAINT or by the WSH_FTE_COMP_CONSTRAINT_PKG and WSH_FTE_CONSTRAINT_FRAMEWORK packages to short-circuit validation when the consolidation grouping is already known to be acceptable or rejectable.
The package delegates detailed rule evaluation to WSH_FTE_COMP_CONSTRAINT_PKG and WSH_FTE_CONSTRAINT_FRAMEWORK, and uses WSH_UTIL_CORE for shared utility routines. No parameter signatures are documented in ETRM, so callers should consult the package specification.
Tables Accessed
The package operates against the following documented tables, referenced via APPS synonyms:
- WSH_NEW_DELIVERIES — the base delivery header, supplying the deliveries under evaluation for grouping.
- WSH_DELIVERY_ASSIGNMENTS — links deliveries to their assigned trip or group, used to determine existing grouping membership.
- WSH_DELIVERY_LEGS — provides routing legs so that stop and sequence compatibility can be assessed.
- WSH_TRIPS — the trip header that a consolidation would attach to, checked for compatibility with the candidate deliveries.
- WSH_TRIP_STOPS — the individual stops within a trip, used by VALIDATE_CONSTRAINT and IS_VALID_CONSOL for stop-level constraint evaluation.
- PLITBLM — a PL/SQL index-by table type used internally for in-memory collections.
Usage Notes
WSH_FTE_COMP_CONSTRAINT_GRP is typically invoked indirectly rather than through a user-facing form. It is called from the trip-building and delivery-consolidation flows within Oracle Shipping Execution, from the WSH_FTE_COMP_CONSTRAINT_PKG and WSH_FTE_CONSTRAINT_FRAMEWORK packages, and potentially from custom extensions that need to validate a candidate consolidation before committing a trip or grouping. Because it depends on FND_API and FND_MSG_PUB, any custom caller must correctly initialise and interrogate the message stack to interpret results. Custom code should call the package only through its published specification and should not modify the body. Debugging traces can be obtained via WSH_DEBUG_SV when FND debug is enabled.