Sie sind auf Seite 1von 5

Data Collections Use and Parameters

I. How often should Data Collections for ATP and APS be run?
A. For ATP from OM where APS is not used Setting for INV: Capable to Promise = ATP based on Collected Data Data Collections needs to run anytime core data --such as Sales orders, PO's, WIP jobs etc. that is used for calculating ATP is changed. The frequency of running this program is certainly a business decision, but for most up to date information, it can be expected to run as frequently as twice an hour, if not more. Oracle has made the Data Collections process very efficient for these frequent updates by offering the Net Change parameter. In general, ATP is calculated by looking at Supply and Demand. The supply is based on scheduled receipts, such as WIP jobs and Purchase Orders. If Global ATP(GATP) is being used, then supply can also be planned orders. Each time supply is changed, i.e. new WIP jobs or purchase orders created, then Data Collections would need to be run to reflect this new supply. Demand includes Sales Orders and WIP Jobs. Sales Orders reflect the availability immediately when scheduled to help ensure the accuracy of ATP, but to capture the WIP demand, collections would need to be run. Consider the following example A newly created PO is not reflected in ATP as supply. Data Collections needs to be ran each time Supply is added. PO's can be changed regularly; therefore it is harder to update proper tables on the fly. The Sales Order demand is reflecting demanded inventory, which directly affects the ATP results. BUT a canceled Sales Order does not reflect in ATP, therefore this information needs to be collected. B. For ATP and CTP based on an APS Plan Setting for INV: Capable to Promise = ATP/CTP based on Planning Data Collecting additional information about from the source and running a comprehensive Plan in APS enables Multi-Level, Multi-Org ATP and CTP to be performed in OM and in ASCP (Advance Supply Chain Planner) responsibilities. This planning data enables the user to run collections less often IF the data produced by the plan is used to implement your production and supply planning. When the data from the plan is used exclusively, then ATP has a complete view of the current plan across Organizations and at multiple levels

When changes to the Supply or Demand for the plan are made in the ERP source transactional instance, then it is necessary to update the changes by running Data Collections and also re-running the plan. This could include cancelling Sales Orders, changes to POs or WIP jobs that were not recommended by the plan, or additional ERP data such as Items, BOMs etc., being created.

II. Explanation of Data Collection Parameters:


When performing a Data Collection, the request set is executing two concurrent requests that require Parameters: The Planning Data Pull Planning ODS Load These will kick off additional requests in order to complete the process. Additionally, all setups for Data Collections are now controlled by concurrent requests. For more information about these requests - please review Note 207644.1 - Data Collections is Failing - All Errors - First Diagnostic Steps In brief, The Planning Data pull gathers information from the ERP tables and transfers it to the Staging tables (shown as MSC_ST_% in the MSC schema) Then the ODS Data Load takes validates as massages the information and transfers it to the core MSC tables under the PLAN_ID 1 (minus one). A. For ATP from OM where APS is not used In the latest Data Collections patch, the user interface for Order Management>Scheduling>ATP Data Collection has been modified. There is now a wrapper for the Data Collections Concurrent request set that offers fewer parameters than in the past. This was implemented since the tables that must be used to collect information for ATP based on Collected Data do not change and no decision on what information to collect needs to be made by the user. Planning Data Pull and Planning ODS Load Parameters: *Instance = Specifies the instance being collected *Number of Workers = Specify the number Planning Data Pull Workers *Time Out (minutes) = Determines how long the process will wait for child processes to complete before erroring. Collection Type - Choose between Net Change Refresh or Complete Refresh Sales Orders - Choose between Net Change Refresh or Complete Refresh Only Net Change Refresh is available if Collection Type Net Change Refresh is chosen.

* - Indicates default is acceptable B. Running Collections for APS Planning The user interface under ASCP>Collections> (choose) Oracle Systems/Legacy Systems>Data Collection allows more choices for collections based on the system and implementation of APS being used in the business. This document serves to review the Parameters only, not an in depth discussion of how to apply them to any particular business.

* - Indicates default is acceptable ** - Indicates recommended collecting on regular schedule for accurate ATP Planning Data Pull and Planning ODS Load Parameters: *Instance = Specifies the instance being collected *Number of Workers = Specify the number Planning Data Pull Workers *Time Out (minutes) = Determines how long the process will wait for child processes to complete before erroring. Purge ODS Data This determines if the MSC tables where the data is stored should be purged/truncated prior to collections. The MSC_ST% tables are purged/trucated as indicated below. Certain core MSC tables are never purged per the system design. If Yes, then Purge ODS Tables and repopulate with newly collected data. If No, then do not purge ODS and add newly collected data. The purge/truncate functionality is controlled by the profile option MSC: Purge Staging Tbl Crtl see the Users Guide for more information on this important profile option. Collection Method Dependent on Purge ODS setting Complete Refresh (Purge ODS Data = Yes) Targeted Refresh (Purge ODS Data = No) Netchange Refresh (Purge ODS Data = No) Complete Refresh = All MSC_ST tables and most MSC tables are purged/truncated and repopulated with new collected data. All Parameters should = YES Targeted Refresh = If specific Parameter = Yes, Then MSC Table is purged/truncated and repopulated with the new collected data

Netchange Refresh = If specific parameter = Yes, then newly collected data is added to the MSC table. Collects only the incremental changes in the transactional data since the most recent refresh. Old data is not removed. For example, if a part is obsoleted, to remove from ATP and APS, Targeted or Complete Refresh must be run. Analyze Staging Tables - the Planning Data Pull will put information into the Staging tables MSC_ST%, then the Planning ODS Load delivers the data to the core MSC tables. By analyzing the Staging tables, the processing time for Planning ODS Load may be reduced. This is useful when running Complete Refresh. Approved Supplier List (Supplier Capacities) - Collects information from ASL for use in ASCP. ATP Rules - Collects the ATP Rules defined in Inventory. Used to determine availability information when scheduling Sales Order Note 208140.1 - Understanding How ATP Rules Are Used In Global Order Promising (OM ATP) gives important information about how ATP Rules are used by OM and ASCP for calculating ATP. Bills of Materials/Routings/Resources (BOM) - Collects BOM information for the purpose of ASCP. Bill of Resources (BOR) - Collects BOR information for the purpose of ASCP. Calendars - Collects Calendar information for the purpose of determining valid work days. Demand Class - Collects the Demand Class Information for ASCP. Forecasts - Collects Forecast Information used in ASCP. Items - Collects Items and Attributes for the items in the Organizations being collected where the ATP Flag = Yes in the Item Organization form. Key Performance Indicator Targets - Collects Key Performance Indicators to be used in ASCP. Master Demand Schedules (MDS) - Collects MDS Plans used in ASCP. Master Production Schedules (MPS) - Collects MPS Plans used in ASCP and also used by ATP for scheduled Supply. **On Hand - Collects On Hand Quantities used in ASCP. Planning Parameters - Collects specific parameters used in ASCP. Planners - Collects information specific to Planners used in ASCP when releasing requisitions. Projects/Tasks - Collects Project/Task information for ASCP. **Purchase Orders/Purchase Requisitions (PO) - Collects valid Purchase supply information to determine availability and used in ASCP. Reservations - Collects current Reservation information to collect Hard Reservations for Sales Orders. Resources Recalculate (NRA) - Primarily for Process Manufacturing, calculates resource availability information. When the instance is set as Mixed/Process, this parameter will populate the Resource Availability. In

the case of Discrete Mfg. instance, the parameter on Planning ODS load form controls whether the resource availability is to be calculated. Safety Stock - Collects available Safety Stock to be used in ASCP and ATP. **Sales Orders - Collects Sales Order information: New Sales Orders will update availability, BUT canceled sales orders do not reflect supply and need to be collected. Sourcing History and ODP parameter - Recalculate Sourcing History Calculates Sourcing History for ASCP. Set this parameter to YES on Planning Data Pull and Planning ODS Load form, ONLY if using Sourcing history calculations in ASCP. There is a profile option 'MSC:Sourcing History Start Date Offset (in months) to set how many months of Sourcing History to be calculated, going backward - starting from today. This profile option is useful when the parameter 'Purge Sourcing History' is set to yes on Planning ODS Load form. This functionality was introduced for Inventory Optimization-Sourcing Splits. Sourcing Rules - Collects Sourcing Rules for ASCP. Subinventories - Collects Subinventories for ATP and ASCP. Trading Partners (customers) - Collects Customer data, which includes Global Entities for ATP and ASCP. Also collects the Customers + Customers sites information and Key Transformations is done. Trading Partners (suppliers) - Collects Supplier data, which includes Global Entities for ATP and ASCP. Also collects the Suppliers + Suppliers sites information and Key Transformations is done. Unit Numbers - Used in ASCP for Project Planning. Unit of Measure (UOM) - Collects the listed Unit of Measure Conversions to be used in ASCP. User Supplies and Demand - For ATP functionality where User defines the Supplies and Demands. **Work in Process (WIP) - Collects valid WIP jobs for Supply and Demand information to be used in ASCP and ATP. References: Note 145419.1 - How to Set Up Data Collection for Order Management ATP Availability Note 170253.1 - List of High Priority Patches for OM ATP ASCP and ODP Note 207644.1 - Data Collections is Failing - All Errors - First Diagnostic Steps Note 208140.1- Understanding How ATP Rules Are Used In Global Order Promising (OM ATP) .