Order Management Defaulting Rule Is Not Working Based On The Order Type Rule
Last updated on JANUARY 09, 2018
Applies to:Oracle Order Management - Version 12.1.3 and later
Information in this document applies to any platform.
On : 12.1.2 version, Transaction Payment
Order Management defaulting is not working based on the Order Type rule when Application “Order Management” and Entity “Order Header”.
User able to create rule based on the Defaulting Condition Template with validation rules attribute on Org and Order Type by grouping these in "1". Saying that these two condition must be satisfied then only ship to location will be populate otherwise not. Now the issue is when you build your Defaulting Condition Template based only Org it is working fine but when you add order type then stops firing.
Created one table to capture just a condition and the value returned during execution but found that order type has some junk character which does not make sense and causing rule to not fire.
Why is it when using Org and order type it does not work together when using defaulting Condition Template with validation rules attributes? What setup is needed to get this to work?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms