How To Fix FDT_SERVICE098 - Collisions occurred during activation of function &1 (&2)

SAP Error Message - Details

• Message type: E = Error

• Message class: FDT_SERVICE - Formula & Derivation Tool: Services

• Message number: 098

• Message text: Collisions occurred during activation of function &1 (&2)

What causes this issue?

The service provider (triggered by central deployment) tried to deploy a
certain BRFplus function into a runtime system. This runtime system is
marked as a customer system. In the customer system an old version of
that function exists which was created in that system. Now a new version
of the function has been shipped by the content owner (= developer).
The BRFplus service provider does not deploy the new version of the
content object since this would overwrite the existing version. This
again would lead to content loss which definitely needs to be prevented.
Therefore the deployment keeps the old version and replies with a
collision message in the log.

System Response

Collision in deployment.

How to fix this error?

Contact the content owner in order to find a solutiuon.

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 FDT_SERVICE098 - Collisions occurred during activation of function &1 (&2) ?

  The SAP error message FDT_SERVICE098 indicates that there were collisions during the activation of a function in the SAP system. This typically occurs in the context of the SAP Fiori or SAP Gateway framework, where multiple changes or activations are being processed simultaneously, leading to conflicts.
  
  Cause:
  
  Concurrent Changes: Multiple users or processes may be trying to activate or modify the same function or object at the same time.
  Inconsistent State: The system may be in an inconsistent state due to previous failed activations or changes that were not properly completed.
  Transport Issues: If changes are being transported from one system to another, there may be conflicts with existing objects.
  Version Conflicts: Different versions of the same function or object may be present, leading to conflicts during activation.
  
  
  Solution:
  
  Check for Active Sessions: Ensure that no other users or processes are trying to activate the same function simultaneously. You can use transaction codes like SM50 or SM66