How To Fix CONT_TOOLS602 - Check category IAD: InfoObject &1, attribute &2 was deleted

CONT_TOOLS602 - Overview

• Message type: E = Error

• Message class: CONT_TOOLS - Message for BI Content Tools German

• Message number: 602

• Message text: Check category IAD: InfoObject &1, attribute &2 was deleted

What causes this issue?

System Response

An incompatible change was made for the InfoObject .
This may cause serious problems at the customer site if the InfoObject w
as already delivered.

How to fix this error?

Please, check whether the change is really necessary.
If NOT -> Reverse the change and activate the InfoObject again.
If YES -> ,,
Step 1: Create a note which describes how to deal with the change.
Step 2: Mark the Content Analyzer Error as 'checked':
,,,,Go to transaction RSBICA (Content Analyzer)
,,,,Settings -> ,,Confirm Check-Results:
,,,,,,,,,,Maintain the appropriate check result:
,,,,,,,,,,Input: Confirmed = Yes (error message is checked)
,,,,,,,,,,,,Note number = enter note number
,,,,,,,,,,,,Message or Comment = enter short explanation why the change
is necessary .

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

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

CONT_TOOLS602 - Details

• The SAP error message "CONT_TOOLS602 Check category IAD: InfoObject &1, attribute &2 was deleted" typically indicates that there is an issue related to the InfoObject and its attributes in the SAP BW (Business Warehouse) environment. This error usually arises when an InfoObject or one of its attributes has been deleted or is no longer available in the system, which can lead to inconsistencies in data modeling or reporting.
  
  Cause:
  
  Deletion of InfoObject or Attribute: The most common cause is that the InfoObject (e.g., a characteristic or key figure) or one of its attributes has been deleted from the data model.
  Transport Issues: If the InfoObject was deleted in one system (e.g., development) and the changes were transported to another system (e.g., production) without proper synchronization, it can lead to this error.
  Inconsistent Data Model: The data model may have inconsistencies due to changes made without proper adjustments in dependent objects.
  
  
  Solution:
  
  Check InfoObject and Attributes: Verify