How To Fix ON167 - Local object types will now also be displayed

SAP Error Message - Details

• Message type: E = Error

• Message class: ON - Tools in area Object Modeler / Object Editor

• Message number: 167

• Message text: Local object types will now also be displayed

What causes this issue?

You have switched (explicitly or implicitly) from the display with the
application component hierarchy to the display without this hierarchy.
The filter 'local' was automatically set in order to display the local
object types as well.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

If you do not want to display the local object types then switch the
filter 'local' off by means of the function Filter.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message ON167 - Local object types will now also be displayed ?

  The SAP error message ON167 indicates that local object types will now also be displayed. This message typically arises in the context of ABAP development when you are working with local objects (objects that are not transported between systems) in the SAP environment.
  Cause:
  The error message ON167 is not necessarily an error in the traditional sense but rather an informational message. It indicates that the system is now configured to display local object types in the relevant transaction or report. This can happen when you are trying to access or display objects that are defined as local (e.g., in a development environment) rather than global objects that are part of a transportable package.
  Solution:
  
  
  Understanding Local Objects: If you are developing in a local environment and see this message, it is important to understand that local objects are not intended for transport to other systems. If you need to transport your objects, consider creating them in a transportable package.
  
  
  Check Object Type: If you are trying to access a specific object and receive this message, check whether the object is indeed a local object. You can do this by looking at the object’s attributes in the ABAP Workbench.
  
  
  Change Object Type: If you need the object to be transportable, you can change its type from a local object to a global object by assigning it to a transportable package. This can be done in the object’s properties.
  
  
  Ignore the Message: If you are aware of the implications of local objects and do not need to change anything, you can simply acknowledge the message and continue with your work.
  
  
  Related Information:
  
  
  Local vs. Global Objects: Local objects are typically used for development and testing purposes and are not included in transport requests. Global objects are part of a transportable package and can be moved between different SAP systems (e.g., from development to quality assurance to production).
  
  
  Transport Management: Familiarize yourself with the SAP Transport Management System (TMS) to understand how to manage and transport objects effectively.
  
  
  ABAP Development: If you are new to ABAP development, consider reviewing SAP documentation or training materials that cover the basics of object types, transport requests, and the development environment.
  
  
  If you continue to experience issues or have specific scenarios related to this message, consulting with your SAP Basis or ABAP development team may provide additional insights tailored to your environment.