How To Fix GMAVC518 - Derivation strategy &1 cannot be deleted: it is still in use

GMAVC518 - Overview

• Message type: E = Error

• Message class: GMAVC - Message class for Grant Management AVC

• Message number: 518

• Message text: Derivation strategy &1 cannot be deleted: it is still in use

What causes this issue?

The <DS:DE.FM_KEDR_ENV>derivation strategy</> &V1& (strategy ID &V2&)
cannot be deleted, because it is still used in Customizing (at least in
company code &V4& for <DS:DE.BUAVC_ALDNR>control ledger</> &V3&).

System Response

The strategy &V1& is not deleted.

How to fix this error?

Choose a strategy, which is not used in Customizing, or assign another
derivation strategy in the Customizing activity
<DS:SIMG.SIMG_GM_AVC_ATTRIB>Assign Attributes for GM Availability
Control Ledger</>

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.

GMAVC518 - Details

• The SAP error message GMAVC518 indicates that a derivation strategy (identified by &1) cannot be deleted because it is still in use. This typically occurs in the context of SAP's Controlling (CO) module, particularly in the area of Activity-Based Costing (ABC) or similar functionalities where derivation strategies are used to determine how costs are allocated or derived.
  
  Cause:
  
  Active Usage: The derivation strategy is currently being used in one or more configurations, such as in cost center planning, internal orders, or other controlling applications.
  Dependencies: There may be dependencies on the derivation strategy from other objects or processes within the SAP system.
  Configuration Settings: The strategy might be linked to specific settings or configurations that prevent its deletion.
  
  
  Solution:
  
  
  Identify Usage: 
  
  Check where the derivation strategy is being used. You can do this by navigating to the relevant configuration settings in SAP and reviewing the assignments or dependencies.
  Use transaction codes like OKB9 (for cost center planning)