JDE-VCP Collection Program Changing The Internal Requisiton's Due Date Instead Of Dock Date
Last updated on MARCH 08, 2017
Applies to:Oracle Advanced Supply Chain Planning - Version 188.8.131.52 and later
Information in this document applies to any platform.
184.108.40.206 - Collect Planning Data (Collections from JDE - VCP)
Once the ISO is shipped and inventory is in Intransit Shipment, JDE-VCP Collection Program (ODS Load) changes the Intransit Shipment's Dock Date in case of non-working date.
Why is JDE-VCP Collection Program (ODS Load) treating Internal Requisition and Intransit Shipment dates differently?
In the Collections workbench, we can see a Suggested Dock Date that is past the Suggested Due Date.
There is no issue with plan output, only with the collected data.
The customer is looking for a consistent approach for IR/ISO order progression.
Collection logic for IR and Intransit Shipment must be consistent while calculating the DOCK and DUE dates.
See uploaded screenshots.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms