This appendix covers the following topics:
When the Default Value of a profile option states that it is automatically calculated, this means that the Planning Engine determines the default value of that particular profile option. These profile options are included in this appendix for information purposes only. If you must change these profile option values, do so only after consulting Oracle Development and Oracle Support.
Flexfield attribute profile options store the name of the flexfield column that contains the value in the corresponding table. For example, if the Aggregate Resource Name is stored in column ATTRIBUTE1, the profile option MSC: Aggregate Resource Name Flexfield Attribute will contain the value 1.
This setup is performed only during an Oracle Applications installation. Do not modify it unless absolutely necessary.
Certain quantities used by Oracle Advanced Supply Chain Planning have fractional values. For internal processing purposes these quantities must have integer values. To resolve this problem, floating-point precision profile options act as internal multipliers. When a fractional quantity is encountered it is multiplied by the appropriate floating-point precision profile option value, and the resulting integer is processed by the Planning Engine.
There are several floating-point precision profile options. This enables greater flexibility in controlling the precision with which to consider each quantity. It also provides more flexibility to avoid numerical overflow on 32-bit platforms where the each equivalent integer processed by the Planning Engine cannot exceed 2.1 x 109. The floating-point precision profile options are: Floating Point Precision for Usages in Routing, Floating Point Precision, Floating Point Precision for Transportation Capacities (Weight and Volume), Floating Point Precision for Planning Bucket Efficiency.
The following table lists and defines the INV profile options in Oracle Advanced Planning.
The following table lists and defines the MRP and CRP profile options available with Oracle Advanced Planning.
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: 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: 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: 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 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. |
| 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: 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:59: The planned order timestamps are set to 23:59:59. 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 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: 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: 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 Calendarr | 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: 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 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: 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: Planning Currency | - | - | Not used. |
| MSC: Planning Hub 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: 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 Currency Symbol | text | $ | The currency symbol used by PS for measurement of costs and calculation of key performance indicators. |
| 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: 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 (dock) date: - Promise Date: If the Promise Date is not available, the planning engine uses Need by Date so that unacknowledged purchase orders consume supplier capacity. - Need By Date: Existing purchase orders do not consume supplier capacity. This is a site level profile option. Use the same setting of this profile option for running both collections and plans. |
| 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 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: 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 |
| 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. |
| 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 only uses this profile option if its value is No. |
| 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: 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 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. |
The following table lists and defines the MSD profile options in Oracle Advanced Planning.
In general. MSO: profile options apply only to constrained and optimized plans. If an MSO: profile option applies to unconstrained plans, its description specifically mentions it.
The following table lists and defines the MSO profile options available with Oracle Advanced Planning.
| Profile Option Name | Valid Values | Default Value | Description |
|---|---|---|---|
| MSO: Activity Selection Window (Days) | any number | 7 | This profile option specifies the number of days over which the planning engine groups activities that are candidates for scheduling. The larger the number, the greater the chance of finding an activity that can be scheduled with another activity of the same setup type. Making this number too large might result in demand priorities not being fully respected while scheduling. |
| MSO: Additional Demand Slices for Shared Supply Rescheduling | Number >= -1 | 0 | Controls the maximum number of slices to which supply can be rescheduled. Accepts values from -1 to maximum number of slices. Controls the maximum number of slices to which supply can be rescheduled. Supply is not rescheduled after this maximum even when demand will be delayed. Possible values include: -1: Reschedule to last slice 0: Does not reschedule. For example, if a supply pegs to demand in slice 2, 3, 4, 5, and 6, and the parameter value is 2, supply will reschedule if needed in slice 3 and 4 (rescheduled 2 times, in slice 3 and 4) and will not reschedule in slice 5 and 6. If the plan planning mode is Constrained (Without Detailed Scheduling), the planning engine does not use this profile option. |
| MSO: Allow Partial Demand Completion | All End Demands, Sales Orders, or None | None | Enables supply orders to individually schedule for partial satisfaction of a demand when demand is split across several supply orders. Valid values include: All End Demands: Enable Partial Demand Satisfaction for all independent demands (forecasts, sales orders, and MDS entries). Sales Orders: Enable Partial Demand Satisfaction for all Sales Order demand only. None: Schedules all supplies to coincide with completion date (latest supply date) to meet demand. This functionality can be enabled for all independent demands or only for Sales Orders. If the plan planning mode is Constrained (Without Detailed Scheduling), the planning engine only uses this profile option if its value is All End Demands. |
| MSO: Allow Schedule Gaps for Shared Supplies | Yes/No | No | This profile option controls the scheduling of shared supplies (scheduled receipts, firm planned orders, and planned orders with multiple demands pegged to them). - Yes: When scheduling shared supplies, the shared supply is moved to the right (moving the schedule date later) during the final scheduling step (to coincide with the start time of downstream supplies) if it would make one of the pegged demands late or later. The shared supply schedule is always right justified if it does not make any pegged demands late or later. When a lower-level shared supply is scheduled for the highest priority demand pegged to it, there may be a gap between the shared supply end date and the start date of the next downstream supply. By not right justifying it, it is more likely to be on time for the lower priority demands in later demand slices which are also pegged to it. Before selecting Yes, consider the setting for MSO: Additional Demand Slices for Shared Supply Rescheduling. If this profile is not 0, shared supplies may be rescheduled and this profile option does not need to be Yes. For example, Demand A with priority 100 and Demand B with priority 500 are in different slices. If the shared supply is late for Demand B, it may still be rescheduled to be on time depending on available capacity and the number of additional demand slices in which it is scheduled. If MSO: Additional Demand Slices is 0 and this profile option is Yes, the planning engine does not right justify the shared supply due date; the shared supply might still be on time for demand B even though it is not rescheduled in a later slice. - No: When scheduling shared supplies and moving them to the right (moving the schedule date later), the planning engine does not consider demands in other slices that are not yet unscheduled but pegged to this supply. This yields a schedule with fewer gaps but at the expense of potentially more late demands. 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. |
| MSO: Alternate Process Penalty | Number > 0 | See Automatic Calculations. | Specifies weight for alternate process objective in optimization. This value is specified as a number greater than 0, and is an internal value. |
| MSO: Alternate Resource Penalty | Number > 0 | See Automatic Calculations. | Specifies weight for alternate resource objective in optimization. |
| MSO: Alternate Resource Selection Method | Rank of Alternate Setup Type Match |
If Rank of Alternate, ASCP will prefer to load the primary resource if it is available even if it means incurring a setup that could have been avoided by going to the alternate. If Setup Type Match, ASCP will prefer the alternate that is the best option from a setup minimization perspective. If all alternates are equal from a setup perspective, then ASCP chooses the alternate based on rank. |
|
| MSO: Alternate Source Penalty | Number > 0 | See Automatic Calculations. | Specifies weight for alternate source objective in optimization. |
| MSO: Avoid non working days for Buy/Transfer order dates | Yes/No | No | This profile option applies only when profile option MSO: Use Shift definitions when scheduling lead-times is No. Valid vales are: - Yes: The planning engine avoids placing the ship, dock, due dates of buy and transfer orders on non-workdays according to the appropriate calendar. - No: The planning engine does not schedule buy and transfer orders with regard to the appropriate calendar. This profile option does not govern the placement of order dates. If profile option MSO: Use Shift definitions when scheduling lead-times is Yes, the planning engine assumes accurate shift timings. If the plan planning mode is Constrained (Without Detailed Scheduling), the planning engine only uses this profile option if its value is Yes. |
| MSO: Barrier Optimizer Algorithm Choice | 0, 1, 2, or 3 | Null (interpreted as 0) | This profile indicates which starting point algorithm the planning engine when it uses the barrier algorithm to solve an optimization problem. It applies only when multiple threads are used in optimization. |
| MSO: Calculate Constraint Exceptions | Yes/No | No | Determines whether constraint exceptions are calculated for plans with Enforce Capacity Constraints selected. If the plan planning mode is Constrained (Without Detailed Scheduling), the planning engine does not use this profile option. |
| MSO: Capacity Units Recalculation Threshold | Any value between 0 and 1 | 0 | The planning engine schedules supplies in two phases: - Backward schedule: From demand due date to see if demand can be met on time. - Forward schedule: If the backward schedule results in a late demand, the forward schedule from the plan start date meet demands with minimum lateness. At the end of the forward schedule phase, the planning engine adjusts the schedule to remove gaps between supplies (right justification). It may move a supply to occur at a time where there are more resource units available that there were in its previously scheduled time. If this profile option is 1, the planning engine considers assigning more resource units to the supply. For example, this profile option is 0.5. The planning engine considers changing the number of resource units if the current capacity units value is less than 0.5 * Max assigned units on the routing for the item. If this profile option is 0, the planning engine does not consider assigning more resource units. 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. |
| MSO: Check Redundant Constraints | 0 and 1 | See Automatic Calculations. | Specifies location and removal of redundant constraints. |
| MSO: Choice of supply for substitution | All Supplies, Excess Supplies | All Supplies | Determines which supplies are considered by the Planning Engine for substitution. Valid values are: All Supplies: Oracle Advanced Supply Chain Planning takes supplies belonging to substitute items even when there is demand for substitute items. Demand priorities drive the allocation. Excess supplies - Oracle Advanced Supply Chain Planning takes supplies belonging to substitute items only if it finds that the supply from the substitute item is in excess. Oracle Advanced Planning performs regular netting logic within the Substitution Window and find that excess can be offered for substitution. The native demand satisfaction has priority only within the Substitution Window. After the Substitution Window demand priorities drive the substitution. Oracle Order Promising does not honor this profile option. Oracle Order Promising always honors native demand satisfaction logic. |
| MSO: Component offset logic for optimization | 2 | n/a | n/a |
| MSO: Consume Firm Work Orders Based on Resource Hours | Yes/No | No | Use this profile to instruct the planning engine what data to use for resource load when it determines resource availability. Valid values are: - Yes: The planning engine uses resource hours to determine the resource load. Use this value if you do not attend to work in process timestamps, your work in process times are not adjusted for efficiency, and you specify resource hours. - No: The planning engine uses timestamps to determine the resource load. Use this value if your work in process times are adjusted for efficiency. If work in process is scheduled by the planning engine scheduling process, choose this value. |
| MSO: Continuous transfer across organizations | Yes/No | No | Allows you to model continuous or non-continuous transfers across organizations. - Yes: Allows continuous transfers across organizations. - No: Allows discrete, incremental or non-continuous transfers across organizations. This feature can also be set at the item/organization level using the Continuous Inter-Org Transfers item attribute. The value specified for the item attribute overrides the profile option setting. If the plan planning mode is Constrained (Without Detailed Scheduling), the planning engine does not use this profile option. |
| MSO: Convergent Supplies Consumption Pattern for Inter-Org and Supplier Sourced orders | Series/ Parallel | Parallel | Allows you to fulfill a demand in series or in parallel from multiple supplies from suppliers and/or other organizations. Values are: - Series - Demand is satisfied in series from multiple supplies. - Parallel - This is the default value. Demand is satisfied in parallel from multiple supplies. For supplier sourced orders, use profile option MSO: Convergent Supplies Consumption Pattern for Inter-Org and Supplier Sourced Orders. If the plan planning mode is Constrained (Without Detailed Scheduling), the planning engine does not use this profile option. |
| MSO: Convergent Supplies Consumption Pattern for Intra-Org Sourced orders | Series / Parallel | Parallel | Allows you to satisfy a demand in series or in parallel from multiple supplies in the same organization. Values are: - Series - Demand is satisfied in series from multiple supplies. - Parallel - This is the default value. Demand is satisfied in parallel from multiple supplies If a component is fed by orders from multiple organizations, the value of profile option MSO: Convergent Supplies Consumption Pattern for Inter-Org and Supplier Sourced orders overrides the value of this profile option. If the plan planning mode is Constrained (Without Detailed Scheduling), the planning engine does not use this profile option. |
| MSO: Cost Roll-up incremental factor | Null, positive number | Null | This profile option controls the cost increments used by the internal cost roll up in Oracle Advanced Supply Chain Planning. The cost calculation is: SUM across all components for the assembly [K * Cost of a component * (Usage of the component for the assembly + 0.01)]. K is the value that you set in this profile option. Oracle recommends a minimum value of 1. Valid values are: - Null: Use the standard cost roll-up logic Positive number: Use this factor in the cost roll-up logic of the planning engine optimization phase to calculate the assembly cost based on the components costs |
| MSO: CPLEX Crash Parameter | -1, 0, and 1 | See Automatic Calculations. | Determines how objective coefficients are used to select basis. |
| MSO: CPLEX Refactor Rate | Integer >= 0 | See Automatic Calculations. | Specifies the value of the parameter to control the refactor rate. |
| MSO: CPLEX Scaling Factor | -1, 0, and 1 | See Automatic Calculations. | Contains the scaling factor in the Planning Engine. |
| MSO: Default Forecast Priority | Integer >= 0 | 100000 | Contains default priority value for forecasts and is used by the Scheduling Engine to determine when to schedule the forecast. Can be defined at the site level. |
| MSO: Default Resource Sequencing Window (Days) | any number | 7 | After the planning engine select an unscheduled activity from the activity selection window specified by MSO: Activity Selection Window (Days), this profile option specifies the number of days from the pegged demand date over which the planning engine can look for another activity of the same setup type to schedule the activity with and achieve a good sequence on the resource. This profile option number can be overridden by resource level settings made in the Departments: Resources screen in the source system. The large this number, the longer the time spent by the resource on a setup type before changing over to the next setup type. |
| MSO: Default Sales Order Priority | Integer >= 0 | 10000 | Contains default priority value for sales orders. Used by the Scheduling Engine to determine when to schedule a sales order. Can be defined at the site level. |
| MSO: Default Timestamp for Forecasts | Beginning of Day or End of Day | End of Day | This profile option determines the forecast timestamps that Oracle Advanced Supply Chain Planning uses to plan. It applies to forecast scenarios from Oracle Demand Planning, master demand schedule forecasts, and manual master demand schedule entries. The timestamp denotes the time by which supplies to meet the demand must be available to be considered on time: Values are: - Beginning of Day: Supplies must be available at 00:00 - End of Day: Supplies must be available at 23:59 This profile option does not apply to sales orders. |
| MSO: Default Timestamp for Sales Orders | Beginning of Day, End of Day, or Retain Sales Order Timestamps | End of Day | This profile option determines the sales order line timestamps that Oracle Advanced Supply Chain Planning uses to plan. The timestamp denotes the time by which supplies to meet the demand must be available to be considered on time: Values are: - Beginning of Day: Supplies must be available at 00:00. - End of Day: Supplies must be available at 23:59. - Retain Sales Order Timestamps: Supplies must be available at the timestamp on the sales order line. The sales order demand due timestamp does not affect forecast consumption because forecast consumption is done in daily buckets. This profile option does not apply to forecasts. |
| MSO: Default Timestamp Safety Stocks | Beginning of the Day or End of Day | Beginning of the Day | The planning engine uses this profile option value to determine when safety stock supplies are due. The timestamp value applies to the safety stock requirements from Oracle Inventory, Oracle Inventory Optimization, Oracle Material Requirements Planning, and Oracle Advanced Supply Chain Planning. The values are: - Beginning of Day: Supplies must be available at 00:00. Set this option if you want to use timestamps that match safety stock requirements from Oracle Inventory Optimization. - End of Day: Supplies must be available at 23:59. Set this option if you want to use timestamps that match safety stock requirements from Oracle Inventory or Oracle Material Requirements Planning. If the plan planning mode is Constrained (Without Detailed Scheduling), the planning engine only uses this profile option if its value is End of Day. |
| MSO: Delay fulfillment of small demands | Yes/No | No | Use this profile option to enable the planning engine to delay fulfilling a small demand until it has a later larger demand. If you select Yes, set the item attribute Unsatified Demand Factor on each item whose small demands you want delayed. |
| MSO: Demand Size Tolerance Before Splitting Planned Orders | Number >=0 | Null | Creates a threshold percentage that causes Planned Orders to split prior to scheduling (if the remaining unallocated quantity of a planned order is greater than the remaining unallocated quantity of the pegged demand). Not used if order modifiers exist for an item and not used in a project planning environment. Valid values are positive decimal quantities (.5 is interpreted as 50%). If the plan planning mode is Constrained (Without Detailed Scheduling), the planning engine does not use this profile option |
| MSO: Demand Window Size | integer >=0 | Null | During priority pegging, demands are sorted based on the demand priority within the demand window. After these demands are fully pegged, Oracle Advanced Supply Chain Planning sorts all demands in the next window by priority. This is stated as the number of calendar days including non-workdays. With a value of 10, the first demand window is between the start date of the plan or the first demand date +10 days. The default (Null) is treated as 1 in the Planning Engine. If the plan planning mode is Constrained (Without Detailed Scheduling), the planning engine uses this profile option as value 1 day. |
| MSO: Disable Inference of Item Substitution Relationship | Yes/No/Null | Null | Use this profile option to instruct the planning engine whether to infer end item substitution relationships. Valid values are: - Yes: Do not infer item substitution relationships - No/Null: Do infer item substitution relationships |
| MSO: Divergent Supply Feeding Pattern for Inter-Org and Supplier Sourced orders | Series With MTQ Only / Series | Series With MTQ Only | Allows you to fulfill multiple downstream demands in parallel or in series by a supply from another internal organization. Values are: - Series With MTQ Only - This is the default value. A supply always feeds multiple demands in series when a corresponding MTQ has been specified. - Series - Supply feeds multiple demands in series. If the plan planning mode is Constrained (Without Detailed Scheduling), the planning engine does not use this profile option. |
| MSO: Divergent Supply Feeding Pattern for Intra-Org Sourced orders | Series With MTQ Only / Series | Series With MTQ Only | Allows you to fulfill multiple downstream demands in parallel or in series by a supply in the same organization. Values are: - Series With MTQ Only - This is the default value. A supply always feeds multiple demands in series when a corresponding MTQ has been specified. - Series - Supply feeds multiple demands in series. If the plan planning mode is Constrained (Without Detailed Scheduling), the planning engine does not use this profile option. |
| MSO: Dual Simplex Parameter | 0, 1, 2, 3, and 4 | See Automatic Calculations. | Gradient parameter for dual simplex. |
| MSO: EDD Scheduling Window Control | Any value between 0 and 1 | 0.5 | This profile option is applicable to constrained plans with enforce demand due dates. The planning engine calculates an actual scheduling window for each resource activity and supply. The actual window is defined by the dates: - Latest Possible completion time (LPCT): Determined by the start time of downstream activities that have already been scheduled. - Earliest Allowable Completion Time (EACT): Calculated by the planning engine which accounts for the unscheduled upstream activities and how much time those activities need. If this profile option is the default value, the planning engine uses the calculated EACT. If this profile option is lower than the default value, the planning engine uses an earlier EACT than the calculated EACT which gives the activity a larger scheduling window. If this profile option is higher than the default value, the planning engine uses a later EACT than the calculated EACT which gives the activity a smaller scheduling window. 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. |
| MSO: Enable Cost Rollup for Optimization | Yes/No | Null (interpreted as No) | This profile specifies where the optimization engine looks for costs during cost-based optimization. Valid values are: - No: Use user-provided costs from the source system -Yes: Use costs from the internal cost rollup |
| MSO: Enable Decision Rules | Yes / No | No | The profile option enables User Defined Decision Rules. Yes: Use the user-defined decision rules. No: User defined decision rules are not allowed. The Plan Options tab, Decision Rules, is disabled. If you select No, you can duplicate the functionality of the decision rule Use Alternate Sources parameter for buy items but not for transfers from other organizations; set profile option MSC: Enable Enhanced Sourcing to Yes. |
| MSO: Enable Hard Links Globally | Yes/No | No | Use this profile option to specify whether the planning engine should globally enforce hard link constraints. Valid values are: - Yes: Enforce hard link constraints - No: Do not enforce hard link constraints |
| MSO: Enable Triangulation in Optimization | - | - | Reserved for future use. |
| MSO: Enforce Resource Sequence Contiguity | Yes / No | Yes | Controls contiguity constraints between resource activities within an operation. Valid values are: - Yes: Resource activities within the same operation are scheduled contiguously in time. The end of the preceding activity exactly lines up with the start of the current activity and the end of the current activity exactly lines up with the start of the next (if there is MTQ specified, the activities may also overlap). - No: The contiguity constraint is relaxed and in certain cases, the chances of obtaining feasible schedules improved. If the plan planning mode is Constrained (Without Detailed Scheduling), the planning engine does not use this profile option. |
| MSO: Firm Operations/Orders Within Time Fence | Yes/No/Null | No | Indicates whether or not the planning engine should firm those operations and orders that are within the plannng time fence. The valid values are: - Yes/Null: Firms operations and orders that are within the time fence. - No: The planning engine does not reschedule the non-firm operations and orders that have dock dates within the time fence. This profile option also applies to unconstrained plans. |
| MSO: Firm Purchase Orders Within Time Fence | Yes/No/Null | No | Indicates whether or not the planning engine should firm those purchase orders that are within the planning time fence. The valid values are: - Yes/Null: Firms purchase orders that are within the time fence. - No: The planning engine reschedules and cancels the non-firm purchase orders that have dock dates within the time fence This profile option also applies to unconstrained plans. |
| MSO: Firm Requisitions Orders Within Time Fence | Yes/No/Null | No | Indicates whether or not the planning engine should firm those requisitions that are within the planning time fence. The valid values are: - Yes/Null: Firms requisitions that are within the time fence. - No: The planning engine does not reschedule the non-firm purchase requisitions that have dock dates within the time tence. The planning engine reschedules and cancels recommendations within the time fence. The planning engine uses the start date of the receiving organization as the reference for internal requisitions. This profile option also applies to unconstrained plans. |
| MSO: Firm Supply Allocation Window (Backward days) | Integers >=0 | 1 | The allocation of firm supplies to demands is based on demand priorities within the Firm Supply Allocation window. Set this window using system level profile options. This window is derived dynamically for each demand; it starts with the demand due date and goes backwards to the window size. This is stated as the number of calendar days including non-workdays. |
| MSO: Firm Supply Allocation Window (Forward days) | Integers >=0 | Null | The allocation of firm supplies to demands is based on demand priorities within the Firm Supply Allocation window. Set this window using system level profile options. This window is derived dynamically for each demand; it starts with the demand due date and moves forwards to the window size. This pegs demands to firm supplies that are scheduled after the demand date. After searching backward, it searches forward by the number of days set by this profile option, pegging the supply with the nearest (earliest) schedule to the unallocated demand quantity. This can cause supplies to be late for the demand due date. This is stated as the number of calendar days including non-workdays. To use this feature, set profile option MSO: Net All Firm Supplies Before Creating Planned Orders to Yes. |
| MSO: Firm Work Orders/ Operations Within Time Fence | Yes / No | No | Used for both constrained and unconstrained plans. When set to Yes, all operations of an order with start dates in the Planning Time Fence are treated as firm. Any operation with a start date outside of the Planning Time Fence is not considered firm and can be moved. When set to No, operations with start dates in the Planning Time Fence can be rescheduled out. |
| MSO: Floating Point Precision | - | - | Not used. Replaced by profile option MSO: Floating Point Precision for Order Quantities If the plan planning mode is Constrained (Without Detailed Scheduling), the planning engine does not use this profile option. |
| MSO: Floating Point Precision for Order Q | - | - | Not used. Replaced by profile option MSO: Floating Point Precision for Order Quantities |
| MSO: Floating Point Precision for Order Quantities | Number > 0 | 100 | Internal multiplier for order quantities. Can change the value depending on precision desired. Verify that the product of the floating point precision and the number does not exceed the maximum integer size handled by the machine. See Floating Point Precision for more information. If the plan planning mode is Constrained (Without Detailed Scheduling), the planning engine does not use this profile option. |
| MSO: Floating Point Precision for Planning Bucket Efficiency | Not applicable | Not applicable | This has been changed to MSO: HLS Granularity Precision. |
| MSO: Floating Point Precision for Transportation Capacities (Volume) | Number > 0 | 100 | Internal multiplier for transportation lane capacities by volume, by day. Can change the value depending on precision desired. Verify that the product of the floating point precision and the number does not exceed the maximum integer size handled by the machine. See Floating Point Precision for more information. If the plan planning mode is Constrained (Without Detailed Scheduling), the planning engine does not use this profile option. |
| MSO: Floating Point Precision for Transportation Capacities (Weight) | Number > 0 | 100 | Internal multiplier for transportation lane capacities by weight, by day. Can change the value depending on precision desired. Verify that the product of the floating point precision and the number does not exceed the maximum integer size handled by the machine. See Floating Point Precision for more information. If the plan planning mode is Constrained (Without Detailed Scheduling), the planning engine does not use this profile option. |
| MSO: Floating Point Precision for Usage in Routings | Number > 0 | 100 | Internal multiplier for order quantities. Can change the value depending on precision desired. Verify that the product of the floating point precision and the number does not exceed the maximum integer size handled by the machine. See Floating Point Precision for more information. If the plan planning mode is Constrained (Without Detailed Scheduling), the planning engine does not use this profile option |
| MSO: Generate Compression Days Exception | Yes/No | Yes | Use this profile option to control issuance of exception message Orders with compression days. Valid values: - Yes: Issue the exception message - No: Do not issue the exception message The planning engine issues exception message Orders with insufficient lead-time when it schedules orders for less time than their assembly's lead-time. If the reason for that scheduling is that the planning engine would schedule the order in the past, it also issues exception message Orders with compression days. To avoid seeing both these exceptions for the same order, select No for this profile option. |
| MSO: Generate Compression/Firming Exceptions for Orders in Progress | Yes/No | Yes | When set to No, the planning engine does not issue the following exception messages for firm orders whose start date is in the past (after applying the lead time offset to the due date). The planning engine assumes that these orders are in progress and on time:
|
| MSO: Generate Shared Supply Exceptions | Yes/No | No | The planning engine schedules demands in slices; each slice contains a set of demands in a time period. Sometimes, a supply is pegged to two demands (shared supply) that are each in different slices. If these two slices are separated by more slices than the value of profile option MSO: Additional Demand Slices for Shared Supply Rescheduling, the planning engine does not reschedule the shared supply in the earlier slice when it schedules the demand in the later slice. It is possible that the demand in the later slice is satisfied late because the planning engine did not reschedule in (earlier date) the supply in the earlier slice. If this profile option is Yes, the planning engine issues a Shared Supply Scheduled Late exception message when this occurs. If this profile option is No, the planning engine does not generate the exception message. This is a user level profile option. |
| MSO: Global Batchable Flag | Yes/No | No | This profile option enables resource batching functionality for order scheduling. Valid values are Yes (enable resource batching) and.No (do not enable resource batching). If the plan planning mode is Constrained (Without Detailed Scheduling), the planning engine does not use this profile option. |
| MSO: Global Chargeable Flag | Yes/No | No | This profile option controls whether Oracle Advanced Supply Chain Planning schedules resource charges. If Yes, the planning engine schedules charges for chargeable resources. If No, chargeable resources are considered as item basis an no individual charges are scheduled. Material flows and resource loads are not influenced by charge quantities. |
| MSO: Global Time Limit | Number > 0 | See Automatic Calculations. | Parameter used to set global time limit for halting optimization. |
| MSO: Hard link scheduling window | Integer | 30 | This profile option specifies the time window within which ASCP tries to schedule a set of operations linked together through hard links. If scheduling is unsuccessful, overloads are created. This is a hidden profile option used by development. This defines the scheduling window within which the system schedules the hard-linked operation set. Increasing the window gives room to schedule operations with hard links without overloading. Based on the number of operations per hard linked operation set, increasing this value can have a performance impact. |
| MSO: Hard link scheduling window expansion factor | Integer | 10 | This hidden profile option used by development is used to limit the propagation for the hard linked operation set. Normally, we limit the propagation by a factor of (This profile option value * Minimum duration of hard linked operation set). |
| MSO: Heuristic type | Look Ahead | Look Ahead | Determines which heuristic to use. The look-ahead heuristic reserves time for lower priorities so the schedule begins with the tasks of higher priorities. This is a site level profile option. |
| MSO: HLS flat files path | Text | Null | Specifies the directory to store the Planning Engine debugging data files. |
| MSO: Improved Lead Time Offsetting in Aggregated Buckets | - | - | Reserved for future use. If the plan planning mode is Constrained (Without Detailed Scheduling), the planning engine does not use this profile option. |
| MSO: Internal Demand Aggregation Within Optimization | Yes/No | Null (interpreted as No) | This profile specifies how the optimization engine should prioritize independent demands. Valid values are: - Yes: Prioritize by date. This value improves optimization engine performance. - No: Prioritize by demand priority |
| MSO: Inventory Carrying Costs Percentage | A percentage between 0 and 100 | Null | Specifies inventory carrying costs percentage for all items in the plan. Can be defined at the site level. You can update this value. The inventory carrying cost is a percent (if the user enters 10, the value is 10%). |
| MSO: Late Demands Exceptions Tolerance Minutes | Integer > 0 | 0 | This profile option is used by constrained plans. Sets the value in minutes for a window during which the planning engine does not issue exception messages for late demands. Use it particularly in cases where demands are only a few minutes or a few hours late. The value that you enter is used based on a 24 hour, 7 day per week calendar. For example, enter 1440 minutes (24 hours) for this profile option. A demand due at 15:00 on Tuesday does not cause late demand exception or diagnosis information as long as the supplies are complete by l5:00 on Wednesday. |
| MSO: Lead Time Control | Violate Minimum Processing Times to Meet Demand Due Date and Do Not Violate Minimum Processing Times | Violate Minimum Processing Times to Meet Demand Due Date | This profile option is applicable to constrained plans. Valid values are: - Violate Minimum Processing Times to Meet Demand Due Date: The planning engine meets the demand due date even if it compresses operations and supplies beyond their minimum durations (from item lead-times and routing usages). - Do Not Violate Minimum Processing Times: The planning engine respects the minimum durations of operations and supplies (from item lead-times and routing usages) even if it satisfies demands late. This is a user level profile option. |
| MSO: List Size for Pricing Candidates | Integer > 0 | See Automatic Calculations. | Parameter to set the list size for pricing candidates. |
| MSO: LP Constraint Batch Size | - | - | Not used. |
| MSO: LP Markowitz Coefficient | Number between 0.0001 and 0.99999 | See Automatic Calculations. | Sets the Markowitz Coefficient. |
| MSO: LP Optimization Algorithm | 0: Primal simplex, 1: Dual simplex, 2: Hybrid barrier primal, 3: Hybrid barrier dual | 0 | Determines which optimization algorithm is used. Can be defined at the site level. See Automatic Calculations for more information on the default value for this profile option. |
| MSO: Maximize Search of Availability Intervals | Yes / No | Yes | Enhances the capability of the scheduling engine to accurately identify pockets of available time where resource activities can be feasibly scheduled. Valid values are: - Yes: Maintains a detailed picture of the Resource Profile while scheduling. Resource Profile refers to the time varying picture of requirements and availability. The maintenance of this detailed picture causes the planning engine to miss fewer valid slots for scheduling activities than otherwise. - No: Detailed Resource Profile is not maintained. If you need to change the default value of this profile in your installation, it is recommended that you consult with Oracle Development before doing so. You can set this option if you receive the Requirement causes resource overload exceptions in the Planner Workbench in Enforce Capacity Constraints Plans. For more details, see Exception Messages. If the plan planning mode is Constrained (Without Detailed Scheduling), the planning engine does not use this profile option. |
| MSO: Maximum Activity Duration | Number > 0 | See Automatic Calculations. | Defines the Planning Engine maximum activity duration in days. All requirements should be less in duration than this. If null, the planning horizon duration is used. If the plan planning mode is Constrained (Without Detailed Scheduling), the planning engine does not use this profile option. |
| MSO: Maximum Allowable Days Late | Integer > 0 | 300 | Limits the number of days by which a demand or unfirmed scheduled receipt can be moved out when optimization is turned on. This value is used only to improve performance and reduce the size of the plan for the optimization component of the Planning Engine. Scheduling moves demands and unfirmed scheduled receipts out as long as necessary. Can be defined at the site level. Note: Set this to a number as large as the typical planning horizon to avoid unusual results. |
| MSO: Maximum Allowable Days Late before Forecast Expiration | Integer > 0 | Null | Oracle Advanced Supply Chain Planning uses this profile option when planning supplies for forecast scenarios from Oracle Demand Planning, master demand schedule forecasts, and manual master demand schedule entries. When a forecast or master demand schedule entry cannot be completely satisfied within the allowable days late, the planning engine does not plan supplies for the quantity that is late by this many days. The profile option does not apply to sales orders. |
| MSO: Maximum Demands per Group | Integer > 0, smaller than the size of a slice | 5 | Determines the maximum number of demands that can be grouped together for scheduling. Within a group, the default heuristic can try different orders among the demands. Can be defined at the site level. If the plan planning mode is Constrained (Without Detailed Scheduling), the planning engine does not use this profile option. |
| MSO: Maximum Demands per Group for Advanced Sequencing | Any number | 1 | The profile option specifies the number of demands that are grouped together for scheduling. the larger this number, the greater the chances of obtaining good sequences on the resources. Making this number too large might result in demand priorities not being fully respected while scheduling. |
| MSO: Maximum Demands per Slice | Integer >= 0 | 100 | Determines the number of demands in a slice. Enables the Scheduling Engine to resolve interactions of demands within a slice. Supplies shared between demands are scheduled better when the demands are in the same slice. However, slices that are too large slow down the Scheduling Engine use more memory. Can be defined at the site level. If the plan planning mode is Constrained (Without Detailed Scheduling), the planning engine does not use this profile option. |
| MSO: Maximum Inventory Level % of Safety Stock | Between 0 and 100% | - | Use this option to specify maximum inventory levels. If no other method of calculation is defined for an item-organization maximum inventory level, the levels are based on the specified percentage of the safety stock level. |
| MSO: Maximum Number of Prepones | Number > 0 | 10 | Scalability factor for the Scheduling Engine. The Scheduling Engine attempts to schedule the operations in different orders to find a solution. Limits the number of times the Scheduling Engine attempts to schedule an operation. If there are many components for some items or many small supplies answering a demand, the number of orders is larger; reduce this parameter. Can be defined at the site level. See Automatic Calculations for more information. If the plan planning mode is Constrained (Without Detailed Scheduling), the planning engine does not use this profile option. |
| MSO: Maximum Number of Pull for Operation | Integer > 0 | 8 | When an operation cannot be scheduled on a certain day, the scheduling engine attempts to schedule it on an earlier date (for backward scheduling). This profile option controls how many days are tried in this manner. Many days result in lower performance. Can be defined at the site level. See Automatic Calculations for more information. If the plan planning mode is Constrained (Without Detailed Scheduling), the planning engine does not use this profile option. |
| MSO: Maximum number of pulls/push for hard linked operations | -- | -- | This hidden profile option is not used. |
| MSO: Maximum Number of Pushes for Operation | -1 or Integer > 0 | -1 | When you are running constrained plans with the Enforce Capacity Constraints plan option checked, this profile option controls the number of attempts made to schedule a resource activity feasibly. Valid values are: -1: Continues the search for available capacity till the end of the planning horizon. Integer > 0: The number that you specify here determines the number of attempts that the planning engine makes to schedule the activity. For example, if you set the profile option to 5, the planning engine makes 5 attempts to schedule the activity feasibly, and after that schedules the activity with an overload. The spot chosen to schedule the activity with overload is the initial spot that was tried. If the plan planning mode is Constrained (Without Detailed Scheduling), the planning engine does not use this profile option. |
| MSO: Maximum Operations Per Slice | Integer > 0 | 3000 operations | Determines the number of operations which can be scheduled in a slice. Limits the problem size in a slice and can be a limiting factor in determining the number of demands that can be scheduled in a slice. Oracle recommends that you use a large value such as the default value. If the plan planning mode is Constrained (Without Detailed Scheduling), the planning engine does not use this profile option. |
| MSO: Maximum Resource Over-capacity | Number > 0 | 5 | Assigns resource slacks when it does not find the resource available and it is forced to use slacks. The Scheduling Engine initiate the resource slack from 0 to maximum assigned units and will jump to this number if no solution is possible. This limits the number of tries to assign the resource slack. Can be defined at the site level. See Automatic Calculations for more information. If the plan planning mode is Constrained (Without Detailed Scheduling), the planning engine does not use this profile option. |
| MSO: Maximum Simplex Iterations | Integer > 0 | See Automatic Calculations. | Parameter to set the maximum number of simplex iterations. |
| MSO: Multiplier To Derive Supply Allocation Window | Number >= 0 | Null | You can set the Firm Supply Allocation window using the profile option MSC: Firm Supply Allocation Window or you can use the manufacturing lead-time and the profile option MSC: Multiplier to Derive Firm Supply Allocation Window. If you specify any value for the latter profile option, the information you enter for MSC: Firm Supply Allocation Window is ignored. If the product of this multiplier and cumulative manufacturing lead-time is a fractional quantity, the number is rounded up to the next integer. |
| MSO: Net All Firm Supplies Before Creating Planned Order | No, All Supply Types, Only for Work Orders, Only for Purchase and Transfer Supplies, All Supply Types Including By-product Supplies |
No | Nets all firmed supply available in any future period before creating new planned orders. The profile option treats firmed planned orders the same as real supplies. The values are: - No: Does not net firm supplies before creating planned orders. - All Supply Types: Net all firm supplies before creating planned orders. This includes work orders, purchase orders, transfer supplies and firm planned orders for these supplies. - Only for Work Orders: Net only firm discrete jobs before creating planned orders. - Only for Purchase and Transfer Supplies: Net all firm purchased and transfer supplies before creating planned orders. - All Supply Types Including by-product/co-product supplies: Nets all firm supplies (including by-product and co-product supplies) before creating planned orders. The planning engine does not reschedule by-product and co-product supplies, they follow the scheduling of the supply that generates them. This choice allows these supplies to be netted for earlier demands. This may cause late demands, but may reduce overall inventory. |
| MSO: Network routing cycle time coefficient | Numeric | 2 | Used by the Scheduling Engine to calculate the window of time allocated to schedule a network flow. This is used in conjunction with NFL Fixed Time Window. The window of time is (Coefficient * Cycle time) + Fixed time window. Defined at the site level. |
| MSO: Network routing fixed time window | Number > 0 | 0 | Used by the Scheduling Engine to calculate the window of time allocated to schedule a network flow. This is used in conjunction with NFL Cycle Time Coefficient. The window of time is (Coefficient * Cycle time) + Fixed time window). Defined at the site level. |
| MSO: Nfl Backward Compression Pct | Between 10 and 100% | 100% | Defines the percentage of the actual resources capacity that the network flow takes into account. A value under 100 percent tends to offload more activities to alternate resources. Can be defined at the site level. |
| MSO: Nfl Forward Compression Pct | Between 10 and 100% | 100% | Defines the percentage of the actual resources capacity that the network flow takes into account. Use in forward phase to force the system to use alternates and limit the tardiness of activities. Can be defined at the site level. |
| MSO: Number of Demand Groups for Optimization | Integer > 0 | 50 | You can use this profile option only for constrained plans that have decision rules enabled. In the case of cost-based optimization, the planning engine considers the demand lateness penalty cost instead of demand priorities. Use this profile option to instruct the planning engine how to group demand into demand groups by priority ranges. For example, the demand priority values are from 1 to 100 and you set this profile option to 5. The planning engine assigns demands to five demand groups. Each group includes a range of 20 priorities - 1 to 20, 21 to 40, 41 to 60, 61 to 80, 81 to 100. The planning engine searches for supplies that satisfy all demands having priorities in the same range. It satisfies demands in the higher priority range first. For multiple demands in the same priority range, the planning engine satisfies demands based on individual demand priorities. Note that too many groups may affect performance. |
| MSO: Number of Threads for Optimization | Integer > 0 | Null | This profile option applies to 64-bit platforms only. Values greater than 1 invoke running optimized plans in a multi-threaded mode. This enables various optimization problems to be solved in parallel so that run time may be reduced. However, multi-threading increases the CPU usage and memory consumption. You can control the load on CPU by specifying the number of threads that you want to run in parallel. |
| MSO: Optimization Advanced Start | 0 and 1 | Null (internally defaulted as a value of 1) | This profile option controls whether the planning engine should be set to use advanced start (profile option value 1). This means that the optimization engine uses certain values from a previous run of the plan; it sees improved performance by reusing certain computations. This is an optimization engine profile option and should not be changed under ordinary circumstances. |
| MSO: Optimization Daily Aggregation Buckets | Integer > 0 | Null | Specifies the Daily Aggregation Time Bucket to be used by the Planning Engine if the profile option MSO: Use Optimization Internal Time Aggregation is set to True. |
| MSO: Optimization Weekly Aggregation Buckets | Integer > 0 | Null | Specifies the Weekly Aggregation Time Bucket to be used by the Planning Engine if the profile option MSO: Use Optimization Internal Time Aggregation is set to True. |
| MSO: Order Modifier Maximum Searching Depth | Integer | 3 | Use this profile option to specify the maximum number of lower levels in the supply chain that the planning engine searches for alternate sources, bills of material, components, and resources to resolve a shortage. The shortages often occur when the planning engine rounds down planed orders with respect to capacity constraints and order modifiers. The planning engine searches this many levels down both in: - The organization with the shortage - Organizations that supply the short organization with the short item Oracle suggests that: The solution quality improves with higher numbers while the processing time worsens with higher numbers. For each integer increase in the profile option, processing time worsens at a much higher rate than solution quality improves. You consider the tradeoffs and tend towards lover rather than higher numbers. |
| MSO: Overlap Activities by MTQ | Yes/No | No | Use profile option MSO: Overlap Activities by MTQ to control overlapping activities inside one operation. Valid values are: - Yes: Allow overlapping activities inside one operation. - No: Prevent overlapping activities inside one operation. |
| MSO: Peg By-product Supplies | Yes/No | Yes | Yes: Pegging is considered when scheduling operations with by-product supply. Scheduling of these operations respects demand for the by-product and demand for the main product. After scheduling these operations, the by-product supply date is updated to reflect the operation scheduled date. No: By-Product Supplies are not pegged to demands For constraint-based plans. Set this profile option to No with items that are components on the supply chain bill of materials and that are by-product on a different level of the same supply chain bill of materials. Selecting No prevents the planning engine from continuous looping between the component demand and the by-product supply. |
| MSO: Penalty Basis for Changeovers | Changeover Time Changeover Penalty |
Indicates whether the changeover time of the changeover penalty is to be used as the criterion for calculation the ideal sequence. If Changeover Time, ASCP uses the relative changeover times between setup types as the criteria for deciding on the ideal sequence of setup types. If Changeover Penalty, ASCP uses the relative changeover penalties between setup types as the criteria for deciding on the ideal sequence of setup types. |
|
| MSO: Penalty Cost Factor for Exceeding Item Material Capacity Flexfield Attribute | Integer >= 0 | Null | Stores the flexfield column name that contains the value in the corresponding table. Setup performed only during application install. See Flexfield Attributes for more information. |
| MSO: Penalty Cost Factor for Exceeding Material Capacity | Number >= 0 | Null | Defines a penalty cost factor for exceeding material capacity. |
| MSO: Penalty Cost Factor for Exceeding Material Capacity Flexfield Attribute | Number | Automatically generated to denote flexfield segment holding the penalty factor | This profile option stores the item flexfield segment that holds the penalty cost factor for exceeding material capacity. The collections process Generate Planning Flexfield concurrent program captures the segment when it first runs during installation. |
| MSO: Penalty Cost Factor for Exceeding Org Material Capacity Flexfield Attribute | Integer >= 0 | Null | Stores the flexfield column name that contains the value in the corresponding table. Setup performed only during application install. See Flexfield Attributes for more information. |
| MSO: Penalty Cost Factor for Exceeding Org Resource Capacity Flexfield Attribute | Integer >= 0 | Null | Stores the flexfield column name that contains the value in the corresponding table. Setup performed only during application install. See Flexfield Attributes for more information. |
| MSO: Penalty Cost Factor for Exceeding Org Transportation Capacity Flexfield Attribute | Integer >= 0 | Null | Stores the flexfield column name that contains the value in the corresponding table. Setup performed only during application install. See Flexfield Attributes for more information. |
| MSO: Penalty Cost Factor for Exceeding Resource Capacity | 0 and 1 | Null (internally defaulted as a value of 1) | Denotes a factor for plan profit computations that is invoked only when the plan profit parameter for optimization has a value greater than 0. The penalty cost factor is multiplied by the resource cost to give the cost of overloading a particular resource. |
| MSO: Penalty Cost Factor for Exceeding Resource Capacity Flexfield Attribute | Integer >= 0 | Null | Stores the flexfield column name that contains the value in the corresponding table. Setup performed only during application install. See Flexfield Attributes for more information. |
| MSO: Penalty Cost Factor for Exceeding Transportation Capacity Flexfield Attribute | Integer >= 0 | Null | Stores the flexfield column name that contains the value in the corresponding table. Setup performed only during application install. See Flexfield Attributes for more information. |
| MSO: Penalty Cost Factor for Late Demands | Number > 0 | None | Defines a penalty cost factor common to all demands. The demands include sales orders, forecasts and safety stock. Can be defined at the site level. |
| MSO: Penalty Cost Factor for Late Forecasts Flexfield Attribute | Integer >= 0 | Null | Stores the flexfield column name that contains the value in the corresponding table. Setup performed only during application install. See Flexfield Attributes for more information. |
| MSO: Penalty Cost Factor for Late Item Demands Flexfield Attribute | Integer >= 0 | Null | Stores the flexfield column name that contains the value in the corresponding table. Setup performed only during application install. See Flexfield Attributes for more information. |
| MSO: Penalty Cost Factor for Late Org Demands Flexfield Attribute | Integer >= 0 | Null | Stores the flexfield column name that contains the value in the corresponding table. Setup performed only during application install. See Flexfield Attributes for more information. |
| MSO: Penalty Cost Factor for Late Sales Orders Flexfield Attribute | Integer >= 0 | Null | Stores the flexfield column name that contains the value in the corresponding table. Setup performed only during application install. See Flexfield Attributes for more information. |
| MSO: Penalty Multiplier Outside Unconstrained Window | This profile option specifies an extra lateness penalty when scheduling later than the unconstrained latest possible completion time for a given activity. | ||
| MSO: Postpone Use of Alternates to Latest Possible Time | Yes/No | No | Use this profile option to specify when the planning engine should plan alternate supplies. Valid values are - Yes: Postpone planning them until the last possible moment - No: Plan them when you need to do so to create the best plan for the item |
| MSO: Preprocessing Aggregator Fill | Integer > 0 | See Automatic Calculations. | Preprocessor aggregator fill. |
| MSO: Preprocessing Aggregator Limit | Integer > 0 | See Automatic Calculations. | Parameter to control preprocessing aggregator limit. |
| MSO: Preprocessing Flag for LP Matrix | 0 and 1 | See Automatic Calculations. | Contains the presolve indicator. |
| MSO: Preprocessor LP Compression | - | - | Not used. |
| MSO: Primal Simplex Parameter | -1, 0, 1, 2, 3, and 4 | See Automatic Calculations. | Gradient parameter for primal simplex algorithm. |
| MSO: Primal/Dual Preprocessing Reduction | 0, 1, 2, and 3 | See Automatic Calculations. | Used by optimization. |
| MSO: Pull push base | Positive Integers | 1 | Each time the planning engine needs to search for a new spot to schedule it looks ahead by a certain time period that is dictated by the settings of the profile options MSO: Push Pull Base and MSO: Push Pull Offset. For more details, see Requirement causes resource overload exception. |
| MSO: Pull push offset | Positive integer in mnutes | 1440 | Each time the planning engine needs to search for a new spot to schedule it looks ahead by a certain time period that is dictated by the settings of the profile options MSO: Push Pull Base and MSO: Push Pull Offset. For more details, seeRequirement causes resource overload exception . |
| MSO: Queue Time Factor | Number >= 0 | None | Increases item lead-time in optimization, so that lead-time values are close to those used in the Scheduling Engine. Optimization lead-time is padded to include queue time. |
| MSO: Reschedule Jobs Out to Reduce Inventory Carrying Costs | Yes/No | Yes | This profile option involves right justifying standard and lot-based discrete jobs when rescheduling them out to line up with other supplies for the job. When there is a constraint, the planning engine always moves the jobs based on the constraint. When there are no constraints, you have the option to instruct the planning engine to right justify the jobs: - Yes: The planning engine attempts to schedule the job as late as possible for one or more demands. - No: The planning engine does not reschedule or right justify the job beyond its old due date. If there is existing capacity earlier than the old due date of the job, the planning engine may recommend a reschedule in. This profile option does not apply to other order types, for example, purchase orders and purchase requisitions. |
| MSO: Reschedule Shared Supply to Influence Batching | Yes/No | No | Determines whether the Planning Engine schedules shared supplies early to avoid item-based resource constraints prior to batch resources. Valid values are Yes (considers whether scheduling shared supplies early will allow subsequent resource batching; this value improves the scheduled utilization of batch resources by considering earlier constraints) and No (schedules resource batching when supplies are available). |
| MSO: Resource Adjustment Factor For Improved Offloading to Alternates | A number between and including 0 and 1 | Null (internally defaulted as a value of 1) | The factor that the planning engine uses to reduce the resource availability when making the sourcing decision. For example, if the factor is set to 0.8, the resource availability is reduced by 20% and the planning engine uses more of the alternate processes. Then, at the time of scheduling, planning has more flexibility. |
| MSO: Resource Batching Strategy | Nearest Date/ Level Utilization | Nearest Date | Selects order scheduling strategy used in resource batching. Valid values are Nearest Date (schedules orders to load resources nearest the due date of the order) and Level Utilization (schedules orders to level utilization of the resource). |
| MSO: Setup Pattern Calculation Window (multiplier of Resource Sequencing window | any number | 1 | A window is calculated by multiplying the Resource's Sequencing window value by the value in this profile. The relative mix of various setup types that fall into this window is calculated and then applied to each resource sequencing window. When MSO: Use Sequencing Template is set to Yes, ASCP uses this calculated mix of setup types to determine the desired spots. |
| MSO: Resource Group for the Line Flexfield Attribute | Integer >= 0 | Null | Stores the name of the flexfield column that contains the value in the corresponding table. This setup is only performed during application install. See Flexfield Attributes for more information. |
| MSO: Schedule Across Breaks | Yes/No | Yes (can schedule across break) | Determines whether the scheduling engine starts an activity before a break and ends it after the break. If set to No, verify that every activity has enough resource in one shift (otherwise the activities are moved to the end of the horizon). Can be defined at the site level. |
| MSO: Schedule PO in FIFO | Yes | n/a | n/a |
| MSO: Schedule Simultaneous Resources Across Breaks | Yes/No | Yes (can schedule across break) | This profile option behaves the same as profile option MSO: Schedule Across Breaks. However, it only applies to simultaneous resources. |
| MSO: schedule window width | Integers >=0 | 8 days | Defines time window (days) that the scheduling engine looks for its primary resource. If the primary resource is not in this window, the scheduling engine moves to an alternate resource. Can be defined at the site level. |
| MSO: Scheduler Time Step | - | - | Reserved for future use. |
| MSO: SCO Dual Variables Tolerance | Numeric | 0.000000001 | Parameter used internally for optimization. Consult Oracle Development and Oracle Support before modifying this profile option. |
| MSO: SCO Reduced Cost Tolerance | Numeric | 0.000000001 | Parameter used internally for optimization. Consult Oracle Development and Oracle Support before modifying this profile option. |
| MSO: Simplex Feasibility Tolerance | A number between e-9 and e-4 | See Automatic Calculations. | Parameter to set the simplex feasibility tolerance. |
| MSO: Simplex Optimality Tolerance | A number between e-9 and e-4 | See Automatic Calculations. | Parameter to set the optimality tolerance for the simplex algorithm. |
| MSO: Simplex Perturbation Constant | A number greater than e-8 | See Automatic Calculations. | Parameter to set the simplex perturbation constant. |
| MSO: Simplex Perturbation Limit | Integer > 0 | See Automatic Calculations. | Parameter for the simplex perturbation limit. |
| MSO: Simplex Perturbation Parameter | 0 and 1 | See Automatic Calculations. | Provides a perturbation constant for the Planning Engine. Sets the amount by which the Planning Engine perturbs the upper and lower bounds on the variables when a problem is perturbed. |
| MSO: Simplex Presolve Limit | -1, 0, and integer > 0 | See Automatic Calculations. | Parameter to set the limit on the number of pre-solves. |
| MSO: Simplex Singularity Repair Limit | Integer > 0 | See Automatic Calculations. | Parameter to set the simplex singularity repair limit. |
| MSO: Simultaneous Resource Overlap Mode | - | - | Not used. |
| MSO: Slack Hours for Batch Resource | Integer | Null | This profile value is used by Oracle Advanced Supply Chain Planning to right justify the maximum end date for a scheduled batch resource. The value specified is the amount of slack time (in hours) to delay scheduling the resource so that other supplies can be included in the same batch even though they cannot be scheduled as early as the original supply. This means that the batch must wait for the constrained supply. |
| MSO: Solve Dual Problem | 0 and 1 | See Automatic Calculations. | Controls whether the Planning Engine solves the dual problem or the primal problem. |
| MSO: Sourcing Allocation Window | integer >= 1 | 7 | Specifies the Allocation Percentages Satisfaction Period. The constraints are enforced in a rolling horizon manner. Used with Enforce Sourcing Constraints enabled in specific plan options. |
| MSO: Split Planned Orders for Assigned Units | Yes / No | Yes | This profile option is used by Oracle Advanced Supply Chain Planning optimized plans only. It specifies if the planning engine should attempt to split planned orders such that they can be scheduled within a specific day. The valid values are: - Yes: Create more planned orders with quantities that can be scheduled by the resource units available within a given day. - No: The planning engine generates larger planned orders that may require a resource duration spanning several days. Note that the maximum number of resource units at the routing level will always be respected. |
| MSO: Spread Resource Consumption Within Optimization | Yes/No | Null (interpreted as No) | This profile specifies how the optimization engine should model resource consumption is modeled in optimization. Valid values are: - Yes: Consume resources at the first operation. This value provides improved optimization engine performance. - No: Consume resources at the operation to which they belong. This value provides improved optimization engine accuracy. |
| MSO: Substitute Item Penalty | Number > 0 | None | Defines an internal penalty weight for substitute item objective in supply chain optimization. |
| MSO: Supply Reschedule Window Size for Safety Stock Pegging | Integer > 0 | Null | This profile options provides an estimate of the number of days by which the supply and its associated demand (dependent demand) moves due to constraints. You can use this profile option to specify the number of days a specific supply can satisfy safety stock demand. |
| MSO: Supply Window Size | Integer >= 0 | Null | During priority pegging, supplies are sorted based on supply type, then smallest quantity, then by schedule date. The highest priority demands from the first demand window will peg to the sorted supplies in the first window if possible. When the supplies from one window are all pegged, the demand will peg to the highest sorted supply in the next window until all demands are pegged. This is stated as the number of calendar days including non-workdays. Null is treated as 1 in the Planning Engine. If the plan planning mode is Constrained (Without Detailed Scheduling), the planning engine uses this profile option as value 1 day. |
| MSO: Target Inventory Level % of Safety Stock | Between 0 and 100% | - | Use this option to specify target inventory levels. If no other method of calculation is defined for an item-organization target inventory level, the levels are based on the specified percentage of the safety stock level. |
| MSO: Transfer Quantity Threshold for Enforcing Hard Links | Null, Number between and including 0 and 1 | 0 | Use this profile option to instruct the planning engine to ignore the hard link constraints if a transfer quantity is less than or equal to this percent threshold of the corresponding order quantity. Valid values are - Number between 0 and 1: Ignores hard link constraints for transfer quantities less than or equal to this percent threshold - Null: Respects all hard link constraints regardless of the size of the transfer quantities |
| MSO: Upper Limit for Maximum Time Offset for Hard Links | Integer (including 0), Null | Null | Use this profile option to set an upper limit for the maximum time offset. If a maximum time offset is higher than this number, the planning engine uses this number instead of what you set. Valid values are: - Integer (including 0): Use this number - Null: Use 10,000,000 |
| MSO: Use Breaks in Calculation of Unconstrained Scheduling Windows | Yes/No | Yes | The planning engine calculates an unconstrained scheduling window for each resource activity and supply in a plan. The scheduling window is defined by the dates: - Unconstrained Earliest Possible Start Time (UEPST) - Unconstrained Earliest Possible Completion Time (UEPCT) - Unconstrained Latest Possible Start Time (ULPST) - Unconstrained Latest Possible Completion Time (ULPCT). If this profile option is Yes, the planning engine does not set any of these dates during a break even if the calculation places it there. If this profile option is No, the planning engine does set any of these dates during a break if the calculation places it there. This is a user level profile option. |
| MSO: Use Collections Start Time | Yes No, Use Input Demand Plan Start Time or Collections Start Time, Use Input Demand Plan Start Time or Plan Start Time |
Yes | Use this profile option to coordinate plan start date and collections start time. This affects how the plan calculates resource availability. Valid values are: - No: Always use plan start time. - Yes: Use collections start time. - Use Input Demand Plan Start Time or Collections Start Time: If there is an input demand plan, the planning engine uses the Input Demand Plan Start Time. Otherwise, it uses the Collections Start Time. - Use Input Demand Plan Start Time or Plan Start Time: The planning engine uses the Input Demand Plan Start Time. Otherwise, it uses the Plan Start Time. |
| MSO: Use Effectivity Date to Infer End Item Substitute Priority | Yes/No/Null | Null | Use this profile option to specify the method by which the planning engine selects end-item substitute items. Valid values are: - Yes: Use effectivity date from the substitute list for the demanded item. The substitute item with the earliest effectivity date has the highest priority in the substitution chain. - No/Null: Use substitution distance from the demanded item. The substitute item with the least distance has the highest priority in the substitution chain. |
| MSO: Use Existing Supplies in Alternate BOM/Subs. | 0, 1, 2, 3 | 0 | Use this profile option to specify how the planning engine should use supplies of substitute components and supplies of components in alternate bills of material to satisfy demands. Valid values are: - 0: Use supplies of both substitute components and supplies of components in alternate bills of material - 1: Use supplies of substitute components; do not use supplies of components in alternate bills of material - 2: Do not use supplies of either substitute components or supplies of components in alternate bills of material - 3: Use supplies of components in alternate bills of material; do not use supplies of substitute components |
| MSO: Use Item Shelf Life Days in Scheduling Buy or Make Orders | Yes/No | No | Use this profile option to instruct the planning engine whether to use the item shelf life days as a backup maximum time offset between the operation that produces an item and the operation that consumes it. Valid values are: - Yes: If the operation that produces the item does not have a maximum time offset, use item shelf life days as the maximum time offset. No: Do not use item shelf life days as a backup maximum time offset. |
| MSO: Use of Assigned Units in Scheduling | Variable / Fixed at Routing Value | Variable | Controls the number of resource units to be used when scheduling a resource activity. Valid values are: - Variable: Permits a choice ranging between a minimum of one unit and a maximum value equivalent to the assigned units specified on the routing for the item. - Fixed at Routing Value: Forces the scheduling engine to always choose the number of assigned units specified in the routing when scheduling a resource activity. It is recommended that you choose this option when you do not need to use the flexibility of the Variable option. Note: The assumption that the activity duration is less when more units are chosen is only valid for the basis type of Item specified in the Operation > Resources form. |
| MSO: Use Optimization and Decision Rules for Simulation | Yes/No | No | For online planner sessions against constrained plans with decision rules or optimized plans, select:
|
| MSO: Use Safety Lead Time | Yes/No | No | Use this profile option to instruct the planning engine how to plan material to be completed early as a safety buffer. Values are: - Yes: Use safety lead-time planning. The value in item attribute Safety Stock Percent is the safety lead-time in days; for example, if safety lead-time is two days, enter 200. - No: Use non-transient / transient safety stock planning. The value in item attribute Safety Stock Percent is a percent of demand. |
| MSO: Use SCO Time Aggregation | True/False | False | Determines whether the Planning Engine should use different aggregate time buckets than specified in the aggregation settings of the plan options. The Planning Engine use the values defined in the plan options. You can specify large values for daily and weekly buckets for Planning Engine output, but this increases Planning Engine calculation time. Valid values are: True: The Planning Engine uses aggregate time buckets specified in MSO: Optimization Daily Aggregation Buckets and MSO: Optimization Weekly Aggregation Buckets. The period time bucket is derived. False: The Planning Engine uses the same aggregate time buckets as specified in the Aggregation tab of the Plan Options window. |
| MSO: Use Sequencing Template | Yes/No | No | This profile option specifies whether Oracle Advances Supply Chain Planning tries to schedule activities in accordance with a determined preferred sequence of activities. If Yes, the planning engine determines a preferred sequence of activities on resources and tries to schedule activities in accordance with the sequence. This setting is recommended if the sequence dependent setup resource is the primary bottleneck. If No, the sequence of activities is determined more dynamically when scheduling other activities. This setting is recommended if there are multiple bottleneck resources. |
| MSO: Use Shift Definitions When Scheduling Lead Times | Yes/No | No | Determines whether the planning engine needs to take into account shift times for calculating lead-times on shipping, receiving, and carrier calendars. Values are: - Yes: Considers shift definitions for calculating lead-times on calendars in case of constrained plans. - No: Shift definitions are not considered when offsetting lead-times on calendars. If the plan planning mode is Constrained (Without Detailed Scheduling), the planning engine does not use this profile option. |
| MSO: Use up existing supply of primary components before substitute | Yes/No | Yes | Use this profile option to specify whether to use the supply of substitute components or the primary component first. Valid values are: - Yes: Use the supply of the primary component before using the supply of the substitute components - No: Use the supply of the substitute components before using the supply of the primary component |
The following table lists and defines the MSR profile options in Oracle Advanced Planning.