How To Fix CL_PS_MD_MSG021 - Object number not found

SAP Error Message - Details

• Message type: E = Error

• Message class: CL_PS_MD_MSG - Messages for Project Editor

• Message number: 021

• Message text: Object number not found

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 CL_PS_MD_MSG021 - Object number not found ?

  The SAP error message CL_PS_MD_MSG021: Object number not found typically occurs in the context of Project System (PS) or related modules when the system is unable to locate a specific object number that is being referenced. This can happen for various reasons, including data inconsistencies, incorrect object numbers, or issues with the configuration.
  Causes:
  
  Incorrect Object Number: The object number you are trying to access may not exist in the system or may have been deleted.
  Data Inconsistency: There may be inconsistencies in the database, such as missing entries or corrupted data.
  Authorization Issues: The user may not have the necessary authorizations to view or access the object.
  Configuration Issues: There may be issues with the configuration of the Project System or related modules.
  Transport Issues: If the object was recently transported from another system, it may not have been properly imported.
  
  Solutions:
  
  Verify Object Number: Check the object number you are trying to access to ensure it is correct and exists in the system.
  Check Data Consistency: Use transaction codes like SE11 (Data Dictionary) or SE16 (Data Browser) to check the relevant tables for the existence of the object number.
  Authorization Check: Ensure that the user has the necessary authorizations to access the object. You can check this using transaction SU53 to analyze authorization issues.
  Review Configuration: If the issue is related to configuration, review the settings in the Project System to ensure everything is set up correctly.
  Transport Logs: If the object was recently transported, check the transport logs to ensure that the transport was successful and that all necessary objects were included.
  Consult SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error message or provide additional troubleshooting steps.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  CJ20N: Project Builder
  CJ03: Display Project
  SE11: Data Dictionary
  SE16: Data Browser
  
  
  SAP Support: If the issue persists, consider reaching out to SAP Support for further assistance, providing them with detailed information about the error and the context in which it occurs.
  Documentation: Review SAP documentation related to Project System for additional insights into object management and error handling.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution.