Scheduling Of Sales Orders Failing With "Scheduling Failed. No APS Instance Defined." Error in ATP Session File - Error in mrp_ap_apps_instances : -6508
(Doc ID 2056391.1)
Last updated on DECEMBER 29, 2022
Applies to:Oracle Global Order Promising - Version 12.1.3 and later
Information in this document applies to any platform.
On : 126.96.36.199
Scheduling of sales orders failing with "Scheduling failed. No APS instance defined." error
While trying to schedule sales orders using GOP, we are getting the below error message, "Scheduling failed. No APS instance defined. Set APS instance and run collections".
We have verified all the ATP related set ups and the are fine.
- Instance definition – ATP Flag checked - Yes
- SO header & lines have warehouse - Yes
- Db links are fine - Yes -
- Collections & ATP plan have been run successfully - Yes
- DBAs confirmed that RAC setup for GOP is fine. - Yes
This issue is stalling our testing and development activities and is impacting our milestones severely.
"Scheduling failed. No APS instance defined. Set APS instance and run collections"
This error is usually caused by failing to get row back in ATP code when executing
select instance_id, a2m_dblink from mrp_ap_apps_instances;
-- this is a view which isolates row in mrp_ap_apps_instances_all where allow_atp_flag=1
This setup issue is discussed in Note 421069.1.
The issue can be reproduced at will with the following steps:
- Order Management
- Order , Returns
- Sales Order -> Lines
Due to this issue, users cannot schedule sales orders using GOP
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