How To Fix EMOLC_GEN117 - Non-transportable object &1 &2

SAP Error Message - Details

• Message type: E = Error

• Message class: EMOLC_GEN - OLC: generic checks

• Message number: 117

• Message text: Non-transportable object &1 &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 EMOLC_GEN117 - Non-transportable object &1 &2 ?

  The SAP error message EMOLC_GEN117 indicates that there is a non-transportable object in your system. This typically occurs when you are trying to transport an object that cannot be moved between different SAP systems (e.g., from development to quality assurance or production). Non-transportable objects can include certain types of configuration settings, local objects, or specific customizations that are not designed to be transported.
  Cause:
  
  Local Objects: The object you are trying to transport is marked as a local object (e.g., it starts with a Z or Y but is not properly defined for transport).
  Configuration Settings: Some configuration settings in SAP are not transportable by design.
  Development Class: The object may not be assigned to a transportable development class.
  Object Type: Certain object types, such as some types of customizing or local settings, are inherently non-transportable.
  
  Solution:
  
  Check Object Properties: Verify the properties of the object in question. Ensure that it is assigned to a transportable development class.
  Create a Transportable Version: If the object is a local object, consider creating a transportable version of it. This may involve copying the object to a transportable development class.
  Review Configuration: If the object is a configuration setting, check if there is a way to replicate the configuration in a transportable manner.
  Use Transport Organizer: Use the Transport Organizer (transaction SE09 or SE10) to check the transport requests and see if the object can be included in a transport request.
  Consult Documentation: Refer to SAP documentation or notes related to the specific object type to understand its transportability.
  
  Related Information:
  
  Transaction Codes: SE09 (Transport Organizer), SE10 (Transport Organizer - Modifiable Requests), SE80 (Object Navigator).
  SAP Notes: Check for relevant SAP Notes that may provide additional insights or solutions for specific object types.
  Development Guidelines: Follow SAP development guidelines to ensure that new objects are created in a transportable manner.
  
  If you continue to face issues, consider reaching out to your SAP Basis team or consulting SAP support for further assistance.