Rescheduling of production proposals based on component availability
The objective of this blog post is to explain how you can use the pegged supply UI enhancements done with 2005 to come to a feasible production plan considering the component availability.
Basis for the feasibility analysis is the planned material flow, that is calculated during material planning run execution. The planned material flow is a link between a demand element like forecast, sales order, or a component (dependent) demand, and a supply element like inventory, purchase orders, or production proposal output. This link is often also referred to as ‘pegging’. It explains, what quantity of a certain supply element was used by the planning run to fulfill a certain demand element.
Thus, the material flow can also be used as an explanation of the results of a material planning run.
In the example above a typical pegging network is illustrated.
There are several UIs in the work centers Supply Planning and Supply Control like the ‘Material Flow’, ‘Pegged Supply’, or ‘Top-level Pegged Demand’, that are based on this information.
Imagine the following planning situation: A sales order to be shipped on Friday requires a two-level production, and the corresponding components of the lower production level need to be purchased. As you can see one component (purchase proposal 18085) can only be delivered late.
Of course, a planner does not want to analyze the material flow for each sales order individually. Instead, he might first need to check which of the production proposals has a late component.
He can do this by selecting a set of production proposals in the Supply Control work center, view ‘Process Production Proposals’ and navigate to the ‘Pegged Supply’ UI:
You can see that a new column ‘Component Delay’ was added in the upper table with release 2005 to highlight, that one of the components of production proposal 4621 is not available on time. The corresponding pegged supply elements are listed in the lower table. Again, the ‘Component Delay’ column allows you to identify the delayed document.
A new navigation ‘Open Material Flow’ was added in the lower table to directly access the complete material flow UI for the delayed supply element:
To solve the planning issue a bottom-up scheduling can now be performed. It is important to understand that the bottom-up scheduling can only be done from the reference document upwards, while the reference document is the one, for which the material flow UI was launched.
After bottom-up scheduling, the situation looks like this:
The corresponding production proposals are moved into the future, so that they will only start once the components are available.In addition it is easy to understand the impact of the late component on the pegged sales order.
Please also have a look at this video.
Thanks Stefan, Is there any run that can do a mass reschedule bottom up please? The purchase order is normally pushed back for all products on it. When there are many products on the delayed purchase order, users do not need to go into each of component products and manually click this reschedule bottom up.
Hi Mengya Zhao,
no, there is no such run.
Thanks for your quick response Stefan! It will be very useful if there is such a run. I've submitted an improvement request
Thanks for this useful Blog.
Can you confirm the behavior of the "Component Delay" column in Pegged View?
As it looks like that for Production Proposal outside the horizon that the value is empty if there is no delay instead of being 0 day for production proposal inside the horizon?
However if you open this same Production Proposal outside the horizon with one which is inside the horizon, the value is not anymore empty, it is then 0 days.
It is not very practical to sometime have a value and sometime no value, but at least if you confirm that blank value = 0 Day delays, it is not so bad.
Pegged Supply - Component Delay
are you talking about the opening horizon? Actually, I doubt that the column value depends on that, it should only be based on the pegging information that is created during supply planning (background job as well as interactive planning).
I agree with you the calculation should not be based on the opening horizon and it doesn’t seem. However it seems that display of the 0 Day value is depending on the opening horizon. If you are under the opening horizon, you see 0, if you are outside, you see no value.
Hopefully, if the value is upper > 0 day, then the value stay as it should be in both case.
I have raised an incident for this behavior, waiting feedback on this behavior.