Professional Documents
Culture Documents
However, Running of Data Collection For ASCP Is Accomplished From The ASCP
However, Running of Data Collection For ASCP Is Accomplished From The ASCP
Presented by
Core Manufacturing Product Support Team
The purpose of this document is to serve as a quick setup guide for Data
Collections.
It is targeted for systems where Data Collections is being run to allow for
ATP based on Collected Data
OR
For systems where ATP is not being used, but Data Collections needs to be
run in order for Scheduling in Order Management to complete successfully.
The same setups apply for systems where ATP will be based on Planning Data and the
APS Suite is being used for Advanced Supply Chain Planning (ASCP).
However, running of Data Collection for ASCP is accomplished from the ASCP
Responsibility, NOT from the OM Responsibility. Additional setups are required before
ASCP is fully implemented.
The screen shots in this document reflect data collection parameters as they should look
after the application of the latest data collections patch. See Note 223026.1 List of High
Priority Patches for more information.
For more information please go to Metalink and review the Advanced Planning and
Scheduling Self Service Toolkit (APS SST)
Navigate to the Top Tech docs, then to Advanced Planning and Scheduling.
There are many important articles and links on this page - particularly under Planning
Data Pull and Snapshots on the Source Instance topics.
User Activities
1. Setup the Instance
2. Select the Organizations
3. Run ATP Data Collection
Data Collections
The process of collecting data from the ERP Source transactional instance (or
schemas) and gathering data in a recognizable form in the APS Destination
instance/schema.
The Source ERP information is stored in the product schemas ( INV, OM, BOM,
WIP, MRP, PO, etc.) and collected to the MSC Schema for ATP and ASCP.
For Demand Planning, information is also collected to the MSD schema where
the Demand Planning specific information is stored. This data collections process
is run from the Demand Planning responsibility and requires additional setup.
Centralized Configuration
A Centralized Configuration means only one instance is involved. This is usually
used for ATP based on Collected data. This means that the ERP Source data and
the APS Destination data are stored in one instance.
Decentralized Configuration
A Decentralized Configuration means there are two instances involved. These
two instances (ERP Source and APS Destination) speak to each other via database
links. This will mean that the ERP Source and APS Destination instances are
located on separate boxes. This configuration is generally used when all or part of
the APS suite is being used.
The steps below are optional and can be accomplished at a later date. However,
they can be critical to the overall implementation and should be reviewed and
considered when applicable.
It is highly recommended that patch 2405219 from Section V be applied to
fix an issue with Gather Schema Statistics for partitioned tables. This is a
small 2-file fix with critical benefits for performance in the MSC schema.
If GOP is being used then the latest ATP rollup patch listed under Section
II should also be applied.
If the ASCP is going to be used, then the latest ASCP Rollup patch that is
listed in Section I should also be applied to the system.
Demand Planning has a listing of patches under Section VII that may be
required if this application is being installed for the system.
Note:
In order to perform Basic ATP it is not necessary to have APS installed. When
Order Management is installed, but APS is not installed, then APS is installed by
default as a ‘Shared’ application under the Product Code MSC in order to enable
ATP based on Collected Data.
SQL> select p.application_id,
p.status,
a.application_short_name
from fnd_product_installations p,
fnd_application a
where a.application_id=p.application_id
and a.application_short_name in ('msc')
This should return Status = S when the APS Suite is not licensed.
Other values are:
I – Installed
N – Not installed
The SQL that will reveal how these partitioned tables are setup is:
SQL> select table_name,
partition_name,
num_rows,
sample_size,
last_analyzed,
global_stats,
user_stats
from all_tab_partitions
where table_name like 'msc%'
order by substr(partition_name,instr(partition_name,'_',-1,1)+1);
Also see the following for assistance in maintaining the APS instance:
Note 137293.1 - How Can I Manage MSC Partitions
This note lists the partitioned tables in the MSC schema
Note 174500.1 - ODS-Destination Maintenance and Cleanup when the Source
Instance Changes
FOR ALL INSTALLATIONS – ATP based on Collected Data or Full ASCP Planning.
Dropping the unneeded plan partitions.
There are database issues that can affect performance when partitions are
empty. Therefore, any unused partition (except _0) should be removed
from the system.
If the business plans to set MSC: Shared Plan Partition = Yes, then please
consult the Users Guide for more information about this setup. Also see
Note 137293.1 - How Can I Manage MSC Partitions
The only reason to use ‘inst_partition count’ = 1 would be if the ODS data
is to be collected from a new ERP Source instance.
If using ASCP Planning, then the ASCP User and Implementation Guide
should be used to make sure all necessary setups are completed for a full
implementation.
3. The Planning Manager must be started and complete at least one successful cycle on
the ERP Source Instance in order for Data Collections to complete successfully.
3.1 Navigate to Material Planning>Setup>Planning Manager
3.2 Choose an organization –This only needs to be done once for the instance – not
for each organization.
3.3 The default of 30 seconds is OK.
3.4 Click on the start button.
3.5 If this is the first time the Planning Manager has been started on this instance, and
there is a lot of data on the system, then the first run may take an extended period
of time.
3.6 For issues with the Planning Manager – see the Master Scheduling/MRP SST on
Metalink for more information and troubleshooting.