Need By Date Is Mismatch Between Requisition Form and Printed Requisitions Report (Doc ID 2051377.1)

Last updated on SEPTEMBER 02, 2015

Applies to:

Oracle Purchasing - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

On : 12.0.1 version, Reports - PO and RCV

ACTUAL BEHAVIOR
---------------
Printed Requisitions Report (XML) output shows Requisition Need-By Date is different with value on Requisition entry form.
e.g. In application Requisition need-by date = 31-Dec-2011;
But in Printed Requisitions Report (XML) output shows need-by date = 30-Dec-2011.

EXPECTED BEHAVIOR
-----------------------
Printed Requisitions Report (XML) output shows same need-by date value with need-by date on Requisition entry form.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Purchasing > Requisition > create Requisition, save and submit for approval.
line level
e.g. need-by date = 31-DEC-2011
2. Submit 'Printed Requisitions Report (XML)' > check the output, find need-by date shows in the report is e.g. 30-DEC-2011
which is mismatch with Requisition Need-By date on Requisition entry form.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot get synchronized need-by date between Requisition entry form and Printed Requisitions Report (XML) output. this will make the user who is looking at the Printed Requisitions Report (XML) output can not get the correct Requisition need-by date.

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