SAP ABAP IMG Activity SIMG_CFMENUOPP1OMDW (Define Rescheduling Check)
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_CFMENUOPP1OMDW Define Rescheduling Check  
Transaction Code S_ALR_87006542   IMG Activity: SIMG_CFMENUOPP1OMDW 
Created on 19981222    
Customizing Attributes SIMG_CFMENUOPP1OMDW   Define Rescheduling Check 
Customizing Activity SIMG_CFMENUOPP1OMDW   Define Rescheduling Check 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CFMENUOPP1OMDW    

The rescheduling period represents the period in which the system checks whether the existing dates of the receipt elements that 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 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

You can define which of the above mentioned receipt element 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.

Note

  • 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 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 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.

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_CFMENUOPP1OMDW 0 HLA0006451 O HLA0006250 O HLA0006431  
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