How To Fix 6P752 - Key date for deleting old requirements records is missing

SAP Error Message - Details

• Message type: E = Error

• Message class: 6P - Messages for planned independent requirements (Appl.area 60)

• Message number: 752

• Message text: Key date for deleting old requirements records is missing

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message 6P752 - Key date for deleting old requirements records is missing ?

  The SAP error message 6P752 indicates that there is a missing key date for deleting old requirements records in the system. This error typically arises in the context of managing requirements in SAP, particularly when dealing with the deletion of old records that are no longer needed.
  Cause:
  The error occurs when the system attempts to delete old requirements records, but the key date that determines which records can be deleted is not specified or is missing. This key date is essential for the system to identify which records are considered "old" and eligible for deletion.
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Check Configuration Settings:
  
  Navigate to the relevant configuration settings in SAP where the key date for deleting old requirements is defined. This is usually found in the customizing settings for the specific module you are working with (e.g., Material Management, Production Planning).
  Ensure that a key date is set for the deletion of old requirements records.
  
  
  
  Set Key Date:
  
  If the key date is missing, you will need to set it. This can often be done in the transaction code related to the specific module (e.g., OMD0 for MRP settings).
  Specify a key date that makes sense for your business processes, ensuring it aligns with your data retention policies.
  
  
  
  Run the Deletion Program:
  
  After setting the key date, you may need to run the relevant deletion program again to remove the old requirements records.
  
  
  
  Check User Authorizations:
  
  Ensure that the user executing the deletion has the necessary authorizations to perform this action. Lack of proper authorizations can sometimes lead to errors.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or help files related to the specific module you are working with for any additional guidance on managing requirements and deletion processes.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes that may help in managing requirements, such as MD04 (Stock/Requirements List) or MD06 (Collective Access to MRP List).
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP Notes can provide additional context or solutions that may not be covered in standard documentation.
  Support: If the issue persists after following the above steps, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
  
  By ensuring that the key date is properly set and configured, you should be able to resolve the error message 6P752 and successfully manage the deletion of old requirements records in SAP.