CANNOT USE NULL FOR DEFAULTING RULE
(Doc ID 1050023.1)
Last updated on OCTOBER 08, 2019
Applies to:Oracle Order Management - Version 11.5.9-11.5.10 and later
Information in this document applies to any platform.
Can I have a NULL value for a defaulting rule?
Today, we default the Customer PO on the order header to the order line. We do this for ALL customers. I have created a defaulting condition for the exception of 1 customer. For this 1 customer I would like a NULL value to default and appears I cannot easily do this.
I understand the intent of the defaulting rules is to not default NULL.
However, just so you understand what we are trying to do... currently we have setup a defaulting rule where the PO number defaults from the header to the line for all customers. This is the norm and required business process that all order lines have a po number.
The exception to the rule is for 1 customer where we do not want the header PO to default to the line as it requires a different unique value from the header.
The users are forgetting to go back and update this value on the order line.
This affects downstream processing.
We currently have a validation that this cannot be null ~ however because of the current defaulting rule we cannot get the NULL value on the order line....any other suggestions?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document