How To Fix REXCRAIT358 - Multiple records for same IRE date & (IRE contract statuses & and &)

REXCRAIT358 - Overview

• Message type: E = Error

• Message class: REXCRAIT - Italian localisation RE-FX

• Message number: 358

• Message text: Multiple records for same IRE date & (IRE contract statuses & and &)

What causes this issue?

Likely, IRE contract status "Intermediate" is in conflict with another
IRE contract status happening in the same IRE date.

System Response

An record could not be replaced/deleted during IRE recalculation because
of its "Record Active" state

How to fix this error?

Go to the corresponding IRE detail and remove "Record active" state for
a IRE record and relevant IRE date

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message REXCRAIT358 - Multiple records for same IRE date & (IRE contract statuses & and &) ?

  The SAP error message REXCRAIT358 indicates that there are multiple records for the same IRE (Investment Return Evaluation) date and contract statuses in the system. This typically occurs in the context of contract management or investment evaluations where the system expects unique entries for specific dates and statuses.
  
  Cause:
  
  Duplicate Entries: The primary cause of this error is the presence of duplicate records in the database for the same IRE date and contract statuses. This can happen due to data entry errors, system glitches, or incorrect data imports.
  
  Configuration Issues: There may be issues with the configuration of the IRE process or the way contracts are set up in the system.
  Data Migration Issues: If data has been migrated from another system, it may have resulted in duplicates that were not properly handled during the migration process.
  
  
  Solution:
  
  Identify Duplicates: Use transaction codes like SE16 or SE11 to query the relevant database tables (e.g., the tables