How To Fix MD901 - AggregationLevelCode &1 does not exist

SAP Error Message - Details

• Message type: E = Error

• Message class: MD - Material Requirements Planning (MRP)

• Message number: 901

• Message text: AggregationLevelCode &1 does not exist

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 MD901 - AggregationLevelCode &1 does not exist ?

  The SAP error message MD901, which states "AggregationLevelCode &1 does not exist," typically occurs in the context of SAP's Advanced Planning and Optimization (APO) module, particularly when dealing with planning data and aggregation levels.
  Cause:
  The error is triggered when the system attempts to access or process an aggregation level that has not been defined or does not exist in the system. This can happen due to several reasons:
  
  Incorrect Aggregation Level Code: The code being referenced in the error message may be misspelled or incorrect.
  Missing Configuration: The aggregation level may not have been created or configured properly in the system.
  Transport Issues: If the aggregation level was recently transported from another system, it may not have been included in the transport request.
  Data Consistency Issues: There may be inconsistencies in the data or configuration that lead to the aggregation level not being recognized.
  
  Solution:
  To resolve the MD901 error, you can follow these steps:
  
  
  Verify Aggregation Level Code:
  
  Check the aggregation level code mentioned in the error message. Ensure that it is spelled correctly and matches the expected format.
  
  
  
  Check Configuration:
  
  Go to the transaction code /SAPAPO/MC62 (or the relevant transaction for your version) to view the existing aggregation levels.
  Confirm that the aggregation level you are trying to use is listed and properly configured.
  
  
  
  Create or Modify Aggregation Level:
  
  If the aggregation level does not exist, you may need to create it. Use the transaction /SAPAPO/MC62 to define a new aggregation level.
  If it exists but is not configured correctly, you may need to modify it to ensure it meets your planning requirements.
  
  
  
  Transport Issues:
  
  If the aggregation level was supposed to be transported from another system, check the transport logs to ensure it was included and successfully imported.
  
  
  
  Check for Data Consistency:
  
  Run consistency checks in the APO system to identify any potential issues with the data that could be causing the error.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for additional guidance on aggregation levels and their configuration.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as /SAPAPO/MC62 for managing aggregation levels and /SAPAPO/MC73 for checking planning books.
  SAP Notes: Check SAP Notes for any known issues or patches related to the MD901 error.
  User Forums: Engage with SAP community forums or user groups for insights and solutions shared by other users who may have encountered similar issues.
  
  By following these steps, you should be able to identify the cause of the MD901 error and implement the necessary solutions to resolve it.