Search Results reported_date

Overview

WIP_SCHEDULING_EXCEPTIONS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Work in Process (WIP) product and exposes scheduling exceptions raised by the production scheduling engine when a discrete job cannot be scheduled as requested, or when scheduling produces a warning, error, or informational condition. The view consolidates scheduling exception rows from WIP_SCHEDULING_EXCEPTIONS with descriptive context drawn from the associated job, assembly, resource, and component records.

Because scheduling exceptions are frequently customer-visible problems—for example, an overloaded resource, a missing routing operation, or an infeasible completion date—this view is the primary supported interface for building exception reports, dashboards, and alert queries. Reporting tools such as Oracle Reports, BI Publisher, and custom concurrent programs query it rather than joining the base tables directly, which keeps business logic consistent across implementations.

Underlying Base Objects

The view is defined over six referenced objects: WIP_ENTITIES, WIP_DISCRETE_JOBS, WIP_SCHEDULING_EXCEPTIONS, MTL_SYSTEM_ITEMS_KFV (referenced twice through aliases MSI and MSI2), BOM_RESOURCES, and WIP_OPERATION_RESOURCES. All are accessed through synonyms.

WIP_ENTITIES is the driving entity table and is joined to WIP_DISCRETE_JOBS on WIP_ENTITY_ID and ORGANIZATION_ID, restricting the result set to discrete jobs. WIP_SCHEDULING_EXCEPTIONS supplies the exception itself, joined to WIP_ENTITIES on the same key pair. MTL_SYSTEM_ITEMS_KFV is joined twice: once on PRIMARY_ITEM_ID to resolve the assembly's concatenated segments and description, and once on WSE.INVENTORY_ITEM_ID to resolve the component. BOM_RESOURCES provides RESOURCE_CODE from RESOURCE_ID. WIP_OPERATION_RESOURCES is outer-joined on WIP_ENTITY_ID, OPERATION_SEQ_NUM, and RESOURCE_SEQ_NUM to supply the operation start date. The assembly, resource, component, and operation resource joins are all outer joins, so exception rows survive even when the secondary detail is absent.

Key Columns

• JOB_NAME / JOB_DESC: The WIP entity name and the discrete job description (WDJ.DESCRIPTION).
• ASSEMBLY / ASSEMBLY_DESC / PRIMARY_ITEM_ID: Concatenated segments, description, and internal ID of the primary assembly.
• SCHEDULING_SOURCE_TYPE / SCHEDULING_SOURCE_ID: The source that generated the exception and its identifier.
• MESG_SEQUENCE / MESSAGE_TYPE / MESSAGE_TEXT: Exception sequence number, its type (error, warning, or information), and the message text.
• MARKED_FLAG: Indicates whether the exception has been marked, typically for resolution or suppression.
• REPORTED_DATE: The date and time the scheduling exception was recorded. This is the most frequently filtered column and supports time-bounded exception reporting and aging analysis.
• STATUS_TYPE / SCHEDULED_COMPLETION_DATE / DUE_DATE / SCHEDULING_PRIORITY: Discrete job status and scheduling attributes.
• WIP_ENTITY_ID / ORGANIZATION_ID: Composite keys identifying the job and inventory organization.
• OPERATION_SEQ_NUM / RESOURCE_SEQ_NUM / RESOURCE_CODE / RESOURCE_ID: Operation and resource context for the exception.
• COMPONENT_NAME / COMPONENT_ID / INSTANCE_ID / SERIAL_NUMBER: Component and serial context when the exception relates to a specific component instance.
• START_DATE: Start date of the operation resource, sourced from WIP_OPERATION_RESOURCES.

Common Use Cases and Queries

A typical report lists unresolved scheduling exceptions for an organization within a date range, ordered by reporting time. Marked exceptions can be excluded with MARKED_FLAG.

SELECT job_name, assembly, message_type, message_text, reported_date
FROM apps.wip_scheduling_exceptions_v
WHERE organization_id = :org_id
AND reported_date BETWEEN :from_date AND :to_date
AND NVL(marked_flag, 'N') = 'N'
ORDER BY reported_date DESC;

Aggregate queries count exceptions by message type for a scheduling health dashboard, while joins to WIP_DISCRETE_JOBS on WIP_ENTITY_ID retrieve additional job attributes. Because the view already resolves concatenated item segments and resource codes, it can be used directly in BI Publisher data models and Oracle Alert definitions without additional lookup joins. Note that the view is read-only and intended for query access; it should not be used as the basis for DML.