How To Fix /SMB/CENTRALDATA105 - IMG Activity &1 with cust. obj. &2 (type &3) and sobj. &4 is not in scope

/SMB/CENTRALDATA105 - Overview

• Message type: E = Error

• Message class: /SMB/CENTRALDATA -

• Message number: 105

• Message text: IMG Activity &1 with cust. obj. &2 (type &3) and sobj. &4 is not in scope

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 /SMB/CENTRALDATA105 - IMG Activity &1 with cust. obj. &2 (type &3) and sobj. &4 is not in scope ?

  The SAP error message /SMB/CENTRALDATA105 typically indicates that there is a problem with the configuration of the SAP system, specifically related to the scope of certain objects in the implementation project. This error is often encountered in the context of SAP S/4HANA or SAP Business ByDesign when working with the Implementation Guide (IMG) and customizing objects.
  
  Cause:
  The error message indicates that a specific customizing object (identified by &2 and &3) is not included in the scope of the current project or implementation. This can happen for several reasons:
  
  Missing Scope Definition: The object you are trying to access or configure is not part of the defined scope in your project.
  Incorrect Project Settings: The project settings may not have been properly configured to include the necessary objects.
  Transport Issues: If the object was recently transported from another system, it may not have been included in the transport request correctly.
  
  
  Solution:
  To resolve this error, you can