How To Fix MN245 - Account key for condition type & missing in settlement schema &

SAP Error Message - Details

• Message type: E = Error

• Message class: MN - Message class for subsequent settlement (Purchasing)

• Message number: 245

• Message text: Account key for condition type & missing in settlement schema &

What causes this issue?

The system needs settlement schema (calculation schema) no. &V2& in
order to carry out settlement accounting with respect to rebate
arrangement &V3&. Among other things, this schema contains the account
keys necessary to determine the financial accounts for rebate income
and provisions for income.
The account key is missing from the entry for condition type &V1&.
Without an account key, neither the release of the billing document for
processing by Financial Accounting nor credit-side postings are
possible.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

&WHAT_TO_DO& (system administrator)
Maintain the entry for condition type &V1& in calculation schema &V2&
using the Customizing facility.

<ds:SIMG.SIMG_CFMENUOLMEKONDT>Set up condition technique</>
ENDIF

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message MN245 - Account key for condition type & missing in settlement schema & ?

  The SAP error message MN245 indicates that there is a missing account key for a specific condition type in the settlement schema. This error typically occurs in the context of settlement processes, such as in the SAP Controlling (CO) module, particularly when dealing with internal orders, projects, or other cost objects.
  Cause:
  
  Missing Configuration: The account key for the specified condition type has not been defined in the settlement schema. This can happen if the condition type is not properly set up in the system.
  Incorrect Settlement Schema: The settlement schema being used may not be correctly configured to include the necessary account keys for the condition types involved in the settlement process.
  Changes in Configuration: If there have been recent changes to the configuration of the settlement schema or condition types, it may lead to inconsistencies that result in this error.
  
  Solution:
  
  
  Check Settlement Schema Configuration:
  
  Go to the transaction code OKO7 (Settlement Schema) in SAP.
  Review the settlement schema being used for the relevant cost object (e.g., internal order, project).
  Ensure that the account key for the condition type in question is included in the schema.
  
  
  
  Define Account Key:
  
  If the account key is missing, you will need to define it. This can be done in the configuration settings for the condition type.
  Use transaction code KOT2 to check and maintain the account keys for condition types.
  
  
  
  Review Condition Types:
  
  Check the condition types involved in the settlement process. Ensure that they are correctly configured and linked to the appropriate account keys.
  Use transaction code KOT1 to review the condition types and their settings.
  
  
  
  Test the Settlement Process:
  
  After making the necessary changes, test the settlement process again to ensure that the error is resolved.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for detailed guidance on configuring settlement schemas and condition types.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  OKO7: Settlement Schema Configuration
  KOT1: Condition Type Configuration
  KOT2: Account Key Configuration for Condition Types
  
  
  
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to this error message. SAP Notes can provide patches or additional configuration steps.
  
  
  User Roles and Authorizations: Ensure that the user has the necessary authorizations to make changes to the settlement schema and condition types.
  
  
  By following these steps, you should be able to resolve the MN245 error and ensure that the settlement process functions correctly. If the issue persists, consider reaching out to your SAP support team for further assistance.