How To Fix FMCA_PSOB096 - Reverse obsolete indicator: Contract object &1 is locked

FMCA_PSOB096 - Overview

• Message type: E = Error

• Message class: FMCA_PSOB - Contract Object

• Message number: 096

• Message text: Reverse obsolete indicator: Contract object &1 is locked

What causes this issue?

You want to reverse the clearing of a document. However, this is not
possible because the corresponding master data combination (contract
object &V1&, business partner &V2&, contract account category &V4& and
contract account &V3&) is flagged as <DS:DE.PS_XOBSL>obsolete</>.
To make this master data combination available again for online
processing, you must delete the obsolete indicator. This is not
possible at the moment because contract object &V1& is already locked
for processing.

System Response

It is not possible to reset the obsolete indicator for contract object
&V1&, business partner &V2&, contract account category &V4& and
contract account &V3&.

How to fix this error?

Post the clearing reversal as soon as contract object &V1& is no longer
locked and the obsolete indicator can be deleted.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FMCA_PSOB096 - Reverse obsolete indicator: Contract object &1 is locked ?

  The SAP error message FMCA_PSOB096 indicates that a contract object is locked, which prevents the reverse obsolete indicator from being set. This typically occurs in the context of contract management or financial transactions where certain objects are being modified or updated.
  
  Cause:
  
  Locking Mechanism: The contract object (&1) is currently locked by another user or process. This can happen if another transaction is being processed that involves the same contract.
  Incomplete Transactions: If a previous transaction involving the contract was not completed properly, it may leave the object in a locked state.
  Authorization Issues: The user may not have the necessary permissions to modify the contract object, leading to a lock.
  
  
  Solution:
  
  Check Lock Entries: Use transaction code SM12 to check for lock entries related to the contract object. You can identify the user or process that is holding the lock.
  Release Locks: If you find that the lock is held by a user who is no