How To Fix CONT_TOOLS603 - Check category IRD: InfoObject &1, reference to InfoObject &2 was deleted

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 603

• Message text: Check category IRD: InfoObject &1, reference to InfoObject &2 was deleted

What causes this issue?

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

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 .

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CONT_TOOLS603 - Check category IRD: InfoObject &1, reference to InfoObject &2 was deleted ?

  The SAP error message CONT_TOOLS603 indicates that there is an issue related to the InfoObjects in your SAP BW (Business Warehouse) system. Specifically, it suggests that a reference to an InfoObject has been deleted, which can lead to inconsistencies in your data model or reporting.
  Cause:
  The error typically arises from one of the following scenarios:
  
  Deleted InfoObject: An InfoObject that was previously referenced in a data model (like a DSO, InfoCube, or MultiProvider) has been deleted.
  Inconsistent Data Model: Changes made to the InfoObjects (like renaming or changing attributes) without updating all dependent objects can lead to this error.
  Transport Issues: If InfoObjects were transported between systems (e.g., from development to production) and the dependencies were not correctly handled, this error may occur.
  
  Solution:
  To resolve the CONT_TOOLS603 error, you can follow these steps:
  
  
  Identify the InfoObjects: Check the error message details to identify the specific InfoObjects involved (InfoObject &1 and InfoObject &2).
  
  
  Check Dependencies: Use transaction codes like RSA1 (Data Warehousing Workbench) to check the dependencies of the InfoObjects. Look for any inconsistencies or missing references.
  
  
  Restore Deleted InfoObjects: If an InfoObject was deleted unintentionally, consider restoring it from a backup or re-creating it if possible.
  
  
  Update Data Models: If the InfoObject has been renamed or modified, ensure that all dependent objects are updated accordingly. This may involve adjusting the data model or reassigning references.
  
  
  Transport Management: If the issue arose due to transport, ensure that all related objects are included in the transport request and that they are correctly imported into the target system.
  
  
  Check for Active Versions: Ensure that the InfoObjects are active and that there are no inactive versions that might be causing conflicts.
  
  
  Re-activate Objects: Sometimes, re-activating the affected InfoObjects or the data model can resolve the issue.
  
  
  Consult Documentation: Refer to SAP documentation or support notes related to the specific error message for additional guidance.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as RSA1, RSD1 (for InfoObjects), and RSD5 (for InfoProviders).
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Data Model Integrity: Regularly check the integrity of your data model to prevent such issues from arising in the future.
  
  If the problem persists after following these steps, consider reaching out to SAP support for further assistance.