How To Fix UCF6602 - Location of equity data: Overlapping items/transaction types

UCF6602 - Overview

• Message type: E = Error

• Message class: UCF6 - Messages for Consolidation of Investments

• Message number: 602

• Message text: Location of equity data: Overlapping items/transaction types

What causes this issue?

*** same as UCF6601 except for "reported equity data" ***
The items and transaction types in the reported equity data for various
activities overlap each other. This occurs in the following
combinations of activity/sequence number:
&V1&
&V2&
&V3&
&V4&

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?

A combination of item and transaction type can only be assigned to one
activity. Check the definition of the specified selections of items and
transaction types for the combinations listed above.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

UCF6602 - Details

• The SAP error message UCF6602, which states "Location of equity data: Overlapping items/transaction types," typically occurs in the context of financial transactions, particularly when dealing with equity data in the SAP system. This error indicates that there are overlapping entries or transaction types that are conflicting with each other, which can prevent the system from processing the equity data correctly.
  
  Cause:
  
  Overlapping Transaction Types: The error often arises when there are multiple transaction types that are defined for the same period or location, leading to conflicts in how the equity data is processed.
  Incorrect Configuration: The configuration settings for equity data may not be set up correctly, leading to overlaps in the definitions of transaction types.
  Data Entry Errors: Manual entries or imports of data may have resulted in duplicate or conflicting records.
  Timing Issues: Transactions that are recorded in overlapping periods can also trigger this error.
  
  
  Solution:
  
  Review Transaction Types: Check the transaction types defined in