How To Fix S_ARC_DESTRUCTION114 - BAdI implementation prohibited destruction of resource &1

S_ARC_DESTRUCTION114 - Overview

• Message type: E = Error

• Message class: S_ARC_DESTRUCTION - ILM: Data Destruction Message Class

• Message number: 114

• Message text: BAdI implementation prohibited destruction of resource &1

What causes this issue?

An implementation of the BAdI BADI_ILM_DESTR_FILE_VETO has prevented the
data destruction of resource &V1&.

System Response

The resource will be removed from the data destruction worklist. The
remaining resources in the data destruction worklist are <ZH>not</>
affected as long as there are no reasons for using a veto to prevent
deletion.
Deleting resource &V1& is <ZH>not possible until</> the reason
preventing the deletion has been removed.

How to fix this error?

If necessary, check the log of the data destruction run for the reason
preventing the deletion of the resource.

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.

S_ARC_DESTRUCTION114 - Details

• The SAP error message S_ARC_DESTRUCTION114 indicates that a BAdI (Business Add-In) implementation has prohibited the destruction of a specific resource. This typically occurs in the context of archiving or data management processes within SAP systems, where certain resources or data objects are protected from deletion due to business rules or configurations.
  
  Cause:
  
  BAdI Implementation: The error arises when a BAdI implementation is designed to prevent the deletion of specific resources. This is often done to ensure data integrity or compliance with business rules.
  Resource Protection: The resource in question (indicated by &1 in the error message) is likely marked as protected or is subject to certain conditions that prevent its destruction.
  Configuration Settings: There may be configuration settings in the system that dictate which resources can be deleted and which cannot.
  
  
  Solution:
  
  
  Check BAdI Implementation: Review the BAdI implementation that is causing the error. You can do this by:
  
  Navigating to the BAdI definition in the SAP