Results for “flm_seq_task_constraints”

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

Overview

FLM_SEQ_TASK_CONSTRAINTS is a Flow Manufacturing (FLM) transactional table in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to store the flow sequencing constraint information associated with a flow sequencing task. In event-driven sequencing operations, constraints define the rules that govern how lines are ordered, prioritized, and validated before the sequencing engine produces a workable sequence. Each row therefore represents a single constraint instance attached to a sequencing task and, where applicable, to a specific sequencing line.

The table is owned by the FLM schema and is reported as VALID. It contains 29 documented columns, with the primary key FLM_SEQ_TASK_CONSTRAINTS_PK defined on the composite of LINE_ID, CONSTRAINT_NUMBER, and SEQ_TASK_ID. A unique index, FLM_SEQ_TASK_CONSTRAINTS_U1 on (SEQ_TASK_ID, LINE_ID, CONSTRAINT_NUMBER), serves as the documented business-key candidate and enforces uniqueness of a constraint per task and line.

Heuristic Data Vault classification of this object is satellite-leaning. This suggests that, in a dimensional or Data Vault model, the table is best treated as descriptive context hanging off a sequencing task hub or link rather than as an independent business entity, since its rows carry attribute detail, status, and audit columns tied to a parent sequencing task and line.

Key Information Stored

The most significant columns fall into identification, classification, attribute value, and fulfillment groupings.

• SEQ_TASK_ID — identifies the parent flow sequencing task to which the constraint belongs. Part of the primary key and business-key candidate.
• LINE_ID — identifies the sequencing line the constraint applies to. Part of the primary key and business-key candidate, and a foreign key to FLM_SEQ_TASK_LINES.
• CONSTRAINT_NUMBER — sequence number distinguishing multiple constraints within the same task/line. Part of the primary key and business-key candidate.
• PARENT_CONSTRAINT_NUMBER — supports hierarchical or nested constraint relationships.
• ORGANIZATION_ID — foreign key to MTL_PARAMETERS, identifying the inventory organization context.
• PRIORITY — the precedence assigned to the constraint during sequencing evaluation.
• CONSTRAINT_TYPE — the category of constraint being applied.
• CONSTRAINT_TYPE_VALUE1 / 2 / 3 — parameter values qualifying the constraint type.
• ATTRIBUTE_ID — foreign key to FLM_SEQ_ATTRIBUTES, linking the constraint to a defined sequencing attribute.
• ATTRIBUTE_VALUE1_NAME, ATTRIBUTE_VALUE2_NAME — character-based attribute values used in constraint matching.
• ATTRIBUTE_VALUE1_NUM, ATTRIBUTE_VALUE2_NUM — numeric attribute values.
• ATTRIBUTE_VALUE1_DATE, ATTRIBUTE_VALUE2_DATE — date attribute values.
• FULFILLED_TO_QTY — quantity satisfied against the constraint.
• VIOLATION_COUNT — number of recorded violations, supporting diagnostics and reporting.
• OBJECT_VERSION_NUMBER along with CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, and PROGRAM_UPDATE_DATE — standard audit and concurrent program tracking columns.

Common Use Cases and Queries

Typical reporting scenarios include listing all constraints for a given sequencing task, ranking constraints by priority, and identifying tasks with constraint violations. A basic retrieval pattern is:

• SELECT SEQ_TASK_ID, LINE_ID, CONSTRAINT_NUMBER, CONSTRAINT_TYPE, PRIORITY, VIOLATION_COUNT FROM FLM.FLM_SEQ_TASK_CONSTRAINTS WHERE SEQ_TASK_ID = :p_task_id ORDER BY PRIORITY;
• Joining to FLM_SEQ_ATTRIBUTES on ATTRIBUTE_ID to resolve the attribute name and meaning behind a constraint.
• Joining to MTL_PARAMETERS on ORGANIZATION_ID to restrict results to a specific organization.
• Aggregating VIOLATION_COUNT by CONSTRAINT_TYPE to identify problem constraint categories during a sequencing run.

Related Objects

• FLM_SEQ_TASK_LINES — referenced via LINE_ID; provides the parent line record.
• FLM_SEQ_ATTRIBUTES — referenced via ATTRIBUTE_ID; defines the sequencing attribute used by the constraint.
• MTL_PARAMETERS — referenced via ORGANIZATION_ID; supplies organization context.
• FLM_SEQ_TASK_EXCEPTIONS — references this table through SEQ_TASK_ID, CONSTRAINT_NUMBER, and LINE_ID, capturing exception details raised against constraints.