When we try to book a SO (which has an invalid configuration) we get the following error :
Configuration validation resulted in error(s).
This error prevents SO booking.
Whereas when we have an already booked SO, and add an invalid configuration onto it Oracle puts the SO line / Configuration on config Validation Hold.
How can we allow SO (with invalid configurations) to book successfully (and have those SO line go to Config Validation Hold) ? Any thoughts ?
I see the same behavior as you describe and have never found any settings or profiles to change the behavior. I'd also be interested to know if anyone has overcome this situation.