Sales Order Scheduling Performance Issue When ATP Is Based On Planned Data
(Doc ID 2164055.1)
Last updated on AUGUST 20, 2021
Applies to:Oracle Order Management - Version 12.2.4 and later
Information in this document applies to any platform.
In a VCP 188.8.131.52 Instance (Decentralized, using ATP Based on Planning Output):
Sales Order scheduling performance issue
Enter order with ATO Model, option class, options--> Order booking. Now during order booking, scheduling happens.
They have checked the following:
3 levels - all lines ATP at the FG and component level , 10 lines, 1 ship set, all debug off, time taken for pre-booking, booking and scheduling together= 01 min:27 sec out of which scheduling takes 1 min 07 seconds
3 levels- all line ATP at the FG and component level, 50 lines, 1 ship set, all debug off, time taken for pre-booking, booking and scheduling together= 5 min 16 seconds out of which scheduling takes 3 minutes 49 seconds.
So scheduling is taking maximum time and business is not in agreement of the same.
They have already followed the steps as per document- How to improve performance of entering ATP enabled items on Sales Order, Order Backlog Workbench, Or ATP Inquiry (Doc ID 457840.1) and seen considerable improvement but not able to meet Customer's business requirement.
-- Steps to reproduce the issue
1. Setup ATP multi level ATP as per GOP user and implementation guide for ATO model, option class and options.
2. Create an order with header and line details.
3. Run collections and ATP Plan.
4. Create order header and lines.
5. book the order and order will get scheduled as part of the process
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