Version Change Doesn't Trigger After Updates When Querying From Sales Agreement Organizer (Doc ID 2248538.1)

Last updated on MARCH 28, 2017

Applies to:

Oracle Order Management - Version 12.2.4 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.4 version, Transaction Entry

ACTUAL BEHAVIOR
---------------
Whenever you query sales agreement from SA organizer form and update the Blanket max quantity which has processing constraint enabled for update operation,version change doesn't trigger for the agreements which doesn't have customer(Sold to) details at header level.

EXPECTED BEHAVIOR
-----------------------
Expect that Processing constraint should trigger when opening sales agreement from Sales Agreement Organizer

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1.Defined Processing Constraints setup to change the version number when Max Order Qty is changed. This works only when:
2 Open the Sales Agreement form,
3 enter query more (F11), enter (Active) SA number and then execute query (control+F11)
4 Change the max qty agreed and save
5 This triggers new version number on SA header
6.But this doesn't work when we query the SA number using Sales Agreement Organizer as follows:
7 Open the Sales Agreement Organizer form,
8 Enter (Active) SA number and then click on Find button
9 Click on Open Agreement button
10 Change the max qty agreed and then save
11This DOES NOT trigger new version number on SA header

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot use sales agreement organizer

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