Professional Documents
Culture Documents
Notes
ATP Tips
A. Scheduled run takes longer than one hour or Scheduled run is delayed.
In this case, the next run will abort because the prior run has not completed. No action is required
except to verify that the prior run does complete and that the next scheduled run completes as
well.
B. Error - Run Planning ODS Load
(Resp - Advanced Supply Chain Planner)
1. Other-->Requests-->Planning ODS Load
Parms
Instance:
TST
Timeout:
480
Nbr of Workers:6
Recalc Resource:
No
Recalc Sourcing:
No
Purge Sourcing:
No
C. If ATP Data Collection fails saying that ATP/ODS is already running and no conc
pgm/db processes are actually running (Planning ODS Load/MSCPDC) then
(Resp - Advanced Supply Chain Planner)
1. Other-->Requests-->Planning Data Collection - Purge Staging Tables
Instance:
TST
Validation:
No
D. Nightly Complete Refresh Hangs
Problem - All ' Planning ODS Load Worker' conc programs spawned by Planning ODS Load have
completed, but Planning ODS Load is still marked as Running/Normal
Symptom - Users will be unable to schedule lines - error = ATP Unavailable, Try ATP again later
Fix 1. Kill Planning ODS Load concurrent program through the application
2. Have DBAs kill associated process at the database level
At this point, the next ATP hourly net change refresh will abort, follow the steps as directed in the
concurrent program log file. Most likely this will be to:
a. Run Planning ODS Load (see parms above)
b. Run Planning Data Collection - Purge Staging Tables (see parms above)
ATP Tips
Normal Scheduling of ATP Data Collection
The Data Center will control this, but may need to be given the parameters
(responsibility IVCR OPS Requests US)
ATP Data Collections
For Complete Refresh
ATP Data Pull
Instance:
Nbr of Workers:6
Timeout:
Collection Type:
Sales Orders:
Planning ODS Load
Instance:
Timeout:
Nbr of Workers:6
TST
480
Complete Refresh
Complete Refresh
TST
480
TST
480