How To Manually Update Schedule Arrival Date, Request Date And Schedule Ship Date
(Doc ID 730018.1)
Last updated on MAY 05, 2021
Applies to:Oracle Order Management - Version 188.8.131.52 to 12.2.8 [Release 11.5.10 to 12.2]
Information in this document applies to any platform.
You want to enter order lines and have the ability to control the following dates:
- Request Date
- Schedule Ship Date
- Schedule Arrival Date
The business scenario and setups are:
The Request Date is used to reflect the date that the customer wants the item. There is no Defaulting Rule setup for the Request Date or the Scheduled Arrival Date (SAD). Instead the user is manually entering the Request Date on the order line. Standard ATP Code to determine availability for the line items to determine the Schedule Ship Date (SSD) is being used. User also is manually entering SAD, but the following error is raised:
Schedule arrival date or Schedule Ship Date can be recalculated if you change the request date or the schedule ship or arrival date.
Is there any setup or dependency that can be disabled in order to be able to manually enter all the above dates on an order line?
1. Order Management responsibility
2. Orders, Returns > Sales Orders
3. Enter order header with Order Date Type = Ship
4. Enter line item & quantity
5. Manually enter Request Date = 31-JUL-08 (this is the date the customer wants the item - you want to retain this date for customer sat records, even if you cannot meet this date to ship to the customer)
6. Click Availability button > Results show that the item is not available on request date, but will be on 19-AUG-08
7. Manually enter SSD = 19-AUG-08
8. Manually enter SAD = 22-AUG-08 (since they think it will take about 2 days to ship to customer)
9. Results in the above error.
10. Tried to use 'Override ATP', but the error message still displays.
11. User tried to set the Order Date Type = Arrival in the order header, and they were able to update the SAD. But when they tried to update the SSD with the Availability in the ATP pop-up then the same error as referenced above is raised.
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