The following table lists and defines the MSC profile options available with Oracle Advanced Planning.
| Profile Option Name | Valid Values | Default Value | Description |
|---|---|---|---|
| CP HZ View Default Query | Yes/No | Yes | Displays default results in the Oracle Collaborative Planning Horizontal View. |
| MSC: 64-bit Planner Platform | Yes/No | No | Set to Yes for the supported 64-bit platforms (HP-UX and Sun Solaris 2.8). |
| MSC: Action Allowed on ATP 24x7 Plan While Running | Yes/No | Yes | This profile option controls whether you can access and make changes to the ATP plan while it is running in 24x7 mode. The changes you make to the plan while it is running will not be reflected in the refreshed plan. If you set this profile option, consider setting MSC: ATP Synchronization Downtime (minutes). This is a site level profile option. |
| MSC: Aggregate Resource Name Flexfield Attribute | Integer >= 0 | Null | Stores flexfield column name that contains its value in the corresponding table. See Flexfield Attributes for more information. |
| MSC: Allocated ATP Forward Consumption Method | Reduce future supply from lowest priority and Reduce available supply from any priority | Reduce future supply from lowest priority | This profile controls the forward consumption method for allocated available to promise using the user-defined allocation percentage method. The values are: - Reduce future supply from lowest priority: The shortage --after consuming its own allocated supply and available supply from a lower priority--is accounted for by using available future supply from the lowest priority. If all the demand classes are at the same priority, the shortage from a demand class consumes its own future supply. Use this if you prefer to delay some of the committed demand and hold the supply for higher priority demand classes. - Reduce available supply from any priority: The shortage --after consuming its own allocated supply and available supply from lower priority--is accounted for by using available supply from higher priority demand classes. Therefore, committed demand must be accounted for before allowing more promises. This is a site level profile option. |
| MSC: Allocation Assignment Category Set | Valid category set | Category specified in profile option MSC: Sourcing Category Set | The Assign Allocation Rule form and the Sourcing assignment form both use the MSC: Sourcing Category Set to determine the valid category set. Use this profile option if you want the allocation rule category set to be different from the sourcing assignments category set. |
| MSC: Allow Release of Planned Orders from Demand Schedule Plan | Yes/No | No | This profile option provides increased flexibility for releasing planned orders and applies only to manual release. It is not considered for auto-release. MPS and MPP planned orders cannot be auto-released from the MRP. The planning engine assumes that if the item is marked so that auto-release is allowed then auto-release has already occurred from the MPS or the MPP. Valid values are: - Yes: You can release demand schedule MPP or MPP planned orders from the lower level plan - No: You cannot release demand schedule MPP or MPP planned orders from the lower level plan |
| MSC: Allow Release of Planned Orders from Demand Schedule Plan | Yes/No | No | Use this profile option to allow manually release master production plan and master production schedule planned orders from the material requirements planning plan, when the master production plan or master production schedule is a demand or supply schedule to the material requirements planning plan. Valid values are: - Yes: Allow manual release - No: Do not allow manual release This profile only applies to manual release. It is not considered for auto-release; auto-release of planned orders of the release master production plan and master production schedule planned orders occurred during their plan runs. |
| MSC: Anchor dates for calculating operation yields | Operation start date or Order start date | Operation start date | Use this profile option to instruct the planning engine on which effectivity date to use when it generates resource requirements of operations with yields. This profile option applies to discrete jobs and Oracle ShopFloor Management (OSFM) routings with primary network scheduling method. - Order start date: Use the order start date to check for operation effectivity and select yield value - Operation start date: Use the operation start date to check for operation effectivity and select yield value. The planning engine uses lead-time percent to calculate the operation start date; it assumes that the lead-time percent of an operation that is effective in the future is the same as the lead-time percent of the operation it replaces. If an operation's effectivity ends within a time bucket, the planning engine assumes that its effectivity ends on the first day of the time bucket. |
| MSC: Anchor date for calculating remaining shelf life | Arrival Date/Ship Date | Arrival Date | Use this profile option to instruct the planning engine which date to use as an anchor date for calculating the remaining shelf life. Valid values are: - Arrival Date: Calculate the remaining shelf life from the arrival date at the customer site - Ship Date: Calculate the remaining shelf life from the ship date. |
| MSC: APCC Currency Code | Currency code | <blank> | 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 data with the new currency code. |
| MSC: Apply Lot Modifiers in Weekly/Period Buckets | Yes/No | Null | Determines whether order modifiers are considered when creating planned orders for weekly or period time buckets. A Yes value considers order modifiers in these calculations. A No value does not consider order modifiers in these calculations |
| MSC: Apply Order Modifier To Start Quantity | Yes/No | No | Use this profile option to specify whether order modifiers are applied to start quantities for discrete or lot based jobs. This behavior only applies to routings that have operation yield. In this case the start quantity may be different from the expected supply quantity. Valid values are: - Yes: The planning engine inflates the order start quantity by the routing operation yield and then applies order modifiers. - No: The planning engine applies the order modifiers to the end quantity. |
| MSC: Apply Safety Stock Change interval to non MRP Planned Safety Stock | Yes/No | No | Use this profile option to specify the safety stock to which the smoothing within time interval applies: Valid values are: - Yes: Smoothing applies to all types of safety stock - No: Smoothing applies only to MRP planned safety stock |
| MSC: Apply shortage and excess tolerance percentages to planned orders | Yes/No | Yes | Use this profile option to control the types of supplies to which the planning engine applies Shortage Tolerance Percent and Excess Tolerance Percent. Valid values are: - Yes: Apply them to all supply types -No: Apply to them to all firm supply types except firm planned orders, for example, on-hand and scheduled receipts. Using this option means that, in general, if the quantity of firm supplies used to satisfy a demand is lower than the Shortage Tolerance Percent of the item, the planning engine does not apply the tolerance to planned orders that it recommends. Whenever a demand is not fully satisfied, the planning engine sets the replenishment date to the end of the planning horizon. |
| MSC: ASCP Planning URL | <A url> | Null | Use this profile option to enable access to the web tools browser pages. Set it at the site level. Use format http://domain_name:port_number. Use the domain name of your ASCP managed server and its port number. |
| MSC: ATP Allocation Method | User-Defined Allocation Percentage, Demand Priority | Null | Determines the allocation method used by ATP. This is a site level profile. Valid values are:
|
| MSC: ATP Assignment Set | Text | Null | Indicates name of the assignment set for Oracle Global Order Promising to use to identify all the possible shipping organizations. Oracle Global Order Promising uses this assignment set if profile MRP: ATP Assignment Set is Null on the ERP instance. Users can update it the at site level in the Planning instance. |
| MSC: ATP Capacity Allocation | Yes/No | No | Set it to No. You should only set it to Yes under specific instruction from Oracle Applications development. |
| MSC: ATP Debug Mode | Debug Only, Debug and Database Trace, Database Trace Only, None | Null | Determines whether to enable debug messages within Oracle Global Order Promising. You can update it at the user level. Valid values are: - Debug Only: ATP generates a log file for an ATP request. - Debug and Database Trace: ATP generates a log file and a database trace file. - Database Trace Only: ATP generates a database trace file. - None: ATP does not generate log file or database trace file. |
| MSC: ATP Enforces Lead Time for ATO Model | Yes/No | Yes | Use this profile option to specify how ATP considers lead-time. Valid values are: - Yes: ATP always enforces lead-times for non-ATPable ATO models - No: ATP does not enforce lead-times for non-ATPable ATO models |
| MSC: ATP Infinite Time Fence Pad | Integer >=0 | Null | Oracle Global Order Promising adds the number of days specified in this profile option to the infinite time fence you specify in an ATP rule. It inflates the infinite time fence by that number of days. Use this profile option when you want an infinite time fence date for an item to be based on the item manufacturing lead-times plus extra days. This is a site level profile option. |
| MSC: ATP Synchronization Downtime (minutes) | Integer > 0 | Null | You may need to set this profile option if you run available to promise in 24x7 mode. When new sales orders come in while the synchronization process is running, the process can run for a long time if the order volume is high. Available to promise cannot switch to the new plan until the process finishes. Specify the ATP downtime in minutes. During the downtime, there are no new sales orders for available to promise to process. The synchronization process can finish as soon as possible. There is a trade-off between available to promise downtime and the time it takes to switch to the refreshed plan. This is a site level profile option. |
| MSC: Automatically Recalculate Operation Time | Yes/No | No | If the value of this profile option is Yes, the planning engine recalculates make order New Date (due date) if you both: - Firm the order - Update New Start Date The calculation process uses: - Fixed and variable lead times - Working days. This applies only to unconstrained plans. It has certain limitations. |
| MSC: Auto-Release Compression Days Tolerance | Integer >= 0 | Null | Indicates the number of compression days allowed for the automatic release of planned orders. |
| MSC: Auto-Release Compression Days Tolerance | Null/List of Values | Null | This profile option specifies the workday calendar that the planning engine uses to bucket the beginning and end of weeks and periods. Values are: - Null: If you set this value, the planning engine uses the plan owning organization's calendar for bucketing weeks and periods. This is the organization that you launch the plan from. - List of Values: You can select any calendar in the list of values for this profile option. This list of values includes all calendars that you defined on the source instance and collected. The calendar that you associate with the profile option should be a seven-day calendar without any holidays. If not, some supplies may be adjusted to later weeks when two organizations have different calendars. |
| MSC:Avoid Re-sourcing Sales Orders | Yes/No | Yes | Use this profile option to instruct the planning engine whether to source sales orders. Valid values are: - Yes: Do not source sales orders. - No: Source sales orders. You can plan by arrival date, change ship methods, and change source orgganization if you have set up the correct sourcing rules. |
| MSC: Buy Order Processing Lead Time Calendar | Supplier Capacity Calendar, Org Manufacturing Calendar | Supplier Capacity Calendar | Use this profile option to instruct the planning engine what calendar to use when it offsets processing lead-time for buy orders. Valid values are: - Supplier Capacity Calendar: The planning engine offsets processing lead-time for buy orders using the Approved Supplier List Supplier Capacity Calendar. The Approved Supplier List Supplier Capacity Calendar is the successor to the Approved Supplier List supplier delivery calendar. - The planning engine offsets processing lead-time for buy orders using the organization manufacturing calendar |
| MSC: Cancel Outstanding Sales Order Quantities | Yes/No | No | Use this profile option to specify if distribution planning should cancel unfilled sales orders after the sales order latest acceptable date (Fill or Kill). The canceled quantity is displayed in the Expired Demand field of the Supply Demand window. |
| MSC: Category set for CP Horizontal View | - | - | Indicates a category set that you want to query in the Oracle Collaborative Planning horizontal view. Using this profile option, you can restrict queries to specific categories based on your requirement. |
| MSC: Choice of Item for Which to Create Supplies in Substitute Relationship | Demanded Item, Highest Level Item, Follow Item Attributes | Demanded Item | Determines the item for which Oracle Global Order Promising and Oracle Advanced Supply Chain Planning creates planned supplies when item substitution relationships are specified. When set to Follow Item Attribute and the item attribute Create Supply for all the substitute items in the substitution chain is No, no supplies are created. When you have a substitution chain A --> B --> C, and this profile option is set to Highest Level Item, it is expected that Oracle Advanced Planning creates supply for item C. Item C must be enabled in the organization where you are trying to create supply. If item C is not enabled in the organization, Oracle Advanced Planning creates supply for item B (the next highest level item in the substitution chain) and does not create supply for item C. |
| MSC: Circular Sourcing Surplus Inventory Basis | - | - | Not used. |
| MSC: Circular sourcing surplus days | - | - | Not used. |
| MSC: Class Hierarchy | Demand / Customer | Demand | Indicates which allocation hierarchy to use. Users can update at the site level. Valid values are: - Demand Class: User-defined, single-level hierarchy. - Customer Class: Three levels: customer class, customer, and site. |
| MSC: Collaborative Planning Default Calendar | - | - | The horizontal view buckets supply and demand data into days, weeks and months (periods) according to the receiving calendar of the trading partner who receives material. This profile option indicates the default system calendar that Oracle Collaborative Planning uses when multiple customer sites are displayed together. |
| MSC: Collect CMRO Work Order Demand | No | Yes/No | Specifies if Consumed Items are being imported to Production Scheduling. If no Work Order Consumed Items are being imported, set profile MSC: Collect CMRO Work Order Demand to Yes. Used when performing collections. It is not used in release 12.2 and higher. |
| MSC: Collect Item, Material and Resource Costs | Yes/No | Yes | This profile option indicates whether data collection should include cost information. Specifying No may improve data collections performance. |
| MSC: Collect Routing | Yes/No | No | Use this profile to instruct the targeted collections process how to collect bill of material and routing data. Valid values are: - Yes: Collect bill of material and routing data - No: Collect bill of material data but do not collect routing data This profile option is overridden by profile option INV: Capable To Promise is ATP/CTP based on Planning Output. |
| MSC: Collection Window for Trading Partner Changes (Days) | Integer >= 0 | Null | Used by Oracle Advanced Supply Chain Planning collections. Specifies the number of days backwards that changes in customer names, customer sites, vendors, and vendor sites are collected. If null, then all changes are collected. Used when collections for the trading partners entity is run in complete mode. If you update or delete region ID in a record of tables wsh_regions, wsh_region_locations, or wsh_zone-regions, perform this process: - Set this profile option to null or 0 - Run collections - Reset this profile option to your usual non-zero value |
| MSC: Compute IB Aggregation during Collection | Yes/No/NULL | Yes/NULL | Use this profile option to instruct the collections process whether to collect over the install base under contracts information (run concurrent process Compute Aggre Installbase under Contract). Valid values are:
You can run the concurrent process before the collections run to reduce the collections run processing time. |
| MSC: Compute Project Exception | Yes/No | Yes | This profile option determines whether to generate project specific exceptions when running a project based plan. - Yes: Enable the generation of project specific exceptions. - No: Disable the generation of project specific exceptions. The default value is Yes. |
| MSC: Configuration | Not applicable | Not applicable | Used by Oracle Collaborative Planning. |
| MSC: Consume Forecast Inside Demand Time Fence | Yes/No | No | When set to No, demand time fence control is implemented prior to forecast consumption. Forecast entries in the demand time fence are dropped as demand statements and not used for consumption. When set to Yes, forecast consumption occurs prior to enforcing demand time fence control. The forecast entries within the demand time fence are used for consumption but not as demand. After consumption, demand quantity for all the forecast entries within the demand time fence is zero. If you are using forecast spreading: - For a periodic forecast entry that falls in weekly planning buckets within the demand time fence, the forecast spreading process spreads the entries into daily entries. - If the daily entry is within the demand time fence, the process ignores the value that you set and uses the value Yes in processing. - If the daily entry is outside the demand time fence, the process ignores this profile option and consumes against the entry. |
| MSC: Consume forecast with No demand class | Within Each Bucket, After Consuming Demand Class Specific Forecast | Within Each Bucket | This profile option instructs the forecast consumption process in about the order it should use to consume forecast entries when some of them have a demand class and others do not have a demand class. If you select:
|
| MSC: Cost of Using a BOM/ Routing Flexfield Attribute | - | - | Not used. |
| MSC: Cost Type | Frozen, Average, Any user-defined cost type | Null | Use this profile option on the source instance (execution system) to specify the cost type that collections should use when collecting the item costs. You should perform a cost rollup for the specified cost type before collecting data. If this profile option is null, collections uses the: - Frozen cost type for standard costed organizations and - Average cost type specified in organization setup for average costed organizations |
| MSC: CP Debug Level | Debug - Off, Debug - On, or Debug - High | Debug - High | Controls the level of detail in the concurrent program log messages for Oracle Collaborative Planning. Off: No debug messages generated On: Short debug messages generated High: Detailed debug messages generated. |
| MSC: Create resource requirements for all operations | Yes/No | Yes | If an operation has no resources with Schedule = Yes, when this profile option is set to:
|
| MSC: Currency Conversion Type | A currency conversion type | Corporate | Use this profile option on the destination 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 data with the new currency conversion type. |
| MSC: Daily Allocation to Maintain Safety Stock Level | Yes/No | Yes | Not used. |
| MSC: Day UOM | Text | Null | Supports the unit of measure conversion required for Oracle Advanced Supply Chain Planning resource batching calculations. Batching Window is considered in days, but users can specify the batching window in a unit of measure other than days. The profile option establishes a standard for the Day unit of measure. Users must specify a unit of measure that represents the value Day using this profile option. Users must also set up a unit of measure conversion between the unit of measure used for resources and the Day unit of measure specified here. |
| MSC: Days of Resource Availability before sysdate | Integer > = 0 | 1 | Use this to specify the start date for resource availability calculations. It is the number of days before the plan run date. So, value of 3 means -3 days from today's date. To set the end date for resource availability calculations, use profile option MRP:Cutoff Date Offset Months. |
| MSC: Default Project for Supplies Pegged to Excess | Project code | Null | Use this profile to manage planned supplies pegged to excess inventory when planning in a Project Manufacturing environment. Oracle Advanced Supply Chain Planning allows you to specify a project as a default project for all supplies pegged to excess. This may be setup at the Site, Application, Responsibility, or User Levels. The project must be assigned to all organizations that will be planned at the defined level. |
| MSC: Default Time Stamp for Make Planned Order Release | 00:00:00 and 23:59:59 | 00:00:00 | Use this profile option to specify the timestamp of an Oracle Work in Process and Oracle Shop Floor Manufacturing job recommended for release or reschedule by an unconstrained plan. Valid values are: - 00:00:00: The planned order timestamps are set to 00:00:00. - 23:59:00: The planned order timestamps are set to 23:59:00. This does not apply to constrained and optimized plans. |
| MSC: Default Workbench Height | Specify the default workbench height. Can be defined at the site level. | ||
| MSC: Default Workbench Width | Specify the default workbench width. Can be defined at the site level. | ||
| MSC: Degree of Parallelism for Index Creation | Integer >= 0 | 0 | Controls the use of parallel workers in data collections. Specifies how many parallel workers to use when creating indexes. |
| MSC: Demand Priority Flexfield Attribute | Integer >= 0 | Null | Stores the value of the attribute column that controls the demand priority. See Flexfield Attributes for more information. |
| MSC: Demand Satisfied Percent Threshold for Pegging | Decimal percent | 100.0 | Set this profile option to instruct the planning engine to stop pegging supplies to a demand which is over satisfaction percentage. Oracle recommends setting the value greater than 99.9. Even if you set this profile option below 100.0, the planning engine still satisfies 100% of the demand. |
| MSC: Display Order Rescheduling Supplies | Yes/No | No | This is a profile option is for use by Oracle. When set to Yes, Planner Workbench displays Order Rescheduling Supply and Order Rescheduling Demand inserted by available to promise when it unschedules a sales order for a configured item. |
| MSC: Display Warning Message When Rescheduling Recommendation Not Suggested by the Plan | Yes/No | Yes | This profile option specifies whether or not the Planner Workbench should display a warning message when you release rescheduled orders that the planning engine has not recommended. The values are: - Yes: Use this value if you want the Planner Workbench to prompt you for confirmation when you release rescheduled orders that the planning engine does not recommend. - No: Use this value if you do not want the Planner Workbench to display the message prompting to prompt you for confirmation when you release the rescheduled orders that the planning engine does not recommend. |
| MSC: Distribution Planning Ship Date | Ship full trips early or ship latest (Target), Ship full trips early or ship latest (SS), Latest possible ship date (Target), Latest possible ship date (SS) | Latest possible ship date (SS) | Use this profile option to schedule a trip for departure based on the earliest and latest possible ship dates of the trip. The values are: - Ship full trips early or ship latest (Target): Utilized trips ship on the earliest possible ship date or in time to prevent inventory levels from dropping below target. - Ship full trips early or ship latest (SS): Utilized trips ship on the earliest possible ship date or in time to prevent inventory levels from dropping below safety stock. - Latest possible ship date (Target): Trips ship just in time to prevent inventory levels from dropping below target. - Latest possible ship date (SS): Trips ship just in time to prevent inventory levels from dropping below safety stock. |
| MSC: DPP allocates to existing ISO's before other demands with the same priority | Yes/No | Yes | Use this profile option to specify how you want the DRP allocation process to allocate to sales orders that: - Are in the same allocation bucket - Have the same demand priority Valid values are: - Yes: It allocates supply to internal sales orders first, then allocates supply to external sales orders. - No: It allocates supply to all sales orders regardless of whether they are internal or external. |
| MSC: DPP Discrete Job Cutoff Window (Days) | Integer >=0 | Null | Use this profile option to control the number of days from plan start date that discrete jobs are considered. Valid values are: - Null: All discrete jobs are considered by the distribution plan. - 0: No discrete jobs are considered by the distribution plan. - Integer >=0: All discrete jobs with completion dates from plan launch date + {integer value} are considered by the distribution plan. New planned orders for discrete jobs can be created both inside and outside the job cutoff window. |
| MSC: DPP Multitasking Group ID's per Process | Integer | 1 | Use this profile option to specify how many group IDs an unconstrained demand and supply netting and allocation child process should process. In this phase, a child process loads data based on internal group IDs and will load all the org-items belonging to those group ID's. This option specifies the length of the list of group ID's. This profile option does not control the Load Consolidation processes. This profile option does not apply with operating system Microsoft Windows. |
| MSC: DPP Multitasking Max Concurrent Processes | Integer | 10 | Use this profile option to specify the maximum number of DPP processes that are allowed to run in parallel. For example, if your machine has 4 CPU's, you might choose to run a maximum of one concurrent process on each CPU; in this case, set the value to 4. This profile option does not apply with operating system Microsoft Windows. |
| MSC: Enable Advanced Constraints | Yes/No | No | Use this profile option to control the values that display for plan option Constraints Mode (on the Constraints tab). Valid values for the profile option are: - Yes: All values for plan option Constraints Mode display - No: All values for plan option Constraints Mode display except Constrained (Without Detailed Scheduling) and Constrained (With Detailed Scheduling) |
| MSC: Enable Allocated ATP | Yes/No | No | Use this profile options to indicate whether allocated order promising is used. Users can update this profile at the site level. |
| MSC: Enable ATP for Phantom Components | Yes/No | No | If you set to Yes, Oracle Global Order Promising treats phantom items like standard items and net their supply and demand. If you set to No, Oracle Global Order Promising explodes phantom items to their components and performs availability check for the components only. This is a site level profile option. |
| MSC: Enable ATP Summary Mode | Yes/No | No | Enables the summarization of supply / demand data for performance improvement. This is a site level profile. Valid values are: - Yes: Enable ATP Summary Mode - No: Disable ATP Summary Mode. |
| MSC: Enable ATP Workflow | Yes/No | No | Controls the generation of workflow notifications to send to the planner. This is a site level profile. Valid values are: Yes: Generate ATP Workflow Notifications No: Do not generate ATP Workflow Notifications |
| MSC: Enable DPP Multitasking orders | Yes, No | No | Use this profile option to specify whether the planning engine should use high volume distribution planning. You can set at the user and site levels. Valid values are: - Yes: All DPP plans run by this user or at this site are run in high volume mode. This value does not apply with operating system Microsoft Windows. - No: DPP plans run by this user or at this site are not run in high volume mode |
| MSC: Enable Enhanced Sourcing | Yes/No | Yes | Enables enhanced sourcing logic that considers historical allocations and allows the splitting of planned orders to achieve target sourcing percentages. Rank 2 buy sources are considered if supplier capacity is exhausted for rank 1 sources. This profile option duplicates the functionality of the decision rule Use Alternate Sources parameter for buy items but not for transfers from other organizations. When the decision rules are enabled, the planning engine does not consider this profile option. |
| MSC: Enable Group Based Netting | Yes/No | Yes | Use this profile option to control whether the planning engine uses group based netting features. A value of Yes provides the most recent netting logic. Oracle recommends that you set the value to Yes and use the latest netting features. This profile option is for backward compatibility. |
| MSC: ENFORCE CRITERIA REQUIREMENT BEFORE EXECUTING QUERY | Yes/No | Yes | Use this profile option to specify if a query requestor needs to specify criteria before executing a query: - Yes: They do. This ensures that the query performs more efficiently. |
| MSC: Enforce Hard Links | Yes/No | Yes | This profile option specifies whether time offsets are hard constraints or soft constraints. If Yes, the planning engine can violate resource and material capacities to satisfy minimum and maximum time offsets. If capacity is exceeded, exception messages start the cause as "Hard Link Constraint". If No, the planning engine cannot violate resource and material capacities to satisfy the minimum and maximum time offsets. In this case, the planning engine can violate hard links and generate a "Hard Link Violation" exception message. |
| MSC: Enhanced Project Netting | Yes/No | No | If the planning engine creates a planned order that pegs to multiple projects or tasks, the planning engine splits the planned order. Valid values are: - Yes: If there is an excess, the planning engine includes its quantity in the planned order of one of the projects. - No: If there is an excess, the planning engine creates a separate planned order for it |
| MSC: Enable Enhanced Sourcing | -- | -- | Not used. |
| MSC: Excess and Safety Stock by Demand Class | Yes/No | No | This profile option controls the allocation of supply or demand that pegs to excess or safety stock in the case of allocated ATP using the demand-priority based method. The valid values are: - Yes: If such supply or demand has a demand class, and if the demand class exists on the allocation rule, allocate the supply or demand to the demand class. However, if the supply or demand does not have a demand class or if the demand class does not exist on the allocation rule, allocate the supply or demand to OTHER. - No: Allocate such supply or demand to OTHER. |
| MSC: Explode in WIP when Details are not released | Yes.No/NULL | Yes/NULL | Use this profile option to instruct the planning engine order whether to keep manually added operations and resources on work orders that it reschedules. Valid values are:
The profile option applies to unconstrained plans. |
| MSC: Fast Refresh of Region Site Map | Yes/No/NULL | No/NULL | Use this profile option to instruct concurrent process Refresh Collections Snapshot how to perform the supplier site to region mapping when there are changes to shipping regions. Valid values are:
|
| MSC: File Flush Limit | Integer > 0 | 20000 | Use this profile option to control Planner concurrent process write to database, if the number of records exceed this value, the process uses SQL*Loader or array insert. |
| MSC: Firm Internal Requisition Time Fence | Yes/No | Yes | This profile option creates a natural time fence for an item if a firm internal requisition exists. The natural time fence is the date of the latest firm internal requisition. The values are: - Yes: Use this to create a natural time fence for a firm internal requisition. - No: Use this if you do not want to create a natural time fence for a firm internal requisition. |
| MSC: Firm Intransit and PO in Receiving Supplies | Yes/No | Yes | This profile option applies to unconstrained plans only and instructs the planning engine whether it should consider intransit and purchase order in receiving supplies as firm or it should issue reschedule recommendations for them. If you set the profile option to Yes, the planning engine considers intransit and purchase order in receiving supplies as firm. If you set it to No, the planning engine generates reschedule recommendations for these types of supplies. Use this setting if you expedite shipments that are en route from a supplier to a receiving organization or if you want to expedite the movement of materials in receiving to the shop floor. For example, you might offload a package from a ship at a port and then fly the package to the receiving organization. These recommendations are informational only and cannot be released from the Planner Workbench. This is a user level profile option. |
| MSC: Forecast Priority Flexfield Attribute | Integer >= 0 | Null | Stores the value of the attribute column that will control the forecast priority. See Flexfield Attributes for more information. |
| MSC: Forecast Spreading Calendar | Organization Manufacturing Calendar, Organization Shipping Calendar | Organization Manufacturing Calendar | Use this profile option to specify the calendar that the forecast spreading process should use. Valid values are: - Organization Manufacturing Calendar: Base forecast spreading on the organization manufacturing calendar. - Organization Shipping Calendar: Base forecast spreading on this hierarchy of organization shipping calendars - carrier/organization calendar, organization shipping calendar. If neither of these calendars exists, forecast spreading uses the organization manufacturing calendar. |
| MSC: Future Days for Currency Conversion | Positive number | 90 | Use this profile option to instruct the collections process how many future days of currency conversion rates to collect, starting from today. |
| MSC: Generate Notifications for Transportation Updates | Yes/No | Yes | Use this profile option to specify whether the process that passes estimated arrival time updates from Oracle Transportation Management should create workflow notifications. Valid values are: Yes: Create workflow notifications No: Do not create workflow notifications |
| MSC: High Volume Items | Yes/No | No | This snapshot profile controls plan weed out logic. Since snapshot on 64-bit machines could run out of memory if the number of planned items is high. Valid values: - Yes: Snapshot bypasses the weed out logic and directly inserts items from operational data store to planning data store. If item planning type is All Planned Items, the snapshot inserts all items into the planing data store. If the items have demand schedules only, snapshot only inserts the items in demands schedules into the planning data store. - No: The snapshot uses weed out logic. |
| MSC: History Days for Currency Conversion | Positive number | 180 | Use this profile option to instruct the collections process how many past days of currency conversion rates to collect, starting from today. |
| MSC: Horizontal Plan Demand Bucketing Preference | Plan Recommended Date/Demand Due Date | Demand Due Date | This profile controls how Oracle Global Order Promising treats demand due date when calculating availability. Valid values are: - Plan Recommended Date, Oracle Global Order Promising treats the demand due as the date recommended by Oracle Advanced Supply Chain Planning. - Demand Due Date, Oracle Global Order Promising treats the demand due as the Schedule Ship Date. |
| MSC: Horizontal Plan Extension Program | PackageName.ProdecureName format | <blank> | Use this profile option when you are using a custom row in the Planner Workbench Horizontal Plan. Specify the name of the PL/SQL program unit with no parameters that specifies that information to display in the custom row. |
| MSC: Hour UOM | Text | HR | Specifies unit of measure. Can be defined at the site level. |
| MSC: Ignore CMRO and EAM Work Orders for ASCP | Yes/No | Yes | Specifies if ASCP should ignore cMRO and EAM work orders. If the value is set to No then asset intensive planning features to account for EAM and cMRO work orders are enabled. If set to Yes, then these features are disabled. |
| MSC: Include Firm Planned Orders In Firm Allocation Window | Yes/No | No | For priority pegging, controls the point at which demands peg to firm planned orders. Valid values are: - Yes: Firm planned orders are included in the firm allocation window (along with scheduled receipts). They are eligible for pegging during the first phase of priority pegging. - No: Firm planned orders are not included in the firm allocation window (along with scheduled receipts). They are eligible for pegging during the second phase priority pegging. |
| MSC: Include Safety Stocks in Priority based Pegging | Yes/No | No | Controls whether to exclude non-transient safety stock levels from the priority-based pegging logic. Valid values are:
|
| MSC: Inflate WIP Resource Requirements | Yes/No | No | Determines whether or not the planning engine should inflate the Work in Process resource requirements based on resource efficiency and utilization during collections from Oracle Work in Process. The values are: - Yes: Planning engine inflates the resource requirements for the firm, unfirm, and non-standard discrete jobs considering the resource efficiency and utilization. - No: The planning engine does not consider resource efficiency and utilization to inflate the resource requirements for the collected discrete jobs. Note that this profile option is used in conjunction with shop floor scheduling products such as Oracle Manufacturing Scheduling. It is assumed that the discrete jobs are not released from the planning engine. If the jobs are rescheduled and released by the planning engine, the resource requirements are deflated. This could result in data inconsistency as the resource requirements are deflated on release whereas Oracle Manufacturing and Scheduling might have calculated resource requirements based on the inflated values. The planning engine always sends the original resource requirements upon release. If the resource requirements are already inflated in the source from Oracle Manufacturing Scheduling, set this profile option to No to avoid double inflation of the resource requirements. Otherwise, set it to Yes so that the planning engine inflates the resource requirements. |
| MSC: Inventory Rebalancing Surplus Inventory Basis | Target, Safety Stock | Safety Stock | Use this option to specify whether inventory rebalancing considers target or safety stock inventory levels. Valid values are: - Target: Surplus inventory is defined as the quantity of projected available balance greater than target inventory level. Target inventory demands are considered by inventory rebalancing. - Safety Stock: Surplus inventory is defined as the quantity of projected available balance greater than safety stock inventory level. Target inventory level demands are ignored by inventory rebalancing. |
| MSC: Launch Analyze Plan Partition | Yes/No | Yes | Launches the concurrent request Analyze Plan Partition. |
| MSC: Launch Workflow-Enabled Exception Message Notifications | Yes/No | Yes | Determines if Oracle Collaborative Planning sends notification messages when it generates exceptions. |
| MSC: Legacy Collections Using Lot Based Job Details | Yes/No | No | Used with legacy data collections only. Valid values are:
To control the same behavior for collections from an Oracle E-Business Suite instance, Advanced Planning Suite uses Oracle ShopFloor Management (OSFM) profile option WSM: Create Job Level BOM and Routing Copies |
| MSC: Maximum Number of Planned Orders per Demand | Positive number | 10000 | The maximum number of planned orders that the planning engine can create to satisfy one demand. |
| MSC: Maximum Percentage variation in safety stock values | Null or positive number | Null | The safety stock is not allowed to deviate by more than this value between two adjacent time intervals. Null allows any deviation. |
| MSC: Minimize Project Cross Peg within Window | Yes/No | Yes | Used in conjunction with profile option MSC: Use attribute based netting in priority pegging. Valid values are: - Yes: The planning engine tries to minimize cross pegging within the Supply/Demand window. - No: The planning engine does not attend to the amount of cross pegging. |
| MSC: Minimum Percentage variation in safety stock values | Null or positive number | 0 | The safety stock is held constant across time intervals if the deviation is within this percentage. Zero ignores all deviations. |
| MSC: Minimum Supply/Demand Percent for Pegging | Decimal percent | 0.0 | Set this profile option to instruct the planning engine not to peg tiny supplies and large demands. It skips a supply if (Supply size / Demand size) x 100 is less than the value of this profile option. Oracle recommends setting the value at 0.0001. |
| MSC: Minimize Workorder crossovers during reschedules | Yes/No | No | Controls pegging for work orders pegging to minimize crossovers during rescheduling. - Yes: The planning engine does not push the supply forward even if there is some excess. - No: The planning engine can peg work orders to safety stock supplies available. This may sometimes lead to work orders with later old schedule dates to be pegged to higher priority demands and work orders with earlier schedule dates may be pegged to lower priority demands. If the plan planning mode is Constrained (Without Detailed Scheduling), the planning engine only uses this profile option if its value is Yes. |
| MSC: MPS Auto-Firm Planned Orders | Yes/No | Yes | This profile option specifies how the planning engine deals with master production schedule firm planned orders. You can use this profile option to specify whether or not the planning engine should treat all planned orders in the master production schedule as firm: Valid values are: - Yes: All planned orders in the master production schedule are automatically firmed and not rescheduled during a batch replan. - No: Use the same behavior as distribution requirements plans and material requirements plans. When a master production schedule is a demand schedule for another plan, the planning engine treats all planned orders in the demand schedule plan as firm. This is the same as treating planned orders in distribution requirements plans and material requirements plans that are demand schedules for other plans as firm. This profile option applies only to master production schedule plans. You can set it at the site and user levels. |
| MSC: Net Change Temp Dir | Text | Null | Stores the location of image cache used in the Plan Comparison Report. Indicate the location in the following format: <directory>@<subdir> where <directory> This must match the absolute path of the OA_MEDIA environment variable and <subdir> is the name of a subdirectory under the OA_MEDIA directory. The subdirectory must have write permissions for all. |
| MSC: New Forecast Auto Plan | A valid plan name in Oracle Advanced Supply Chain Planning | Null | The plan launched in Oracle Advanced Supply Chain Planning when Oracle Collaborative Planning receives a supplier's forecast. Oracle recommends that this plan be an unconstrained plan. |
| MSC: New Planner Backward Compatibility | Yes/No | No | Use tis profile option to instruct the planning engine which algorithm to use to plan phantom items. Valid values are: - Yes: Use the old algorithm - No: Use the new algorithm See also profile option MRP: New Planner Backward Compatibility. Oracle recommends that you use Yes, even though it is not the default value, unless you have a specific situation that demands the new algorithim. |
| MSC: New Supply Commit Auto Plan | A valid plan name in Oracle Advanced Supply Chain Planning | Null | The plan launched in Oracle Advanced Supply Chain Planning when Oracle Collaborative Planning receives a supplier's supply commits. Oracle recommends that this plan be a constrained plan. |
| MSC: Organization containing generic BOM for forecast explosion | Any collected organization | Null | Used by collections to identify and populate the bill of material validation organization. |
| MSC: Order Type for Consigned VMI | - | - | This indicates the order type that Oracle Collaborative Planning uses when creating a sales order for consigned VMI. This order type should encompass billing and inventory reduction functions without any shipping being performed. |
| MSC: Operator Company Name | - | - | Used by Oracle Collaborative Planning. |
| MSC: OTM URL | Null, <URL> | Null | Use this profile option to specify the URL of the Oracle Transportation Management instance that is providing the updates. This URL is used for drilling down in Oracle Transportation Management for more details about the order that has been rescheduled. |
| MSC: Overwrite all Order Forecast records | Yes/No | No | Indicates whether or not the previous records regarding customer order forecasts need to be maintained. You can set this profile option to replace all previous forecasts with the latest forecast that the customer provides. The valid values are: - Yes: Use this if you want to delete all previous order forecast records for an item, organization, customer, or customer site combination. - No: Use this if you do not want to delete the previous forecasts. |
| MSC: Overwrite all supplier capacity records | Yes/No | No | Indicates whether or not the previous records regarding supplier capacity need to be maintained. You can set this profile option to replace all previous supplier capacity values with the latest supplier capacity to which the supplier commits. The valid values are: - Yes: Use this if you want to delete all previous supplier capacity records for an item, organization, customer, or customer site combination. When the supplier provides a new commit statement for a specific horizon, the planning engine deletes all previous supplier capacity records for the horizon. - No: Use this if you do not want to delete the previous supplier capacity records. |
| MSC: Pass List Price to OM in DRP Release | Yes/No | No | Use this profile option to specify how the distribution planning engine obtains internal sales order line list prices> Valid values are: - Yes: During the creation of an internal sales order line, the Oracle Order Management Application Programming Interface does not call the pricing engine to get the list price of an item. Distribution planning passes the list price based on the item list price. If the list price is null, it passes the pass the standard cost. If the standard cost is null, it passes 0. In all cases, the internal sales order is created in a Booked status. This is the same process used when concurrent process Create Internal Orders creates internal sales orders from manual internal requisitions. No: During the creation of an internal sales order, the Oracle Order Management Application Programming Interface calls the pricing engine to get the list price of an item. If the item is not an any price list, it creates the internal sales order in an Entered status. |
| MSC: Performance target for Inventory Turns | Integer > 0 | 6 | Use this profile option to set the KPI performance target for inventory turns. |
| MSC: Performance target for Margin Percent | Integer > 0 | 20 | Use this profile option to set the KPI performance target for margn. |
| MSC: Performance target for Ontime Delivery Percent | Integer >0 | 100 | Use this profile option to set the KPI performance target for ontime delivery. |
| MSC: Performance target for Resource Utilization Percent | Integer > 0 | 100 | Use this profile option to set the KPI performance target for planned utilization. |
| MSC: Plan co-products | Yes/No | Yes | Indicate whether co-products are planned and whether supplies are created for the co-products. Can be defined at the site level. If the plan planning mode is Constrained (Without Detailed Scheduling), the planning engine only uses this profile option if its value is Yes. |
| MSC: Plan for order at risk calculation | - | - | Indicates a plan that Oracle Collaborative Planning uses to derive the pegging information for each order that you upload. |
| MSC: Plan Name for CMRO | <A plan name> | Null | In asset intensive planning, the plan that the planning engine uses when it sends resource availability information to Oracle Complex Maintenance, Repair, and Overhaul. |
| MSC: Planning Currency | - | - | Not used. |
| MSC: Priority for Substitute Items Flexfield Attribute | Integer >= 0 | Null | This profile option stores the name of the flexfield column that contains the value in the corresponding table. Set this profile option at the site level only See Flexfield Attributes for more information. |
| MSC: Priority of Alternate Resources for an Operation Flexfield Attribute | Integer >= 0 | Null | This profile option stores the name of the flexfield column that contains the value in the corresponding table. See Flexfield Attributes for more information. |
| MSC: Production Plan for Transportation Updates | Null, All Production Plans, <specific plan name> | Null | Use this profile option to indicate the production plans that receive estimated arrival time updates from Oracle Transportation Management. Valid values are: Null: Do not pass updates to any plan All Production Plans: Pass updates to all plans with Production flag selected <specific plan name>: Pass updates only to the plan that is specified |
| MSC: Project Task Collection Window Days | Null, Integer | Null | Controls which projects/tasks are collected after the collection engine deletes all of the previously collected records for the instance. Valid values: - Null: Collects all of the records from the source. - Integer: Collects all of the records from the source from projects whose end date is within the number of days in the past specified in the profile option value. The collections process never collects tasks whose projects are completed. |
| MSC: Provide Warning for Dates Entered on Non-work Days | Yes/No | No | - No: Use this value if you do not want the warning message to be displayed. |
| MSC: PS - Snapshot Base Package | Yes/No | Yes | Specifies whether the Base Package is used for creating a model in Production Scheduling. |
| MSC: PS - Snapshot Beginning Inventory Package | Yes/No | Yes | Specifies whether the Beginning Inventory Package is used for creating a model in Production Scheduling. |
| MSC: PS - Snapshot Calendar Package | Yes/No | Yes | Specifies whether the Calendar Package is used for creating a model in Production Scheduling. |
| MSC: PS - Snapshot Customer Package | Yes/No | Yes | Specifies whether the Customer Package is used for creating a model in Production Scheduling. |
| MSC: PS - Snapshot Distribution Package | Yes/No | Yes | Specifies whether the Distribution Package is used for creating a model in Production Scheduling. |
| MSC: PS - Snapshot Enterprise Forecast Package | Yes/No | Yes | Specifies whether the Enterprise Forecast Package is used for creating a model in Production Scheduling. |
| MSC: PS - Snapshot Inventory Safety Targets Package | Yes/No | Yes | Specifies whether the Inventory Safety Targets Package is used for creating a model in Production Scheduling. |
| MSC: PS - Snapshot Manufacturing Package | Yes/No | Yes | Specifies whether the Manufacturing Package is used for creating a model in Production Scheduling. |
| MSC: PS - Snapshot Purchase Orders Package | Yes/No | Yes | Specifies whether the Purchase Orders Package is used for creating a model in Production Scheduling. |
| MSC: PS - Snapshot Sales Orders Package | Yes/No | Yes | Specifies whether the Sales Orders Package is used for creating a model in Production Scheduling. |
| MSC: PS - Snapshot Supplier Package | Yes/No | Yes | Specifies whether the Supplier Package is used for creating a model in Production Scheduling. |
| MSC: PS - Snapshot Transfer Orders Package | Yes/No | Yes | Specifies whether the Transfer Orders Package is used for creating a model in Production Scheduling. |
| MSC: PS - Snapshot Work Orders Package | Yes/No | Yes | Specifies whether the Work Orders Package is used for creating a model in Production Scheduling. |
| MSC: PS Allow WO Purchased Item Offloading | Yes/No | No | Specifies item offloading control for purchased items. It allows alternate items on work orders consuming purchased items. This profile globally sets the work order allow offload flag to the appropriate value. The Bill of Material tab allows you to then set the Allow Offloading field to override the default as needed for those purchased items that have alternates. |
| MSC: PS Currency Symbol | text | $ | The currency symbol used by PS for measurement of costs and calculation of key performance indicators. |
| MSC: PS Resource Constraint Horizon | Any numeric value >= 0 | 30 (days) | Sets a time window from the start of the scheduling horizon beyond which resource capacity will be relaxed. Value specified in days. |
| MSC: PS Run Application Script | text | runPS.bat | Specifies the name of the batch script that starts Production Scheduling. |
| MSC: PS Run Connector Script | text | runPSConnector.bat | Specifies the batch script that starts the Production Scheduling Connector. |
| MSC: PS/SNO Alignment Date | Text | 2000-01-01 00:00:00 | The alignment date is the date and time that fixes the start of time periods in a model. The alignment date fixes all time period starts, including the Fiscal Month 445 period type, where it sets the start of 13-week 445 patterns. The alignment date format is yyyy-MM-dd HH:mm:ss. |
| MSC: PS/SNO API Version | Text | 3.2 | The Supply Chain Planning XML format being used to generate SNO and PS models. |
| MSC: PS/SNO Client Install Path | Text | c:\ | The path where the Supply Chain Planning Production Scheduling (PS) or Strategic Network Optimization (SNO) is installed. PS and SNO are installed automatically the first time they are accessed by the E-Business Suite. |
| MSC: PS/SNO Compress Xml Package Files | Yes/No | Yes | Specifies whether data is transferred between the ASCP planning server, PS and/or SNO using a compressed file format also known as .gzip. The compressed XML format reduces the size of data files transferred, thereby minimizing the time involved in the creation of models. |
| MSC: PS/SNO Data Store Path | text | Null | The path to where the refreshed snapshot data from the E-Business Suite, or the published plans from PS or SNO, are temporarily stored before being transferred to the ASCP planning server. |
| MSC: PS/SNO Past Due Supplies Window | Integer | 7 | This value specifies the amount of time in the past to look for supply. Not applicable after 12.1.3.7 and removed from the ldt file. However, if this profile currently exists in your database, you will continue to see it but it can ignored. |
| MSC: Purchase Order Dock Date Calculation Preference | Need By Date and Promise Date | Promise Date | This profile option specifies the purchase order line date that the planning engine uses as the material arrival (suggested dock) date: - Promise Date: If the Promise Date is not available (an unacknowledged purchase order), the planning engine uses Need by Date. - Need By Date This is a site level profile option. Use the same setting of this profile option for running both collections and plans. It does not affect supplier capacity, see profile option MSC: Supplier Capacity Consumption by Purchase Orders. |
| MSC: Purge Staging and Entity Key Translation Tables | Yes/No | No | Controls both truncation of the staging table during data collection process and deletion of the link ID tables. When running data collections for multiple instances simultaneously, set to No to avoid data loss. Set to Yes to conserve disk space when running data collections for single instances, or as separate processes for multiple instances. |
| MSC: Refresh Snapshots Pending Timeout | Integer in minutes | 10 | Sets the time that the Planning Data Pull concurrent process waits for concurrent process Refresh Snapshots on the source before it times out. This time out only applies if concurrent process Refresh Snapshots is at status Pending/Inactive which occurs if another version of concurrent process Refresh Snapshots is running. |
| MSC: Release PO Firm Flag to Purchasing | Yes/No | Yes | Use this profile option to indicate whether the release process should pass information about firm rescheduled purchase orders to the Purchasing source instance. Valid values are: - Yes: Pass the information - No: Do not pass the information See also profile option MSC: Remove Promise Date for Rescheduled Purchase Orders. |
| MSC: Release WIP Dtls if Order Date different then BOM Revision Date | Yes/No | Yes | If the value is Yes, then planning engine releases the WIP details even if the Suggested Start Date is different than BOM Revision Date. If the value is No, the planning engine does not release the WIP details if the new WIP Start Date is different than BOM Revision Date. Oracle Work in Process uses the details effective on the job start date. |
| MSC: Released Only By User | Yes/No | No | Use this profile option to specify whether to restrict implementation of planned orders and recommendations to the current user. Valid values are: - Yes: Only implement planned orders and recommendations that this user marked - No: Implement planned orders and recommendations that any user marked |
| MSC: Remove Promise Date for Rescheduled Purchase Orders | Yes/No | No | Use this profile option to indicate whether the release process should remove the Promise Date on purchase orders on the Purchasing source instance when you firm and reschedule them in ASCP. Valid values are: - Yes: Remove Promise Date - No: Do not remove Promise Date Set profile option MSC: Release PO Firm Flag to Purchasing before you set this one. |
| MSC: Resource Group for a Line Flexfield Attribute | Integer >= 0 | Null | This profile option stores the name of the flexfield column that contains the value in the corresponding table. See Flexfield Attributes for more information. |
| MSC: Resource Type for an Operation Flexfield Attribute | - | - | Not used. |
| MSC: Respect Minimum Remaining Shelf Life Days | Yes/No | No | Use this profile option to instruct the planning engine how to plan supplies using minimum remaining shelf life days. Valid values are: - Yes: Plan supplies taking into account the minimum remaining shelf life days. - No: Plan supplies without enforcing minimum remaining shelf life days The planning engine does not calculate safety stock if you set this profile to Yes and you set item attributes for lot expiration. |
| MSC: Safety stock change interval (Days) | Integer > 0 | 1 | Use this profile option to specify the time interval used for smoothing within the time interval functionality. |
| MSC: Safety Stock Project | Text | Null | Specifies the default project charged for all safety stock demands. Oracle Advanced Supply Chain Planning assigns the project specified for all safety stock demands which originate from non-MRP planned safety stock. When safety stock requirements are specified in Oracle Inventory for specific projects, the profile option value is not honored. The list of values for this profile option is restricted to projects specified in Oracle Projects. This profile option is enabled at project/seiban level, not at the task level. |
| MSC: Sales Orders Offset Days | Integer >= 0 | Null | Completed sales orders are collected within the offset duration. For example, if Sales Orders Offset Days is set to 90, all the sales orders completed in the past 90 days are also collected. Can be defined at the site level. A Null value means all closed sales orders are collected. Does not apply to complex maintenance repair and overhaul where the material scheduled for a visit or task is collected as a sales order in Oracle Advanced Supply Chain Planning. |
| MSC: SCEM Engine Launch Events | None, Load, Publish, or All | All | Launch the Supply Chain Event Manager when data is loaded, published, or both. |
| MSC: Self Service Loads Delimiter | -/, | - | Delimiter used to parse the data files loaded using self service loads, for example, the loading of spreadsheet forecast data to Oracle Demand Planning. |
| MSC: Scope of Analyze Plan Partition | All Partitions, Plan Partition Only | Plan Partition Only | This profile option specifies the partitions that concurrent process Analyze Plan Partitions should analyze. |
| MSC: Share Plan Partitions | - | - | The profile option is a work-around for test/demo scenarios where you expect the creation of many plans by different testers and demonstrators. This profile option is not meant for production use by customers. When enabled the number of plan partitions parameter to the concurrent program mentioned becomes irrelevant; only one partition is created for a plan (you can enter 1). This profile option should only be changed by the system administrator. If the MSC: Share Plan Partitions profile is turned on, you must run the Create APS Partitions program afterwards so that it can create the partition that every plan shares. |
| MSC: Shelf Life Override of Order Modifiers for Transfer Orders | Off/On | Off | Use this profile option to instruct the planning engine whether or not to maximize the number of demands satisfied with respect to minimum remaining shelf life. Valid values are: - Off: Respect order modifiers for transfer orders. Schedule a supply pegged to multiple demands based on the most constraining demand with respect to minimum remaining shelf life. - On: Ignore order modifiers for transfer orders as needed both to maximize the number of demands satisfied with respect minimum remaining shelf life and to maximize the usage of supplies in advance of their expiry dates. |
| MSC: Simultaneous Resource Sequence Flexfield Attribute | Integer >= 0 | Null | This profile option stores the name of the flexfield column that contains the value in the corresponding table. This setup is only performed during application install. |
| MSC: Smoothing method to calculate Safety stock within Change interval | Minimum, Average, or Maximum | Average | Specifies the mathematical construct used to calculate safety stock for a time interval using values within the time interval. |
| MSC: SNO - Snapshot Base Package | Yes/No | Yes | Specifies whether the Base Package is used for creating a model in Strategic Network Optimization. |
| MSC: SNO - Snapshot Beginning Inventory Package | Yes/No | Yes | Specifies whether the Beginning Inventory Package is used for creating a model in Strategic Network Optimization. |
| MSC: SNO - Snapshot Calendar Package | Yes/No | Yes | Specifies whether the Calendar Package is used for creating a model in Strategic Network Optimization. |
| MSC: SNO - Snapshot Customer Package | Yes/No | Yes | Specifies whether the Customer Package is used for creating a model in Strategic Network Optimization. |
| MSC: SNO - Snapshot Demand Package | Yes/No | Yes | Specifies whether the Demand Package is used for creating a model in Strategic Network Optimization. |
| MSC: SNO - Snapshot Distribution Package | Yes/No | Yes | Specifies whether the Distribution Package is used for creating a model in Strategic Network Optimization. |
| MSC: SNO - Snapshot Enterprise Forecast Package | Yes/No | Yes | Specifies whether the Enterprise Forecast Package is used for creating a model in Strategic Network Optimization. |
| MSC: SNO - Snapshot Inventory Safety Targets Package | Yes/No | Yes | Specifies whether the Inventory Safety Targets Package is used for creating a model in Strategic Network Optimization. |
| MSC: SNO - Snapshot Manufacturing Package | Yes/No | Yes | Specifies whether the Manufacturing Package is used for creating a model in Strategic Network Optimization. |
| MSC: SNO - Snapshot Purchase Orders Package | Yes/No | Yes | Specifies whether the Purchase Orders Package is used for creating a model in Strategic Network Optimization. |
| MSC: SNO - Snapshot Sales Order Package | Yes/No | Yes | Specifies whether the Sales Order Package is used for creating a model in Strategic Network Optimization. |
| MSC: SNO - Snapshot Supplier Package | Yes/No | Yes | Specifies whether the Supplier Package is used for creating a model in Strategic Network Optimization. |
| MSC: SNO - Snapshot Transfer Orders Package | Yes/No | Yes | Specifies whether the Transfer Orders Package is used for creating a model in Strategic Network Optimization. |
| MSC: SNO - Snapshot Work Orders Package | Yes/No | Yes | Specifies whether the Work Orders Package is used for creating a model in Strategic Network Optimization. |
| MSC: SNO Connector Precision | Numeric | 8 | Specifies the precision value of the SNO connector. |
| MSC: SNO Currency Precision | Numeric | 2 | Specifies the number of decimal places used to display currency information in the SNO Currency Table. For the most accurate calculations, a precision of 9 is recommended. |
| MSC: SNO Decimal Precision | Numeric | 2 | Specifies the number of decimal places shown for data in properties windows. Within SNO, the number of decimal places is called the display precision. Changing the display precision does not change the actual data values saved in a model. The display precision can affect results when you match data. For example, if the display precision is 2, a Machine node Utilization field with a value of 133.333333 displays 133.33. If you try to match Machine nodes with a Utilization field value of 133.33, the Machine node in this example is not matched because its actual value is 133.333333. |
| MSC: SNO Optimization Type | text | Cost | Specifies the optimization type to be used when solving the model. Valid values are: - Cost: The item list price is not considered. - Profit: The item list price is considered. |
| MSC: SNO Run Application Script | text | runSNO.bat | Specifies the name of the batch script that starts SNO. |
| MSC: SNO Run Connector Script | text | runSNOConnector.bat | Specifies the batch script that starts the SNO Connector. |
| MSC: SNO Transportation Capacity By | text | Weight | Specify the unit of measure that determines transportation capacity. |
| MSC: Source Setup Required | - | See Automatic Calculations. | Internal profile used by the software during collections configuration. Do not manually update. |
| MSC: Sourcing History Start Date Offset (in months) | Integer >= 0 | Null | Offsets the starting date of sourcing history calculations and is used in conjunction 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). System performance can be degraded when there is a high value for this profile option and a high volume of source transaction data. Valid values are: - Null: Collect all of it - Positive integer: Collect that many number of months of it Set Planning Data Pull parameter Recalculate Sourcing History to Yes. |
| MSC: Sourcing Rule Category Set | Text | Null | Determines the category set used in Oracle Advanced Supply Chain Planning in the assignment set form. If this not set, the user cannot assign sourcing rules and bills of distribution at the Category- Instance-Organization and Category-Instance level. |
| MSC: Sourcing Variance Tolerance | Number between 0 and 1 | 0.05 (5%) | Used when Enforce Sourcing Constraints is enabled for a plan. This percentage value establishes a threshold for triggering exception messages if sourcing allocations are violated. Exceptions are generated if the difference between the user-specified sourcing allocation percentages and the plan-derived allocation percentages is greater than the Sourcing Variance Tolerance. The profile option is entered as a number and converted to a percentage. If the user enters 0.5 it becomes 50%. |
| MSC: Split Planned Order to perform safety stock pegging | No, Yes but do not violate order modifier, or Yes | No | Use this profile option to instruct the planning engine how to split a planned order that pegs to customer demand when pulling it in to meet transient safety stock. Valid values are: - No: Do not split planned orders - Yes but do not violate order modifier: Split planned orders only if the split does not violate an order modifier - Yes: Split planned orders If the plan planning mode is Constrained (Without Detailed Scheduling), the planning engine only uses this profile option if its value is No. |
| MSC: Split Planned Orders for Scheduling Flexibility | Yes/No | Yes | For constrained plan with decision rules and optimized plans, it determines whether the planning engine consolidates planned orders that were split during optimization processing prior to scheduling them. For unconstrained plans, set it to No. - Yes: Do not consolidate planned orders prior to scheduling. The planning engine splits them into multiple planned orders whose quantities generally satisfy one planning time bucket's worth of capacity against the resources or suppliers used in the planned order. During scheduling, the planning engine has more flexibility to place smaller quantities into available time slots. You cannot specify the size of the durations and the planning engine does not guarantee that each planned order in the final plan output spans exactly one planning bucket. - No: Consolidate orders when possible prior to scheduling. Use this value if you tend to have long production runs per routing that cross multiple planning buckets. The planning engine creates a single planned order. If the plan planning mode is Constrained (Without Detailed Scheduling), the planning engine ignores this profile option and does not consolidate planed orders prior to scheduling. |
| MSC: Supplier Capacity Accumulation (multiplier) | Numeric value > 0; may be larger than 1 | 1 | This profile option is a multiplier to ASL lead-time. The planning engine uses it to derive the date when capacity accumulation begins for a supplier. If profile option MSC: Purchase Order Dock Date Calculation Preference is Promise Date, Oracle suggests that you set this profile option to 0 so that suppliers accumulates capacity within their lead-time. This is a site level profile option. |
| MSC: Supplier Capacity Consumption by Purchase Orders | Yes, No Consumption, Unacknowledged Purchase Orders Only, Purchase Orders outside Lead Time Only | No Consumption | This profile option specifies which purchase orders the planning engine uses to consume supplier capacity. Valid values are: - Yes: All purchase orders consume supplier capacity - No Consumption: No purchase orders consume supplier capacity - Unacknowledged Purchase Orders Only: Only purchase orders without a promise date consume supplier capacity - Purchase Orders outside Lead Time Only: Only purchase orders with dock date outside of lead time consume supplier capacity |
| MSC: Suppress Exception for Selection of Alternates | Yes/No | No | Controls whether the planning engine generates exceptions related to alternate bills of material and routings. If the profile option is No, it does not generate those exceptions. |
| MSC: Temp Index Extent Size (Bytes) | - | - | Not used |
| MSC: Temp Table Extent Size (Bytes) | - | - | Not used |
| MSC: Transportation Domain | Null, <domain name> | Null | Use this profile option to specify the domain name that identifies the source instance integrated with Oracle Transportation Management. Enter the same value that is in profile option OTM: Domain Name. |
| MSC: Unit of Measure | - | - | Not used. |
| MSC: Update Requested Completion Date when Releasing Reschedules | n/a | n/a | n/a |
| MSC: Use attribute based netting | Yes/No | No | Use this profile option to control netting in a project manufacturing environment. Valid values: - Yes: Planning nets at the reservation level. It respects pegging level and creates planned orders based on hard pegging level. It does not respect order modifiers if the reservation level and hard pegging level are not the same. With this approach, you can enable priority pegging can be enabled. - No: The planning engine uses customary netting in a project manufacturing environment. |
| MSC: Use Base Model during Forecast Consumption | Yes/No | No | Use this profile option to instruct the planning engine whether to consume configure to order forecasts with attention to the top-level models. Valid values are: - Yes: Consume configure to order forecasts for the same top-level model on the sales order line - No: Consume configure to order forecasts without attention to their top-level models Coordinate how you set this profile option with how you set profile option MSD: Publish CTO Forecast Percentages by Top-level Model. |
| MSC: Use FIFO Pegging | Yes/No | No | If this profile option is Yes, the planning engine uses FIFO pegging. For all demands and supplies, it proceeds item by item and pegs supplies to demands on a daily basis. Daily supplies and demands are not sorted. When supplies or demands on a given date are used up, it picks from supplies or demands on the next date. The unpegged supplies are pegged to excess. If the plan option Peg Supplies by Demand Priority is selected, it performs a priority based allocation of firm supplies prior to performing the FIFO pegging of the non-firm supplies. If profile option MSC: Use FIFO pegging is No, it uses either standard pegging or priority pegging logic. See profile options MSO: Demand Window Size, MSO: Supply Window Size, MSO: Firm Supply Allocation Window (Backward days), and MSO: Firm Supply Allocation Window (Forward days). This is a user level profile option. If the plan planning mode is Constrained (Without Detailed Scheduling), the planning engine does not use this profile option. The planning engine performs safety stock smoothing only if this profile option is No. |
| MSC: Use Hash Key | - | - | This profile option is for use by Oracle |
| MSC: Use Optimization Supply Due Dates for Pegging | Yes/No | No | Use this profile option to instruct the planning engine on the date fields to use when pegging. - Yes: Pegging uses the optimization recommended supply date for planned orders and scheduled receipts. In FIFO pegging, the supply sequence is based on the optimization supply date. In priority pegging, the division of the supply window is based on optimization supply date. This setting has no effect on form supplies because optimization does not move the schedule date. For independent demands, the optimization demand date is the schedule date. For dependent demands, the planning engine offsets optimization demand date from the optimization supply date of its assembly's supply In co-product/by product environments, the planned order/scheduled receipt and its related by-product planned order/scheduled receipt have the correct optimization supply date for pegging. It reduces pegging discrepancies in which the main supply is pulled out and the by product supply remains at the original schedule date. - No: Pegging behaves in the standard way. If the plan planning mode is Constrained (Without Detailed Scheduling), the planning engine only uses this profile option if its value is Yes. |
| MSC: Use Shipping Receiving Calendars | Yes/No | Yes | Controls the use of shipping, receiving, and carrier calendars. Values are: - Yes: Use shipping, receiving, or, carrier calendar for planning/scheduling - No: Use the organization manufacturing calendar while generating a plan. This profile option specifies: - At the site level, whether the collection engine collects the calendars. If the calendars are collected, the planning engine uses them. - At the user level, whether Planner Workbench displays the collected calendars. Even if the planning engine used the calendars, if the user level value is No, the Planner Workbench displays calendars as 24x7. This should be avoided. If the plan planning mode is Constrained (Without Detailed Scheduling), the planning engine only uses this profile option if its value is Yes. |
| MSC: Vertical view default query | Not applicable | Not applicable | Used by Oracle Collaborative Planning to display default results in the vertical view. |
| MSC: VMI Default Query | Not applicable | Not applicable | Used by Oracle Collaborative Planning to display default results on the VMI page. |
| MSC: Wait Time to Obtain Lock on Table/Partition for Snapshot Delete Worker (in sec) | Number >=0 | 60 seconds | Time (in seconds) the Snapshot Delete Worker waits to obtain a lock on a table/partition before aborting. Releasing plans recommendations through Workbench and running Purge Plan can cause locks on the table/partition preventing the Snapshot Delete Worker from obtaining a lock. If the timer expires, the program prints the following message in the log file: Unable to obtain a lock on table. |
| MSC: Write MBP Flat Files | Yes/No | No | Profile provide controls whether to flush the Planner concurrent process data files and setup data files during the plan run. If Yes, the process writes all the files to the $APPLCSF/out/data<planid> directory. |
| MSC: Distribution Planning Respects Minimum Remaining Shelf Life | Yes/No | Yes | This profile option enables Distribution Planning to plan supplies with respect to shelf life, including the minimum remaining shelf life days. |