Results for “seq_fix_sequence_type”

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

Overview

WIP_LINES is the master table of production lines within the Oracle Work in Process (WIP) module in Oracle E-Business Suite 12.1.1 and 12.2.2. A "line" in this context is a discrete production entity — a physical or logical manufacturing resource such as an assembly line, a repetitive manufacturing line, a kanban-controlled line, or a sequencing line — that is defined within a specific inventory organization. The table sits at the intersection of discrete manufacturing, repetitive scheduling, kanban replenishment, and sequencing (flow) manufacturing, acting as the central reference point for how production capacity is organized and scheduled.

The table is owned by the WIP schema and is currently marked VALID. It contains 41 documented columns. From a Data Vault modeling perspective, the mined foreign-key structure classifies WIP_LINES as a hub. This is a modeling suggestion: the table is referenced by an unusually large number of downstream and planning tables, and it holds stable business keys (LINE_CODE plus ORGANIZATION_ID) rather than transactional or frequently-changing descriptive state. Its descriptive attributes, such as rates and schedule types, could be modeled as a satellite on the LINE_ID hub in a warehouse implementation.

Key Information Stored

The surrogate primary key is LINE_ID, enforced by the WIP_LINES_PK constraint. Business-key candidates are captured by the unique indexes: WIP_LINES_U1 on (LINE_ID, ORGANIZATION_ID), and WIP_LINES_U3 and WIP_LINES_U4, both on (LINE_CODE, ORGANIZATION_ID). The duplication of LINE_CODE/ORGANIZATION_ID in two unique indexes reflects the standard EBS pattern for enabling and disabling keys on a multi-organization table. LINE_CODE is the user-facing production line name, and ORGANIZATION_ID scopes every line to a single inventory organization.

The most significant columns include:

• LINE_ID — surrogate primary key; the value propagated to all dependent tables.
• ORGANIZATION_ID — foreign key to WIP_PARAMETERS; identifies the owning inventory organization.
• LINE_CODE — the business key, unique within an organization.
• DESCRIPTION — free-text line description.
• DISABLE_DATE — date the line is retired from active use.
• MINIMUM_RATE, MAXIMUM_RATE, FIXED_THROUGHPUT — capacity and throughput constraints used in repetitive scheduling.
• LINE_SCHEDULE_TYPE — controls whether the line operates on a rate-based or discrete schedule.
• SCHEDULING_METHOD_ID — links the line to its scheduling method.
• START_TIME, STOP_TIME — daily operating window for the line.
• ATP_RULE_ID — available-to-promise rule applied to line capacity.
• SEQ_DIRECTION, SEQ_CONNECT_FLAG, SEQ_FIX_SEQUENCE_TYPE, SEQ_FIX_SEQUENCE_AMOUNT, SEQ_DEFAULT_RULE_ID, SEQ_COMBINE_SCHEDULE_FLAG — the sequencing (flow manufacturing) configuration, including direction, connection logic, fixed-sequence rules, and schedule combination behavior.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard EBS flexfield extension columns.
• EXCEPTION_SET_NAME — exception set assigned to the line for exception reporting.

Standard WHO audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) are also present.

Common Use Cases and Queries

A frequent requirement is listing all active production lines for an organization, which drives repetitive scheduling, kanban, and capacity reports:

• SELECT line_id, line_code, description FROM wip_lines WHERE organization_id = :org AND disable_date IS NULL;
• Capacity reporting: query MINIMUM_RATE, MAXIMUM_RATE, FIXED_THROUGHPUT, and START_TIME/STOP_TIME to calculate available daily line time.
• Sequencing configuration: query the SEQ_* columns to determine how flow manufacturing lines are sequenced and combined.
• Resolving LINE_ID to LINE_CODE when joining from dependent tables such as WIP_REPETITIVE_ITEMS, MTL_KANBAN_CARDS, or WIP_MOVE_TRANSACTIONS, which store only the foreign key.
• Identifying retired lines via DISABLE_DATE for historical analysis and to exclude them from current scheduling.

Related Objects

WIP_LINES has one outgoing foreign key and is referenced by a broad set of production, planning, and kanban tables. Significant referencing objects include:

• WIP_REPETITIVE_ITEMS (LINE_ID) — repetitive schedules attached to the line.
• WIP_MOVE_TRANSACTIONS and WIP_MOVE_TXN_INTERFACE (LINE_ID) — shop-floor move activity on the line.
• MTL_KANBAN_CARDS, MTL_KANBAN_CARD_ACTIVITY, and MTL_KANBAN_PULL_SEQUENCES (WIP_LINE_ID) — kanban replenishment tied to the line.
• BOM_OPERATIONAL_ROUTINGS and BOM_STANDARD_OPERATIONS (LINE_ID) — routing and standard operation definitions.
• CRP_PLANNED_RESOURCES (LINE_ID) — capacity planning resources.
• MRP_REPETITIVE_SCHEDULES and MRP_SUGG_REP_SCHEDULES (REPETITIVE_LINE) — planning interface schedules.
• WIP_JOB_SCHEDULE_INTERFACE and WIP_COST_TXN_INTERFACE (LINE_ID) — open interfaces carrying line references.
• WIP_PARAMETERS — the parent table supplying ORGANIZATION_ID.

These relationships confirm the hub role of WIP_LINES: it is a low-cardinality, organization-scoped reference table whose surrogate key is consumed across discrete, repetitive, kanban, and sequencing manufacturing subprocesses.