How To Fix COM_DML_CUST104 - Set type &: text set type & does not exist or is inactive

SAP Error Message - Details

• Message type: E = Error

• Message class: COM_DML_CUST - MDF Messages

• Message number: 104

• Message text: Set type &: text set type & does not exist or is inactive

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 COM_DML_CUST104 - Set type &: text set type & does not exist or is inactive ?

  The SAP error message COM_DML_CUST104 indicates that there is an issue with a set type in the SAP system. Specifically, the message states that the specified set type does not exist or is inactive. This error typically occurs in the context of the SAP Controlling (CO) module, particularly when dealing with cost elements, cost centers, or other master data that relies on set types.
  Cause
  The error can be caused by several factors:
  
  Non-Existent Set Type: The set type you are trying to use has not been created in the system.
  Inactive Set Type: The set type exists but has been marked as inactive, meaning it cannot be used in transactions.
  Configuration Issues: There may be issues in the configuration settings related to the set types in the SAP system.
  Authorization Issues: The user may not have the necessary authorizations to access the set type.
  
  Solution
  To resolve the error, you can take the following steps:
  
  
  Check Set Type Existence:
  
  Go to the transaction code OBY6 (or the relevant configuration transaction) to check if the set type exists.
  If it does not exist, you will need to create it.
  
  
  
  Activate Set Type:
  
  If the set type exists but is inactive, you can activate it. This is usually done in the configuration settings where you manage set types.
  Ensure that the set type is properly configured and active.
  
  
  
  Review Configuration:
  
  Check the configuration settings related to the set types in the SAP system. Ensure that all necessary settings are correctly defined.
  You may need to consult with your SAP configuration team or refer to the SAP documentation for guidance.
  
  
  
  Check Authorizations:
  
  Ensure that the user encountering the error has the necessary authorizations to access and use the set type.
  You may need to work with your SAP security team to verify and adjust user roles and permissions.
  
  
  
  Consult SAP Notes:
  
  Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message. There may be patches or updates that resolve known issues.
  
  
  
  Related Information
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OBY6 for configuration and SE11 for data dictionary checks.
  Documentation: Review SAP documentation related to set types and their configuration in the Controlling module.
  Support: If the issue persists after following the above steps, consider reaching out to SAP support 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.