Inactive Modifier Taken Into Account By Price_Request API When Running With Pattern Search Engine
Last updated on JANUARY 30, 2018
Applies to:Oracle Advanced Pricing - Version 12.2 and later
Information in this document applies to any platform.
Find that when one uses pattern search that an inactive Modifier had been taken into consideration in the price calculated by the Price_Request() API.
This inactive Modifier is NOT taken into consideration when using the Traditional Search - which is correct.
Expects that this inactive Modifier is NOT taken into consideration when using the pattern search engine.
The issue can be reproduced at will with the following steps:
1. Responsibility: Order Management Super User (or equivalent)
2. Navigate to: Orders, Returns > Sales Orders
3. Enter an order line and save.
Pattern Search Engine was enabled:
Profile Options set as follows:
QP: Pattern Search = Both Modifier and Price List
QP: Pattern Search Path = Search Headers First
Concurrent program Pattern Upgrade was run wide-open
Oracle Pricing Manager responsibility, navigate to: Reports
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