Search Results wip_schedule_groups




Overview
Explore in AI Chat

Overview

The WIP_SCHEDULE_GROUPS table is a core data object within the Oracle E-Business Suite Work in Process (WIP) module. It serves as the master repository for discrete job schedule groups. In manufacturing execution, a schedule group is a logical classification used to collect and manage discrete jobs for common operational purposes, such as scheduling, releasing, or prioritizing work orders on the shop floor. This table provides the foundational definition for these groups, enabling planners to organize production workloads efficiently. Its existence is critical for the sequencing and dispatch of manufacturing tasks, particularly when integrated with advanced shop floor control systems.

Key Information Stored

While the provided ETRM metadata specifies the primary key, the core column defining a schedule group is SCHEDULE_GROUP_ID. This unique numeric identifier is the primary key for the table (WIP_SCHEDULE_GROUPS_PK). Standard implementation suggests the table would also contain columns such as SCHEDULE_GROUP_NAME for the user-defined identifier, a DESCRIPTION field, and standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE). The SCHEDULE_GROUP_ID is the critical piece of data referenced by other entities, such as discrete jobs and sequencing tasks, to associate them with a specific scheduling cohort.

Common Use Cases and Queries

The primary use case is the reporting and management of jobs belonging to a specific schedule group for release or priority sequencing. A common query involves joining WIP_SCHEDULE_GROUPS to the primary discrete jobs table (WIP_DISCRETE_JOBS) to list all jobs in a given group. Another critical scenario, directly indicated by the foreign key relationship, involves querying the link between shop floor sequencing tasks and their assigned schedule group for detailed line scheduling. A sample SQL pattern to find all schedule groups and a count of associated jobs would be:

  • SELECT ws.SCHEDULE_GROUP_NAME, COUNT(wdj.WIP_ENTITY_ID) AS JOB_COUNT
  • FROM WIP.WIP_SCHEDULE_GROUPS ws
  • LEFT JOIN WIP.WIP_DISCRETE_JOBS wdj ON ws.SCHEDULE_GROUP_ID = wdj.SCHEDULE_GROUP_ID
  • GROUP BY ws.SCHEDULE_GROUP_NAME;

Related Objects

The WIP_SCHEDULE_GROUPS table maintains defined relationships with other key manufacturing tables. As documented in the provided metadata, it is referenced by the FLM_SEQ_TASKS table via a foreign key. This relationship (FLM_SEQ_TASKS.SCHEDULE_GROUP_ID → WIP_SCHEDULE_GROUPS.SCHEDULE_GROUP_ID) is fundamental for connecting detailed sequencing tasks from the Flow Manufacturing module to higher-level schedule groups. Furthermore, while not listed in the brief excerpt, the table has a primary relationship with the WIP_DISCRETE_JOBS table, where the SCHEDULE_GROUP_ID column is a foreign key, linking each discrete job to its assigned schedule group for management and reporting.