FLMSEQ: Flow Sequencing: Flow Schedules For Component Items Are No Longer Linked To Parent Schedules After Running the Flow Sequencing Concurrent Request
Last updated on MARCH 08, 2017
Applies to:Oracle Flow Manufacturing - Version 22.214.171.124 to 126.96.36.199 [Release 11.5]
Information in this document applies to any platform.
After creating a Flow Schedule, running the Feeder Line Synchronization Concurrent Request (FLMCPSY), and then running the FLMSEQ: Flow Sequencing concurrent request, the flow line is disassociated from the parent schedule and the scheduled quantity is one.
The feeder schedule should still be associated with the parent schedule after running the FLMSEQ: Flow Sequencing concurrent request. The parent/schedule Line is null in the WIP_FLOW_SCHEDULES table and a new (duplicate) schedule is created.
The issue can be reproduced at will with the following steps:
PRODUCTION feds ASSY
1: Schedule orders in line scheduling workbench (Flow Manufacturing: Line Scheduling: Line Scheduling Workbench)
Org/Line = 1/ASSY, Line Scheduling Workbench, 9/9/2013 ... 9/9/2103
Shows Assy = FTC*480365
2: Run the the Feeder Line Synchronization Concurrent Request (FLMCPSY), Org/Line = 1/ASSY, Line Scheduling Workbench, 9/9/2013 ... 9/9/2103
3. Many schedules from the PRODUCTION line, and are all linked to flow schedule for the ASSY line, Org 1
22 existing schedules, 4 have quantity = 2
4. Resequence PRODUCTION line using Flow Sequencing (run the FLMSEQ: Flow Sequencing concurrent request)
The 4 schedules that were 2 are replaced with 8 schedules of 1
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms