How To Fix WS155 - No account key exists for condition type &

SAP Error Message - Details

• Message type: E = Error

• Message class: WS - Supplier Billing Document

• Message number: 155

• Message text: No account key exists for condition type &

What causes this issue?

As part of conditions determination, the system found conditions without
account key relevant for the settlement document list. Conditions that
do not have an account key are not passed on to Financial Accounting,
i.e. no G/L lines are created for these conditions.

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

System Response

This is possibly an account determination error.

How to fix this error?

Check if the settings for the account key for condition type &V1& are
correct. Check the Customizing settings for calculation schemas for the
settlement document list items. If the settings are wrong, you have to
cancel the documents that have faulty account keys and enter them again.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message WS155 - No account key exists for condition type & ?

  Certainly! Here's a detailed explanation for the SAP error message:
  
  SAP Error Message:
  WS155 No account key exists for condition type &
  
  Cause:
  This error occurs during pricing or condition processing in SAP Sales and Distribution (SD) or Materials Management (MM) when the system tries to determine the account key for a particular condition type but fails to find it.
  
  Account key is a crucial element in pricing procedures that links condition types to specific General Ledger (G/L) accounts in the system.
  The system uses the account key to find the correct G/L account for posting pricing conditions (e.g., discounts, surcharges, taxes).
  If the account key is missing or not maintained for the condition type in the pricing procedure or in the account determination configuration, the system cannot proceed and throws this error.
  
  
  Where it happens:
  
  During invoice creation, billing, or goods movement when pricing conditions are being posted.
  In SD pricing procedure or MM condition technique.
  When the system tries to determine the G/L account for a condition type but the account key is not assigned.
  
  
  Solution:
  
  
  Check the Condition Type Configuration:
  
  Go to transaction V/06 (Maintain Condition Types).
  Verify that the condition type in question has an Account Key assigned.
  If missing, assign the appropriate account key.
  
  
  
  Check Account Determination for the Account Key:
  
  Go to transaction OBYC (Automatic Account Determination).
  Verify that the account key assigned to the condition type has valid G/L accounts maintained for the relevant transaction keys.
  Maintain the G/L accounts if missing.
  
  
  
  Check Pricing Procedure:
  
  Go to transaction V/08 (Pricing Procedure).
  Ensure the condition type is correctly included and linked with the account key.
  
  
  
  Check Condition Records:
  
  Sometimes, the condition records might be incomplete or incorrect.
  Use VK13 to display condition records and verify.
  
  
  
  Check Account Determination Procedure:
  
  For SD billing, check the account determination procedure assigned to the sales area.
  Use transaction OVK1 to check the account determination procedure.
  
  
  
  
  Additional Information:
  
  The account key is a bridge between pricing conditions and financial accounting.
  Common account keys include PR00 (Price), MWST (Tax), SKTO (Cash Discount), etc.
  If you are dealing with custom condition types, ensure that the account key is properly configured.
  This error is often encountered when customizing new pricing conditions or when migrating data.
  
  
  Summary:
  
  
  
  Aspect
  Details
  
  
  
  
  Error Message
  WS155 No account key exists for condition type &
  
  
  Cause
  Missing account key assignment for condition type
  
  
  Solution
  Assign account key in V/06 and maintain G/L accounts in OBYC
  
  
  Transactions to Check
  V/06, OBYC, V/08, VK13, OVK1
  
  
  
  
  If you provide the specific condition type causing the error, I can help you with more targeted steps.
  
  Let me know if you need help with the exact configuration steps!