Search Results entity_value

Overview

The APPS.WMS_WP_EXCEPTIONS_GTMP_V view is a Warehouse Management System (WMS) reporting object shipped in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It exposes exception records generated by the warehouse planning and execution engine, providing a denormalized, read-oriented projection of the underlying global temporary table WMS_WP_EXCEPTIONS_GTMP. Its principal role is to surface warehouse execution exceptions — conditions that prevent or delay the release, planning, allocation, picking, packing, or shipping of material within a warehouse — to concurrent programs, dashboards, and integration interfaces.

The view does not store data. It is a pass-through projection whose content is governed by the lifecycle of the global temporary table beneath it. Consequently, the rows visible at any moment depend on the session that populated the temporary table, and the view is typically queried immediately after the planning or exception-generation process has run. For the user investigating entity_value, this view is the primary WMS surface where that attribute appears, linking an exception to the specific business entity it concerns.

Underlying Base Objects

Per the ETRM metadata, the view is defined over a single referenced base object: the synonym WMS_WP_EXCEPTIONS_GTMP, which resolves to the APPS-owned global temporary table of the same name. The view text is a straightforward SELECT of every column from that base object, with no joins, unions, or filters applied:

• Owner/Schema: APPS
• Object Type: VIEW, status VALID
• Referenced base object: WMS_WP_EXCEPTIONS_GTMP (SYNONYM)
• Product/Module: WMS – Warehouse Management

Because the base is a global temporary table, the view inherits on-commit or on-session delete semantics. Data is transient and scoped to the process that inserted the exception rows.

Key Columns

The view exposes twenty columns. Those most relevant to warehouse exception analysis include:

• EXCEPTION_ID / EXCEPTION_NAME: The unique identifier and human-readable name of the exception type.
• LOGGING_ENTITY / ENTITY_VALUE: The business entity type that the exception is logged against and the specific value (for example, a document number, item, order, or LPN) identifying the affected record. ENTITY_VALUE is the column most often queried when tracing an exception back to a concrete warehouse object.
• SEVERITY_LEVEL: Indicates the criticality of the exception, used to prioritize resolution.
• EXCEPTION_MESSAGE: Descriptive text explaining the condition.
• CREATION_DATE: Timestamp of exception generation.
• STATUS / READY_TO_RELEASE: Current processing state and release readiness.
• Lifecycle flags: BACKORDERED, CROSSDOCK_PLANNED, REPLENISHMENT_PLANNED, TASKED, PICKED, PACKED, STAGED, LOADED_TO_DOCK, and SHIPPED indicate where the associated material sits in the outbound execution flow.

Common Use Cases and Queries

Typical scenarios include monitoring exceptions blocking wave release, diagnosing backordered or crossdock-constrained lines, and integrating WMS exception data into external dashboards. The following queries illustrate common access patterns, including the entity_value search the user performed:

• List all current exceptions: SELECT exception_id, exception_name, severity_level, exception_message FROM wms_wp_exceptions_gtmp_v;
• Find exceptions for a specific entity value: SELECT exception_name, logging_entity, entity_value, exception_message FROM wms_wp_exceptions_gtmp_v WHERE entity_value = :entity_value;
• Identify high-severity release blockers: SELECT exception_id, entity_value, exception_message FROM wms_wp_exceptions_gtmp_v WHERE severity_level = 'HIGH' AND ready_to_release = 'N';
• Trace outbound progress: SELECT entity_value, tasked, picked, packed, staged, loaded_to_dock, shipped FROM wms_wp_exceptions_gtmp_v ORDER BY creation_date DESC;

Because the base object is a global temporary table, results are only meaningful within the session or transaction that populated it. Queries should therefore be executed in the context of the exception-generating concurrent request, and results should not be relied upon for persistent historical reporting.