How To Fix UG098 - LOCTEST: -> & local objects to be exported

SAP Error Message - Details

• Message type: E = Error

• Message class: UG - Messages for Repository Switch

• Message number: 098

• Message text: LOCTEST: -> & local objects to be exported

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 UG098 - LOCTEST: -> & local objects to be exported ?

  The SAP error message UG098 typically occurs when you are trying to export local objects (development objects that are not part of a transport request) from the SAP system. This message indicates that the system has detected local objects that need to be handled before the export can proceed.
  Cause:
  The error message UG098 is triggered when:
  
  You attempt to export a transport request that contains local objects.
  Local objects are not included in the transport system and cannot be exported directly.
  
  Solution:
  To resolve this issue, you can take the following steps:
  
  
  Identify Local Objects: Check the transport request to identify which local objects are causing the issue. You can do this by reviewing the transport request in the Transport Organizer (transaction code SE09 or SE10).
  
  
  Remove Local Objects: If the local objects are not needed, you can remove them from the transport request. This can be done by editing the transport request and deselecting the local objects.
  
  
  Create Transportable Objects: If the local objects need to be transported, you should create transportable versions of these objects. This typically involves:
  
  Creating a new development object in the appropriate package.
  Assigning the object to a transportable package.
  Moving the local objects to the new transportable objects.
  
  
  
  Use Transport Organizer: After making the necessary changes, use the Transport Organizer to manage your transport requests and ensure that only transportable objects are included.
  
  
  Re-attempt Export: Once you have addressed the local objects, try to export the transport request again.
  
  
  Related Information:
  
  Local Objects: Local objects are development objects that are created in the SAP system without being assigned to a transportable package. They are typically used for testing or temporary changes.
  Transport System: The SAP transport system is used to move development objects between different SAP systems (e.g., from development to quality assurance to production).
  Transaction Codes: Familiarize yourself with transaction codes like SE09 (Transport Organizer) and SE10 (Transport Organizer for Workbench Requests) to manage transport requests effectively.
  
  If you continue to experience issues, consider consulting with your SAP Basis team or reviewing SAP Notes related to transport management for further guidance.