!--a11y-->
Features
The rescheduling run is divided into the following steps:
For background information on this, see the example in the first section under
A document is only saved if data relevant for requirements has been changed due to the availability check result. This includes data such as:
The following greatly contribute to the performance of the rescheduling procedure even for a larger number of requirements records:
the system sets the requirements lock once for all requirements records and then removes it if the requirement is currently being processed
a document only has to be saved if changes in delivery date or quantity of a requirement have been made

Even so, you should try to keep the number of materials per rescheduling run as low as possible. Please note that the materials for operating that have been selected for rescheduling, such as those for entering new sales documents or for executing the allocation, are locked until the report is completed.
We therefore recommend that you select only a few materials for each run and that you choose a time for the start of the report when the system is not being worked on and/or when no other reports are planned.
The estimated end of the report and the time of the resumption of normal business should not lie too close together. This way, if rescheduling has to be terminated, you will have enough flexibility to reset the requirements lock for your materials again (see the section on
Reset requirements lock indicator under Selection.)