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

CRM_SSC072 - Overview

• 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.,