Results for “flm_seq_task_exceptions”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FLM.FLM_SEQ_TASK_EXCEPTIONS is a Flow Manufacturing (FLM) transactional table that stores constraint violations detected during flow sequencing of production lines. When the sequencing engine evaluates a flow schedule against the rules defined in FLM_SEQ_TASK_CONSTRAINTS, any rule that cannot be satisfied is recorded here as an exception row. Each record therefore represents a single sequencing rule breach associated with a specific flow schedule, line, task, and exception type.

The table resides in the FLM schema and is classified as VALID under both Oracle EBS 12.1.1 and 12.2.2. Its documented physical schema contains 18 columns, a composite primary key (FLM_SEQ_TASK_EXCEPTIONS_PK), and a unique business-key index (FLM_SEQ_TASK_EXCEPTIONS_U1). Based on the foreign-key topology — references to FLM_SEQ_TASK_CONSTRAINTS and MTL_PARAMETERS — the ETRM heuristic Data Vault classification is link. This suggests the table behaves as an associative entity connecting sequencing tasks, constraints, inventory organizations, and schedules, rather than as a pure reference or descriptive satellite.

Key Information Stored

The most operationally significant columns are:

• SEQ_TASK_ID — Identifier of the sequencing task that generated the exception; also part of the primary key and foreign key to FLM_SEQ_TASK_CONSTRAINTS.
• SEQ_EXCEPTION_NUMBER — Business-facing exception sequence number; combined with SEQ_TASK_ID it forms the unique business key FLM_SEQ_TASK_EXCEPTIONS_U1.
• EXCEPTION_TYPE — Categorizes the nature of the constraint violation; contributes to the composite primary key.
• LINE_ID — Production line on which the violation occurred; part of the primary key.
• CONSTRAINT_NUMBER — The constraint rule that was violated; references FLM_SEQ_TASK_CONSTRAINTS.
• SCHEDULE_NUMBER — The flow schedule against which sequencing was attempted; part of the primary key and the column most often used for targeted lookups.
• ORGANIZATION_ID — Inventory organization context; foreign key to MTL_PARAMETERS.
• VIOLATION_COUNT — Number of times the violation was observed for the task/constraint combination.
• OBJECT_VERSION_NUMBER — Optimistic locking token used by the OAF/BC4J layer.
• CREATED_BY / CREATION_DATE / LAST_UPDATED_BY / LAST_UPDATE_DATE — Standard WHO audit columns.
• REQUEST_ID / PROGRAM_ID / PROGRAM_APPLICATION_ID — Concurrent program context that produced the exception, useful for traceability back to the sequencing run.

Common Use Cases and Queries

Planners and shop-floor supervisors query this table to identify why a flow schedule failed sequencing. A typical filter is by schedule number:

• SELECT seq_exception_number, exception_type, line_id, constraint_number, violation_count FROM flm_seq_task_exceptions WHERE schedule_number = :p_schedule ORDER BY seq_exception_number;
• Joining to FLM_SEQ_TASK_CONSTRAINTS to retrieve rule descriptions for each violation.
• Joining to MTL_PARAMETERS to resolve the organization name for multi-org reporting.
• Aggregating VIOLATION_COUNT by EXCEPTION_TYPE to identify systemic constraint problems across lines.

Reporting use cases include exception dashboards for line balancing, root-cause analysis of repeated violations, and reconciliation of sequencing concurrent program output by REQUEST_ID.

Related Objects

• FLM_SEQ_TASK_CONSTRAINTS — Parent of SEQ_TASK_ID; defines the rule set that generated the exception.
• MTL_PARAMETERS — Referenced via ORGANIZATION_ID; provides organization context.
• FLM_SEQ_TASK_HEADERS / FLM_SEQ_TASKS — Parent sequencing task definition used to resolve task-level details.
• FLM_SCHEDULES / FLM_FLOW_SCHEDULES — Source of SCHEDULE_NUMBER for schedule-level reporting.
• FLM_LINES — Resolves LINE_ID to a line name.
• FND_CONCURRENT_REQUESTS — Links REQUEST_ID back to the sequencing concurrent request.