Concurrent Programs

This appendix covers the following topics:

Overview

The Collections process uses a number of concurrent programs (requests) to refresh snapshots, pull planning data into staging tables on the planning server, and load data into the ODS. The parameters set will determine the requests that will be called during the collection process, and their order. You can view the process of the concurrent requests from the System Administration responsibility by choosing Requests > Monitor. Requests can also be scheduled from Requests > Schedule.

If your data needs considerable modification and transformation, you can run requests individually instead of running the full Collections process so that you can adjust the data at various stages. Requests can be run individually from the System Administrator responsibility by choosing Requests > Run.

Collection Requests

The following requests are involved in the collection process. For more information about collection requests, please see the listing of Advanced Supply Chain Planning Concurrent Programs at http://oracleappscommunity.com/oracle/blog/1121/advanced-supply-chain-planning-concurrent-programs.

Request Description
Collections Synonyms This concurrent process drops and creates synonyms during the collections run.
Collections Triggers This concurrent process drops and creates triggers during the collections run.
Collections Views This concurrent process drops and creates views during the collections run.
Create AHL Snapshots This concurrent process drops and recreates AHL snapshots during the collection process. Typically, it runs as part of concurrent process Refresh Collection Snapshots when profile option MSC: Source set up required is Yes.
Create BOM Snapshots This concurrent process drops and recreates BOM snapshots during the collection process. Typically, it runs as part of concurrent process Refresh Collection Snapshots when profile option MSC: Source set up required is Yes.
Create Collections BOM Snapshot Triggers This concurrent process drops and creates BOM snapshot triggers during the collections run.
Create Collections BOM Views This concurrent process dops and creates BOM views during the collections run.
Create Collections Demand Snapshot Triggers This concurrent process drops and creates demand snapshot triggers during the collections run.
Create Collections Demand Views This concurrent process dops and creates demand views during the collections run.
Create Collections Item Snapshot Triggers This concurrent process drops and creates item snapshot triggers during the collections run.
Create Collections Item Views This concurrent process dops and creates item views during the collections run.
Create Collections Other Snapshot Triggers This concurrent process drops and creates other snapshot triggers during the collections run.
Create Collections Other Views This concurrent process dops and creates other views during the collections run.
Create Collections Repair Order Snapshot Triggers This concurrent process drops and creates repair order snapshot triggers during the collections run.
Create Collections Repair Order Views This concurrent process dops and creates repair order views during the collections run.
Create Collections Routing Snapshot Triggers This concurrent process drops and creates routing snapshot triggers during the collections run.
Create Collections Routing Views This concurrent process dops and creates routing views during the collections run.
Create Collections Setup Views This concurrent process dops and creates setup views during the collections run.
Create Collections Supply Snapshot Triggers This concurrent process drops and creates supply snapshot triggers during the collections run.
Create Collections Supply Views This concurrent process dops and creates supply views during the collections run.
Create Collections WIP Snapshot Triggers This concurrent process drops and creates WIP snapshot triggers during the collections run.
Create Collections WIP Views This concurrent process dops and creates WIP views during the collections run.
Create CSP Snapshots This concurrent process drops and recreates CSP snapshots during the collection process. Typically, it runs as part of concurrent process Refresh Collection Snapshots when profile option MSC: Source set up required is Yes.
Create EAM Snapshots This concurrent process drops and recreates EAM snapshots during the collection process. Typically, it runs as part of concurrent process Refresh Collection Snapshots when profile option MSC: Source set up required is Yes.
Create INV Snapshots This concurrent process creates new segment definitions in existing descriptive flexfields to hold data that may be required for inventory planning. It also populates profile values with the value corresponding to the descriptive flexfield attribute number for each attribute created.
Parameters:

  • Service Level (Item): The service level value that you want to maintain for the items.

  • Service Level (Org): The service level value that you want to maintain for the organizations.

  • Service Level (Customers): The service level value that you want to maintain for the customers.
Create MRP Snapshots This concurrent process drops and recreates MRP snapshots during the collection process. Typically, it runs as part of concurrent process Refresh Collection Snapshots when profile option MSC: Source set up required is Yes.
Create OE Snapshots This concurrent process drops and recreates OE snapshots during the collection process. Typically, it runs as part of concurrent process Refresh Collection Snapshots when profile option MSC: Source set up required is Yes.
Create PO Snapshots This concurrent process drops and recreates PO snapshots during the collection process. Typically, it runs as part of concurrent process Refresh Collection Snapshots when profile option MSC: Source set up required is Yes.
Create WIP Snapshots This concurrent process drops and recreates WIP snapshots during the collection process. Typically, it runs as part of concurrent process Refresh Collection Snapshots when profile option MSC: Source set up required is Yes.
Create WSH Snapshots This concurrent process drops and recreates WSH snapshots during the collection process. Typically, it runs as part of concurrent process Refresh Collection Snaphots when profile option MSC: Source set up required is Yes.
Create WSM Snapshots This concurrent process drops and recreates WSM snapshots during the collection process. Typically, it runs as part of concurrent process Refresh Collection Snaphots when profile option MSC: Source set up required is Yes.
Drop Changed Snapshots This concurrent process drops the source snapshot definitions. Use it when there is an error or corruption in a particular snapshot or materialized view. The next collection recreates the snapshots. Parameter: Snapshot Name: The name of the snapshot to drop.
Planning Data Collection - Purge Staging Tables This concurrent process deletes the data from the staging tables. Use it either before regenerating and launching a new data pull or after the collections data pull fails.
Parameters:

  • Instance: the instance-organization against which you want to run the concurrent process.

  • Validation: Specify whether the concurrent process needs to verify if a planning data collection is running.
Planning Data Pull This concurrent process pulls Oracle Applications data from the source (transaction) instance to the destination (planning) instance interface tables. See Planning Data Pull Parameters for more information,
Planning ODS Load This concurrent process moves data from the destination (planning) instance interface tables to the destination (planning) instance planning tables. See Planning ODS Load Parameters for more information.
Refresh Collected Data in APCC Repository This concurrent program refreshes the APCC repository. Parameters include instance (required) and Complete (Yes/No). The data range of the collected data available to APCC depends on the following profile options: MSC: Horizon for APCC Collected data - Forward days and MSC: Horizon for APCC Collected data - Backward days.
Refresh Collect Snapshots This concurrent request refreshes the snapshot in the source. After the refresh, the snapshot reflects the most current master data. If profile option MSC: Source set up required is Yes, this process runs the following concurrent processes:

  • Create AHL Snapshots

  • Create BOM Snapshots

  • Create INV Snapshots

  • Create MRP Snapshots

  • Create OE Snapshots

  • Create PO Snapshots

  • Create WIP Snapshots

  • Create WSH Snapshots

  • Create WSM Snapshots

Setup Requests

The Request ID and Request Name are listed in the Refresh Collection Snapshots log file when these requests are launched as part of Data Collections.

Shortname Request Name
MSCDROPS Drop Changed Snapshots
MSCWSMSN Create WSM Snapshots
MSCBOMSN Create BOM Snapshots
MSCINVSN Create INV Snapshots
MSCCSPSN Create CSP Snapshots
MSCMRPSN Create MRP Snapshots
MSCPOXSN Create PO Snapshots
MSCONTSN Create OE Snapshots
MSCWSHSN Create WSH Snapshots
MSCAHLSN Create AHL Snapshots
MSCEAMSN Create EAM Snapshots
MSCWIPSN Create WIP Snapshots
MSCSYNMS Collections Synonyms
MSCVIEWS Collections Views
MSCTRIGS Collections Triggers
MSCTRITM Create Collections Item Snapshot Triggers
MSCTRBOM Create Collections BOM Snapshot Triggers
MSCTRRTG Create Collections Routing Snapshot Triggers
MSCTRWIP Create Collections WIP Snapshot Triggers
MSCTRDEM Create Collections Demand Snapshot Triggers
MSCTRSUP Create Collections Supply Snapshot Triggers
MSCTROTH Create Collections Other Snapshot Triggers
MSCTRRPO Create Collections Repair Order Snapshot Triggers
MSCVWSTP Create Collections Setup Views
MSCVWITM Create Collections Item Views
MSCVWBOM Create Collections BOM Views
MSCVWRTG Create Collections Routing Views
MSCVWWIP Create Collections WIP Views
MSCVWDEM Create Collections Demand Views
MSCVWSUP Create Collections Supply Views
MSCVWOTH Create Collections Other Views
MSCVWRPO Create Collections Repair Order Views

Running Refresh Collection Snapshots as a Standalone Concurrent Request

Running a complete collection will launch the refresh collection snapshots concurrent request automatically, there are occasions where you might want to run the request on its own. For example, you can run the refresh collection snapshots concurrent request prior to running a complete collection. This reduces the time involved with running a complete data collection because all the snapshots are already up-to-date.

The Refresh Collection Snapshots request is available under a number of responsibilities:

In addition, using the System Administrator responsibility, it can be added to the Request Group OM Concurrent Programs so that it is visible in the Order Management responsibility where customers may run ATP data collections.

For distributed installation with separate instances for transactions (EBS source) and planning (VCP destination), the Refresh Collection Snapshots is always run on the EBS source instance.

To run the Refresh Collection Snapshots request:

  1. Using the Advanced Supply Chain Planner responsibility, navigate to Setup, then Run Requests.

  2. Select the relevant organization and click OK.

  3. In the Submit a New Request form, choose Single Request and click OK.

  4. In the Submit Request form, Name field, enter Refresh Collection Snapshots.

  5. In the Parameters form, fill in the following parameters:

    Parameter Description
    Refresh Mode Valid values:

    • Fast Refresh: only processes changes since the last run of the Refresh Snapshots or data collections.

    • Complete Refresh: processes all the snapshots and completely refreshes the snapshots.

    • Automatic Refresh: explicitly truncates the snapshot log when you set the parameter Threshold = 0 and perform a complete refresh of the snapshots. The automatic refresh does not check the profile MSC: Source Setup Required, so if you are running for the first time after a patch or in a newly cloned instance, then use Complete Refresh.

    Note: When running Data Collections request set, Refresh Snapshots always uses a Fast Refresh for performance reasons. This is usually not a problem, unless the snapshot logs have grown very large. Then corrective steps are required. See Managing the MLOG Growth for VCP Data Collections for more information.
    Snapshot Name Use default "All Snapshots" or choose a snapshot from the list.

    Important: When running as a standalone request, Oracle recommends that you run this for each snapshot as required. When launched for All Snapshots, then this can require a lot of UNDO (or Rolback) space since all snapshots and transactions are performed in one atomic transaction.

    For list of snapshots for your release see Appendix D -- Snapshots.
    Threshold for Truncating Logs Used only in Automatic Refresh mode.
    Use Threshold = 0. This truncates the MLOG$ Snapshot log table, which can help resolve performance issues.
    Oracle has no reason to recommend any other setting than zero at this time.
    For example, a value of 50 truncates the log if 50 or more lines are in the MLOG$ snapshot log table and then performs a complete refresh of the snapshot.
    Degree Refers to the degree of parallelism to be used by the database to process the request. Maximum value is 10. The higher the degree of parallelism, the faster the process will complete.
    Currently Oracle recommends the default value of 0.
    Ensure that you have followed all the steps for setting up the latest RDBMS patches. If the RDBMS patches are applied, then setting this value higher should not cause a problem.

    Note: Entering a number higher than 10 will result in the use of 10 for this value. Oracle's Support has seen RDBMS issues when this is higher than 1.

Note: See Running Collections for the First Time in a New Instance for more information about how the MSC: Source Setup Required = Yes parameter affects the Refresh Collect Snapshots concurrent program.

Performance or Errors with the Refresh Collection Snapshots Program

The following performance issues or errors may be experienced with the Refresh Collection Snapshots program run either as standalone or part of the Data Collection request set.