Date parameter on a periodic schedule request jumps to future years on resubmission (Doc ID 2850381.1)

Last updated on FEBRUARY 22, 2022

Applies to:

Symptoms

On Production: 12.1.3 version, Request Submission/Scheduling

ACTUAL BEHAVIOR
---------------
When scheduling the Order Management concurrent program 'Reserve Orders' OMRSVORD, the parameter 'Line Request Date (High)' changes to a future 2024 year on resubmitted requests.

The date on the initial request is okay.

This issue occurs only for this one concurrent program.
 

EXPECTED BEHAVIOR
-----------------------
The parameter 'Line Request Date (High)' should be a valid current date on the resubmitted requests


STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1. Responsibility: Order Management Super User
2. Navigate: Reports, Requests > Run Requests
3. Select the “Reserve Orders” concurrent request

4. Enter parameters:
Schedule the Reserve Orders with below parameters
Parameters:
Use Reservation Time Fence : No
Warehouse : BEG
Line Request Date (High) : 23-DEC-2021 00:00:00
Booked : Yes
Reservation Mode: Partial Reservation(Include Only Unreserved Lines)
Reservation Run Types : Reserve
Order By: Date Ordered

Run every hour
5. Submit the request and wait for it to complete.
6. Result: Reserve Orders program taking 2024 or 2022 as a request date for
subsequent run.
 

Changes

Cause

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