How To Fix FKKRD099 - Unassigned payment &1 already has a distribution key

FKKRD099 - Overview

• Message type: E = Error

• Message class: FKKRD - Messages for Revenue Distribution

• Message number: 099

• Message text: Unassigned payment &1 already has a distribution key

What causes this issue?

Document item &V1& is an unassigned payment (a payment on account with a
subtransaction flagged as relevant for payment). For unassigned payments
the <DS:DE.RDI_DISKEY_KK>distribution keys</> are defined at event 5420,
which is called by the <LS>revenue distribution</> mass activity
(FP60M). However, document item &V1& was already posted with a
distribution key.

System Response

The system cannot distribute document item &V1&.

How to fix this error?

Define event 5420 accordingly. Reverse document &V1& and post it again
without a distribution key. Execute the mass activity for <LS>revenue
distribution</> (FP60M) again.

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 FKKRD099 - Unassigned payment &1 already has a distribution key ?

  The SAP error message FKKRD099 indicates that there is an issue with an unassigned payment that already has a distribution key associated with it. This typically occurs in the context of contract accounts receivable and payable (FI-CA) when trying to process a payment that cannot be assigned correctly due to existing distribution settings.
  
  Cause:
  
  Existing Distribution Key: The payment you are trying to process has already been assigned a distribution key, which means it has been allocated to specific accounts or items.
  Unassigned Payment: The system is expecting a payment to be unassigned or not linked to any distribution key, but it finds that it already has one.
  
  Configuration Issues: There may be configuration settings in the payment processing or distribution key settings that are causing this conflict.
  Data Integrity Issues: There could be inconsistencies in the data, such as missing or incorrect entries in the relevant tables.
  
  
  Solution:
  
  Check Payment Details: Review the payment document to