Search Results flm_seq_task_demands

Overview

The FLM_SEQ_TASK_DEMANDS table is a core transactional data store within the Oracle E-Business Suite Flow Manufacturing (FLM) module. It functions as the central repository for demand information that is directly linked to flow sequencing tasks. In the context of Flow Manufacturing, which emphasizes lean, pull-based production, sequencing tasks are critical for scheduling and executing work on the shop floor. This table enables the system to associate specific customer or internal demands with the discrete sequencing tasks that will fulfill them, thereby providing a direct link between the demand signal and the manufacturing execution plan. Its role is essential for maintaining the integrity of the demand-driven production schedule in both EBS releases 12.1.1 and 12.2.2.

Key Information Stored

The table's primary key is a composite of DEMAND_ID, SPLIT_NUMBER, and SEQ_TASK_ID, indicating that a single demand line can be associated with multiple sequencing tasks, potentially split across operations. Based on its documented foreign key relationships, the table stores several critical pieces of information. The SEQ_TASK_ID and LINE_ID columns link the demand to a specific task and its associated flow line. The PRIMARY_ITEM_ID and ORGANIZATION_ID columns identify the manufactured item and its inventory organization. Furthermore, the ALTERNATE_ROUTING_DESIGNATOR column, linked to the BOM_ALTERNATE_DESIGNATORS table, specifies which routing alternative is used to fulfill the demand for that particular task, a key feature for flexible manufacturing execution.

Common Use Cases and Queries

A primary use case is generating shop floor reports that show the underlying demand (e.g., sales order number, customer) for every active sequencing task. This visibility is crucial for prioritizing work and responding to changes. Another common scenario involves analyzing demand fulfillment by tracing which sequencing tasks were created for a specific sales order line. Troubleshooting and data validation queries are also frequent, such as identifying tasks that have no associated demand or validating that all demands for a critical item have been properly scheduled. A sample query pattern would join FLM_SEQ_TASK_DEMANDS to FLM_SEQ_TASKS and MTL_SYSTEM_ITEMS_B to list all tasks for a given item, along with their demand identifiers.

Related Objects

• FLM_SEQ_TASKS: The table has a self-referential foreign key relationship via LINE_ID and SEQ_TASK_ID, linking demands to the core sequencing task definitions.
• MTL_SYSTEM_ITEMS_B: Joined via PRIMARY_ITEM_ID and ORGANIZATION_ID to provide item master details for the demanded product.
• BOM_ALTERNATE_DESIGNATORS: Joined via ALTERNATE_ROUTING_DESIGNATOR and ORGANIZATION_ID to determine the specific manufacturing routing used.
• MTL_PARAMETERS: Joined via ORGANIZATION_ID to obtain organization-level manufacturing parameters and settings.