You are on page 1of 3

ATP Tips

Notes

Custom ATP called from PLL - xxont_atp_ck_pkg.main_proc


Right-click schedule will call seeded ATP
Custom Debugging - XXONT Custom ATP Logging = Yes at user level - file at /var/tmp on
database server (usaxs09)
Seeded Debugging - MSC: ATP Debug Mode = Debugging or trace - debug file by session
name found at /var/tmp
ATP does not include Purchase Orders for supply
Secondary/Tertiary determination based on quantity - comes into play when not enough
inventory in any one Distribution Center (DC)
XXONT Re-Try Custom ATP Notifications daily at 8 PM
ATP Notification Summary - Preparing an alert for this information
Known problem - Item specified is invalid or does not exist in the warehouse specified Requires knowing rank of DCs. Until recently, haven't been able to find this. Now, need to
determine if number of errors warrants modifying custom code

Sourcing Logic Summary


(current as of 5/25/06)
if total qty > 0
if l_total_quantity >= ordered qty then
-- Overall there is enough
if pri qty > ordered qty then
-- schedule for primary
if more than 0 in primary, but pri not > ordered then
if enough in primary and secondary then
-- schedule in primary and secondary
if some qty in secondary (and non-0 in pri)
-- schedule in secondary, remaining in pri (ssd is time fence date)
if some qty in tertiary (and non-0 in pri) --- don't see how this can be hit
-- schedule in tertiary, remaining in pri
if pri = 0 then
if tertiary = 0 or secondary has enough then
-- put all in secondary (not sure tertiary = 0 can be hit)
else.....
-- put in secondary and tertiary
elseif l_total_quantity < ordered quantity then
if secondary <> 0 then
-- schedule in secondary, rest in primary
else
-- schedule all in primary
else ( total qty = 0)
-- schedule all in primary

ATP Tips

Dealing with ATP Data Collection

ATP Data Collection Schedule


Complete - 1 AM Daily
Net Change - hourly from 7 AM to 10 PM
If the 1 AM Complete Refresh fails that is a big deal. Potentially Customer Service will not
be able to place orders until the issue is resolved.
It is not as critical if one of the Net Change Refreshes fails. If a Net Change Refresh fails,
you can wait until the next refresh runs to see if the problem corrects itself.

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

For Net Change Refresh


ATP Data Pull
Instance:
TST
Nbr of Workers:6
Timeout:
480
Collection Type:
Net Change Refresh
Sales Orders:
Net Change Refresh
Planning ODS Load
Instance:
Timeout:
Nbr of Workers:6

TST
480