Subscribe

RSS Feed (xml)

Powered By

Skin Design:
Free Blogger Skins

Powered by Blogger

Rescheduling Check System Functions in a Planning Run

Rescheduling proposals form an important group which belongs to the above-mentioned exception messages. These refer to receipt elements which are not automatically changed by the system. These include, for example, purchase orders or firm planned orders. During rescheduling, the appropriate elements are automatically provided with an exception message which is linked with a course of action. This helps you with reprocessing, firstly, as the elements to be reprocessed are easy to find and, secondly, because the system has already offered you a suggestion of how to go about reprocessing. Proposals offered by the system can be, for example:

  • cancel event
  • bring forward event with specification of the proposal date
  • postpone event with specification of the proposal date

Rescheduling proposals are only created for receipts that can no longer be changed by the system. Other receipts are automatically adapted to the availability situation during the planning run.

In Customizing, you can select whether the following are taken into consideration for the rescheduling check:

  • firmed planned orders
  • firmed purchase requisitions
  • order item schedule lines

In order to improve system performance, you can set a rescheduling horizon in Customizing so that rescheduling is only carried out for part of the planning period instead of for all of it. The system checks whether the receipts participating in the rescheduling check are necessary to cover requirements. If not, the system creates a cancel proposal in order to avoid excessive warehouse stocks.

If the receipts do not fit the particular situation in question, the system checks whether they can either be brought forward or postponed. The new date is then saved when the receipt takes place.

By using comparison values (which you can set in Customizing), you can control how much of a variance from the original goods receipt date is accepted by the system before it creates deadline shift proposals. The receipt is then used in the following net requirements calculation with the rescheduling date.

The rescheduling check is further explained in the following example:

You have entered two firm planned orders for a material and you have carried out an individual planning run. The planned order for 8/5 covers the reservation's requirements, but it would be too late. As the corresponding exception messages states, the date for the planned order would have to be brought forward to the 8/3.

The planned order of the 8/10 is too early and would have to be postponed to the 8/24.

The planned order of the 8/31 can be cancelled as it would result in an excess in warehouse stock of 1000 pieces.

After processing the planned orders, that is, after changing the dates correspondingly and cancelling the planned order for 8/28, the quantities and dates of the planned orders will then match the requirements situation.


No comments:

Post a Comment

Google
 

Subscribe Here

AddThis Feed Button

Content