The EBS Source and VCP Destination profile options, in conjunction with the Flex Field profile options, are the basic profile options that need to be set for VCP collections. The EBS source and VCP destination profile options are used to customize the ASCP and EBS planning applications. These profile options can be modified at any time. The MSC: Source Setup Required profile option is critical for establishing the EBS source instance database objects used for Refresh Collections Snapshots and data collection. The flex field profile options are only used for the VCP planning applications and are run after the EBS source instance link is defined.
If you are using ATP with Oracle Order Management alone, you configure the set of profile options specified. If you are planning to use GOP with ASCP, you will need to configure additional profile options. Please refer to Other Profile Options for information.
If you are integrating with legacy systems or other VCP applications, you will need to configure additional profile options.
When all profile options are set, enter any data that may be required for VCP.
| BIS: Primary Rate Type |
Y |
Y |
|
Lookup from GL tables. If populated, then can be used for price information of supplies and demands from GL_DAILY_CONVERSION_TYPES.
Profile DB Name: BIS_PRIMARY_RATE_TYPE |
| BOM: Hour UOM |
Y |
Y |
Y |
Used for collecting Resource Requirements. HR is the usual setting.
Profile DB Name: BOM:HOUR_UOM_CODE |
| CRP: Spread discrete requirements |
Y |
Y |
|
Used in ASCP for resource horizontal plan. Not used for collections. Valid values: Yes/No.
Profile DB Name: CRP_SPREAD_LOAD |
| GMD: Yield Type |
|
Y |
|
Used for OPM - UOM Class for common conversions from SY_UOMS_TYP. Values come from a lookup for OPM conversion. Typically MASS or something similar.
Profile DB Name: FM_YIELD_TYPE |
| INV: Capable to promise |
Y |
Y |
Y |
Determines the source of ATP/CTP information.
Valid values:
-
ATP Based on Collected Data: If ASCP is not installed or if the ATP will not be using ASCP planning data. Default.
-
ATP/CTP Based on Planning Data: If ASCP is installed and the ATP will be using ASCP planning data.
Profile DB Name: INV_CP |
| MRP: Compute Standard Mandatory Components for ATO Models |
|
Y |
Y |
Determines whether to call the CTO API to calculate the dependent demand for ATO items during the Refresh Snapshots process. This will cause performance to be slower when Yes. Setting this to Yes would be normal if ATO models are present in the system. Collections code will default this profile to Yes if it is Null. Valid values: Yes/No.
Profile DB Name: MRP_EXPLODE_ATO
Note: When a new CTO/ATO item is created from a model, a * (asterisk) is inserted into the new item number. The CTO BMO not found for the item error prompt is a setup violation since the requirement for CTO is to configure and create the * (asterisk) item using CTO Auto-Create or by progressing the sales order.
Warning: ITEM_ID = 781553, ORG_ID=5002; No BOM found for configured item in ship-from org: You may safely disregard this warning if the configured item is transferred across orgs, and the warning points to an org in which no assembly of the configured item takes place.
If you are using ODS-based ATP, check that you have the BOM in shipping org. If you are using PDS-based ATP, check that item attribute "Create Configured Item, BOM" equals "Based on Model" and BOM exists in ship-from org.
|
| MRP: Consume MPS |
|
Y |
Y |
Specifies if the Planning Manager must be running in EBS Source instance. Valid Values: Yes (default)/No.
Profile DB Name: MRP_MPS_CONSUMPTION |
| MRP: Cutoff Data Offset Months |
Y |
Y |
|
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. Valid values: Integer/Null. Null is seen as 99999. This should be set between 12-24 in most cases.
System performance can be degraded when there is a high value for this profile option and a high volume of source transaction data.
Profile DB Name: MRP_CUTOFF_HISTORY_DAYS |
| MRP: Debug Mode |
Y |
Y |
|
Specifies whether more complete messaging is required for Refresh Collections Snapshots requests. Valid values: Yes/No (default).
Profile DB Name: MRP_DEBUG
Note: Do not set at site level, only at user level. For Collections, information written into MSRFWOR Refresh Collections Snapshots log file. For ASCP Planning: this profile makes very large log files and could slow down performance.
|
| MRP: Plan Revenue Discount Percent |
Y |
Y |
|
Optional. Specifies the average discount to be applied when calculating revenue of a plan as part of the plan performance indicators. This value is a key performance indicator used to calculate performance in a plan for Business Intelligence reports. Valid values: Integer 0-100.
Profile DB Name: MRP_BIS_AV_DISCOUNT |
| MRP: Plan Revenue Price List |
|
Y |
|
Optional. The Price List is used to calculate revenue of a plan as part of plan performance indicators from SO_PRICE LISTS. Key performance indicator used to calculate revenue of a plan for Business Intelligence reports. Valid values: Lookup for Price List in Order Management.
Profile DB Name: MRP_BIS_PRICE_LIST |
| MRP: Purge Batch Size |
Y |
Y |
Y |
This setting is used in Data Collections:
Valid values: Integer; default 75000. Generally, there is no reason to change this profile from the default setting.
Profile DB Name: MRP_PURGE_BATCH_SIZE
Note: In some circumstances, a delete process is taking too much time due to millions of rows of data. In the case of millions of records, Oracle suggests a setting of 250000. A higher value is not recommended since this profile option value is also used as a limit for BULK FETCH in ODS Load and a higher value could cause errors if the memory limit is reached.
|
| MRP: Purchasing By Revision |
Y |
Y |
Y |
Determines if ASCP Planning is released from the workbench. Valid values: Yes/No.
Profile DB Name: MRP_PURCHASING_BY_REVISION |
| MRP: Retain Dates Within Calendar Boundary |
Y |
Y |
Y |
Some applications do not look at the calendar assigned to the org and allow you to enter a date that is outside the calendar date. For example: Latest Acceptable Date in the Order Management application. This setting avoids failures related to dates that are outside the calendars defined in the system. Valid values: Yes/No (default). It is recommended that you set this profile to Yes.
Profile DB Name: MRP_RETAIN_DATES_WTIN_CAL_BOUNDARY |
| MRP: Use Ship Arrived Flag |
|
Y |
Y |
Used when collecting Intransit Supplies. Valid values:
-
Yes: the wsh_new_deliveries.ultimate_dropoff_date is checked to populate MRP_AP_INTRANSIT_SUPPLIES_V.ARRIVED_FLAG. If Arrived, then the supply is not collected.
-
No or Null: Intransit supply collected.
Profile DB Name: MRP_SHIP_ARRIVE_FLAG |
| MSC: Calendar Reference for Bucketing |
Y |
|
|
Calendar used for bucketing KPIs. |
| MSC: Category for Jobs without an Item Reference |
Y |
|
|
Displays category for jobs without an item reference in the ASCP planner workbench. Valid values are NULL (unspecified items) or specific category for jobs without an item reference.
Profile DB Name: MSC_NO_ACTIVITY_ITEM_CATEGORY |
| MSC: Category Set for Jobs without an Item Reference |
Y |
|
|
Displays category set for jobs without an item reference in the ASCP planner workbench. Valid values are NULL (NEW.MISC) or specific category set.
Profile DB Name: MSC_NO_ACTIVITY_ITEM_CATEGORY_SET |
| MSC: Coll Error Debug Mode |
Y |
|
|
Collects error messages for debugging purposes. Valid values: Off (default), Medium, High, 384-do not use, 128-do not use, 0-do not use. Leave this as Off if you have a performance issue. Unless instructed by Support or Development, do not use the other options.
Profile DB Name: MSC_COLL_ERR_DEBUG |
| MSC: Coll Performance Debug Mode |
Y |
|
|
Collects performance information for debugging purposes. Valid values: Off (default), Medium, High, 384-do not use, 128-do not use, 0-do not use. Leave this as Off if you have a performance issue. Unless instructed by Support or Development, do not use the other options.
Profile DB Name: MSC_COL_PERF_DEBUG |
| MSC: Collect CMRO Work Order Demands for PS |
Y |
|
|
Supports Production Scheduling application and Complex Maintenance, Repair and Overhaul). Valid values: Yes/No (default).
Profile DB Name: MSC_CMRO_WO_DEMAND_PS |
| MSC: Collect Completed Jobs |
Y |
|
Y |
Specifies whether completed jobs are collected. Valid values:
-
Yes: Collect jobs with the status "complete". If some component demands have not been fully issued to the job, then the component demands are collected and will be seen in the ASCP plan and for ATP.
-
No: Do not collect requirements for completed jobs. This option was created to stop the collection of requirements left when the job is completed and not yet set to Complete - No Charges Allowed or Closed.
Profile DB Name: MSC_COLLECT_COMPLETED_JOBS |
| MSC: Collect Item, Material and Resource Costs |
Y |
|
Y |
Specifies whether item, material and resource costs are collected. Valid values are:
-
Yes: Collects item, material and resource costs. Will join with CST_ITEM_COSTS table or for OPM items, will launch OPM package to get costs from OPM tables. Item cost is seen in MSC_SYSTEM_ITEMS table. If using Inventory Optimization or Constrained Optimized plan, Yes is required. Null is seen as Yes.
-
No: Uses a different view and collects costs as 0.
Tip: Using No can be faster for collections to complete, so if not required, set to No.
Profile DB Name: MSC_COLLECT_COSTS_FOR _ITEM |
| MSC: Collect Routing |
Y |
|
Y |
Specifies whether routings are collected. Valid values:
-
Yes: Collects routings. If profile INV: Capable to Promise = ATP/CTP based on Planning output, then will always be seen as Yes and collect data. Null seen as Yes.
-
No: Doesn't collect routings. It is useful to avoid collecting routing information when using ATP based on Collected Data or if you have large routing tables.
Tip: Using No can be faster for collections to complete, so if not required, set to No.
Profile DB Name: MSC_COLLECT_ROUTING |
| MSC: Collection Window for Trading Partner Changes (Days) |
Y |
|
|
Specifies the number of days backwards to check for changes in customer names, customer sites, vendors and vendor sites to be collected. Use when suppliers, customers, orgs are set to yes for collections when using ATP and when running ASCP plans. Valid values: Integer/Null (default). Null is the equivalent of 0, which will collect all records. Null must be used for the first run. After the first run, you should set up for a smaller number. Generally, 7 days should be sufficient. As long as you run a complete refresh at least once per 7 days, then this will collect the changes.
Profile DB Name: MSC_COLLECTION_WINDOW_FOR_TP_CHANGES
Caution: Setting to Null or 0 after the first run of data collection can cause performance issues.
|
| MSC: Collections Snapshot Threshold |
Y |
|
Y |
Checks the numbers of rows in table and number of rows in the MLOG. If ratio exceeds the threshold, then a Complete Refresh of the Snapshot is launched. Valid values: Integers 0-100/Null (default).
Tip: It is not recommended to set this profile unless directed by Development. It is faster to perform a complete refresh when a large number of rows exist in the MLOG, than reference the MLOG table for a fast refresh. This profile is usually triggered when a large data load is performed to load data into setup tables.
Profile DB Name: MSC_SNAPSHOT_THRESHOLD |
| MSC: Configuration |
Y |
|
Y |
Specifies whether the Collaboration ODS Load for Collaborative Planning is launched at the end of Data Collections for ASCP. This process does not affect ASCP Planning. You can launch the ASCP plan while this process is still running. If using CP, then the process does need to complete before you can launch any other CP processes. Valid values:
-
APS: Will not launch the Collaboration ODS Load for Collaborative Planning.
-
CP: Launches the Collaboration ODS Load for Collaborative Planning. Only used for standalone implementation of CP.
-
APS & CP: Launches Collaboration ODS Load for Collaborative Planning.
Important: This option is required for Demantra.
Profile DB Name: MSC_X_CONFIGURATION |
| MSC: Cost Type |
|
Y |
|
Specifies the cost type that collections should use when collecting the item costs from CST COST TYPES. Valid Values:
Profile DB Name: MSC_COST_TYPE |
| MSC: Currency Conversion Type |
|
Y |
|
Set this profile option on the source instance to specify currency conversion type. If you change the value, the next time you run collections, the collections process purges the data with the previous currency conversion type and replaces it with the new currency conversion type. Valid values: A currency conversion type; Corporate is the default. |
| MSC: Days of Resource Availability before sysdate |
Y |
|
|
Calculates resource availability for the number of days specified before sysdate. Valid values: Integer/Null (equals 1).
Tip: If a high number, then resource availability calculation during ODS Load could take a longer time.
Profile DB Name: MSC_RES_AVAIL_BEFORE_SYSDAT |
| MSC: Degree of Parallelism for Index Creation |
Y |
|
Y |
Controls the use of parallel processes when creating indices on the temporary tables created during the ODS Load. Valid values: Integer 0 (default) to 10. Required setting of 1 if fails with NULL or 0. The value can be increased if there are performance problems with the ODS Load and system resources can be allotted.
Profile DB Name: MSC_INDEX_PARALLEL_THREADS |
| MSC: Enable ATP Summary Mode |
Y |
|
Y |
Enables summarization of supply and demand data following the data collection and plan launch processes. These tables are only for ATP based on collected data. Valid values:
-
Yes: Enable ATP Summary Mode.
Note: If this profile set to Yes and INV: Capable to Promise = ATP/CTP based on Planning Data, then the request Load ATP Summary Tables will run at the end of Data Collections and will error. This can be ignored or you can set the profile to No in order to avoid the error.
-
No: Disable ATP Summary Mode.
Profile DB Name: MSC_ENABLE_ATP_SUMMARY |
| MSC: Future Days for Currency Conversion |
Y |
|
|
Number of days in the future to be considered for collecting currency conversions. Collects currency conversion data for display in APCC. Valid values: Integer. Set this to a reasonable number of future days for displaying currency conversion data. A very high number or NULL with long calendar end date 10 years out could cause performance issues. If you are not using APCC, do not set this profile.
Profile DB Name: MSC_FUTURE_DAYS_FOR_CURR_CON |
| MSC: History Days for Currency Conversion |
Y |
|
|
Number of days in the past to be considered for collecting currency conversions and displayed in APCC. Valid values: Integer. A high number could cause longer collection times when using Currency Conversion = Yes. In most casts, 365 days should be sufficient.
Profile DB Name: MSC_HISTORY_DAYS_FOR_CURR_CON |
| MSC: Inflate WIP Resource Requirements |
Y |
Y |
|
Determines whether ASCP should inflate the Work in Process resource requirements based on resource efficiency and utilization during collections from Oracle Work in Process. Used for ASCP Planning. See "Appendix A" in the ASCP User's Guide for more information. Valid values: Yes/No.
Profile DB Name: MSC_INFLATE_WIP |
| MSC: Operator Company Name |
Y |
Y |
Y |
Specifies the operator company name. Valid values:
-
My Company is defaulted at application level for ASCP during the installation. MSCXUPG.sql is SQL that inserts MSC_COMPANIES.COMPANY_ID = 1, COMPANY_NAME = My Company during installation.
-
Null: Data Collections will fail if not specified.
Profile DB Name: MSC_X_COMPANY_NAME |
| MSC: Organization containing generic BOM for forecast explosion |
|
Y |
|
Used by Collections to identify and populate the Bill of Material validation organization. This is used for ASCP Planning to explod the BOM for forecast explosion and consumption. In a distributed installation, this profile is setup on the EBS Source. Then Data Collections will populate this organization_id in MSC_APPS_INSTANCES in column VALIDATION_ORG_ID. Valid values: Null (default)/Organization code of organization that will hold the BOM for ATO models (usually the master org). |
| MSC: Planning Hub Currency Code |
Y |
|
|
Use this profile option on the destination instance to specify reporting currency. If you change the value, the next time you run collections, the collections process purges the data with the previous currency code and replaces it with the new currency code. Valid values: Currency code; blank is the default. |
| MSC: Project Task Collection Window Days |
Y |
|
|
Used to limit the collection of completed projects and tasks. Valid values: Integer. Defaults as NULL (seen as 0) which will collect all records. A value of 100 means that projects and tasks marked as completed for 100 days are collected. On day 101, those completed projects and tasks are no longer collected. This profile can be set to help performance if you are using projects and tasks and have many records.
Profile DB Name: MSC_COLLECTION_WINDOW_FOR_PROJ_TASKS |
| MSC: Purchase Order Dock Date Calculation Preference |
Y |
Y |
|
Specifies the purchase order line date that ATP and ASCP Plan use as the material arrival (dock) date. Valid values: Promised Date or Need By Date.
Profile DB Name: MSC_PO_DOCK_DATE_CALC_PREF |
MSC: Purge Staging and Entity Key Translation Tables
(formerly called MSC: Purge Stg Tbl Cntrl pre-R12.0.6) |
Y |
|
|
Specifies whether the staging tables will be truncated or deleted when Data Collections retrieve data from an instance (usually a single instance).
Valid values:
Yes -- Truncates the staging table during the data collection process to improve performance and conserve disk space. Set to Yes if you are collecting from only one EBS source instance. For multiple instances, separate the processes.
No -- Causes staging tables to be deleted instead of using the Truncate command. Since the tables are not truncated, their size can increase over time without space being recovered when deleted, ultimately leading to slower collections performance. In this case, it is recommended that the DBA periodically schedule a truncate of the MSC_ST% tables when Data Collections are not running to recover space and help performance.
Profile DB Name: MSC_PURGE_ST_CONTROL |
| MSC: Refresh Site to Region Mappings Event |
|
Y |
|
This profile performs mapping of regions to supplier sites based on setups in the Order Management Regions and Zones form. Valid values:
-
Collection of Sourcing Rules: When Parameter Sourcing Rules is set to Yes, then run Region to Site mapping (recommended). This just collect supplier information, which is not performance-intensive.
-
Running of Refresh Collection Snapshots Request: Only run this integration when you launch Refresh Collection Snapshots as a standalone request.
Note: This profile is only used for vendor site to region mapping, which is used for Transit Times setup in ASCP with Region and Zones. After initial collection, only changes to current regions are collected. But when new regions or zones are defined, all the vendor sites are remapped, which can be time-consuming and affect performance.
Profile DB Name: MSC_REFRESH_REGION_SITE |
| MSC: Refresh Snapshots Pending Timeout |
Y |
|
|
Specifies timeout when Refresh Collections Snapshots is launched. Valid values: Integer. 10 is the default (minutes). No changes are recommended unless there is a problem with launching Refresh Snapshots.
Profile DB Name: MSC_REF_SNAP_PENDING_TIMEOUT |
| MSC: Sales Orders Offset Days |
Y |
Y |
|
Specifies the number of days of closed sales orders to be collected after the SYSDATE. Uses Shipped Sales Order line information during ASCP Planning to indicate the forecast for the demand schedule of a plan. Designed to collect only closed sales orders where open_flag = no or order_quantity = shipped_quantity. Valid values: Integer/NULL. The smaller the number, the faster Data Collections can complete Sales Order loading. The number required depends on forecasts consumption Forward Days setting. For example, if Maximum Foreward Days setting for any Collected Forecast or ODP forecast is 30 days, then the setting should be at least 30 days. NULL is (not recommended as it will collect all closed sales orders after the SYSDATE -99999 (or 10,000 days). Used in the MRP_AP2_SALES_ORDERS_V collections view.
Note: Calculated using calendar days. Must be the same on both the Source and Destination.
Profile DB Name: MSC_SO_OFFSET_DAYS |
| MSC: Share Plan Partitions |
Y |
|
|
Specifies whether to share the plan partitions.
Valid values:
|
| MSC: Source Setup Required |
|
Y |
|
Automatically sets the application when a Collections Patch is applied. Valid values:
-
Yes: Setup requests are run during Data Collections. The profile is read by the request Refresh Collection Snapshots. These requests create all the EBS source instance database objects that are needed for data collections to complete successfully.
-
No: Does not run setup request during Data Collections.
Note: This profile is not considered when you run Refresh Collection Snapshots as a standalone request and use Automatic Refresh.
Profile DB Name: MSC_SOURCE_SETUP |
| MSC: Sourcing History Start Date Offset (in months) |
Y |
|
|
Offsets the starting date of sourcing history calculations and is used with collections parameters Purge Sourcing History = Yes and Recalculate Sourcing History = Yes. These settings delete, then calculate Sourcing History from the Start date determined by the profile option value (in months). Used to calculate planned orders when the sourcing rules are split for ranks. Valid values: Integer/NULL (default). System performance can be degraded when left as NULL or set to a high value with a high volume of source transaction data. Set 0 if you have no sourcing splits defined in the sourcing rules. For sourcing rules with splits, choose a setting of between 3 and 12 depending on your business requirements.
Profile DB Name: MSC_START_SOURCING_HISTORY |
| MSC: Use Shipping/Receiving Calendar |
Y |
Y |
|
Specifies whether the Shipping/Receiving Calendar is collected for use with ASCP and Global Order Promising (GOP). Valid values:
Profile DB Name: MSC_USE_SHIP_REC_CAL |
| Items |
Late Demands Penalty (Item) |
MTL_SYSTEM_ITEMS |
MSO: Penalty Cost Factor for Late Item Demands Flexfield Attribute |
| Items |
Material Over-Capacity Penalty (Item) |
MTL_SYSTEM_ITEMS |
MSO: Penalty Cost Factor for Exceeding Item Material Capacity Flexfield Attribute |
| Organization Parameters |
Late Demands Penalty (Org) |
MTL_PARAMETERS |
MSO: Penalty Cost Factor for Late Demands (Organization) flexfield attribute |
| Organization Parameters |
Material Over-Capacity Penalty (Org) |
MTL_PARAMETERS |
MSO: Penalty cost factor for exceeding material capacity (Organization) flexfield |
| Organization Parameters |
Resource Over-Capacity Penalty (Org) |
MTL_PARAMETERS |
MSO: Penalty cost factor for exceeding resource capacity (Organization) flexfield |
| Organization Parameters |
Transport Over-Capacity Penalty (Org) |
MTL_PARAMETERS |
MSO: Penalty cost factor for exceeding transportation capacity (Organization) |
| Department Resource Information |
Aggregate Resources |
BOM_DEPARTMENT _RESOURCES |
MSC: Aggregate Resource Name Flexfield Attribute |
| Department Resource Information |
Resource Over-Capacity Penalty (Resource) |
BOM_DEPARTMENT _RESOURCES |
MSO: Penalty cost factor for exceeding resource capacity (Resource) flexfield |
Attribute
(Purchasing) |
Material Over-Capacity Penalty (Supplier) |
PO_ASL_ATTRIBUTES |
MSO: Penalty Cost Factor for Exceeding Material Capacity Flexfield Attribute |
| Substitute Component Information |
Substitute Items Priority |
BOM_SUBSTITUTE_ COMPONENT |
MSC: Priority for Substitute Items Flexfield Attribute |
| MTL Interorg ship methods |
Transport Over-Capacity Penalty (Ship Method) |
MTL_INTERORG_SHIP _METHOD |
MSO: Penalty cost factor for exceeding transportation capacity flexfield attribute |
| Bill of Material Information |
BOM/Routing Cost |
BOM_BILL_OF_MATERIALS |
MSC: Cost of Using a BOM/ Routing Flexfield Attribute |
| MRP Forecast Dates |
Late Forecasts |
MRP_FORECAST_DATES |
MSO: Penalty cost factor for late forecasts |
| Additional Line Information |
Late Sales Order Penalty |
SO_LINES |
MSO: Penalty cost factor for late sales orders |
| Production Line |
Resource Group (Line) |
WIP_LINES |
MSC: Resource Group for a Line Flexfield Attribute |
The following table provides the source of the profile option documentation for the following VCP applications: