Results for “seq_task_type”

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

Overview

FLM_SEQ_TASKS is a Flow Manufacturing (FLM) table that stores the parameters governing flow sequencing tasks in Oracle E-Business Suite environments running 12.1.1 or 12.2.2. A sequencing task represents a discrete execution of the flow sequencing engine, in which the application re-orders and levels demand across a schedule group according to defined demand criteria. Each row in FLM_SEQ_TASKS captures the configuration under which that sequencing run was requested and executed, including the demand window, the schedule group affected, the sequencing request that triggered the run, and the resulting sequence date range. The table resides in the FLM schema and is classified as VALID in the ETRM repository.

From a Data Vault modeling perspective, the heuristic classification of this table is satellite-leaning. This suggests FLM_SEQ_TASKS functions primarily as a descriptive attribute container hanging off one or more parent business keys. Its two foreign keys point to WIP_SCHEDULE_GROUPS and MTL_PARAMETERS, which would typically behave as hubs or links in a Data Vault model, with FLM_SEQ_TASKS supplying the contextual attributes for those associations.

Key Information Stored

The table contains 23 documented columns. The surrogate primary key is SEQ_TASK_ID, enforced by the FLM_SEQ_TASKS_PK constraint. A unique index, FLM_SEQ_TASKS_U1, is also defined on SEQ_TASK_ID, confirming its role as the primary business-key candidate. The most significant descriptive and operational columns include:

• SEQ_TASK_NAME – the user-identified name for the sequencing task.
• ORGANIZATION_ID – the inventory organization in which the sequencing task executes; foreign key to MTL_PARAMETERS.
• SCHEDULE_GROUP_ID – the schedule group whose demand is being sequenced; foreign key to WIP_SCHEDULE_GROUPS.
• SEQ_TASK_TYPE – discriminates the type of sequencing task being run.
• DEMAND_START_DATE / DEMAND_END_DATE – the demand horizon considered by the sequencing engine.
• SEQ_START_DATE / SEQ_END_DATE – the resulting sequencing window applied to production lines.
• SEQ_REQUEST_ID – the concurrent request identifier that submitted the sequencing task.
• DEMAND_CRITERIA_GROUP_ID – references the demand criteria group used to evaluate and rank demand.
• ALTERNATE_ROUTING_FLAG – indicates whether alternate routings may be considered during sequencing.
• HONOR_PLANNING_FLAG – controls whether planning schedules are respected by the sequencing engine.
• OBJECT_VERSION_NUMBER – supports optimistic locking on the row.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – standard audit columns.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE – concurrent program audit columns that record which program created or last modified the row.

Common Use Cases and Queries

Typical uses include auditing sequencing history for a schedule group, troubleshooting why a particular demand window was not sequenced, and reporting on sequencing throughput by organization. A representative query joining to the schedule group and organization context:

• SELECT t.SEQ_TASK_ID, t.SEQ_TASK_NAME, t.SEQ_TASK_TYPE, t.DEMAND_START_DATE, t.DEMAND_END_DATE, t.SEQ_START_DATE, t.SEQ_END_DATE FROM FLM.FLM_SEQ_TASKS t WHERE t.SCHEDULE_GROUP_ID = :group_id AND t.ORGANIZATION_ID = :org_id ORDER BY t.CREATION_DATE DESC;
• To identify sequencing requests that produced line-level results, join to FLM_SEQ_TASK_LINES on SEQ_TASK_ID.
• To reconcile a sequencing task to the concurrent request that spawned it, filter on SEQ_REQUEST_ID or REQUEST_ID.

Related Objects

The following objects are most significant in relation to FLM_SEQ_TASKS, per documented foreign-key relationships:

• FLM_SEQ_TASK_LINES – child table; referenced via FLM_SEQ_TASK_LINES.SEQ_TASK_ID = FLM_SEQ_TASKS.SEQ_TASK_ID. Holds the individual line-level sequencing results for each task.
• WIP_SCHEDULE_GROUPS – parent reference via SCHEDULE_GROUP_ID; defines the schedule group being sequenced.
• MTL_PARAMETERS – parent reference via ORGANIZATION_ID; supplies organization-level inventory parameters.
• FLM_SEQ_TASKS_PK / FLM_SEQ_TASKS_U1 – the primary key and unique index on SEQ_TASK_ID that anchor integrity and lookups.
• Demand criteria groups – referenced through DEMAND_CRITERIA_GROUP_ID, controlling how demand is ranked during sequencing.