Do you have any question about this error?
Message type: E = Error
Message class: MD - Material Requirements Planning (MRP)
Message number: 502
Message text: &1: Start date of components in past (T3)
The start date of order proposals for the components is in the past.
This exception message appears in the MRP list for a planning run in
the main memory.
Check whether the order proposals for the components are to be
rescheduled and/or converted. You can access these order proposals by
choosing the function 'Order structure' for the receipt you are
viewing.
Error message extract from SAP system. Copyright SAP SE.
MD502
- &1: Start date of components in past (T3) ?The SAP error message MD502, which states "Start date of components in past (T3)," typically occurs in the context of production planning and material requirements planning (MRP). This error indicates that the start date for a component in a production order or planned order is set to a date that is earlier than the current date, which is not allowed in the system.
Cause:
- Past Start Date: The most common cause is that the start date for the component is set to a date that has already passed. This can happen if the production order or planned order was created with incorrect dates.
- Scheduling Issues: If the scheduling parameters are not set correctly, it may lead to the system calculating a start date that is in the past.
- Changes in Production Plan: If there have been changes in the production plan or if the order was rescheduled, it might result in components being assigned start dates that are no longer valid.
Solution:
- Check Dates: Review the start date of the components in the production order or planned order. Ensure that the start date is set to a future date.
- Reschedule Orders: If the order is in the past, you may need to reschedule the production order or planned order to a future date. This can be done in the order management screen.
- Adjust MRP Parameters: If the issue is recurring, check the MRP parameters and settings to ensure they are configured correctly to avoid scheduling components in the past.
- Review Component Availability: Ensure that the components required for production are available and that their lead times are correctly defined.
- Consult Documentation: Refer to SAP documentation or help resources for specific steps on how to adjust dates and reschedule orders.
Related Information:
By following these steps, you should be able to resolve the MD502 error and ensure that your production planning processes run smoothly.
Get instant SAP help. Start your 7-day free trial now.
MD501
&1: Not covered by master production schedule at component level (S8)
What causes this issue? After an ATP check, the system has determined that the requirements for the components are not covered by the master producti...
MD500
***** COMMENT: new exception messages in MRP for components
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
MD503
&1: Finish date of components in past (T4)
What causes this issue? The finish date of the order proposals for the components is in the past.System Response This exception message appears in t...
MD504
&1: Preference for operation at component level (U1)
What causes this issue? The rescheduling check has calculated that the receipts of the components are not available until too late of a date. The del...
Click on this link to search all SAP messages.