Booking A Sales Order Created Inconsistent ATP Resource Requirement In ASCP Due To CTO Code
(Doc ID 2018140.1)
Last updated on FEBRUARY 27, 2019
Applies to:Oracle Configure to Order - Version 12.1.3 and later
Information in this document applies to any platform.
On : 12.1.3 version, Scheduling & Planning
Booking a Sales Order created Inconsistent ATP Resource requirement in ASCP due to CTO code
It is observed that GOP is still not getting consistent values for ATO_PARENT_MODEL_LINE_IDs. Customer has given a testcase where, for the Same sales order, first Availability_Check Failed and Subsequent Availability_Check succeeded. In both the cases, line_ids are same as inquiry was performed on the same order.
The issue can be reproduced at will with the following steps:
a) Enter PTO item in the sales order
b) Click Configurator button
c) Select attributes / options and click finish button
d) At this point all the items gets populated (based on configurator rules) in sales order form
When booking a sales order, sometimes they see the correct number of requirement lines. This is the expectation.
But many times for the same configuration ( create new sales order by copying or new sales order by doing configuration) they are seeing 3 or 2 or 1 or even null records for resource requirements.
They could not observe a pattern here (inconsistent results).
In cases where they do not see equal lines of resource requirements, these are cases where the resource requirements are not created for the resource.
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