How To Fix CRM_SSC072 - Scrn control data already exists for scrn prof.type &1 and trans.type &2

SAP Error Message - Details

• Message type: E = Error

• Message class: CRM_SSC - Screen Sequence Control - CRM Transaction

• Message number: 072

• Message text: Scrn control data already exists for scrn prof.type &1 and trans.type &2

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 CRM_SSC072 - Scrn control data already exists for scrn prof.type &1 and trans.type &2 ?

  The SAP error message CRM_SSC072 indicates that there is a conflict with screen control data in the SAP CRM system. Specifically, it means that there is already existing screen control data for the specified screen profile type and transaction type. This can occur when there are attempts to create or modify screen control data that overlaps with existing entries.
  Cause:
  
  Duplicate Entries: The error typically arises when there are attempts to create a new screen control entry that already exists in the system for the same screen profile type and transaction type.
  Configuration Issues: There may be issues in the configuration settings where the same screen control data is being referenced multiple times.
  Transport Issues: If changes were transported from one system to another (e.g., from development to production), it might lead to conflicts if the same data already exists in the target system.
  
  Solution:
  
  
  Check Existing Entries: 
  
  Go to the relevant transaction in SAP (e.g., CRMD_ORDER or SPRO) and check the existing screen control data for the specified screen profile type and transaction type.
  Use transaction SE11 or SE16 to view the relevant database tables (like CRMC_SCRNCTRL) to see if the entry already exists.
  
  
  
  Modify or Delete Duplicate Entries:
  
  If you find that the entry already exists and is not needed, you can delete or modify it as necessary.
  If the existing entry is required, you may need to adjust your new entry to avoid the conflict.
  
  
  
  Review Configuration:
  
  Review the configuration settings in the SAP Customizing Implementation Guide (IMG) to ensure that there are no conflicting settings.
  Ensure that the screen profile and transaction types are correctly defined and do not overlap.
  
  
  
  Transport Management:
  
  If the issue arose after a transport, check the transport logs to see if there were any errors during the transport process.
  Ensure that the transport does not contain duplicate entries that could lead to this error.
  
  
  
  Consult Documentation:
  
  Refer to SAP Notes and documentation for any specific guidance related to the error message CRM_SSC072. SAP Notes may provide additional insights or patches that can resolve the issue.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SPRO for configuration, SE11 for data dictionary, and SE16 for table display.
  SAP Notes: Search for SAP Notes related to CRM_SSC072 for any known issues or fixes.
  Support: If the issue persists, consider reaching out to SAP support or your internal SAP support team for further assistance.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.