Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: 60 - Real Estate
Message number: 911
Message text: Conditions for & not found
No conditions for the active rental agreement have been found for the
current date. The last conditions assigned to the rental agreement are
loaded instead.
Error message extract from SAP system. Copyright SAP SE.
60911
- Conditions for & not found ?The SAP error message "60911 Conditions for & not found" typically indicates that the system is unable to find the necessary condition records for a specific pricing condition type in the context of sales documents, such as sales orders or quotations. This error can occur in various scenarios, including pricing determination, discounts, or surcharges.
Causes:
- Missing Condition Records: The most common cause is that the required condition records for the specified condition type do not exist in the system.
- Incorrect Condition Type: The condition type being referenced may not be correctly configured or may not be applicable to the current transaction.
- Master Data Issues: Related master data (like customer master, material master, or info records) may not be set up correctly, leading to the absence of condition records.
- Pricing Procedure Configuration: The pricing procedure assigned to the sales document may not include the necessary condition types.
- Access Sequence Issues: The access sequence for the condition type may not be set up correctly, preventing the system from finding the condition records.
Solutions:
Check Condition Records:
- Use transaction code
VK11
(Create Condition) orVK12
(Change Condition) to check if the condition records for the specific condition type exist.- If they do not exist, create the necessary condition records.
Review Pricing Procedure:
- Check the pricing procedure assigned to the sales document type. Ensure that it includes the required condition types.
- Use transaction code
V/08
to review and modify pricing procedures if necessary.Verify Access Sequences:
- Check the access sequence assigned to the condition type. Ensure that it is correctly configured to retrieve the condition records based on the relevant keys (like customer, material, etc.).
- Use transaction code
V/07
to review and modify access sequences.Check Master Data:
- Ensure that the relevant master data (customer, material, etc.) is correctly maintained and that it corresponds to the condition records.
- Verify that the customer and material are correctly linked in the system.
Consult Documentation:
- Review SAP documentation or consult with your SAP support team for specific details related to your configuration and setup.
Related Information:
Transaction Codes:
VK11
, VK12
: For creating and changing condition records.V/08
: For maintaining pricing procedures.V/07
: For maintaining access sequences.SAP Notes: Check for any relevant SAP Notes that may address specific issues related to this error message.
Debugging: If the issue persists, consider debugging the pricing procedure to identify where the condition records are not being found.
By following these steps, you should be able to identify the root cause of the error and implement the necessary solutions to resolve it.
Get instant SAP help. Sign up for our Free Essentials Plan.
60910
Conditions for lease-out & & & not found
What causes this issue? There are no conditions for the rental agreement you are now processing.System Response The system issues an error message a...
60909
Enter contract number
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
60912
Entry not suitable for any object type
What causes this issue? The entries you have made are not enough to determine which object type you want to address.System Response The system issue...
60913
RA & & & not adjusted: Adjustment data not found
What causes this issue? The rent adjustment data (Table VIMI16) for the agreement you are processing could not be read. This is probably a program er...
Click on this link to search all SAP messages.