Search Results schedule_number

Overview

The FLM_SEQ_TASK_EXCEPTIONS table is a core data object within the Oracle E-Business Suite Flow Manufacturing (FLM) module, specifically for versions 12.1.1 and 12.2.2. Its primary function is to log and store constraint violations that occur during the flow sequencing process. Flow sequencing is a critical manufacturing operation that determines the optimal order for building products on an assembly line based on defined constraints, such as material availability, resource capacity, and scheduling rules. When a sequencing task encounters a violation of these predefined constraints, the details of that violation are recorded in this table. This makes FLM_SEQ_TASK_EXCEPTIONS an essential diagnostic and audit table for troubleshooting scheduling failures, analyzing production bottlenecks, and ensuring the integrity of the sequencing engine's output.

Key Information Stored

The table captures the specific context of each sequencing violation. Its composite primary key uniquely identifies each exception record through a combination of five columns: LINE_ID, CONSTRAINT_NUMBER, EXCEPTION_TYPE, SCHEDULE_NUMBER, and SEQ_TASK_ID. The SCHEDULE_NUMBER is a particularly critical field, as it ties the exception to a specific production schedule or sequencing run, allowing users to analyze all violations for a particular scheduling instance. Other significant columns include ORGANIZATION_ID, which links the exception to a specific manufacturing organization, and the foreign key columns (SEQ_TASK_ID, CONSTRAINT_NUMBER, LINE_ID) that establish relationships to the source constraint definitions. The EXCEPTION_TYPE column categorizes the nature of the violation.

Common Use Cases and Queries

The primary use case is generating exception reports for production planners after a flow sequencing run. A common query pattern involves filtering by SCHEDULE_NUMBER and ORGANIZATION_ID to review all issues for a recent schedule. For example:

• Identifying all constraint violations for a specific schedule: SELECT * FROM flm_seq_task_exceptions WHERE schedule_number = &SCHED_NUM AND organization_id = &ORG_ID ORDER BY line_id, constraint_number;
• Analyzing the frequency of exception types to pinpoint recurring scheduling problems: SELECT exception_type, COUNT(*) FROM flm_seq_task_exceptions WHERE schedule_number = &SCHED_NUM GROUP BY exception_type;
• Joining with the constraint definition table (FLM_SEQ_TASK_CONSTRAINTS) to get descriptive details of the violated rules for a more comprehensive report.

Related Objects

FLM_SEQ_TASK_EXCEPTIONS has defined foreign key relationships with two other key tables in the Flow Manufacturing schema, as documented in the ETRM metadata.

• FLM_SEQ_TASK_CONSTRAINTS: This is the primary parent table. The relationship is defined on the columns SEQ_TASK_ID, CONSTRAINT_NUMBER, and LINE_ID. This join retrieves the detailed definition of the constraint that was violated.
• MTL_PARAMETERS (INV): A foreign key exists on the ORGANIZATION_ID column, linking the exception to the organization's inventory parameters, which provides context about the specific manufacturing entity.

These relationships are essential for constructing meaningful diagnostic reports that combine the exception log with descriptive master data from related manufacturing tables.