How To Fix COM_ATTRFRG_GEN118 - Set type & is already on transport list

SAP Error Message - Details

• Message type: E = Error

• Message class: COM_ATTRFRG_GEN - Message Class for Generating Attributes and Sets

• Message number: 118

• Message text: Set type & is already on transport list

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_ATTRFRG_GEN118 - Set type & is already on transport list ?

  The SAP error message COM_ATTRFRG_GEN118 indicates that a specific set type is already included in the transport request. This error typically occurs when you attempt to add a set type to a transport request that has already been included in another transport request or the same one.
  Cause:
  
  Duplicate Inclusion: The set type you are trying to add is already part of the transport request.
  Transport Request Status: The transport request may be locked or in a status that prevents further modifications.
  Multiple Users: If multiple users are working on the same set type, one user may have already added it to a transport request.
  
  Solution:
  
  
  Check Transport Request: Verify the transport request to see if the set type is already included. You can do this by:
  
  Going to the transaction code SE09 or SE10.
  Searching for the transport request and checking its contents.
  
  
  
  Remove from Transport Request: If you find that the set type is included in a transport request that you do not need, you can remove it from that request if you have the necessary permissions.
  
  
  Use a Different Transport Request: If the set type is needed in a different transport request, consider creating a new transport request and adding the set type there.
  
  
  Check for Locks: Ensure that the transport request is not locked by another user. If it is, you may need to wait until the other user releases the lock.
  
  
  Consult with Colleagues: If you are unsure about the transport requests being used, consult with your colleagues or the transport administrator to avoid conflicts.
  
  
  Related Information:
  
  Transaction Codes: SE09 (Transport Organizer), SE10 (Transport Organizer - Workbench Requests).
  Transport Management System (TMS): Understanding how TMS works can help in managing transport requests effectively.
  SAP Notes: Check for any relevant SAP Notes that might provide additional insights or solutions related to this error message.
  
  If the issue persists after trying the above solutions, consider reaching out to your SAP Basis team or support for further assistance.