How To Fix ME172 - Provision account key missing for condition type &1 in schema &2

ME172 - Overview

• Message type: E = Error

• Message class: ME - Purchasing: General Messages

• Message number: 172

• Message text: Provision account key missing for condition type &1 in schema &2

What causes this issue?

Condition type &V1& is marked as "provision-relevant". However, the
account key for posting provisions is missing in schema &V2& for this
condition type.
It is not possible to make a posting to the provision account without
an account key.

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?

Maintain the provision account key for the condition type in
Customizing for Purchasing.

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 ME172 - Provision account key missing for condition type &1 in schema &2 ?

  The SAP error message ME172, which states "Provision account key missing for condition type &1 in schema &2," typically occurs in the context of pricing and conditions in the SAP system, particularly in the Materials Management (MM) module. This error indicates that there is a missing configuration related to the account key for a specific condition type in the pricing schema.
  
  Cause:
  
  Missing Account Key: The primary cause of this error is that the account key associated with the specified condition type is not defined in the pricing schema. The account key is essential for determining how the financial postings related to the condition type should be handled.
  Incorrect Configuration: The pricing procedure may not be correctly configured to include the necessary account keys for the condition types being used.
  Condition Type Not Assigned: The condition type may not be properly assigned to the relevant pricing procedure or schema.
  
  
  Solution:
  To resolve the ME172 error, follow