Search Results gmp_scheduling_exceptions_v

Overview

GMP_SCHEDULING_EXCEPTIONS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, residing in the Process Manufacturing Process Planning (GMP) product family. It exposes scheduling exceptions raised against Oracle Process Manufacturing (OPM) batches, joining exception records to batch header, item, and organization context so that planners and schedulers can diagnose why a batch cannot be scheduled as intended. The view carries a VALID status in ETRM for both 12.1.1 and 12.2.2, and its definition is identical across those releases.

The object presents one row per scheduling exception message, enriched with the batch number, organization, primary assembly, planned and required dates, scheduling priority, and the associated recipe, routing, and formula identifiers. Because it surfaces messages originating from the work in process scheduling engine, it is commonly reached by users searching for wip_scheduling_exceptions — the base table that the OPM-specific view wraps and filters.

Underlying Base Objects

The view is defined over five referenced objects, all accessed through APPS synonyms:

• WIP_SCHEDULING_EXCEPTIONS — the source of exception messages, message sequencing, message type, reported date, scheduling source, and WIP entity identifier.
• GME_BATCH_HEADER — the OPM batch master, supplying batch number, status, planned start, planned completion, due date, priority, and the delete marker.
• GMD_RECIPE_VALIDITY_RULES — linked on RECIPE_VALIDITY_RULE_ID to resolve the recipe and its inventory item.
• MTL_SYSTEM_ITEMS_KFV — the concatenated item key flexfield view, providing assembly, assembly description, primary item identifier, and organization.
• MTL_PARAMETERS — organization parameters, used to restrict results to process-enabled organizations.

Joins are performed on WIP_ENTITY_ID = BATCH_ID, ORGANIZATION_ID across batch header, items, and parameters, and on RECIPE_VALIDITY_RULE_ID combined with INVENTORY_ITEM_ID between the batch header and the recipe validity rules. The predicate GBH.DELETE_MARK = 0 excludes soft-deleted batches, and MP.PROCESS_ENABLED_FLAG = 'Y' excludes non-process inventory organizations, ensuring only genuine OPM batches appear.

Key Columns

• JOB_NAME — the OPM batch number, aliased from GME_BATCH_HEADER.BATCH_NO.
• ORGANIZATION_CODE / ORGANIZATION_ID — the process organization owning the batch.
• ASSEMBLY / ASSEMBLY_DESC / PRIMARY_ITEM_ID — the primary product item and its description.
• SCHEDULING_SOURCE / SCHEDULING_SOURCE_ID — the entity that generated the exception.
• MESG_SEQUENCE / MESSAGE_TYPE / REPORTED_DATE — exception message ordering, classification, and timestamp.
• BATCH_STATUS — current status of the OPM batch.
• PLANNED_START / PLANNED_COMPLETION / REQUIRED_COMPLETION — planned start and completion dates and the required (due) completion date.
• SCHEDULING_PRIORITY — priority value carried from the batch header.
• WIP_ENTITY_ID — the WIP entity key linking the exception to the batch.
• RECIPE_VALIDITY_RULE_ID / ROUTING_ID / FORMULA_ID — identifiers for the recipe validity rule, routing, and formula governing the batch.

Common Use Cases and Queries

Typical usage includes exception dashboards, root-cause analysis for unschedulable batches, and integration extracts feeding planning or MES systems. Filtering by organization and message type is common, as is restricting to batches whose required completion date is imminent.

• Listing all current exceptions for a process organization, ordered by scheduling priority and required completion.
• Identifying batches with specific message types to determine whether a recipe, routing, or formula issue is blocking scheduling.
• Extracting batch, assembly, and date information for downstream planning reconciliation.

Sample query:

• SELECT job_name, organization_code, assembly, message_type, reported_date, batch_status, planned_start, required_completion, scheduling_priority FROM apps.gmp_scheduling_exceptions_v WHERE organization_code = :org ORDER BY scheduling_priority, required_completion;

Because the view is read-only and defined only over documented OPM and WIP tables, it is safe for custom reporting and integration use without affecting transactional processing.