Qualifier Is Not Considered While Adding a Manual Modifier Using OE_ORDER_PUB.PROCESS_ORDER API (Doc ID 1622734.1)

Last updated on NOVEMBER 30, 2016

Applies to:

Oracle Advanced Pricing - Version 11.5.10 and later
Oracle Order Management - Version 11.5.10.0 and later
Information in this document applies to any platform.

Symptoms

On : 12.1.3 version, Qualifiers

ACTUAL BEHAVIOR
---------------

OE_ORDER_PUB.PROCESS_ORDER api does not honor qualifier. More than 80% of Orders come through Interfaces. There are several interfaces that use the Modifier API and none of them are picking up Qualifiers. Hence 80% of the Sales Order are coming through with wrong prices. When I try to add a modifier which is excluded by qualifier, system doesn't show in the LOV. That functionality is correct. My requirement is when I try to add a modifier which is excluded by qualifier thru API, system should not add that modifier to the order line.

I have created a modifier as M1. I created a qualifier Q1 to exclude customer C1. I created a order thru front end for customer C1. When I try to add modifier M1 using Actions, I am not able to see the modifier M1 in the list, because of qualifier Q1. But when I try to add modifier to the same Order ( for customer C1), using OE_ORDER_PUB.PROCESS_ORDER, api adds modifier M1 to order line, even though the Order is for customer C1.

  ------ Unable to see modifier, is the correct action. But when I upload thru API, modifier is getting created.


For example, I have created a modifier called 'RT Test'. I added one qualifier to this modifier, to exclude customer 'XX CUSTOMER'. I created one order for customer 'XX CUSTOMER'. In the lines block I choose View Adjustments and tried to add modifier 'RT Test'. In the LOV I am not able to see the modifier 'RT Test', since it is excluded by the qualifier. This is correct.

But when I try to add the modifier 'RT Test' using api, to an order which was created for the customer 'XX CUSTOMER'. The api adds modifier 'RT Test' to the order line. This is not expected one. System should not add this modifier 'RT Test' to this order because the order was created for 'XX CUSTOMER'. Here the qualifier is not applied. I need to know why this qualifier is applied while we add modifier thru api.




EXPECTED BEHAVIOR
-----------------------
Expect OE_ORDER_PUB.PROCESS_ORDER api to honor or validate the qualifier to not add the modifier (like the form does).

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Responsibility: Pricing Manager / Order Management Super User
2. Navigate: create a modifier as M1
3. Create a qualifier Q1 to exclude customer C1.
4, Created a order thru front end for customer C1. When trying to add modifier M1 using Actions, I am not able to see the modifier M1 in the list, because of qualifier Q1 (correct and expected result).
However, when trying to add modifier to the same Order ( for customer C1), using OE_ORDER_PUB.PROCESS_ORDER, api adds modifier M1 to order line, even though the Order is for customer C1.
5. Actions > View Adjustments > Expect OE_ORDER_PUB.PROCESS_ORDER api to honor or validate the qualifier to not add the modifier (like the form does).

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot use the OE_ORDER_PUB.PROCESS_ORDER api because it does not honor the qualifier.

Cause

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