How To Fix CTE_FND_GDPR020 - Data destruction/blocking failed. See long text for details.

CTE_FND_GDPR020 - Overview

• Message type: E = Error

• Message class: CTE_FND_GDPR -

• Message number: 020

• Message text: Data destruction/blocking failed. See long text for details.

What causes this issue?

The feedback loop contains at least one Concur document that has already
been acknowledged, but for which no confirmation has been sent yet.

System Response

The destruction run fails, meaning <ZH>no </>data is deleted.

How to fix this error?

Open the <LS>Concur Documents</> monitor.
To do so, on the <LS>Setting Up the Integration with SAP Concur</>
screen, click <PF>Financial Posting</> or <PF>Payroll </>and select
<LS>Concur Documents</>.
In the <LS>View Documents</> field, select <LS>Without Confirmation</>.
In the <LS>Document Type</> field, select <LS>All</>.
In the <LS>Changes Made</> field, select <LS>Show All</>.
Click <PF>Search</>.
Check the list and make sure that all documents for which an
acknowledgement has been sent have completed the feedback loop. You can
verify this by checking the <LS>Confirmation Sent </>column.

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.

CTE_FND_GDPR020 - Details

• The SAP error message CTE_FND_GDPR020, which indicates that "Data destruction/blocking failed," is related to the General Data Protection Regulation (GDPR) compliance features in SAP systems. This error typically arises when there is an attempt to delete or block personal data, but the operation fails for some reason.
  Causes:
  
  Data Integrity Issues: The data you are trying to delete or block may be linked to other records, leading to integrity constraints that prevent the operation.
  Authorization Issues: The user executing the data destruction/blocking may not have the necessary authorizations to perform the action.
  Technical Errors: There may be underlying technical issues, such as database locks, system errors, or configuration problems.
  Incomplete Configuration: The GDPR-related configuration in the SAP system may not be fully set up, leading to failures in data handling processes.
  Custom Code: If there are custom developments or enhancements in the system, they may interfere with the standard data destruction/blocking processes.
  
  Solutions:
  
  Check Long Text: Review the