Results for “requested_qty”

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

Overview

FLM.FLM_SEQ_TASK_DEMANDS is a Flow Manufacturing (FLM) transactional table that stores demand information associated with flow sequencing tasks. In Oracle EBS 12.1.1 and 12.2.2, Flow Manufacturing supports demand-driven, sequenced production on mixed-model lines, where work is pulled by actual customer demand rather than by traditional work orders. This table records the demand quantities that a given sequencing task must satisfy, tying together the sequencing task, the demand source (such as a sales order line or a planning recommendation), and the item being produced.

From a Data Vault modeling perspective, and based on the documented foreign key structure, this table is heuristically classified as a link. It resolves relationships between sequencing tasks, demand records, and item/organization entities. This classification is offered as a modeling suggestion rather than a definitive statement of EBS internal design.

Key Information Stored

The table contains 20 documented columns. The primary key is the composite constraint FLM_SEQ_TASK_DEMANDS_PK, defined over DEMAND_ID, SPLIT_NUMBER, SEQ_TASK_ID, and LINE_ID. A separate unique index, FLM_SEQ_TASK_DEMANDS_U1, is defined over the same four columns in a different sequence (SEQ_TASK_ID, LINE_ID, DEMAND_ID, SPLIT_NUMBER), reinforcing the business-key combination used to uniquely identify a demand line. The most significant columns include:

• SEQ_TASK_ID — identifies the parent flow sequencing task to which this demand belongs.
• LINE_ID — identifies the sequencing line on which the task executes.
• DEMAND_ID — references the originating demand record, such as a sales order line or planning recommendation.
• SPLIT_NUMBER — distinguishes split portions of a demand when a single demand is divided across tasks.
• ORGANIZATION_ID — the inventory organization context for the demand.
• PRIMARY_ITEM_ID — the item being manufactured to satisfy the demand.
• ALTERNATE_ROUTING_DESIGNATOR — the alternate routing used for the item.
• OPEN_QTY, REQUESTED_QTY, FULFILLED_QTY — the demand quantities driving fulfillment and completion tracking.
• OBJECT_VERSION_NUMBER — supports optimistic locking for concurrent updates.
• Standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) and concurrent program columns (REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE).

Common Use Cases and Queries

Typical reporting scenarios include tracing which demands a sequencing task satisfies, measuring fulfillment against requested quantities, and reconciling flow line output to originating sales orders. A representative query joining demands to their sequencing tasks and items:

• Select d.SEQ_TASK_ID, d.DEMAND_ID, d.OPEN_QTY, d.FULFILLED_QTY from FLM_SEQ_TASK_DEMANDS d where d.ORGANIZATION_ID = :org_id and d.OPEN_QTY > 0.
• Join to MTL_SYSTEM_ITEMS_B on PRIMARY_ITEM_ID and ORGANIZATION_ID to resolve item descriptions.
• Join to OE_ORDER_LINES_ALL on DEMAND_ID to link demand back to the sales order line.

Related Objects

The documented foreign keys and relationships connect this table to the following significant objects:

• FLM_SEQ_TASK_LINES — joined via LINE_ID.
• FLM_SEQ_TASK_DEMANDS self-reference — via SEQ_TASK_ID.
• MTL_SYSTEM_ITEMS_B — via PRIMARY_ITEM_ID and ORGANIZATION_ID.
• BOM_ALTERNATE_DESIGNATORS — via ALTERNATE_ROUTING_DESIGNATOR and ORGANIZATION_ID.
• MTL_PARAMETERS — via ORGANIZATION_ID.
• OE_ORDER_LINES_ALL — via DEMAND_ID.
• MRP_RECOMMENDATIONS — via DEMAND_ID, allowing planning-driven demand to populate sequencing tasks.