Results for “logged_at_location_id”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The APPS.WSH_EXCEPTIONS_V view is a denormalized reporting and integration object within the Oracle E-Business Suite Shipping Execution (WSH) module. It consolidates shipping exception records from the WSH_EXCEPTIONS base table with contextual data drawn from trips, trip stops, deliveries, delivery details, inventory items, locations, and exception definitions. Its principal role is to expose a flattened, human-readable representation of shipping exceptions that would otherwise require multi-table joins to assemble. Because it resolves lookup codes, replaces internal status synonyms with normalized values, and enriches records with organizational, location, and item context, the view serves as the primary access point for exception dashboards, alerting programs, and downstream integrations in EBS 12.1.1 and 12.2.2. It is owned by the APPS schema and carries a VALID status in the ETRM repository.
Underlying Base Objects
Documented base objects referenced by the view are: WSH_EXCEPTIONS (synonym), WSH_EXCEPTION_DEFINITIONS_V (view), WSH_TRIP_STOPS (synonym), WSH_LOCATIONS (synonym, joined three times as WLO, WLAL, and WSL for exception, logged-at, and stop locations), HR_LOCATIONS_ALL (synonym), HR_ORGANIZATION_INFORMATION (synonym), MTL_PARAMETERS (synonym), and the WSH_XC_UTIL package. WSH_EXCEPTIONS supplies the primary rows, including exception identifiers, severity, status, and the departure_date and arrival_date fields central to trip stop timing. WSH_TRIP_STOPS provides STOP_LOCATION_ID and STOP_SEQUENCE_NUMBER, linking exceptions to specific stops on a trip. WSH_EXCEPTION_DEFINITIONS_V supplies the exception description and exception type. WSH_XC_UTIL.GET_LOOKUP_MEANING resolves lookup meanings for logging entity and severity behavior. MTL_PARAMETERS yields ORGANIZATION_ID and ORGANIZATION_CODE, while HR_LOCATIONS_ALL and HR_ORGANIZATION_INFORMATION support organization and location resolution.
Key Columns
- EXCEPTION_ID, EXCEPTION_NAME, DESCRIPTION – Unique identifier, functional name, and descriptive text of the exception.
- DEPARTURE_DATE and ARRIVAL_DATE – Planned or actual departure and arrival timestamps associated with the trip stop, used for transit exception analysis.
- LOGGING_ENTITY, LOGGING_ENTITY_ID – The entity type that generated the exception (with lookup meaning) and its identifier.
- SEVERITY – Decoded to ERROR, WARNING, or INFO from the underlying HIGH, MEDIUM, or LOW values.
- STATUS – Normalized to OPEN or NO_ACTION_REQUIRED from internal values such as MANUAL, LOGGED, IN_PROCESS, ERROR, and NOT_HANDLED.
- TRIP_ID, TRIP_NAME, TRIP_STOP_ID, STOP_SEQUENCE_NUMBER – Trip and stop context for the exception.
- DELIVERY_ID, DELIVERY_NAME, DELIVERY_DETAIL_ID, DELIVERY_ASSIGNMENT_ID – Delivery and line-level association.
- ORGANIZATION_ID, ORGANIZATION_CODE – Inventory organization context from MTL_PARAMETERS.
- INVENTORY_ITEM_ID, LOT_NUMBER, REVISION, SERIAL_NUMBER, QUANTITY, UNIT_OF_MEASURE – Item and quantity detail.
- EXCEPTION_LOCATION_ID, LOGGED_AT_LOCATION_ID and related UI_LOCATION_CODE columns – Location codes resolved through WSH_LOCATIONS.
- MESSAGE, ERROR_MESSAGE, MANUALLY_LOGGED – Diagnostic text and origin flag.
Common Use Cases and Queries
Typical scenarios include monitoring high-severity exceptions by organization and reporting trip stop departure delays. A representative query retrieving open, high-severity exceptions with departure timing is shown below:
SELECT exception_id,
exception_name,
severity,
status,
trip_name,
delivery_name,
departure_date,
organization_code
FROM apps.wsh_exceptions_v
WHERE status = 'OPEN'
AND severity = 'ERROR'
ORDER BY departure_date DESC;
Analysts commonly filter on TRIP_ID or DELIVERY_ID to trace exceptions for a specific shipment, and aggregate counts by ORGANIZATION_CODE for exception trending. Because DEPARTURE_DATE is exposed directly, the view supports transit-time reporting and alert programs that compare departure and arrival timestamps.
-
View: WSH_EXCEPTIONS_V 12.1.1
APPS.WSH_EXCEPTIONS_V·↳ HR_LOCATIONS_ALL·↳ HR_ORGANIZATION_INFORMATION·↳ MTL_PARAMETERS·Explore WSH module →
-
View: WSH_EXCEPTIONS_DLVY_V 12.2.2
APPS.WSH_EXCEPTIONS_DLVY_V·↳ FND_LOOKUP_VALUES·↳ HR_LOCATIONS_ALL·↳ MTL_PARAMETERS·Explore WSH module →
-
Shipping Exceptions
-
Shipping Exceptions
-
View: WSH_EXCEPTIONS_V 12.2.2
APPS.WSH_EXCEPTIONS_V·↳ HR_LOCATIONS_ALL·↳ HR_ORGANIZATION_INFORMATION·↳ MTL_PARAMETERS·Explore WSH module →
-
View: WSH_EXCEPTIONS_DLVY_V 12.1.1
APPS.WSH_EXCEPTIONS_DLVY_V·↳ FND_LOOKUP_VALUES·↳ HR_LOCATIONS_ALL·↳ MTL_PARAMETERS·Explore WSH module →
-
VIEW: WSH.WSH_EXCEPTIONS# 12.2.2
-
VIEW: APPS.WSH_EXCEPTIONS_V 12.2.2
-
TABLE: WSH.WSH_EXCEPTIONS 12.2.2
-
VIEW: WSH.WSH_EXCEPTIONS# 12.2.2
-
TABLE: WSH.WSH_EXCEPTIONS 12.1.1
-
VIEW: APPS.WSH_EXCEPTIONS_V 12.1.1
-
PACKAGE: APPS.WSH_XC_UTIL 12.2.2
-
PACKAGE: APPS.WSH_XC_UTIL 12.1.1