SAP ABAP IMG Activity SIMG_CFMENUOLMDOMDW (Define Rescheduling Horizon)
Hierarchy
☛ SAP_APPL (Software Component) Logistics and Accounting
   ⤷ PP-MRP-BD (Application Component) Master Data
     ⤷ MD0C (Package) Customizing R/3 Material Requirements Planning
IMG Activity
ID SIMG_CFMENUOLMDOMDW Define Rescheduling Horizon  
Transaction Code S_ALR_87000727   IMG Activity: SIMG_CFMENUOLMDOMDW 
Created on 19981222    
Customizing Attributes SIMG_CFMENUOLMDOMDW   Define Rescheduling Horizon 
Customizing Activity SIMG_CFMENUOPP1OMDW   Define Rescheduling Check 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CFMENUOLMDOMDW    

The rescheduling horizon is the period in which the SAP System checks whether the existing dates still suit the requirements situation for receipt elements that can no longer be automatically changed in the planning run. If the dates of a particular element are no longer suitable, the following exception messages are created depending on the requirements situation:

  • bring element forward, if the date of the requirement lies before the date of the receipt element
  • postpone element, if the date of the requirement lies after the date of the receipt element
  • delete element, if the requirement no longer exists

When defining the rescheduling horizon, think about the period in which you want to carry out a precise planning run. You define the rescheduling horizon per plant or per MRP group.

The following receipt elements are not changed during the planning run:

  • firmed planned orders
  • firmed purchase requisitions
  • purchase orders
  • production orders
  • QM inspection lots

You can define which of the above mentioned receipt elements should be provided with rescheduling proposals, if necessary, for rescheduling in. Rescheduling proposals for postponing are always created for all receipt elements.

You can also define a tolerance time for the rescheduling proposal, that is, a tolerance by which the requirements date can vary from the order finish date or the delivery date of the receipt element. Only once this tolerance value has been exceeded, will the system create a rescheduling proposal.

Note

  • If no rescheduling horizon has been maintained, the system will not carry out a rescheduling check. This means, the system does not create an exception message for firm order proposals. Instead, a new receipt element is created for every new planned requirement and the system does not take the existing, firmed, receipt elements into account whose dates are unsuitable.
  • The system calculates the rescheduling horizon from the end of the replenishment lead time in reorder point planning.

Recommendation

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.

Actions

  1. Define the rescheduling horizon for your plants or MRP groups.
  2. Decide which receipt elements are to be included in the rescheduling check.
  3. Define the tolerances for your plants or MRP groups, within which you do not want rescheduling proposals.

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 1   Mandatory activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG SIMG_CFMENUOLMDOMDW 0 HLA0006803 Consumption-Based Planning (See Also PP-MRP) 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
V_399D_U V - View OMDW 02 Plant Rescheduling 
V_438M_U V - View OMDW 02 Rescheduling per MRP Group 
History
Last changed by/on SAP  19981222 
SAP Release Created in