Scribd
Upload
452 views2 pages

Document To Purge ATP Table

Very Good Doc

Uploaded by

Keyur Pandya
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
452 views2 pages

Document To Purge ATP Table

Very Good Doc

Uploaded by

Keyur Pandya
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

5/9/12 https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=HOWTO&id=329398.

How Often Should the Program Purge ATP Temp Tables be Run? [ID 329398.1]

Modified 02-AUG-2011 Type HOWTO Status PUBLISHED

In this Document
Goal
Solution
FAQ:
References

Applies to:
Oracle Advanced Supply Chain Planning - Version: 11.5.10 to 12.1.3 - Release: 11.5 to 12.1
Information in this document applies to any platform.
EXECUTABLE:MSCATPPURG - Purge ATP Temp Tables

Goal
How Often Should the Program Purge ATP Temp Table be Run?

Solution
Description: GOP stores temporary data (supply, demand, horizontal plan, pegging) for each ATP transaction. The table size grows proportionally to the number of ATP transactions. This concurrent pro
according to the 'age of the data' you specify for deletion. We recommend users to run this program Weekly, Daily or even Hourly if your ATP transaction volume is very high (see Notes).

Parameter of the concurrent program:


Age of Entry (in hours): you can specify the age of the data you want to delete.
For example, if you enter '1', this program will delete any data that is more than 1 hour old.
If 0 <zero> is entered, then the tables will be truncated. This should only be used when users are not entering Sales Orders or using the ATP inquiry.

Tables deleted by this process are:

MRP_ATP_SCHEDULE_TEMP
MRP_ATP_DETAILS_TEMP
in 11.5.10.2
Rate and above also includes MSC_ATP_SRC_PROFILE_TEMP
this document

Notes:
1. This data is throw away data populated for the purpose of providing data for Scheduling results (MRP_ATP_SCHEDULE_TEMP) and that is viewed in the ATP Details window (MRP_ATP_DETAILS_TE
-- Once the Availability window is closed, the data has no purpose unless debugging an ATP issue and data is requested by Support or DEV to debug the issue.

2. More data will be present in the table MRP_ATP_DETAILS_TEMP if profile MRP: Calculate Supply/Demand = Yes, since we write extra data for the ATP Details and other screens.
When the profile = Yes, then MRP_ATP_DETAILS_TEMP gets rows with record_type = 1, 2 and 3.
Record Type 1 and 2 are used to show detailed information available when you use rt-click functionality in the Pegging window of the ATP Details to view Supply Demand, or Horizontal Plan or other info
Record_Type = 3 is the pegging information seen in the ATP details screen.

When the profile = No, we still insert record_type = 3 into the table so we can display the pegging information in the ATP Details screen.
For example, if the item is a large configuration with many rows in the pegging view, then we could still insert many records into the table with only record_type = 3

3. This data has no effect on ASCP planning.


BUT - if you have separate EBS Source and APS Destination, then you need to run this request on BOTH the EBS Source and APS Destination.

4. Many customers will set this to run once per week with parameter 250 (hours).
OR In higher volume operations, it may run once per day with parameter 24,
OR in very high volume operations, it may run even once or twice per hour with parameter = 1
Note: Before setting up the request to run on a schedule, it is important to truncate the tables (run with parameter = 0) to make sure the space is recovered

5. Support may request that this be put on hold during an investigation of an ATP issue, but this is not always required.

6. If the number of rows in MRP_ATP_DETAILS_TEMP exceeds 1 million rows, then it would be desirable for the DBA to truncate the table (using <zero> for the program parameter) during either;
A) An application downtime event
or
B) When no users are entering sales orders on the system. This will prevent excessive use of rollback which can happen using the standard Purge concurrent program with many rows in the table. This
which cannot be accomplished using delete statements of the concurrent program.
-- Even if a user was scheduling an order at the time of the truncate and received an error, then they could try scheduling again and will be successful.

FAQ:

Q #1: How can I check the tables to see if we need to truncate them?
A #1: Run the following SQL to check sizes tables and indexes used for this process.

select DS.OWNER, OBJECT_NAME, OBJECT_TYPE, BYTES/1024/1024 SIZE_IN_MB


from DBA_SEGMENTS DS, DBA_objects DT
where DS.OWNER=DS.OWNER
and DS.SEGMENT_NAME=DT.OBJECT_NAME
and dt.object_name like 'MRP%ATP%TEMP%';
-- When Decentralized installation, Then
-- MRP objects are populated on EBS Source
-- MSC objects are populated on APS Destination

Q #2: Why are the tables very large when we have been running Purge ATP Temp Tables regularly
A #2: They may not have been truncated before you started running the program. When we delete from tables, then the RDBMS will not recover the space used and table size can continue to grow, even
rows in the table.

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=HOWTO&id=329398.1 1/2
5/9/12 https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=HOWTO&id=329398.1
Suggest that if this is encountered, then run Purge ATP Temp Tables with parameter = 0 when users are not entering orders and this will recover the space.
In very high volume operations, we have seen customers report that tables sizes grow to several GB in a single day. In this case, we recommend that you truncate the tables using Purge ATP Temp Tab
0, then schedule the request to run every hour with parameter = 1.

References

Related

Products

More Applications > Value Chain Planning > Supply Chain Planning > Oracle Advanced Supply Chain Planning

Keywords

ATP; MRP_ATP_DETAILS_TEMP; MRP_ATP_SCHEDULE_TEMP; MSCATPPURG; PURGE; TABLE GROWS

Back to top

Copyright (c) 2007, 2010, Oracle. All rights reserved. Legal Notices and Terms of Use | Privacy Statement

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=HOWTO&id=329398.1 2/2

You might also like