Results for “fix_sequence_type”

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

Overview

FLM_SEQ_TASK_LINES is a Flow Manufacturing (FLM) transactional table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the production line detail for a flow sequencing task. Where the parent table FLM_SEQ_TASKS defines a sequencing job header, FLM_SEQ_TASK_LINES captures the per-line configuration that the sequencing engine uses to order, schedule, and balance production across the lines within a manufacturing organization. Each row associates one sequencing task with one production line and carries the operational parameters — sequencing direction, timing, capacity, resequencing quantities, and rule references — required to generate the actual line sequence.

Because the table exists only to associate two principal entities (a sequencing task and a production line) and to resolve rules, the heuristic Data Vault classification mined from its foreign key structure is a link. In a dimensional or Data Vault model it would typically be modeled as a link table bridging FLM_SEQ_TASKS and WIP_LINES, with the descriptive scheduling attributes carried on a satellite. Practically, it functions as the configuration driver for the flow sequencing concurrent programs and the Line Scheduling workbench.

Key Information Stored

The table is owned by the FLM schema and contains 25 documented columns. The composite primary key, FLM_SEQ_TASK_LINES_PK, is defined on the surrogate key pair (LINE_ID, SEQ_TASK_ID). A unique index, FLM_SEQ_TASK_LINES_U1 on (SEQ_TASK_ID, LINE_ID), enforces the business rule that a given line may appear only once per sequencing task and serves as the business-key candidate. The most significant columns include:

• SEQ_TASK_ID — foreign key to FLM_SEQ_TASKS; identifies the sequencing task that owns this line row.
• LINE_ID — foreign key to WIP_LINES; identifies the specific production line being sequenced.
• ORGANIZATION_ID — foreign key to MTL_PARAMETERS; scopes the row to a manufacturing organization.
• RULE_ID — foreign key to FLM_SEQ_RULES; the sequencing rule applied to this line.
• SEQ_DIRECTION — indicates the direction in which the line is sequenced (forward or backward).
• START_TIME / STOP_TIME — the scheduling window applied to the line's sequence.
• HOURLY_RATE — the throughput rate used to pace sequencing calculations.
• AVAILABLE_CAPACITY — line capacity available to the sequencing task.
• CONNECT_FLAG — controls whether this line is linked to adjacent lines in the sequence.
• FIX_SEQUENCE_TYPE / FIX_SEQUENCE_AMOUNT — define whether and how many jobs are pinned in the sequence.
• COMBINE_SCHEDULE_FLAG — governs whether the line participates in combined scheduling.
• RESEQUENCED_QTY / REQUESTED_RESEQUENCE_QTY — track quantities pending or completed for resequencing runs.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — standard EBS audit and concurrent program context columns.

Common Use Cases and Queries

Typical scenarios include diagnosing why a line failed to sequence, reviewing the parameters of a completed sequencing run, and reporting capacity and throughput assumptions per line. A join to the parent task and line definitions is the standard access pattern:

• Listing all lines for a given sequencing task:

  SELECT l.line_id, l.seq_direction, l.start_time, l.stop_time, l.hourly_rate
  FROM   flm.flm_seq_task_lines l
  WHERE  l.seq_task_id = :task_id;

• Resolving line and organization names:

  SELECT stl.line_id, wl.line_code, stl.available_capacity, stl.rule_id
  FROM   flm.flm_seq_task_lines stl,
         wip.wip_lines          wl
  WHERE  stl.line_id = wl.line_id
  AND    stl.organization_id = :org_id;

• Identifying lines awaiting resequencing by comparing RESEQUENCED_QTY against REQUESTED_RESEQUENCE_QTY.
• Auditing concurrent program activity via REQUEST_ID, PROGRAM_ID, and PROGRAM_APPLICATION_ID for a sequencing batch.

Related Objects

The following objects are directly documented as related through foreign keys or dependent child tables:

• FLM_SEQ_TASKS — parent task header; joined on SEQ_TASK_ID.
• WIP_LINES — production line master; joined on LINE_ID.
• MTL_PARAMETERS — organization definition; joined on ORGANIZATION_ID.
• FLM_SEQ_RULES — sequencing rules; joined on RULE_ID.
• FLM_SEQ_TASK_CONSTRAINTS — child table referencing this table on (LINE_ID, SEQ_TASK_ID).
• FLM_SEQ_TASK_DEMANDS — child table referencing this table on (LINE_ID, SEQ_TASK_ID).

Together these objects form the flow sequencing data model, with FLM_SEQ_TASK_LINES at the center linking tasks, lines, rules, constraints, and demands.