How To Reduce No ATP Error Time During Complete Refresh Data Collection
(Doc ID 2299123.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Advanced Supply Chain Planning - Version 12.2.4 and later
Information in this document applies to any platform.
On : 12.2.4 version, Data Collections
How to reduce No ATP error time during Complete Refresh data collection
From last 4-5 months , Complete Refresh Data collection request is running in R12 ASCP Prod instance to collect all data from R12 EBS Prod instance at 23.30 GMT (6.30 SGT).
We are running this request at this time because US , EMEA, India business are closed during this period .
But any User or Dealer cannot book the sales order from 00.25 am to 00.58 am (7.25 am to 7.58 am Singapore time) due to ATP error ( Item + Sourcing Rule data collection). But In July 2017 Singapore Org + one of China Org will be Go live in R12 instance . So we want to reduce this time as user can not book the sales orders during this time through OM or i_store. One of work around we tested that we will collect data of only ATP Plan orgs (42 Orgs) during working days which ATP based on planned data and on Saturday , Sunday we will collect ALL Orgs data including Sales and service which ATP is based data collected. But this has reduce the such time from 35 min to 24 min. So we want to find any alternative to reduce this time or any other work around . We do not want to run Net refresh data collection as COE team observed many issues raised by users from all region . Also we are collecting many Item categories in ASCP instance . Can you provide the solution to reduce the Item category count ?
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