How To Fix JB036 - Enter a condition date

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 036

• Message text: Enter a condition date

What causes this issue?

You entered a date range as a selection criterium. The yield curves in
the extended MCM table are used for date ranges.
The specified yield curves were not found in the extended MCM table.
This indicates that an interpolation of the annual grid points has not
yet been made for these yield curves.
In this case (using a date range as a selection criterium), no yield
curves could be selected.

System Response

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

How to fix this error?

Enter a date for which you would like to create interest rates.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message JB036 - Enter a condition date ?

  The SAP error message JB036, which states "Enter a condition date," typically occurs in the context of pricing conditions in SAP, particularly when working with sales documents, purchase orders, or other transactions that involve condition records.
  
  Cause:
  The error is triggered when a user attempts to create or modify a pricing condition without specifying a condition date. The condition date is essential because it determines the validity period of the pricing condition. If this date is not provided, SAP cannot process the pricing information correctly.
  
  Solution:
  To resolve the JB036 error, follow these steps:
  
  
  Enter a Condition Date: 
  
  When you are in the relevant transaction (e.g., creating or changing a sales order, purchase order, or condition record), look for the field labeled "Condition Date" or similar.
  Enter a valid date that indicates when the pricing condition should be effective.
  
  
  
  Check Configuration:
  
  If you are consistently encountering this error, it may be worth checking the configuration settings for pricing