Wednesday, January 8, 2014

Oracle ASCP Standard Collection

Oracle Advanced Supply Chain Planning Standard Data Collection Program

Using Oracle ASCP standard collection process, you can pull data from your source/legacy system into ASCP interface tables.Oracle ASCP uses a data store based on the planning data model that is exposed through interface tables. The data is pulled from the designated data sources into its data store; Oracle ASCP Collections are responsible for synchronization as changes are made to the data sources.

Navigation:
Login to Oracle Applications

Responsibility: Advanced Planning Administrator

Collections > Oracle Systems > Stanard Collection


 Planning Data Pull parameters:












Planning ODS Load Paramerers:






The data collection process consists of the Data Pull and the Operational Data Store (ODS) Load. The collection process lets you collect across Oracle Application Versions 11.0 or higher. It supports several configurations.



Using the standard collections process, you can manually run three types of collection methods including a complete refresh, a net change refresh, or a targeted refresh on specific business entities. Standard data collection consists of the following processes:
  • Pull program: Collects the data from the ADS and stores the data into the staging tables. This pull program is a registered AOL concurrent program that could be scheduled and launched by a system administrator. If you are using a legacy program, you must write your own pull program.
          The pull program performs the following major processes.
§  Refresh snapshots.
§  Launch the pull Workers to perform pulls from the appropriate source tables and insert the data in the Staging tables.

 
  • ODS Load: A PL/SQL program which performs the data transform and moves the data from the staging tables to the ODS. This collection program is a registered AOL concurrent program that could be scheduled and launched by the system administrator.
Collection methods:
• The Complete Refresh method clears all transaction data for all business entities from the planning server (for the source instance being collected), then copies over information about the user-selected entities. This method can be time consuming.
• The Net Change Refresh method copies only incremental changes to business entities to the planning server (and is thus faster), but is supported mainly for demand and supply business entities only.
• The Targeted Refresh method clears transaction data for only the user-selected business entities from the planning server, and then copies the entity information over from the transaction instance. Information about nonselected entities remains intact on the planning server. All planning business entities are supported by Targeted Refresh collections.


Define Instances


Navigation path for defining the instances.
Advanced Planning Administration àAdminàInstances

The Database Administrator uses this form to setup instance names and to specify the release version of the source database, Application Database link and Planning Database link associated with the instance names.


Below image For reference only-

2 comments:

  1. Thanks a lot Sagar. This has helped me a lot. !

    ReplyDelete
  2. Regards
    Sridevi Koduru (Senior Oracle Apps Trainer Oracleappstechnical.com)
    LinkedIn profile - https://in.linkedin.com/in/sridevi-koduru-9b876a8b
    Please Contact for One to One Online Training on Oracle Apps Technical, Financials, SCM, SQL, PL/SQL, D2K at training@oracleappstechnical.com | +91 - 9581017828.

    ReplyDelete