My Oracle Support Banner

Duplicated Version Number Data Is Created in OE_ORDER_HEADER_HISTORY, OE_ORDER_LINES_HISTORY When Updating Same Order from Different Session (Doc ID 2206282.1)

Last updated on FEBRUARY 20, 2019

Applies to:

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


Actual Behavior
Duplicated Version Number data is created in OE_ORDER_HEADER_HISTORY, OE_ORDER_LINES_HISTORY.

Expected Behavior
Duplicated Version Number data is not created in OE_ORDER_HEADER_HISTORY, OE_ORDER_LINES_HISTORY.

Steps to Reproduce

Create a processing constraint for update of order line and action as
generate version and require reason if the order is booked.

  1. Open 2 Sales Order Forms from UserA and UserB (SO FormA, SO FormB)
  2. Query the booked order in both SO FormA, SO FormB
  3. In SO FormA, update header field (Request Date) and save
  4. Go to line in both SO FormA and SO FormB
  5. In SO FormB, update order line 2.1 "Request Date" and save.
  6. In SO FormA, update order line 1.1 "Request Date" and save.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.