How To Fix OIUCM856 - Escheat Code 'S' cannot be changed to 'Y'

OIUCM856 - Overview

• Message type: E = Error

• Message class: OIUCM - E&P Common Messages Across All Sub-Systems

• Message number: 856

• Message text: Escheat Code 'S' cannot be changed to 'Y'

What causes this issue?

If an owner is not in escheat, the code value needs to be 'N' or left
blank. Once an owner is identified as being in escheat, the codes can
be set to 'Y' and the escheat date must be set.
Once this owner is processed through the E<(>&<)><(>&<)>P revenue batch
process, the escheat code may get updated to 'S' to identify the owner
as being in subsequent escheat. An owner can never be set to being in
subsequent escheat (S) via on-line.
The owner can be updated from being in subsequent escheat (S) to not
being in escheat (N) via the on-line transaction. The owner cannot be
updated from 'S' to 'Y' via the on-line transaction.

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?

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 OIUCM856 - Escheat Code 'S' cannot be changed to 'Y' ?

  The SAP error message OIUCM856 indicates that there is an issue with the escheat code in the context of unclaimed property management. Specifically, it states that the escheat code 'S' (which typically stands for "suspended") cannot be changed to 'Y' (which usually stands for "escheat"). This error often arises in the context of managing unclaimed property, where specific codes are used to classify the status of funds or accounts.
  
  Cause:
  
  Business Rules Violation: The system is enforcing business rules that prevent the transition from a suspended status to an escheat status. This could be due to regulatory requirements or internal policies that dictate how unclaimed property should be managed.
  Data Integrity Issues: There may be data integrity issues or inconsistencies in the records that prevent the change from being processed.
  Configuration Settings: The configuration settings in the SAP system may not allow for such a transition based on the current status of the account