How To Fix FICUSTOM190 - Item was already posted in year &3

FICUSTOM190 - Overview

• Message type: E = Error

• Message class: FICUSTOM - Customizable Messages for Funds Management

• Message number: 190

• Message text: Item was already posted in year &3

What causes this issue?

You want to undo the commitment carryforward for document &V1& item &V2&
. After the carryforward to the receiver year &V1&, this item has
already been posted (for example, partially reduced) so the open amount
is different.

System Response

When undoing the commitment carryforward, only the amount not yet
reduced is undone.
This message is issued as a warning by default. It is possible to undo
the commitment carryforward in this case.
This message can also be issued as an error, in which case, it is
<ZH>not</> possible to undo the commitment carryforward when an open
amount changes.

How to fix this error?

Reverse the documents that caused the change to the open amount after
the commitment carryforward.

Procedure for System Administrators

To issue the message as an error, you must define the corresponding
settings in the IMG of Funds Management.
INCLUDE NA_PSM_CUSTOMIZ OBJECT DOKU ID TX

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FICUSTOM190 - Item was already posted in year &3 ?

  The SAP error message FICUSTOM190 indicates that an item has already been posted in a specific fiscal year, which is denoted by the placeholder &3 in the error message. This typically occurs when there is an attempt to post a transaction that would affect a closed fiscal year or when the posting period is not open for the specified year.
  
  Cause:
  
  Closed Fiscal Year: The fiscal year in question has been closed, and no further postings are allowed.
  Posting Period: The posting period for the transaction is not open. This can happen if the period is closed in the configuration settings.
  Duplicate Posting: There may be an attempt to post the same item or transaction again, which is not allowed.
  
  
  Solution:
  
  
  Check Fiscal Year Status: Verify if the fiscal year is indeed closed. You can do this by checking the configuration in the Financial Accounting (FI) module.
  
  Navigate to Transaction Code: OB52 to check the open and