Parameters

This appendix covers the following topics:

Overview

There are three types of parameters that determine the collection of data. They include:

These parameters are set when running collections, depending on the type of collection (Standard, Continuous or Legacy).

For more details about parameters, please see My Oracle Support Note #179522.1 - "Data Collection Parameters".

For more information about running collections, please see Running Collections.

Note: If you are running Standard Collections in Complete Refresh mode, then setting No will remove all data for the entity. Use Targeted Collection if you require to collect only certain data entities and are not going to use default values populated for Complete Refresh.

Planning Data Pull Parameters

Parameter Values Avaliable for Net Change Refresh?
Instance Source instance code from list of values.  
Collection Group Collection group, set up in the Admin/Instances form in the Organization screen.

Important: If you have very large BOM tables and plan to use collection groups to collect information for only certain orgs, be aware that this can use very significant TEMP space during the ODS Load. Oracle has seen reports where all orgs takes only 6-12 Gb of TEMP space, but when using a collection group, the TEMP space requirements exceed 30 Gb.

  
Number of Workers One or greater. Increase this number to increase the amount of computational resources to devoted to the Planning Data Pull process. This allows you to specify the number of workers for the Data Pull, which can now be different from the number of workers specified for the ODS load process.
It is recommended that you increase to 4-8 workers to improve performance. The default is 2.		  
Timeout (Minutes) The maximum amount of time you would like to allocate to the Planning Data Pull process. If the Planning Data Pull process has not completed within this amount of time, it will be terminated with an error.
For the initial run on a new instance, this may need to be set to 600-900. The default is 180.		  
Language Default language.  
Purge Previously Collected Data Yes (default) or No. Setting this to Yes wipes out all data in the APS planning server operational data store associated with the selected source instance as the first step in the collections process. If you set this to Yes, the only allowable collection method is Complete Refresh. If you set this to No, the allowable collection methods are Targeted Replacement and Net Change.  
Collection Method Complete Refresh/Targeted Refresh/Net Change Refresh.  
Analyze Staging Tables Yes or No (default). Set this to Yes periodically to recompute database access statistics on the APS staging tables. This speeds up the subsequent Planning ODS Load process. Should only set to Yes if directed by Development.  
Approved Supplier Lists Set to Yes if you want to collect Approved Supplier Lists. Y
ATP Rules Set to Yes if you want to collect ATP Rules.  
Bills of Materials/Routings/Resources Set to Yes if you want to collect Bills of Materials/Routings/Resources. Y
Bills of Resources Set to Yes if you want to collect Bills of Resources. Y
Calendars Set to Yes if you want to collect Calendars and Calendar Assignments.  
Demand Class Set to Yes if you want to collect the Demand Class.  
End Item Substitutions Set to Yes if you want to collect the End Item Substitutions.  
Forecasts Set to Yes if you want to collect Forecasts. Y
Items Set to Yes if you want to collect Items. Y
Key Performance Indicator Targets Set to Yes if you want to collect Key Performance Indicator Targets.  
Master Demand Schedules Set to Yes if you want to collect Master Demand Schedules. Y
Master Production Schedules Set to Yes if you want to collect Master Production Schedules. The default is No. Y
On Hand Set to Yes if you want to collect On Hand amounts. Y
Planning Parameters Set to Yes if you want to collect Planning Parameters.  
Planners Set to Yes if you want to collect Planners.  
PO Receipts Set to Yes if you want to collect PO Receipts. Y
Projects/Tasks Set to Yes to collect Projects/Tasks.  
Purchase Orders/Purchase Requisitions Set to Yes to collect Purchase Orders/Purchase Requisitions. Y
Reservations Set to Yes to collect Reservations. Y
Resources Availability Valid Values:

  • Regenerate and Collect Data. In this case, Regenerate and Collect Data will collect OPM data and discrete data.Default.

  • Do Not Collect Data.

Note: Profile option MRP: Cutoff Data Offset Months is used for Discrete Orgs only. It determines how many months of resource availability should be computed for resources and simulation sets. No resource availability is calculated beyond this horizon. For constrained plans beyond this horizon, resource capacity is viewed as infinite. Set this value to your plan horizon. A large setting (greater than 12 months) could have performance implications during ODS Load when the resource availability is calculated for each resource for each day.

 Net change - discrete organizations.
OPM organizations require Complete Refresh.
Safety Stock Set to Yes to collect Safety Stock. Only for User Defined Safety Stock from the Inventory application.  
Sales Orders Set to Yes to collect Sales Orders.

Note: Sales Orders are collected in the Net Change Mode for performance reasons and to reduce the ATP downtime during Complete Refresh.

Note: The Profile option MSC: Sales Order Offset Days determines how many days back Closed Sales orders are collected to be used for forecast consumption in ASCP. This profile is only applicable for Complete Refresh.

Set to 0 if not required. However, in 11.5.10, you must be on the latest 11.5.10 collection rollup to prevent errors during Net Change Collections.

 Y
Sourcing History Not used anymore. See ODS Load parameter: Recalculate Sourcing History.  
Sourcing Rules Set to Yes to collect sourcing rules. BODs, Assignment Sets, Region to Site Mapping are also triggered by this parameter.  
Sub Inventories Set to Yes to collect Sub Inventories.  
Supplier Responses Set to Yes to collect Supplier Responses. For Collaborative Planning, Net Change not supported; only Complete or Targeted supported.  
Suppliers/Customers/Orgs Set to Yes to collect Suppliers/Customers/Orgs. Collects 4 partner types to MSC_TRADING_PARTNERS and related tables. Partner_Type:
1 - Supplier
2 - Customer
3 - Organization
4 - Buyer		  
Transportation Details Set to Yes to collect Transportation Details. Shipping Details from WSH tables. Y
Unit Numbers Set to Yes to collect Unit Numbers. These are used for Project MFG for unit effectivity (serial number) in the bill of material.  
Unit of Measures (UOM) Set to Yes to collect Unit of Measure.  
User Company Association This parameter is used for Collaborative Planning Only.
Valid values:

  • No: During data collections, the destination instance does not accept the following: New users' company association and existing users with changes to their company association.

  • Create users and enable user company association: A user created on one of the source instances can be automatically created on the planning server or destination instance. You can use this option when you need to work with multiple source instances or systems. Default.

    Create a new user, specify the user's contact information during setup, and initiate a data collection. The user is created on the destination instance or planning server and is assigned the Supply Chain Collaboration Planner responsibility. The new user can log onto Oracle Collaborative Planning and view data that is visible to the associated company.

  • Create a new user, specify the user's contact information during setup, and initiate a data collection. The user is created on the destination instance or planning server and is assigned the Supply Chain Collaboration Planner responsibility. The new user can log onto Oracle Collaborative Planning and view data that is visible to the associated company.

    Create a new user on the source instance and specify the user's contact information during the setup. Create the user on the destination instance or planning system and assign the user responsibilities. Start a data collection to complete the user's company association. This ensures that the user has all the assigned responsibilities.

  
User Supplies and Demand Set to Yes if you want to collect User Supplies and Demand. Used when manually populating MTL_USER_SUPPLY and/or MTL_USER_DEMAND. Y
Work in Process Set to Yes if you want to collect Work in Process. Jobs that are in status Unreleased, Released, Complete and On Hold (wip_discrete_jobs.status_type) collected. Y
Sales Channel Set to Yes if you want to collect Sales Channel. Used for Demantra only.  
Fiscal Calendar Set to Yes if you want to collect the Fiscal Calendar. Used for Demantra only.  
Internal Repair Orders Set to Yes if you want to collect Internal Repair Orders. Used for Depot Repair integration - SRP/SPP. Y
External Repair Orders Set to Yes if you want to collect External Repair Orders. Used for Depot Repair integration - SRP/SPP. Y
Payback Demand/Supply Set to Yes if you want to collect Payback Demand/Supply.  
Currency Conversion Set to Yes if you want to collect Currency Conversion. Used for Demantra only.  
Delivery Details Set to Yes if you want to collect Delivery Details. Used for OTM integration (Oracle Transportation Management).  

Planning ODS Load Parameters

Parameter Values
Instance Source instance code from list of values.
Timeout (Minutes) Number of minutes before the concurrent program will end. The default is 60. For new instances or when using Recalculate options below, increase to a higher value.
Number of Workers One or greater. Increase this number to increase the amount of computational resources to devoted to the Planning ODS Load process. The default is 3. Increase to 4-8 workers to improve performance.
Recalculate Sourcing History The value that you set here is the one that actually determines whether sourcing history is collected or not. If you select Yes, then VCP will collect all new sourcing history not already on the planning server in the time range [(today - x months) through (today)] from the source transaction system. The number x is given by the value that you set for the profile option MSC: Sourcing History Start Date Offset (in months). During planning, ASCP will use the total cumulative sourcing history on the planning server in addition to the planned sourcing in the plan to determine whether sourcing percentages in sourcing rules are being respected or not. Used in conjunction with the Purge Sourcing History parameter below, which deletes existing sourcing history before calculating sourcing history again.
For distributed installations, set this profile option on the VCP Destination. Offsets the starting date of sourcing history calculations and is used in conjunction with the Purge Sourcing History parameter below.
Defaults to Null which Collects All Data. Set to prevent performance problems when the parameter is set to Yes. System performance can be degraded when there is a high value for this profile option and a high volume of source transaction data.
Purge Sourcing History Valid values are Yes and No (default). If you select Yes, then all sourcing history present on the planning server will be deleted before the collection process commences. All previous history is removed in the base table.
If Sourcing History needs to be removed for business reasons, then you can set this to Yes, and Recalculate Sourcing History to No. This effectively removes all Sourcing History on the system.
Refresh Collected Data in APCC Repository This parameter is used when you want to refresh the collected data in the APCC repository.
Valid values:

  • Yes

  • No (default)

Legacy Collections

Parameter Values
Purge Legacy Data Runs MSCPPURB.pls - MSC_PURGE_LID
Purge Interface Tables The MSC_SRS_INSTANCE_CODE_ODS is used to get the instance code. Runs MSCCLPSB.pls - MSC_CL_PURGE_STAGING