How To Fix MN247 - Acct. key for provisions missing for cond. type &, settlement schema &

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 247

• Message text: Acct. key for provisions missing for cond. type &, settlement schema &

What causes this issue?

For settlement accounting in respect of rebate arrangement &V3&,
provisions for accrued income have to be dissolved (reversed). However,
the account key permitting account determination for rebate income and
provisions for income has not been entered in settlement schema &V2&.
Without the account key, neither the release of the billing document to
Financial Accounting nor credit-side posting is 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 account key for provisions for accrued income for
condition type &V1& in calculation schema &V2&.

<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 MN247 - Acct. key for provisions missing for cond. type &, settlement schema & ?

  The SAP error message MN247 indicates that there is a missing account key for provisions related to a specific condition type and settlement schema. This error typically occurs during the settlement process in SAP, particularly in the context of controlling (CO) and financial accounting (FI) modules.
  Cause:
  
  Missing Account Key: The primary cause of this error is that the account key for the specified condition type is not defined in the system. This can happen if the configuration for the condition type is incomplete or if the necessary account assignments have not been made.
  Settlement Schema Issues: The settlement schema may not be properly configured to handle the specific condition type, leading to the inability to find the appropriate account key.
  Incorrect Configuration: There may be incorrect or missing configuration settings in the pricing procedure or settlement profile that are preventing the system from determining the correct account key.
  
  Solution:
  
  
  Check Configuration:
  
  Go to the configuration settings for the condition type in the SAP system. You can do this by navigating to the following path:
  
  SPRO > Controlling > Product Cost Controlling > Cost Object Controlling > Settlement > Define Settlement Profiles.
  
  
  Ensure that the account key for provisions is correctly assigned to the relevant condition type.
  
  
  
  Define Account Keys:
  
  If the account key is missing, you will need to define it. This can be done in the following path:
  
  SPRO > Financial Accounting > General Ledger > Master Data > G/L Accounts > Prepare G/L Accounts for Posting.
  
  
  Ensure that the account key is linked to the correct G/L accounts.
  
  
  
  Review Settlement Schema:
  
  Check the settlement schema to ensure that it includes the necessary condition types and that they are correctly configured to use the appropriate account keys.
  
  
  
  Test the Configuration:
  
  After making the necessary changes, perform a test settlement to ensure that the error no longer occurs.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for detailed guidance on configuring condition types and settlement profiles.
  
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes such as OKO7 (for settlement profiles) and KOH1 (for condition types) to access the relevant configuration settings.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  User Roles: Ensure that you have the necessary authorizations to make changes to the configuration settings in SAP.
  
  By following these steps, you should be able to resolve the MN247 error and ensure that the account key for provisions is correctly set up for the specified condition type and settlement schema.