How To Fix JB059 - No conditions found for account (& &)

SAP Error Message - Details

• Message type: E = Error

• Message class: JB - General Message Class for IS-B (Development Class JBD)

• Message number: 059

• Message text: No conditions found for account (& &)

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message JB059 - No conditions found for account (& &) ?

  The SAP error message JB059 "No conditions found for account (& &)" typically occurs in the context of pricing or condition records in SAP, particularly when dealing with sales and distribution (SD) or materials management (MM) modules. This error indicates that the system could not find any pricing conditions for the specified account or customer.
  Cause:
  
  Missing Condition Records: The most common cause is that there are no condition records set up for the specified account (customer or vendor) in the pricing procedure.
  Incorrect Account Assignment: The account number or key provided may be incorrect or not properly assigned in the system.
  Condition Type Not Maintained: The specific condition type being referenced may not have been maintained for the relevant account.
  Pricing Procedure Issues: The pricing procedure assigned to the sales document may not be configured correctly to include the necessary condition types.
  Validity Period: The condition records may not be valid for the date of the transaction, meaning they are either expired or not yet active.
  
  Solution:
  
  
  Check Condition Records: 
  
  Go to transaction code VK13 (Display Condition) or VK11 (Create Condition) to check if the necessary condition records exist for the account in question.
  Ensure that the condition records are maintained for the correct condition type and that they are valid for the relevant time period.
  
  
  
  Verify Account Assignment:
  
  Ensure that the account number provided in the transaction is correct and corresponds to the customer or vendor master data.
  
  
  
  Review Pricing Procedure:
  
  Check the pricing procedure assigned to the sales document or purchase order. Ensure that it includes the necessary condition types and that they are configured correctly.
  
  
  
  Check Validity Dates:
  
  Verify the validity dates of the condition records to ensure they are active for the date of the transaction.
  
  
  
  Consult with Configuration Team:
  
  If you are unable to resolve the issue, consult with your SAP configuration team to ensure that the pricing procedure and condition types are set up correctly.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  VK11 - Create Condition
  VK12 - Change Condition
  VK13 - Display Condition
  V/06 - Maintain Pricing Procedure
  
  
  Documentation: Refer to SAP Help documentation for detailed information on pricing procedures and condition records.
  User Exits and BAdIs: If custom logic is involved, check for any user exits or BAdIs that might affect pricing determination.
  
  By following these steps, you should be able to identify and resolve the issue related to the JB059 error message in SAP.