Professional Documents
Culture Documents
How To Setup and Run Data Collections PDF
How To Setup and Run Data Collections PDF
Contents
PDF for Printing This Document .................................................................................................................... 2
Purpose.......................................................................................................................................................... 2
Understanding Centralized vs. Distributed Installation ................................................................................ 3
Understanding the Data Collections Process ................................................................................................ 4
3 Key Stages to the Data Collections Process............................................................................................ 4
Refresh Snapshots Process .................................................................................................................... 4
Planning Data Pull ................................................................................................................................. 4
ODS Load ............................................................................................................................................... 5
Complete, Net Change and Targeted Refresh........................................................................................... 5
Setup Requests for Data Collections ......................................................................................................... 6
Purge Staging Tables - A Special Note ....................................................................................................... 6
ATP Data Collections vs. Standard Data Collections ................................................................................. 6
Fresh Installation or Upgrade - Basic Steps ................................................................................................... 7
For 12.1 ..................................................................................................................................................... 7
For 12.0.6 .................................................................................................................................................. 8
For 11.5.10.2 ............................................................................................................................................. 8
Upgrading EBS Applications - Special Considerations ................................................................................... 9
DBA Checklist................................................................................................................................................. 9
VCP Applications Patch Requirements ...................................................................................................... 9
RDBMS Patches and Setups for Known Issues .......................................................................................... 9
Other RDBMS Setups / Maintenance ......................................................................................................10
RAC Database - Special Requirements ....................................................................................................11
System Administrator Setups ..................................................................................................................11
Applications Super User Checklist ...............................................................................................................12
VCP Applications Patch Requirements ....................................................................................................12
Fresh Install/Upgrade Setup Steps ..........................................................................................................12
Running Data Collections for the First Time in a New Instance ..............................................................13
Parameters for First Run of Data Collections ......................................................................................13
Purpose
This document will offer recommendations for customers using Value Chain Planning - VCP (aka
Advanced Planning and Scheduling - APS) who are performing:
We will explain the difference between Centralized vs. Distributed and other Terminology used
in this document
We will help you insure the patching and setups are correct so you can launch and complete
Data Collections successfully.
We will address this functionality for 11.5.10 and above, with a concentration on R12.1.
Patching for a Centralized Installation - All patches are applied to the single
instance. You can ignore references in the patch readme for centralized and distributed
installation and apply all patches to your single instance. Most patches will mention to
just apply the patch to your instance when Centralized.
Distributed Installation - Two (or more) databases located on different machines. One is the
EBS Source Instance where all OLTP transactions and setups are performed. The APS Destination
is where Data Collections process is launched and uses database links to communicate and
move the data to the MSC tables in the APS Destination.
1. The processing performed for Planning in ASCP, IO, DRP, etc. can take huge amounts of
memory and disk IO. This can slow down the OLTP processing while the plan processes
are running. It is not unusual for large plans to consume anywhere from 5-20+ GB of
memory while running and move millions of rows into and out of tables to complete the
planning process.
2. It is possible to have APS Destination on different release. APS Destination could be 12.1
with EBS Source running 11.5.10 or 12.0.6
a. Note that you may NOT have an APS Destination with lower version that EBS
Source (example - APS Destination on 12.0 or 11.5 with EBS Source on 12.1)
3. It is possible to have more than one EBS Source connected to the APS Destination. This
requires careful consideration as patching for all instances must be maintained.
Example: 2 EBS Source instances connected to 1 APS destination instance and all are on
the same EBS applications release. For VCP patches that effect Collections, all three
instances must be patched at the same time in order to prevent breaking this
integration. Or customer may have 2 EBS Source on different releases. APS destination
on 12.1 with an EBS Source on 12.1 and another on 11.5.10.
Patching for a Distributed Installation - This requires careful attention to the patch
readme to make sure the patches are applied to the correct instance and that pre-
requisite and post-requisite patches are applied to the correct instance. Patch readme
should be clear on where the patch is to be applied. Usually the patch will refer to the
EBS (or ERP) Source (or 'source instance') and to the APS Destination (or 'destination
instance') for where the patch is to be applied.
12.0.x and 11.5.10 – For these releases we have separate patches for different
parts of the VCP applications.
• ASCP Engine/UI patches are applied only to the APS Destination. There
is also a Source Side UI patch to be applied to the EBS Source only - see
the readme.
• Data Collections patches are applied to BOTH the EBS and APS
instances. The readme may list specific patches to be applied to the EBS
Source for certain functionality.
• GOP (or ATP) and Collaborative Planning are applied to BOTH the EBS
and APS instances.
• For Demantra, the main patch is applied to the APS Destination
instance. And there is usually a Source side patch listed in the readme.
1. This process is launched by the stage Planning Data Pull to refresh the snapshots
used to collect the data.
2. The snapshots work in conjunction with the views to provide the Planning Data Pull
with the information that will be loaded into the staging tables.
3. If the setup profile MSC: Source Setup Required = Yes (or Y in 11.5.10 and below),
then this process will also launch the Setup Requests that create all the objects used
by Data Collections in the EBS Source applications.
4. When deployed with Distributed installation, these processes are launched on the
EBS Source instance. In a Centralized - single instance installation all requests are
launched in the same instance.
1. When the Snapshot process is finished, then the Planning Data Pull will move the
data from the Snapshots and Views to the Staging Tables - all named MSC_ST%
2. This will spawn workers to help manage the many tasks (40+) that gather the data
into the staging tables.
1. This will launch to perform Key Transformations of critical data into unique keys for
the VCP applications. For instance, since we can collect from multiple instances, the
INVENTORY_ITEM_ID in MSC_SYSTEM_ITEMS must be given a unique value. This
happens for several entities. We store the Source instance key values in columns
with SR_ like SR_INVENTORY_ITEM_ID in MSC_SYSTEM_ITEMS
2. Then ODS also launches workers to handle the many different load tasks that move
data from the MSC_ST staging tables to the base MSC tables.
3. During complete refresh we create TEMP tables to copy data from MSC_ST staging
tables into the TEMP tables, then use Exchange Partition technology to flip this
temp table into the partitioned table.
a. For instance, if your instance code is TST, you can see in the log file where
we create temp table SYSTEM_ITEMS_TST,
b. Then we move data into this table from MSC_ST_SYSTEM_ITEMS
c. Then we exchange this table with the partition of MSC_SYSTEM_ITEMS used
for collected data - example here shows table name if the instance_id is
2021 - partition name is SYSTEM_ITEMS__2021)
4. Lastly, the ODS Load will launch Planning Data Collections - Purge Staging Tables to
remove data from the MSC_ST staging tables and if Collaborative planning is setup,
then we launch the Collaboration ODS Load.
For 12.1
Customers must install the latest release of EBS Applications and during the implementation
cycle, if a new release of EBS becomes available, plan to install that release (example: Installed
EBS 12.1.2, and three months later EBS 12.1.3 becomes available, then it is very important to
plan a move to this latest release.)
For the applications install, review Note 806593.1 Oracle E-Business Suite Release 12.1 - Info
Center.
1. Note 746824.1 12.1 - Latest Patches and Installation Requirements for Value Chain
Planning. Use this note to reference:
For 12.0.6
Customers should NOT be planning to use this release, but should move to 12.1.
Note 401740.1 - R12 Info Center is available for customers who must perform this installation
1. Note 421097.1 R12 - Latest Patches and Critical Information for VCP - Value Chain
Planning (aka APS - Advanced Planning and Scheduling)
a. You must apply the latest CU Patches available after the installation and before
releasing the instance to users.
b. If you are using only ATP Data Collections, then apply the GOP Patch and Data
Collections patches.
2. Note 412702.1 Getting Started with R12 - Advanced Planning and Scheduling Suite FAQ
3. Note 414332.1 Getting Started With R12 - Advanced Planning Support Enhanced RCD
4. Note 552415.1 INSTALL ALERT - Setting Up The APS Partitions and Data Collections
Instance in R12
For 11.5.10.2
In the rare case that an upgrade to 11.5.10.2 is being considered, AND it is not an intermediate
step on the way to R12.1, then it is very critical that the latest patches be applied.
Review Note 223026.1 and apply the latest Rollup patches for at minimum:
1. Using ASCP - then apply ASCP Engine/UI and Data Collections rollup
Also review Note 883202.1 - Minimum Baseline Patch Requirements for Extended Support on
Oracle E-Business Suite 11.5.10
DBA Checklist
Note: After Patching, there may be invalids or missing objects used for Data Collections.
The patch should set profile MSC: Source Setup Required = Yes (or Y in 11.5.10)
Then with the first run of Data Collections, the Setup Requests will be launched and build all
the required objects for Data Collections, so this will resolve any invalid or missing objects
used for Data Collections. As noted above, you can find more information on the Data
Collection objects and the Setup Requests, etc in Note 179522.1
All three of these RDBMS bugs relate to some data not being collected and the issue has been
seen in different entities under different conditions in different database versions. So we
recommend all these patches,
If you have this issue NOW, see step #3.c and execute this as a workaround immediately. It has
resolved most issues, but there will be exposure to other RDBMS bugs below
1. RDBMS bug 6720194 fix should be applied - Wrong results from SQL with semijoin and
complex view merging
It is not unusual for the first run to require that you use Timeout parameter of 600-1600
minutes to get all data collected from the EBS Source tables to the APS Destination MSC
tables. It does not matter if you are using database links and two instances or a single
instance. Be sure to set this high parameter for both the Planning Data Pull and ODS
Load.
Do not use a Collection Group during the first run, collect using parameter = All
If you are not collecting from all Orgs defined in the EBS source, then only define the
required orgs in the Instances form. Be sure to include the Master Org in the Instances
form.
Once Data Collections has completed successfully for the first time, run Gather Schema
Stats for the MSC schema, then the timing should settle down and be reasonable. The
default timeout of 180 for Planning Data Pull and 60 minutes for the ODS Load can be
maintained.
However, if you want to change the Instance Code in the Instances form, then you must
follow steps in Note 137293.1 - Section X to clean up all the old data BEFORE you create
Key Points
1. You will have to MANUALLY manipulate the EBS Source instance table
MRP_AP_APPS_INSTANCES_ALL.
2. You cannot have TWO instances which have the same INSTANCE_ID or
INSTANCE_CODE in EBS Source table MRP_AP_APPS_INSTANCES_ALL
3. You cannot have TWO instances which have the same INSTANCE_ID or
INSTANCE_CODE in APS Destination table MSC_APPS_INSTANCES
Make sure the INSTALL ALERT Note 552415.1 is resolved for R12 and R12.1 installations.
DBA’s Information
All steps in DBA Checklist apply, EXCEPT that no database links are required and Note 137293.1
will not be so important unless you move to Distributed installation.
Patching is simpler, since all patches are applied to the same instance.
Appendix A
Note 179522.1 should be the primary resource for information about the requests and other
information on data collections objects, parameters, profiles, etc.
References
Note 179522.1 - Data Collection Use and Parameters
Note 137293.1 - How to Manage Partitions in the MSC Schema