Kontakt

Ansicht
Dokumentation

SIMG_CFMENUOPP1OMDW - Define Rescheduling Check

SIMG_CFMENUOPP1OMDW - Define Rescheduling Check

PERFORM Short Reference   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.
SAP E-Book

Define the rescheduling periods and the relevant receipt elements.

The rescheduling period represents the period in which the system checks whether the existing dates of the receipt elements, which are no longer allowed to be changed automatically, still suit the requirements situation.

If the dates of these elements are no longer suitable, the system creates the following exception messages for the Monitor Stock / Requirements List app and for the Material Planning Data – Read API (API_MRP_MATERIALS_SRV_01) depending on the requirements situation:

If the dates of these elements are no longer suitable, the system creates the following exception messages depending on the requirements situation:

  • Bring operation forward, if the date of the requirement lies before the date of the receipt element.
  • Postpone operation, if the date of the requirement lies after the date of the receipt element.
  • Reverse operation, if the requirement no longer exists.

When determining the rescheduling period, take the period in which a precise planning run is to be carried out into account.

You define the rescheduling period per plant or per MRP group.

You use the tolerance values to determine whether a tolerance period exists in which no exception messages are created.

The following receipt elements are not changed in the planning run.

  • Firmed planned orders
  • Firmed purchase requisitions
  • Purchase orders
  • Production orders
  • QM inspection lots
  • Shipping notifications

You can define which of the receipt element mentioned above are to be provided with a rescheduling proposal for rescheduling in. Rescheduling proposals for rescheduling out are always created for all receipt elements. You can also determine a time tolerance for the rescheduling proposal, that is, a tolerance by which the requirements date is allowed to deviate from the order finish date or the delivery date. Only once this tolerance value is exceeded, will the system create a rescheduling proposal.

  • If you maintain no rescheduling period, the system will not carry out a rescheduling check. This means, the system does not create an exception message for firm order proposals. For every newly planned requirement, the system will create an appropriate receipt element without first checking the firmed receipts that already exist, although their dates are unsuitable.
  • The system calculates the rescheduling horizon from the end of the replenishment lead time.

In joint production it is not possible to reschedule receipt elements at will, because the goods receipt depends on the planning run for another material. For this reason, it is best to use a very small rescheduling horizon.

  1. Define the rescheduling period for the plants or for the MRP groups.
  2. Decide which receipt elements are to be included in the rescheduling check.
  3. Define the tolerances for the plants and the MRP groups within which you want no rescheduling proposals.
  1. Define the rescheduling period for the plants.
  2. Decide which receipt elements are to be included in the rescheduling check.
  3. Define the tolerances for the plants within which you want no rescheduling proposals.





ROGBILLS - Synchronize billing plans   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 3883 Date: 20240523 Time: 203418     sap01-206 ( 71 ms )