Order Import Does Not Price Correctly For Modifier Qualified With A TSN Modified Attribute
Last updated on MARCH 08, 2017
Applies to:Oracle Order Management - Version 18.104.22.168 to 12.2.3 [Release 11.5.10 to 12.2]
Information in this document applies to any platform.
When the customer has pricing modifiers setup such that a modifier is
disqualified based on a field that is modified by a Term Substitution (TSN)
modifier, Order Import is giving different results than to those shown through order entry
on the sales order form.
During Order Import, only a single pricing call being made so the field
modified by the TSN modifier is updated, but the modifier that is applied due
to the previous term isn't removed. During order entry, there are two
pricing calls made in succession so the TSN is applied and then the
qualification (and subsequent removal) of the modifier upon this is based is removed.
It is expected that the price should be calculated the same if the same order
details are entered through the sales order form or via order import.
The issue can be reproduced at will with the following steps:
1. Setup modifiers such that the qualification of one is based on an attribute that is changed by a TSN modifier.
2. Run Order Import
3. The qualification of the modifier is coming from the pre-tsn-midifiedqualifier attribute value.
The issue has the following business impact:
Due to this issue, users are required to reprice all orders on subsequent Order Import.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms