My Oracle Support Banner

PRC: PO: Original Promised Ship Date Not Populating After Supplier Creates A Change Order (Doc ID 2667048.1)

Last updated on MAY 06, 2020

Applies to:

Oracle Fusion Purchasing Cloud Service - Version 11.13.20.01.0 and later
Oracle Fusion Purchasing - Version 11.13.20.01.0 and later
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR

Original Promised Ship date Not Populating after Supplier creates a change order

When Buyer Managed Transportation (BMT) selected on the Purchase order, Promise Ship Date is not getting archived into Original Promised Ship Date field when Supplier creates a change order.



EXPECTED BEHAVIOR

Original Promised Ship Date is retained.


STEPS TO REPRODUCE THE ISSUE

The issue can be reproduced at will with the following steps:
1) Create a PO, Enable BMT flag.
2) Enter a requested ship date 2/15/20 and submit the PO. The PO goes to Pending Supplier Acknowledgement.
3) Log into Supplier Portal. Since the requested ship date is not acceptable, edit the PO. Enter Promise Date as 3/3/20 and submit the PO.
4) The PO goes into Open status. Now the Promise date shows as 3/3/20 but Original Promised Ship Date is blank.

 

Changes

 

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
Changes
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.