There have been multiple posts in which the logic behind the Sched Capacity on the Inventory Part has been presented and what happens when Finite vs. Always Finite is used.
This post is questioning how a user is supposed to load data into the APB when manufactured components are either Finite or Always Finite.
Customer has the following product structure:
- P/N 100
- P/N 200 (QPA = 30)
P/N 200 is always manufactured in lot sizes of 8 and each shop order takes 1 day (8 hours) to process its lone operation.
5-day work week M-F, 8-hour days, 8 AM - 4 PM no breaks.
There are (4) shop orders for component p/n 200, and each is scheduled to end on Day1, Day2, Day3, and Day4 respectively. These have been APB Scheduled and saved to the database.
I have multiple shop orders for p/n 100 that consist of only one operation.
- When loading and scheduling only the shop orders for p/n 100
- If P/N 200 is set to Always Finite, APB does not schedule the orders for p/n 100. It is in Unscheduled status in APB, with the message "Not enough materials..." But there will be sufficient supply of p/n 200 to start p/n 100 on Day5.
- When loading the shop orders for p/n 200 and p/n 100, but only scheduling Unreleased, Unscheduled, and Infinite operations (i.e., schedule p/n 100 and consider the schedule of the components)
- If P/N 200 is set to Always Finite, APB returns all shop orders for p/n 100 as Scheduled.
In summary the findings by the customer are:
- If a manufactured child component is set to Sched Capacity = Always Finite, and only the parent shop orders are loaded into APB (even if child shop orders have been previously scheduled), APB will show the parent shop orders as Unscheduled.
- If a manufactured child component is set to Sched Capacity = Always Finite, both parent and child shop orders must be loaded at the same time in APB to have APB actually use that Sched Capacity setting as a constraint.
Is this requirement of loading the child shop orders with the parent shop orders valid?
Best answer by Saman K
View original
