Condition record exists, but has not been set
I have maintained the condition record in VK11 well before creating the STO. The main condition type ZSTP is not flowing in the records in the delivery. When I check the analysis I see the message "Condition record exists, but has not been set" against the access for which the condition record has been maintained.
Claudia Neudeck replied
the message means, if you trigger a new pricing with B the condition will be determine in the document.
The message occurs often due to modifications via Userexits.
Let me explain:
If you have a customer own field in the condition table and this field will be filled after the pricing is runing then you will get these message, because the field is emty at the point of the pricing and it will be filled after the pricing.
An ohter point can be, that the condtion record was boocked after the creation of the document or the validity date of the condition record is in future.
Please check the validation of the condition record.
I hope that the information is helpful.