Search Results mesg_sequence

Overview

WIP_SCHEDULING_EXCEPTIONS is a WIP (Work in Process) module table in the Oracle E-Business Suite 12.1.1 and 12.2.2 environments. It stores scheduling exceptions raised against discrete jobs during the scheduling process. When Oracle's scheduling engine evaluates a discrete job and detects a constraint, conflict, or informational condition, it records a row in this table containing the diagnostic message, its severity, and the manufacturing context in which it occurred. The table therefore acts as the persistent exception log for discrete job scheduling, enabling planners to review, mark, and act upon scheduling messages generated by the system.

From a dimensional modeling perspective, the mined foreign key structure suggests a satellite-leaning classification. The table carries descriptive, non-key transactional attributes — message text, severity, timestamps, and scheduling source — that describe the state of a scheduling event keyed to a parent discrete job entity. It is best modeled as a satellite hanging off the WIP_ENTITY (discrete job) hub, rather than as an independent hub or a link table. The primary key, WIP_SCHEDULING_EXCEPTIONS_PK, is a composite of WIP_ENTITY_ID and MESG_SEQUENCE, confirming that exceptions are uniquely identified only within the scope of a single discrete job.

Key Information Stored

The table contains 22 documented columns. The most significant are:

• WIP_ENTITY_ID — The discrete job identifier; part of the composite primary key and the principal join path to WIP_DISCRETE_JOBS.
• MESG_SEQUENCE — The message sequence number, forming the second component of the primary key. It distinguishes multiple exceptions raised against the same discrete job.
• ORGANIZATION_ID — The inventory organization under which the job and exception are recorded.
• MESSAGE_TEXT — The full text of the scheduling exception message displayed to the planner.
• MESSAGE_TYPE — The severity or classification of the message (for example, error, warning, or information).
• EXCEPTION_TYPE — A categorical code indicating the nature of the exception.
• SCHEDULING_SOURCE and SCHEDULING_SOURCE_ID — Identify the source mechanism that generated the exception.
• MARKED_FLAG — Indicates whether the user has flagged or acknowledged the exception.
• REPORTED_DATE — The date and time the exception was raised, central to aging and trend reporting.
• OPERATION_SEQ_NUM, RESOURCE_SEQ_NUM, RESOURCE_ID — Locate the exception to a specific routing operation and resource where applicable.
• INVENTORY_ITEM_ID — The item being manufactured by the discrete job.
• INSTANCE_ID and SERIAL_NUMBER — Carry component or serial context when the exception relates to a serialized item.
• SCHED_RELATIONSHIP_ID — The documented foreign key column, linking the exception to a scheduling relationship record.

The audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — are standard WHO columns present on nearly all EBS transactional tables.

Common Use Cases and Queries

The most frequent operational scenario is retrieving all current exceptions for a discrete job so a planner can triage scheduling problems. A representative query joins the exception table to the discrete job:

• SELECT wse.wip_entity_id, wse.mesg_sequence, wse.message_type, wse.message_text, wse.reported_date FROM wip.wip_scheduling_exceptions wse WHERE wse.wip_entity_id = :job_id ORDER BY wse.mesg_sequence;
• SELECT wdj.wip_entity_name, wse.message_type, COUNT(*) FROM wip.wip_scheduling_exceptions wse, wip.wip_discrete_jobs wdj WHERE wse.wip_entity_id = wdj.wip_entity_id GROUP BY wdj.wip_entity_name, wse.message_type;
• SELECT * FROM wip.wip_scheduling_exceptions WHERE organization_id = :org_id AND reported_date >= :start_date AND marked_flag = 'N';

Because MESG_SEQUENCE is a search term frequently associated with this table, queries filtering on that column are used to page through messages for a single job or to detect the highest sequence number issued. Trend reports aggregate exceptions by REPORTED_DATE, ORGANIZATION_ID, or EXCEPTION_TYPE to identify recurring shop-floor constraints. Acknowledgement workflows update MARKED_FLAG to suppress already-reviewed messages from planning dashboards.

Related Objects

The following objects are most significant in relation to WIP_SCHEDULING_EXCEPTIONS:

• WIP_DISCRETE_JOBS — Parent entity; joined on WIP_ENTITY_ID, supplying the job name and status.
• WIP_SCHEDULING_EXCEPTIONS_PK — The composite primary key constraint on (WIP_ENTITY_ID, MESG_SEQUENCE) that guarantees unique exception numbering per job.
• SCHED_RELATIONSHIP_ID foreign key target — The documented FK reference from SCHED_RELATIONSHIP_ID; depending on configuration this links the exception to the scheduling relationship definition that produced it.
• MTL_SYSTEM_ITEMS_B — Joined on INVENTORY_ITEM_ID to resolve item descriptions for reporting.
• BOM_RESOURCES — Joined on RESOURCE_ID to identify the constrained resource.
• WIP_OPERATIONS — Joined on WIP_ENTITY_ID and OPERATION_SEQ_NUM to place the exception on the routing.
• HR_ALL_ORGANIZATION_UNITS / ORG_ORGANIZATION_DEFINITIONS — Resolve ORGANIZATION_ID to a reporting organization name.
• WIP_SCHEDULING_EXCEPTIONS public views and the Discrete Job scheduler concurrent process — The scheduler populates this table; custom reports and DBI-style extracts typically read from it directly.

Because rows are keyed to a discrete job and sequenced by message, this table behaves as a dependent child of the discrete job across the scheduling lifecycle, and any purge or close-out of a job should account for its associated exception rows.