How To Fix CN_EVWB005 - Not all objects were imported. See the message log

SAP Error Message - Details

• Message type: E = Error

• Message class: CN_EVWB - Message class of Eanred Value Workbench

• Message number: 005

• Message text: Not all objects were imported. See the message log

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 CN_EVWB005 - Not all objects were imported. See the message log ?

  The SAP error message CN_EVWB005 indicates that not all objects were successfully imported during a transport request or a similar operation. This can occur in various contexts, such as during the import of transport requests in the Change and Transport System (CTS) or while working with project objects in SAP.
  Causes:
  
  Missing Dependencies: Some objects may depend on other objects that were not included in the transport request.
  Transport Errors: There may have been errors during the transport process, such as syntax errors or missing authorizations.
  Version Conflicts: The target system may have different versions of the objects, leading to conflicts during import.
  Lock Issues: Objects may be locked in the target system, preventing their import.
  Inconsistent Data: Data inconsistencies or issues in the source system can lead to incomplete imports.
  
  Solutions:
  
  Check the Message Log: Review the detailed message log associated with the transport request to identify which objects failed to import and why.
  Resolve Dependencies: Ensure that all dependent objects are included in the transport request. You may need to create additional transport requests for missing objects.
  Correct Errors: If there are syntax errors or other issues, correct them in the source system and re-export the transport request.
  Unlock Objects: If objects are locked, you may need to unlock them or wait until the lock is released.
  Re-import the Transport: After addressing the issues, try re-importing the transport request.
  Check Authorizations: Ensure that you have the necessary authorizations to import the objects in the target system.
  
  Related Information:
  
  Transaction Codes: You can use transaction codes like SE01 (Transport Organizer), SE09 (Workbench Requests), or SE10 (Customizing Requests) to manage transport requests.
  Transport Logs: The transport logs can be accessed through transaction STMS (Transport Management System) to get more details about the import process.
  SAP Notes: Check SAP Notes for any known issues related to the specific objects or transport requests you are working with. You can search for relevant notes in the SAP Support Portal.
  
  If the problem persists after following these steps, consider reaching out to your SAP Basis team or SAP support for further assistance.