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

SAP Error Message - Details

• 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.

Smart SAP Assistant

• What is the cause and solution for SAP error message GMAVC518 - Derivation strategy &1 cannot be deleted: it is still in use ?

  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) or KSV5 (for internal orders) to see if the strategy is linked to any active planning scenarios.
  
  
  
  Remove Dependencies:
  
  If the derivation strategy is linked to any active configurations, you will need to remove those links or deactivate the configurations that are using it.
  Ensure that no active planning or reporting processes are relying on the derivation strategy.
  
  
  
  Check for Custom Code: 
  
  If there are any custom developments or enhancements that reference the derivation strategy, you may need to modify or remove those as well.
  
  
  
  Consult Documentation: 
  
  Review SAP documentation or help resources for specific guidance on managing derivation strategies and their dependencies.
  
  
  
  Testing: 
  
  After making changes, test to ensure that the removal of the derivation strategy does not negatively impact other processes.
  
  
  
  Delete the Strategy: 
  
  Once you have confirmed that the derivation strategy is no longer in use, you can proceed to delete it.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes for managing derivation strategies and related configurations.
  SAP Notes: Check SAP Notes for any known issues or additional guidance related to the GMAVC518 error.
  User Roles: Ensure that you have the necessary authorizations to make changes to derivation strategies and related configurations.
  
  If you continue to face issues after following these steps, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.