Search Results planned_completion

Overview

APPS.GMP_SCHEDULING_EXCEPTIONS_V is a process manufacturing (OPM) reporting view in Oracle E-Business Suite that consolidates scheduling exception messages raised against production batches. In Oracle Process Manufacturing, the scheduling engine evaluates batch requirements against resource capacity, material availability, and routing constraints, and emits exceptions whenever a batch cannot be scheduled as planned. This view surfaces those exceptions together with the batch header context — assembly, organization, planned dates, required completion, and scheduling priority — so that planners can review, triage, and act on scheduling conflicts from a single queryable structure.

The view is relevant to both 12.1.1 and 12.2.2; in 12.2.2 it is owned by APPS and resolves the same logical structure. It plays a dual role: as a reporting object for scheduling exception dashboards and concurrent programs, and as an integration surface for custom inquiries or downstream extracts that need to correlate exception messages with batch and item attributes. Because the view joins the exception table directly to the batch header, it exposes a denormalized, planner-friendly picture without requiring the caller to reconstruct the relationships manually.

Underlying Base Objects

The view is defined over five documented base objects, all referenced as APPS synonyms:

• WIP_SCHEDULING_EXCEPTIONS — the fact table holding individual exception messages, their scheduling source, sequence, type, and reported date.
• GME_BATCH_HEADER — the process batch master, supplying batch number, status, planned start/completion, due date, priority, and recipe/routing identifiers.
• GMD_RECIPE_VALIDITY_RULES — the recipe validity rule linking an inventory item to a batch's formula/recipe context.
• MTL_SYSTEM_ITEMS_KFV — the key-flexfield item view providing concatenated segments, description, and inventory item identifier for the assembly.
• MTL_PARAMETERS — organization parameters, used to restrict results to process-enabled organizations.

The joins are driven by WIP_ENTITY_ID = BATCH_ID, with supporting joins on organization, inventory item, and recipe validity rule. The view filters on GBH.DELETE_MARK = 0 and MP.PROCESS_ENABLED_FLAG = 'Y' so that only active batches in process-enabled organizations are returned.

Key Columns

• JOB_NAME (GBH.BATCH_NO) — the batch number identifying the production job (also referred to as job_name in the view alias).
• ORGANIZATION_CODE — the process organization in which the batch resides.
• ASSEMBLY / ASSEMBLY_DESC / PRIMARY_ITEM_ID — the concatenated item key, description, and internal inventory item identifier for the batch assembly.
• SCHEDULING_SOURCE / SCHEDULING_SOURCE_ID — the origin of the scheduling exception, letting users trace which scheduling process raised it.
• MESG_SEQUENCE / MESSAGE_TYPE / REPORTED_DATE — the sequence, classification, and timestamp of each exception message.
• BATCH_STATUS — current status of the batch (for example, released, pending, or cancelled).
• PLANNED_START (GBH.PLAN_START_DATE) and PLANNED_COMPLETION (GBH.PLAN_CMPLT_DATE) — the scheduled start and completion dates for the batch. The user's search term, "planned_completion", maps to this column — GBH.PLAN_CMPLT_DATE aliased as PLANNED_COMPLETION.
• REQUIRED_COMPLETION (GBH.DUE_DATE) — the due date by which the batch must complete.
• SCHEDULING_PRIORITY (GBH.PRIORITY_VALUE) — the priority assigned to the batch for scheduling purposes.
• WIP_ENTITY_ID, ORGANIZATION_ID, RECIPE_VALIDITY_RULE_ID, ROUTING_ID, FORMULA_ID — supporting identifiers that allow further drill-down into the batch's routing, formula, and recipe configuration.

Common Use Cases and Queries

Typical use cases include scheduling exception worklists, batch slippage analysis, and comparison of planned versus required completion dates. A representative query retrieving exceptions with their planned and required completion dates is:

SELECT job_name, organization_code, assembly, batch_status, planned_completion, required_completion, scheduling_priority, message_type, reported_date FROM apps.gmp_scheduling_exceptions_v WHERE planned_completion > required_completion ORDER BY organization_code, planned_completion;

This identifies batches whose planned completion falls after the required completion — a clear indicator of potential schedule slippage. A variant restricting to a single organization and item supports focused planning reviews:

SELECT job_name, assembly, planned_start, planned_completion, required_completion, message_type FROM apps.gmp_scheduling_exceptions_v WHERE organization_code = :org AND primary_item_id = :item AND reported_date >= SYSDATE - 30;

Because the view filters to process-enabled organizations and non-deleted batches, it can be queried directly in reports, concurrent programs, or custom OAF pages without additional filtering. Where the metadata is silent on exact message-type codes and status meanings, those values should be confirmed against the WIP_SCHEDULING_EXCEPTIONS and GME_BATCH_HEADER reference data in the target environment.