How To Fix PPECMP356 - &1 &2 is still used on initial screen

SAP Error Message - Details

• Message type: E = Error

• Message class: PPECMP - Messages for iPPE CMP Application (Components)

• Message number: 356

• Message text: &1 &2 is still used on initial screen

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 PPECMP356 - &1 &2 is still used on initial screen ?

  The SAP error message PPECMP356 typically indicates that a certain object (like a program, report, or transaction) is still being used or referenced in the initial screen of a particular application or module. This can occur in various contexts, such as when trying to delete or modify a program or transaction that is still in use.
  Cause:
  
  Active References: The object you are trying to delete or modify is still referenced in the system, which prevents the action from being completed.
  User Sessions: There may be active user sessions or transactions that are currently using the object.
  Configuration Settings: The object might be configured in a way that it is still linked to other processes or screens.
  
  Solution:
  
  Check Active Sessions: Verify if there are any active sessions or users currently using the object. You can use transaction codes like SM04 (User Overview) or SM50 (Process Overview) to check for active sessions.
  Review Object References: Use transaction SE80 (Object Navigator) or SE11 (Data Dictionary) to check for any references to the object in question. Look for any dependencies or links that might be causing the issue.
  Remove References: If you find any references, you may need to remove or update them before you can proceed with your intended action.
  Transport Requests: If the object is part of a transport request, ensure that the transport is not in a state that prevents changes.
  Consult Documentation: Review any relevant documentation or notes related to the specific object or transaction to understand its dependencies better.
  
  Related Information:
  
  SAP Notes: Check the SAP Support Portal for any specific notes related to the error message PPECMP356. There may be patches or updates that address this issue.
  Transaction Codes: Familiarize yourself with relevant transaction codes that can help you diagnose and resolve the issue, such as SE80, SE11, SM04, and SM50.
  System Logs: Review system logs for any additional error messages or warnings that might provide more context about the issue.
  
  If the problem persists after following these steps, consider reaching out to your SAP Basis or technical support team for further assistance. They may have additional tools or insights to help resolve the issue.