My Oracle Support Banner

E1: 42: Enhancement Request to Add Request Date in the Data Sequencing for R42118 Backorder Release process (Doc ID 2738264.1)

Last updated on DECEMBER 18, 2020

Applies to:

JD Edwards EnterpriseOne Sales Order Management - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

Data sequencing by Requested Date (DRQJ) does not work. R42118 still releases order by DOCO

Steps to replicate:

  1. In P41001, set availability for branch 30 as follows: Subtract Quantity HardCommit to SO, Subtract Quantity HardCommit to WO, Subtract Quantity On Hold
  2. Find an item with no on hand.
  3. Create a 2 sales orders, 1st one with a Requested Date (DRQJ) date of August 30. 2nd one with 2 lines, line 1 Requested Date (DRQJ) of August 29, line 2 with Requested Date (DRQJ) of August 28
  4. Adjust in 2 lots, quantity of 1 each.
  5. Version on R42118 has data sequencing by Request Date (DRQJ) so we would expect that the 7936 line 2 gets committed first, then 7936 line 1, then 7935 line 1.
  6. Verify R42118 sequences by DOCO and does not commit in the correct order.

In the above scenario, client wants to sequence by Request Date(DRQJ), however it would be best if R42118 was corrected so that Data Sequencing worked for all fields as it is an option to run the job this way.

Cause

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
Symptoms
Cause
Solution
References


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