How To Fix FKKDPR027 - Retention start for partner &1, rule var. &2 determined suffic. from DB

FKKDPR027 - Overview

• Message type: E = Error

• Message class: FKKDPR - Message Class for Data Privacy

• Message number: 027

• Message text: Retention start for partner &1, rule var. &2 determined suffic. from DB

What causes this issue?

The system was able to determine the retention start from the database
for the combination of business partner and rule variant &V1&/&V2& and
application object &V3&. The retention start that was determined is
after the threshold date.
Based on the settings in Customizing for Contract Accounts Receivable
and Payable under <LS>Technical Settings -> Data Security ->
<DS:SIMG._FICADS_V_TFKDPR_GLO>Make Global Settings for Protection of
Personal Data</></>, the system cannot determine an earlier retention
start for the business partner from the archive. Accessing the archive
is therefore not necessary.

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 FKKDPR027 - Retention start for partner &1, rule var. &2 determined suffic. from DB ?

  The SAP error message FKKDPR027 typically relates to issues in the area of contract accounts receivable and payable (FI-CA) within the SAP system, specifically concerning the retention start date for a partner in relation to a specific rule variable.
  
  Cause:
  The error message indicates that the system was unable to determine a sufficient retention start date for the specified partner and rule variable from the database. This can occur due to several reasons, including:
  
  Missing Configuration: The retention rules or the relevant configuration for the partner may not be set up correctly in the system.
  Data Inconsistencies: There may be inconsistencies or missing data in the master data records for the partner or the relevant rule variable.
  Incorrect Partner Assignment: The partner may not be correctly assigned to the relevant retention rules or may not have the necessary data to determine the retention start date.
  Database Issues: There could be issues with the database that prevent