Search Results scheduling_source_type

Overview

APPS.WIP_SCHEDULING_EXCEPTIONS_V is a read-only database view owned by the APPS schema and registered in Oracle E-Business Suite under FND Design Data WIP.WIP_SCHEDULING_EXCEPTIONS_V. The object is classified as an internal view with a VALID status, and Oracle explicitly warns that access to applications data through this object should occur only from standard Oracle Applications programs rather than from customer-written code. Functionally, the view consolidates scheduling exception information raised against discrete jobs in Oracle Work in Process, joining each exception message to the affected job, assembly, operation, resource, and component context. This makes it a single denormalized source for messages such as resource overloads, material shortages, and priority or date conflicts generated during scheduling activities.

The view surfaces descriptive attributes from the parent job and item records alongside the exception text, status, and reporting metadata. Because it resolves many of the foreign keys into human-readable names, it is convenient for reporting and diagnostic queries, though its internal designation means it is not a supported integration interface.

Underlying Base Objects

The documented dependency list identifies six base objects referenced by the view, all exposed to APPS through synonyms: WIP_SCHEDULING_EXCEPTIONS, WIP_ENTITIES, WIP_DISCRETE_JOBS, WIP_OPERATION_RESOURCES, BOM_RESOURCES, and MTL_SYSTEM_ITEMS_KFV. WIP_SCHEDULING_EXCEPTIONS is the primary driving table, supplying the exception rows themselves, including message identifiers, message text, status, marking, and reported dates. WIP_ENTITIES provides the header-level work order identity and organization context, while WIP_DISCRETE_JOBS supplies job-specific attributes such as job name, scheduled completion, and due dates. WIP_OPERATION_RESOURCES links exceptions to specific routing operations and resource assignments, and BOM_RESOURCES resolves the resource code and identifier. MTL_SYSTEM_ITEMS_KFV supplies the descriptive flexfield-aware item concatenations for the assembly and, in material exceptions, the component.

Key Columns

• SCHEDULING_SOURCE_TYPE and SCHEDULING_SOURCE_ID — classify the origin and identity of the scheduling source that produced the exception, allowing consumers to distinguish the type of scheduling driver involved.
• JOB_NAME, JOB_DESC, ASSEMBLY, ASSEMBLY_DESC, PRIMARY_ITEM_ID — identify the discrete job and its primary assembly.
• MESG_SEQUENCE, MESSAGE_TYPE, MESSAGE_TEXT — the exception message number, category, and rendered text.
• MARKED_FLAG, REPORTED_DATE, STATUS_TYPE — user marking, creation timestamp, and current exception status.
• SCHEDULED_COMPLETION_DATE, DUE_DATE, SCHEDULING_PRIORITY — scheduling dates and priority driving the exception.
• WIP_ENTITY_ID, ORGANIZATION_ID, OPERATION_SEQ_NUM, RESOURCE_SEQ_NUM, RESOURCE_CODE, RESOURCE_ID — job, organization, operation, and resource context.
• COMPONENT_NAME, COMPONENT_ID, INSTANCE_ID, SERIAL_NUMBER, START_DATE — component-level material exception detail and serial control.

Common Use Cases and Queries

Typical usage centers on exception reporting and troubleshooting. Planners query unresolved exceptions for a given organization or job, filtering on STATUS_TYPE or MARKED_FLAG, while integration teams may inspect SCHEDULING_SOURCE_TYPE to categorize exception origins. A representative query follows:

• SELECT ORGANIZATION_ID, JOB_NAME, ASSEMBLY, SCHEDULING_SOURCE_TYPE, MESSAGE_TEXT, REPORTED_DATE, STATUS_TYPE FROM APPS.WIP_SCHEDULING_EXCEPTIONS_V WHERE ORGANIZATION_ID = :org_id AND STATUS_TYPE = :status ORDER BY REPORTED_DATE DESC;
• Resource-focused analysis joins on RESOURCE_CODE and OPERATION_SEQ_NUM to isolate capacity-driven exceptions.
• Material analysis filters rows where COMPONENT_ID is not null to obtain shortage exceptions by component.

Because the view is flagged for Oracle internal use only, production queries should be confined to supported interfaces where possible.