Supply Demand For Internal Orders Incorrect After Ship Confirm.

(Doc ID 1192357.1)

Last updated on JUNE 06, 2018

Applies to:

Oracle Shipping Execution - Version 12.1.2 and later
Information in this document applies to any platform.

Symptoms

Customer has an issue where every time an internal order is initially created, it shows the expected arrival date based on the transit time. However, after ship confirm, that date gets updated with the Ultimate Ship To Date from the delivery which is the request date, or the current date if the request date is in the past. Customer's expectation is to have the Ultimate Ship to Date always gets updated with the date it was shipped. Even if the request date is in the future, Customer would expect that Supply Demand would add the Transit time to that date to provide a real date for the supply.

EXPECTED BEHAVIOR
Expect that the Ultimate Ship To date reflects the actual date that the ship confirm took place.

STEPS
1. Enter a new sales order and note the Request Date.
2. Book the order and perform pick release and ship confirm.
3. Note that the Ultimate Ship To date reflects the Request Date on the order instead of the actual Ship Confirm date.

BUSINESS IMPACT
Due to this issue, users cannot obtain the correct Ultimate Ship To Date.

Changes

 

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