Order Import failure leaves phantom demand records in msc_sales_orders
(Doc ID 2523120.1)
Last updated on APRIL 10, 2019
Applies to:Oracle Order Management - Version 12.2.6 and later
Information in this document applies to any platform.
# ACTUAL BEHAVIOR
Order Import leaves phantom demand records in msc_sales_orders after import failure
# EXPECTED BEHAVIOR
Expect no record in msc_sales_orders after order import failure
1. Go to: Order Management Super User
2. Run Order Import
- When an internal order is imported into EBS instance for several items (say, two items A, B) ...
-- item-A has an Item Orderability rule which prevents the import (or, any other cause that can lead to failure of Order Import)
-- sales order demand created during the import for the other item-B remains in MSC_SALES_ORDERS table whereas the order is not imported.
- This is causing ATP inconsistencies afterwards for item-B
- All items are setup to use ATP based on collected data.
# BUSINESS IMPACT
Due to this issue, phantom demand records remain in msc_sales_orders table after Order Import failure, thereby causing ATP inconsistencies.
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