ASCP Data Collection: A high level overview

Process of collecting data in proper format from ERP(transactional) instance/schemas to APS(Planning) instance/schema, for easy usage by APS modules like ASCP, GOP, IO, Demantra and others. ERP stores all master data & transactional data, in respective product schemas like INV, BOM, WIP, MRP, PO etc., which is collected to MSC schema for planning applications.

Components of Collection process:
1. Refresh Snapshots: runs always only on the ERP source instance in Distributed environment
2. Planning Data Pull: Pulls data from ERP source schemas to MSC_ST% tables
3. ODS Load: Does data cleansing & manipulation, followed by loading base MSC% tables from MSC_ST%(Staging) tables

For integrated Demantra, further collection of history & related data is required to populate Demantra base tables. The processes for these collections are run from the responsibility "Demand Management System Administrator". The Standard collection option in Demantra responsibility is same as ASCP standard collection. The other collections processes are Demantra specific.

Modes of Collection:

1. Standard: Using this option, one can manually launch collection in three methods, Complete Refresh, Targeted Refresh & NetChange.
2. Continuous: this is an automated collection process, which requires minimal manual intervention and it keeps planning instance data synchronized with ERP source instances. It automatically determines which method of collection should be used.

Few notes to remember:
1. Source ERP instances can be a mixture of releases and can be a legacy instance as well
2. ASCP instance can share instance with one of the ERP instances
3. Collection is required even if APS & ERP instances reside on same instance
4. Supplies against Drop Ship are not collected, as ASCP doesn't plan for drop ship sales