Restrict data flow to MRP_ATP_DETAILS_TEMP

Question

Hi,
we have a custom program which pulls the details of item availability for SOs through ATP rules. we are using the api MRP_ATP_PUB.CALL_ATP to pull the atp detail for the items.
but when this program is run each time it inserts about *70million* rows into MRP_ATP_DETAILS_TEMP table. then we have to run the purge atp temp table program to truncate the temp table. But as per our DBA this is a risk for the db storage space. so we have stopped running of this program now.
please answer my below 2 questions -
1) is it really a risk if the table rows reaches 70 million records? upto what maximum number of rows it is safe?
2) is there a way to stop data insert to atp temp tables when the api is called? any profile option or debug level responsible for this? we dont want data to be inserted into the temp table.
Regards,
Samir Kumar Das

Answer 1

1) is it really a risk if the table rows reaches 70 million records? upto what maximum number of rows it is safe?
There is no magic number. It depends on the size of your database. 70m is huge for a small company but peanuts for say, Boeing.
2) is there a way to stop data insert to atp temp tables when the api is called? any profile option or debug level responsible for this? we dont want data to be inserted into the temp table
Oracle uses this table to calculate ATP results. So if you use the API, it will insert records.
Having said that, 70m for ATP check is excessive.
Are you doing an ATP check for ALL open sales orders?
If it is just one or even hundred order lines, 70m seems too much. You need to raise an SR with Oracle.
If you are doing it for all open lines (and there are thousands and thousands) here are a few things you can try
1) Find how many sales order lines the custom program processes. See if you can reduce it by putting more conditions (such as ignore orders more than a year old, ignore orders more than 2 months in future etc.)
2) Try to process in chunks. Instead of calling purge AFTER your custom program finishes, try calling it from your custom program every time say x number of order lines are processed.
Sandeep Gandhi