aps profile options 2205931

8/10/2019 Aps Profile Options 2205931

1/26

Profile Options A-1

AProfile Options

This appendix discusses profile options associated with Oracle Advanced Planning.Topics covered include:

Introductionon page A-2

MRP Profile Optionson page A-3 MSC Profile Optionson page A-8

MSO Profile Optionson page A-14

MSR Profile Optionson page A-24

INV Profile Optionson page A-25


2/26

Introduction

A-2 Oracle Advanced Planning and Scheduling Implementation and Users Guide

IntroductionThere are several types of profile options in Oracle Advanced Planning. The typesinclude:

MRP Profile Options

MSC Profile Options

MSO Profile Options

MSR Profile Options INV Profile Options

The following sections contain tables which list the profile option names and theircorresponding descriptions.

Special Considerations

Automatic Calculations

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 particularprofile option. These profile options are included in this appendix for informationpurposes only. If you must change these profile option values, do so only afterconsulting Oracle Development and Oracle Support.

Flexfield Attributes

Flexfield attribute profile options store the name of the flexfield column thatcontains the value in the corresponding table. For example, if the AggregateResource 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 notmodify it unless absolutely necessary.

Floating Point Precision

Certain quantities used by Oracle Advanced Supply Chain Planning have fractionalvalues. For internal processing purposes these quantities must have integer values.To resolve this problem, floating-point precision profile options act as internalmultipliers. When a fractional quantity is encountered it is multiplied by theappropriate floating-point precision profile option value, and the resulting integer is

processed by the Planning Engine.


3/26

MRP Profile Options

Profile Options A-3

There are several floating-point precision profile options. This enables greater

flexibility in controlling the precision with which to consider each quantity. It alsoprovides more flexibility to avoid numerical overflow on 32-bit platforms where theeach equivalent integer processed by the Planning Engine cannot exceed 2.1 x 109.The floating-point precision profile options are: Floating Point Precision for Usagesin Routing, Floating Point Precision, Floating Point Precision for TransportationCapacities (Weight and Volume), Floating Point Precision for Planning BucketEfficiency.

MRP Profile OptionsThe following table lists and defines the MRP profile options available with OracleAdvanced Planning.

Profile Option Name Valid Values Default Value Description

MRP: Activate OLP Not applicable Not applicable Not used by Oracle Advanced Planning. Used by Oracle

MRP.

MRP: ATP Assignment Set Text Null Indicates assignment set name for use with Supply ChainOrder Promising. Update this profile at site level in thesource instance. When set to Null, Oracle Global OrderPromising uses the assignment set from profile optionMSC: ATP Assignment Set from Oracle AdvancedPlanning instance.

MRP: ATP Database Link Text Null Determines whether distributed Order Promising is used.

MRP: Backlog ProgressTime-out

Not applicable Not applicable Not used by Oracle Advanced Planning. Used by OracleMRP.

MRP: Calculate ExcessExceptions on Time Fence

Yes/No Yes Indicates whether excess exceptions are calculated at thetime fence or up to the time fence.

MRP: Calculate MATODemand

Yes/No Yes Calculates demand at the manufacturing organizationwhen set to Yes for multi-level ATO. When set to no,demand is not calculated at the manufacturingorganization and consumption does not occur correctly.

MRP: Calculate Plan

Performance

Not applicable Not applicable Not used by Oracle Advanced Planning. Used by Oracle

MRP.MRP: Calculate SupplyDemand

Yes/No Yes Controls whether you calculate supply demand for anorder promising check. Can update at site level.

MRP: Category Set forBacklog Form

Text Null Indicates which items in the category set are displayed inthe Backlog Scheduling Workbench Tree Navigator. If novalue is entered, no items are displayed in the BacklogScheduling Workbench tree navigator. Can update at thesite level.


4/26

MRP Profile Options


MRP: Combine Sugg RepSchedules

Yes/No Yes Combines repetitive schedules, if scheduled back-to-backfor the same quantity. Used only by unconstrained plans.

MRP: Complete SupplyChain ATP


MRP: Compute Sales OrderChanges


MRP: Compute StandardMandatory Components for

ATO Models

Yes/No Yes Prevents mandatory component demands for ATO Modelscalculation during refresh snapshot process when set to

Yes. Omission of this process can increase performance.Must be set on the source instance.

MRP: Consume Fcst SetSummary


MRP: Consume Forecast Not applicable Not applicable Not used by Oracle Advanced Planning. Used by OracleMRP.

MRP: Consume MDS Not applicable Not applicable Not used by Oracle Advanced Planning. Used by OracleMRP.

MRP: Consume MPS Not applicable Not applicable Not used by Oracle Advanced Planning. Used by OracleMRP.

MRP: Create Time fence Yes/No Yes Set to Yes to create natural time fence for firm purchaseorders or work orders. When set to No, the PlanningEngine does not create a time fence at a firm purchaseorder or work order.

MRP: Cutoff Date OffsetMonths

Integer >= 0 6 Determines how many months of resource availabilityshould be computed for resources and simulation sets. Noresource availability is calculated beyond this horizon. For

constrained plans beyond this horizon, resource capacity isviewed as infinite. Set this value to your plan horizon.

MRP: Cutoff History Days Not applicable Not applicable Not used by Oracle Advanced Planning. Used by OracleMRP.

MRP: Debug Mode Yes/No No Enables debug messages within Oracle MasterScheduling/MRP and Oracle Advanced Supply ChainPlanning when set to Yes.

MRP: Default Criteria Set Not applicable Not applicable Not used by Oracle Advanced Planning. Used by Oracle

MRP.MRP: Default DRP PlanName


MRP: Default Forecast Date Not applicable Not applicable Not used by Oracle Advanced Planning. Used by OracleMRP.

MRP: Default ForecastName


MRP: Default Plan Name Not applicable Not applicable Not used by Oracle Advanced Planning. Used by Oracle

MRP.



5/26

MRP Profile Options

Profile Options A-5

MRP: Default ScheduleName


MRP: Default SourcingAssignment Set


MRP: Demand Time FenceDays


MRP: Enhanced Exception Not applicable Not applicable Not used by Oracle Advanced Planning. Used by OracleMRP.

MRP: Environment variableto set path for MRP files

Text Null Specifies appropriate path for the MRP files. If this profileoption is not used, files are written to $MRP_TOP/$APPLOUT.

MRP: Firm Internal ReqTransferred to OE

Yes/No Yes When set to Yes, all internal requisitions transferred toOracle Order Management are automatically firmed byOracle Advance Supply Chain Planning. No reschedule inor out recommendations are generated for these internalrequisitions in subsequent plan runs. When set to No, thegenerated reschedule in/out recommendations for internal

requisitions are transferred to Oracle Order Management.Automatically changes dates of internal sales orders in thePlanning Workbench to reflect internal requisition dates inreschedule in/out recommendations minus transit leadtimes. Users must set up procedures to reschedule internalrequisitions and internal sales orders in the sourceinstance.

MRP: Firm Planned OrderTime Fence

Yes/No Yes Set to Yes for firm planned orders to create a natural timefence. When set to No, the Planning Engine does not create

a time fence at a firm planned order.MRP: Firm Requisitionswithin time fence

Yes/No No Set to Yes to prevent requisitions from rescheduling withinthe time fence.

MRP: Include Schd Rcpts inUse-up

Yes/No No If set to Yes it includes scheduled receipts when computingthe eco use-up date.

MRP: Include SubstituteComponents

Yes/No No Indicates whether to include substitute components inOrder Promising calculation. Can update at the site level.

MRP: Interface Table

History Days


MRP.MRP: Maintain OriginalSchedule Version


MRP: MPS Relief Direction Not applicable Not applicable Not used by Oracle Advanced Planning. Used by OracleMRP.

MRP: New PlannerBackward Compatibility


MRP: Old Sales Orders

Cutoff Days


MRP.



6/26

MRP Profile Options


MRP: Perform PlanningManager Functions in Loads


MRP: Plan RevenueDiscount Percent

Text Null Specifies the average discount percent applied to all itemsin a plan. This value is a key performance indicator used tocalculate performance in a plan for Business Intelligencereports.

MRP: Plan Revenue PriceList

Numeric Null Specifies the sales order price list applied to items in aplan. Used to calculate the plan margin key performanceindicators for Business Intelligence reports.

MRP: Planner Batch Size Not applicable Not applicable Not used by Oracle Advanced Planning. Used by OracleMRP.

MRP: Planner Workers Not applicable Not applicable Not used by Oracle Advanced Planning. Used by OracleMRP.

MRP: Planning ManagerBatch Size


MRP: Planning ManagerMax Workers


MRP: Planning ManagerRun First Time


MRP: Purchasing ByRevision

Yes/No Yes When set to Yes, creates purchase requisitions using thelatest revision date on the item.

MRP: Purge Batch Size Numeric 25000 Used by Oracle Advanced Supply Chain Planningcollections and Snapshot.

MRP: Recommend action

within PTF

Yes/No Yes Used by unconstrained planning. When set to Yes

recommendations are generated inside the planning timefence.

MRP: Repetitive Past DueSupply Days




7/26

MRP Profile Options

Profile Options A-7

MRP: Requisition LoadGroup Option

All on One,Buyer, Planner,Vendor,Category, Item,One Each

Null Indicates group by option used when loading requisitionsusing the Planner Workbench form. Valid values are:

All on One: Creates one purchase requisition for allrecommended orders.

Buyer: Creates one purchase requisition for buyer.Within each requisition, creates one line for eachplanned order for the buyer.

Planner: Creates one purchase for planner. Withineach requisition, creates one line for each plannedorder for the buyer.

Vendor: Creates one purchase requisition for eachvendor. Within each requisition, creates one line foreach planned order for the vendor.

Category: Creates one purchase requisition for eachcategory of items. Within each requisition, creates oneline for each planned order for the category.

Item: Creates one purchase requisition for eachinventory item. Within each requisition, creates oneline for each planned order for the item.

One each: Creates a purchase requisition for eachplanned order.

MRP: Retain Dates WithinCalendar Boundary

Yes/No No Determines whether to pull dates outside the calendarboundary into calendar horizon.

MRP: RHX Check Profile Not applicable Not applicable Not used by Oracle Advanced Planning. Used by OracleMRP.

MRP: Snapshot Pause for

Lock (Minutes)


MRP.

MRP: Snapshot Workers Integer >= 0 1 Determines number of workers launched by the snapshotmonitor. When set 1, the Snapshot runs as a single-threaded process. Snapshot workers collect data on bills ofmaterial, work in process, on- hand quantities, purchasing,firm planned orders, routings, and work-in-process jobresource requirements.

MRP: Sourcing RuleCategory Set


MRP: Time Fence Warning Not applicable Not applicable Not used by Oracle Advanced Planning. Used by OracleMRP.

MRP: Trace Mode Yes/No No Determines whether trace is enabled for all OracleAdvanced Supply Chain Planning processes.

MRP: Use Direct LoadOption

Yes/No No Determines whether load worker can use the direct loadoption instead of conventional loads.



8/26

MSC Profile Options


MSC Profile OptionsThe following table lists and defines the MSC profile options available with OracleAdvanced Planning.

MRP: Use Ship Arrived Flag Yes/No No Determines whether sales orders are automatically viewedas arrived at a customer site after transit lead time hasexpired. You can an manually update the ARRIVED_FLAGin SO_PICKING_HEADERS. Used when a customer ismodeled as an organization. Valid Values are:

Yes: Use arrived flag in SO_PICKING_HEADERS.

No: Use transit time between source and thedestination organizations.


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: Aggregate ResourceName Flexfield Attribute

Integer >= 0 Null Stores flexfield column name that contains its value in thecorresponding table. See Flexfield Attributesfor moreinformation.

MSC: Apply Lot Modifiersin Weekly/Period Buckets

Yes/No Null Determines whether order modifiers are considered whencreating 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 thesecalculations

MSC: ATP AllocationMethod

Null Determines allocation method used by ATP. In case ofuser-defined allocation method, ATP uses percentagesdefined in allocation rule. When set to demand priority,ATP pre-allocates supply/demand based on plan'spegging. If null, GOP assumes it as User-definedAllocation Percentage.

MSC: ATP Assignment Set Text Null Indicates name of the assignment set to use for OracleGlobal Order Promising. Can update at site level in thePlanning instance. Oracle Global Order Promising uses this

assignment set if profile MRP: ATP Assignment Set is Nullon the ERP instance.

MSC: ATP CapacityAllocation

Yes/No No Set to Yes when upgrading to Oracle Applications Release11i. Valid values are:

Yes: Current behavior continues.

No: No Department Resource or Resource Groupassignment type on the Assign Allocation Rule form,and you can only enter item on the View AllocationForm.



9/26

MSC Profile Options

Profile Options A-9

MSC: ATP Debug Mode Debug Only,Debug andDatabase Trace,Database TraceOnly, None

Null Determines whether to enable debug messages withinOracle Global Order Promising. Can update at the userlevel. Valid values are:

Debug Only: ATP generates a log file for an ATPrequest.

Debug and Database Trace: ATP generates a log fileand a database trace file.

Database Trace Only: ATP generates a database tracefile.

None: ATP does not generate log file or database tracefile.

MSC: Auto-ReleaseCompression DaysTolerance

Integer >= 0 Null Indicates the number of compression days allowed for theautomatic release of planned orders.

MSC: Batchable Flag Integer >= 0 Null Stores the attribute column value that contains the flag forresources to indicate whether they are batch resources. SeeFlexfield Attributesfor more information.

MSC: Batching Window Integer >= 0 Null Stores the attribute column value that contains the flag forresources to indicate the size of the batching window. SeeFlexfield Attributesfor more information.

MSC: Choice of Item forWhich to Create Supplies inSubstitute Relationship

Demanded Item,Highest LevelItem, FollowItem Attributes

DemandedItem

Determines the item for which Oracle Global OrderPromising and Oracle Advanced Supply Chain Planningcreates planned supplies when item substitutionrelationships are specified.

When set to Follow Item Attribute and the item attributeCreate 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 thisprofile option is set to Highest Level Item, it is expectedthat Oracle Advanced Planning creates supply for item C.Item C must be enabled in the organization where you aretrying to create supply. If item C is not enabled in theorganization, Oracle Advanced Planning creates supply foritem B (the next highest level item in the substitutionchain) and does not create supply for item C.

MSC: Class Hierarchy Demand/Customer Demand Indicates which allocation hierarchy to use. Valid valuesare:

Demand Class: User-defined, single-level hierarchy.

Customer Class: Three levels: customer class,customer, and site.

Can update at the site level.



10/26

MSC Profile Options


MSC: Collection Windowfor Trading Partner Changes(Days)

Integer >= 0 Null Used by Oracle Advanced Supply Chain Planningcollections. Specifies the number of days backwards thatchanges in customer names, customer sites, vendors, andvendor sites are collected. If null, then all changes arecollected. Used when collections for the trading partnersentity is run in complete mode.

MSC: Compute ProjectException

Yes/No Yes This profile option determines whether to generate projectspecific exceptions when running a project based plan. Yes:Enable the generation of project specific exceptions.No:

Disable the generation of project specific exceptions.Thedefault value is Yes.

MSC: Configuration Not applicable Not applicable Used by Oracle Collaborative Planning.

MSC: Consume ForecastInside Demand Time Fence

Yes/No No When set to No, demand time fence control isimplemented prior to forecast consumption. Forecastentries in the demand time fence are dropped as demandstatements and not used for consumption.

When set to Yes, forecast consumption occurs prior toenforcing demand time fence control. The forecast entries

within the demand time fence are used for consumptionbut not as demand. After consumption, demand quantityfor all the forecast entries within the demand time fence iszero.

MSC: Cost of Using a BOM/Routing Flexfield Attribute

Not applicable Not applicable Not used.

MSC: Day UOM Text Null Supports the unit of measure conversion required forOracle Advanced Supply Chain Planning resource

batching calculations. Batching Window is considered in

days, but users can specify the batching window in a unitof measure other than days. The profile option establishesa standard for the Day unit of measure. Users must specifya unit of measure that represents the value Day using thisprofile option. Users must also set up a unit of measureconversion between the unit of measure used for resourcesand the Day unit of measure specified here.

MSC: Default WorkbenchHeight

Specify the default workbench height. Can be defined atthe site level.

MSC: Default WorkbenchWidth

Specify the default workbench width. Can be defined atthe site level.

MSC: Degree of Parallelismfor Index Creation

Integer >= 0 0 Controls the use of parallel workers in data collections.Specifies how many parallel workers to use when creatingindexes.

MSC: Demand PriorityFlexfield Attribute

Integer >= 0 Null Stores the value of the attribute column that controls thedemand priority. See Flexfield Attributesfor moreinformation.



11/26

MSC Profile Options

Profile Options A-11

MSC: Enable Allocated ATP No Use this profile options to indicate whether AllocatedOrder Promising is used. Can update this profile at the sitelevel.

MSC: Enable ATP SummaryMode

Yes/No No Enables summarization of supply and demand datafollowing the data collection and plan launch processes.Valid values are:

Yes: Enable ATP Summary Mode

No: Disable ATP Summary Mode.

MSC: Enable ATP Workflow Controls generation of workflow notifications to send toplanner. Valid values are:

Yes: Generate ATP Workflow Notifications

No: Do not generate ATP Workflow Notifications

MSC: Enable EnhancedSourcing

Yes/No Yes Enables enhanced sourcing logic that considers historicalallocations and allows the splitting of planned orders toachieve target sourcing percentages. Rank 2 buy sourcesare considered if supplier capacity is exhausted for rank 1sources.

MSC: Forecast PriorityFlexfield Attribute

Integer >= 0 Null Stores the value of the attribute column that will controlthe forecast priority. See Flexfield Attributesfor moreinformation.

MSC: Hour UOM Text HR Specifies unit of measure. Can be defined at the site level.

MSC: Launch Analyze PlanPartition

Yes/No Yes Launches the concurrent request Analyze Plan Partition.

MSC: Map Server Host Not applicable Not applicable Not used.

MSC: Map Server Port Not applicable Not applicable Not used.

MSC: Maximum Capacity Integer >= 0 Null Stores the value of the attribute column that contains thevalue for batch resources which specifies the maximumcapacity. See Flexfield Attributesfor more information.

MSC: Minimum Capacity Integer >= 0 Null Stores the value of the attribute column that contains thevalue for batch resources which specifies the minimumcapacity. See Flexfield Attributesfor more information.

MSC: Net Change Temp Dir Text Null Stores the location of image cache used in the Plan

Comparison Report. Indicate the location in the followingformat: @ where

This must match the absolute path of the OA_MEDIAenvironment variable and is the name of asubdirectory under the OA_MEDIA directory. Thesubdirectory must have write permissions for all.



12/26

MSC Profile Options


MSC: New PlannerBackward Compatibility

Yes/No No Determines whether phantom items are planned asstandard items or if they are planned to components.

Yes: Phantoms are planned as standard items.

No: Phantoms are exploded to their components andsupplies are not planned for the phantom.

MSC: Operator CompanyName

Not applicable Not applicable Used by Oracle Collaborative Planning.

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 atthe site level.

MSC: Planning Currency Not applicable Not applicable Not used.

MSC: Priority for SubstituteItems Flexfield Attribute

Integer >= 0 Null This profile option stores the name of the flexfield columnthat contains the value in the corresponding table. SeeFlexfield Attributesfor more information.

MSC: Priority for SubstituteItems Flexfield Attribute

Integer >= 0 Null This profile option stores the name of the flexfield columnthat contains the value in the corresponding table. See

Flexfield Attributesfor more information.MSC: Priority of AlternateResources for an OperationFlexfield Attribute


MSC: Purge Stg Tbl Cntrl Yes/No No Truncates the staging table during data collection process.When running data collections for multiple instancessimultaneously, set to No to avoid data loss. Set to Yes toconserve disk space when running data collections forsingle instances, or as separate processes for multipleinstances.

MSC: Release WIP Dtls ifOrder Date different thenBOM Revision Date

Yes/No Yes If the value is set to Yes, then WIP details are released evenif the New WIP Start Date is different than the BOMRevision Date. If the value is set to No, then the WIPdetails are not released if the new WIP Start Date isdifferent than the BOM Revision Date. In this case, OracleWIP explodes the details effective as of the job start date.

MSC: Released Only ByUser

Yes/No No Controls the behavior of Planner's Workbench whenreleasing orders or schedule changes. Can restrict selectionof changes to the specific user or from all users. Valid

values are:

Yes: Restrict the releases or schedule changes selectedto those created by this User.

No: Do not restrict releases or schedule changesselected to those created by this user. Implementingchanges select changes made by any user of this plan.

MSC: Resource Group for aLine Flexfield Attribute




13/26

MSC Profile Options


MSC: Safety Stock Project Text Null Specifies the default project charged for all safety stockdemands. Oracle Advanced Supply Chain Planningassigns the project specified for all safety stock demandswhich originate from non-MRP planned safety stock.When safety stock requirements are specified in OracleInventory for specific projects, the profile option value isnot honored. The list of values for this profile option isrestricted to projects specified in Oracle Projects. Thisprofile option is enabled at Project/Seiban level, not at thetask level.

MSC: Sales Orders OffsetDays

Integer >= 0 Null Completed sales orders are collected within the offsetduration. For example, if Sales Orders Offset Days is set to90, all the sales orders completed in the past 90 days arealso collected. Can be defined at the site level. A Null valuemeans all closed sales orders are collected.

MSC: Share Plan Partitions Not applicable Not applicable The profile option is a work-around for test/demoscenarios where you expect the creation of many plans bydifferent testers and demonstrators. This profile option isnot meant for production use by customers. When enabled

the number of plan partitions parameter to the concurrentprogram mentioned becomes irrelevant; only one partitionis created for a plan (you can enter 1). This profile optionshould only be changed by the system administrator.

If the MSC:Share Plan Partitions profile is turned on, youmust run the Create APS Partitions program afterwards sothat it can create the partition that every plan shares.

MSC: SimultaneousResource Sequence FlexfieldAttribute

Integer >= 0 Null This profile option stores the name of the flexfield columnthat contains the value in the corresponding table. Thissetup is only performed during application install.

MSC: Source Setup Required Not applicable See AutomaticCalculations.

Internal profile used by the software during collectionsconfiguration. Do not manually update.

MSC: Sourcing History StartDate Offset (in months)

Integer >= 0 Null Offsets the starting date of sourcing history calculationsand is used in with collections parameters Purge SourcingHistory = Yes and Recalculate Sourcing History = Yes.These settings delete, then calculate Sourcing History fromthe Start date determined by the profile option value (inmonths). System performance can be degraded when thereis a high value for this profile option and a high volume of

source transaction data.

MSC: Sourcing RuleCategory Set

Text Null Determines the category set used in Oracle AdvancedSupply Chain Planning in the assignment set form. If thisnot set, the user cannot assign sourcing rules and bills ofdistribution at the Category- Instance-Organization andCategory-Instance level.



14/26

MSO Profile Options


MSO Profile OptionsThe following table lists and defines the MSO profile options available with OracleAdvanced Planning.

MSC: Sourcing VarianceTolerance

Numberbetween 0 and 1

0.05 (5%) Used when Enforce Sourcing Constraints is enabled for aplan. This percentage value establishes a threshold fortriggering exception messages if sourcing allocations areviolated. Exceptions are generated if the difference

between the user-specified sourcing allocation percentagesand the plan-derived allocation percentages is greater thanthe Sourcing Variance Tolerance. The profile option isentered as a number and converted to a percentage. If theuser enters 0.5 it becomes 50%.

MSC: Split Planned Ordersfor Scheduling Flexibility

Yes/No Yes Determines whether planned orders that were split duringoptimization processing will be consolidated prior toscheduling. Possible values are: Yes: Do not consolidateorders prior to scheduling.No: Consolidate orders whenpossible prior to scheduling.

MSC: Temp Index ExtentSize (Bytes)

Number 1000000 (1meg)

Controls the size of the next extent when creatingtemporary tables while running collections or copy plan.The recommended value is calculated as the size of theindex / 5. The default value is 1000000 (1 meg).

MSC: Temp Table ExtentSize (Bytes)

Number 1000000 (1meg)

Controls controls the size of the next extent when creatingtemporary tables while running collections or copy plan.The recommended value is calculated as the size of thetable / 5. The default value is 10000000 (10 meg).

MSC: Unit of Measure Text Null This is the unit of measure for values specified for batchresource Maximum Capacity and Minimum Capacity.

MSC: Vertical View DefaultQuery

Not applicable Not applicable Used by Oracle Collaborative Planning.

MSC: VMI Default Query Not applicable Not applicable Used by Oracle Collaborative Planning.

MSC: Wait Time to ObtainLock on Table/Partition forSnapshot Delete Worker

Number >=0 60 seconds Time (in seconds) the Snapshot Delete Worker waits toobtain a lock on a table/partition before aborting.Releasing plans recommendations through Workbench andrunning Purge Plan can cause locks on the table/partitionpreventing the Snapshot Delete Worker from obtaining alock. If the timer expires, the program prints the followingmessage in the log file: Unable to obtain a lock on table.



15/26

MSO Profile Options



MSO: Additional DemandSlices for Shared SupplyRescheduling

Number >= -1 0 Controls the maximum number of slices to which supplycan be rescheduled. Accepts values from -1 to maximumnumber of slices. Controls the maximum number of slicesto which supply can be rescheduled. Supply is notrescheduled 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 willreschedule if needed in slice 3 and 4 (rescheduled 2times, in slice 3 and 4) and will not reschedule in slice 5and 6.

MSO: Allow PartialDemand Completion

All End Demands,Sales Orders orNone

None Enables supply orders to individually schedule forpartial satisfaction of a demand when demand is splitacross several supply orders. Valid values include:

All End Demands: Enable Partial DemandSatisfaction for all independent demands (forecasts,sales orders, and MDS entries).

Sales Orders: Enable Partial Demand Satisfaction forall Sales Order demand only.

None: Schedules all supplies to coincide withcompletion date (latest supply date) to meetdemand.

This functionality can be enabled for all independentdemands or only for Sales Orders.

MSO: Alternate ProcessPenalty Number > 0 See AutomaticCalculations. Specifies weight for alternate process objective inoptimization. This value is specified as a number greaterthan 0, and is an internal value.

MSO: Alternate ResourcePenalty

Number > 0 See AutomaticCalculations.

Specifies weight for alternate resource objective inoptimization.

MSO: Alternate SourcePenalty


Specifies weight for alternate source objective inoptimization.

MSO: Calculate ConstraintExceptions

Yes/No No Determines whether constraint exceptions are calculatedfor plans with Enforce Capacity Constraints selected.

MSO: Check RedundantConstraints

0,1 See AutomaticCalculations.

Specifies location and removal of redundant constraints.


16/26

MSO Profile Options


MSO: Choice of Supply forSubstitution

All Supplies,Excess Supplies

All Supplies Determines which supplies are considered by thePlanning Engine for substitution. Valid values are:

All Supplies: Oracle Advanced Supply ChainPlanning takes supplies belonging to substituteitems even when there is demand for substituteitems. Demand priorities drive the allocation.

Excess supplies - Oracle Advanced Supply ChainPlanning takes supplies belonging to substituteitems only if it finds that the supply from the

substitute item is in excess. Oracle AdvancedPlanning performs regular netting logic within theSubstitution Window and find that excess can beoffered for substitution. The native demandsatisfaction has priority only within the SubstitutionWindow. After the Substitution Window demandpriorities drive the substitution.

Oracle Order Promising does not honor this profileoption. Oracle Order Promising always honors nativedemand satisfaction logic.

MSO: CPLEX CrashParameter

-1, 0, and 1 See AutomaticCalculations.

Determines how objective coefficients are used to selectbasis.

MSO: CPLEX RefactorRate

Integer >= 0 See AutomaticCalculations.

Specifies the value of the parameter to control therefactor rate.

MSO: CPLEX ScalingFactor

-1, 0, 1 See AutomaticCalculations.

Contains the scaling factor in the Planning Engine.

MSO: Default ForecastPriority

Integer >= 0 100000 Contains default priority value for forecasts and is usedby the Scheduling Engine to determine when to schedule

the forecast. Can be defined at the site level.MSO: Default Sales OrderPriority

Integer >= 0 10000 Contains default priority value for sales orders. Used bythe Scheduling Engine to determine when to schedule asales order. Can be defined at the site level.

MSO: Demand SizeTolerance PCT BeforeSplitting Planned Orders

Number >=0 Null Creates a threshold percentage that causes PlannedOrders to split prior to scheduling (if the remainingunallocated quantity of a planned order is greater thanthe remaining unallocated quantity of the peggeddemand). Not used if order modifiers exist for an item.

Valid values are positive decimal quantities (.5 isinterpreted as 50%).

MSO: Demand WindowSize

integer >=0 Null During priority pegging, demands are sorted based onthe demand priority within the demand window. Afterthese demands are fully pegged, Oracle AdvancedSupply Chain Planning sorts all demands in the nextwindow by priority. This is specified as the number ofworking days. With a value of 10, the first demandwindow is between the start date of the plan or the firstdemand date +10 days. The default (Null) is treated as 1

in the Planning Engine.



17/26

MSO Profile Options


MSO: Dual SimplexParameter

0, 1, 2, 3, 4 See AutomaticCalculations.

Gradient parameter for dual simplex.

MSO: Enable DecisionRules

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.

MSO: FirmOperations/Orders 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. Anyoperation with a start date outside of the Planning TimeFence is not considered firm and can be moved. When setto No, operations with start dates in the Planning TimeFence can be rescheduled out.

MSO: Firm SupplyAllocation Window(Backward days)

Integers >=0 1 The allocation of firm supplies to demands is based ondemand priorities within the Firm Supply Allocationwindow. Set this window using system level profileoptions. This window is derived dynamically for eachdemand; it starts with the demand due date and goes

backwards to the window size.

MSO: Firm SupplyAllocation Window(Forward days)

Integers >=0 Null The allocation of firm supplies to demands is based ondemand priorities within the Firm Supply Allocationwindow. Set this window using system level profileoptions. This window is derived dynamically for eachdemand; it starts with the demand due date and movesforwards to the window size. This pegs demands to firmsupplies that are scheduled after the demand date. Aftersearching backward, it searches forward by the numberof days set by this profile option, pegging the supplywith the nearest (earliest) schedule to the unallocateddemand quantity. This can cause supplies to be late forthe demand due date.

MSO: Floating PointPrecision for Increments ofShift Start/End TimesWithin a Planning Bucket


MSO: Floating PointPrecision for Order Q


MSO: Floating PointPrecision for OrderQuantities

Number > 0 100 Internal multiplier for order quantities. Can change thevalue depending on precision desired. Verify that theproduct of the floating point precision and the numberdoes not exceed the maximum integer size handled bythe machine. See Floating Point Precisionfor moreinformation.

MSO: Floating PointPrecision for PlanningBucket Efficiency

Not applicable Not applicable This has been changed to MSO: HLS GranularityPrecision.



18/26

MSO Profile Options


MSO: Floating PointPrecision forTransportation Capacities(Volume)

Number > 0 100 Internal multiplier for transportation lane capacities byvolume, by day. Can change the value depending onprecision desired. Verify that the product of the floatingpoint precision and the number does not exceed themaximum integer size handled by the machine. SeeFloating Point Precisionfor more information.

MSO: Floating PointPrecision forTransportation Capacities(Weight)

Number > 0 100 Internal multiplier for transportation lane capacities byweight, by day. Can change the value depending onprecision desired. Verify that the product of the floatingpoint precision and the number does not exceed themaximum integer size handled by the machine. SeeFloating Point Precisionfor more information.

MSO: Floating PointPrecision for Usage inRoutings

Number > 0 100 Internal multiplier for order quantities. Can change thevalue depending on precision desired. Verify that theproduct of the floating point precision and the numberdoes not exceed the maximum integer size handled bythe machine. See Floating Point Precisionfor moreinformation.

MSO: Global Batchable

Flag

Yes/No No Enables resource batching functionality for order

scheduling. Valid values are:

Yes: Enable resource batching functionality.

No: Do not enable resource batching functionality.

MSO: Global Time Limit Number > 0 See AutomaticCalculations.

Parameter used to set global time limit for haltingoptimization.

MSO: Heuristic type Classic, LookAhead

Classic Determines which heuristic to use. Valid values are:

Classic: Corresponds to the default heuristic whichproceeds priority by priority, and schedulesdemands just in time to minimize lateness.

Look Ahead: Corresponds to the look-aheadheuristic. This heuristic reserves time for lowerpriorities, so the schedule begins with the tasks ofhigher priorities.

Can be defined at the site level.

MSO: HLS Flat Files Path Text Null Specifies the directory to store the Planning Enginedebugging data files.

MSO: HLS GranularityPrecision

number > 0 100 Converts floating point numbers to integer values.Determines the resolution with which date/times anddurations are considered by Oracle Advanced SupplyChain Planning. Can be defined at the site level.

MSO: Inventory CarryingCosts Percentage

A numberbetween 0 and 100(%)

Null Specifies inventory carrying costs percentage for all itemsin the plan. Can be defined at the site level. You canupdate this value. The inventory carrying cost is apercent (if the user enters 10, the value is 10%).



19/26

MSO Profile Options


MSO: List Size for PricingCandidates

Integer > 0 See AutomaticCalculations.

Parameter to set the list size for pricing candidates.

MSO: LP Constraint BatchSize


MSO: LP MarkowitzCoefficient

Number between0.0001 and 0.99999

See AutomaticCalculations.

Sets the Markowitz Coefficient.

MSO: LP OptimizationAlgorithm

0=primal simplex,1=dual simplex,

2=hybrid barrierprimal, 3=hybrid

barrier dual

0 Determines which optimization algorithm is used. Canbe defined at the site level. See Automatic Calculations

for more information on the default value for this profileoption.

MSO: Maximum ActivityDuration


Defines the Planning Engine maximum activity durationin days. All requirements should be less in duration thanthis. If null, the planning horizon duration is used.

MSO: MaximumAllowable Days Late

Integer > 0 300 Limits the number of days by which a demand orunfirmed scheduled receipt can be moved out whenoptimization is turned on. This value is used only to

improve performance and reduce the size of the plan forthe optimization component of the Planning Engine.Scheduling moves demands and unfirmed scheduledreceipts out as long as necessary. Can be defined at thesite level.

Note: Set this to a number as large as the typical planninghorizon to avoid unusual results.

MSO: Maximum Demandsper Group

Integer > 0,smaller than thesize of a slice

5 Determines the maximum number of demands that canbe grouped together for scheduling. Within a group, thedefault heuristic can try different orders among the

demands. Can be defined at the site level.

MSO: Maximum Demandsper Slice

Integer >= 0 100 Determines the number of demands in a slice. Enablesthe Scheduling Engine to resolve interactions of demandswithin a slice. Supplies shared between demands arescheduled better when the demands are in the same slice.However, slices that are too large slow down theScheduling Engine use more memory. Can be defined atthe site level.

MSO: Maximum Number

of Prepones

Number > 0 10 Scalability factor for the Scheduling Engine. The

Scheduling Engine attempts to schedule the operations indifferent orders to find a solution. Limits the number oftimes the Scheduling Engine attempts to schedule anoperation. If there are many components for some itemsor many small supplies answering a demand, thenumber of orders is larger; reduce this parameter. Can bedefined at the site level. See Automatic Calculationsformore information.



20/26

MSO Profile Options


MSO: Maximum Numberof Pull for Operation

Integer > 0 8 operations When an operation cannot be scheduled on a certain day,the Scheduling Engine attempts to schedule it on anearlier date (for backward scheduling). This profileoption controls how many days are tried in this manner.Many days result in lower performance. Can be definedat the site level. See Automatic Calculationsfor moreinformation.

MSO: MaximumOperations Per Slice

Integer > 0 3000 operations Determines the number of operations which can bescheduled in a slice. Limits the problem size in a slice andcan be a limiting factor in determining the number ofdemands that can be scheduled in a slice

MSO: Maximum ResourceOver-Capacity

Number > 0 5 Assigns resource slacks when it does not find theresource available and it is forced to use slacks. TheScheduling Engine initiate the resource slack from 0 tomaximum assigned units and will jump to this number ifno solution is possible. This limits the number of tries toassign the resource slack. Can be defined at the site level.See Automatic Calculationsfor more information.

MSO: Maximum Simplex

Iterations

Integer > 0 See Automatic

Calculations.

Parameter to set the maximum number of simplex

iterations.

MSO: Multiplier To DeriveSupply AllocationWindow

Number >= 0 Null You can set the Firm Supply Allocation window usingthe profile option MSC: Firm Supply Allocation Windowor you can use the manufacturing lead time and theprofile option MSC: Multiplier to Derive Firm SupplyAllocation Window. If you specify any value for the latterprofile option, the information you enter for MSC: FirmSupply Allocation Window is ignored. If the product ofthis multiplier and cumulative manufacturing lead-timeis a fractional quantity, the number is rounded up to the

next integer.

MSO: Net All FirmSupplies Before CreatingPlanned Orders

Yes/No No Nets all firmed supply available in any future periodbefore creating new planned orders.

MSO: Network routingcycle time coefficient

Numeric 2 Used by the Scheduling Engine to calculate the windowof time allocated to schedule a network flow. This is usedin conjunction with NFL Fixed Time Window. Thewindow of time is (coefficient * + fixed_window). Can be defined at the site level.

MSO: Network routingfixed time window

Number > 0 0 Used by the Scheduling Engine to calculate the windowof time allocated to schedule a network flow. This is usedin conjunction with NFL Cycle Time Coefficient. Thewindow of time is (coefficient * + fixed_window). Can be defined at the site level.

MSO: NFL BACKWARDCOMPRESSION PCT

Between 10 and100%

100% Defines the percentage of the actual resources capacitythat the network flow takes into account. A value under100 percent tends to offload more activities to alternateresources. Can be defined at the site level.



21/26

MSO Profile Options


MSO: NFL FORWARDCOMPRESSION PCT

Between 10 and100%

100% Defines the percentage of the actual resources capacitythat the network flow takes into account. Use in forwardphase to force the system to use alternates and limit thetardiness of activities. Can be defined at the site level.

MSO: Optimization DailyAggregation Buckets

Integer > 0 Null Specifies the Daily Aggregation Time Bucket to be usedby the Planning Engine if the profile option MSO: UseOptimization Internal Time Aggregation is set to True.

MSO: OptimizationWeekly Aggregation

Buckets

Integer > 0 Null Specifies the Weekly Aggregation Time Bucket to be usedby the Planning Engine if the profile option MSO: Use

Optimization Internal Time Aggregation is set to True.

MSO: Peg By-productSupplies

Yes/No Yes Yes: Pegging is considered when scheduling operationswith by-product supply. Scheduling of these operationsrespects demand for the by-product and demand for themain product. After scheduling these operations, the

by-product supply date is updated to reflect theoperation scheduled date.

No: By-Product Supplies are not pegged to demands Forconstraint-based plans. Set this profile option to No with

items that are components on the supply chain bill ofmaterials and that are by-product on a different level ofthe same supply chain bill of materials. Selecting Noprevents the planning engine from continuous looping

between the component demand and the by-productsupply.

MSO: Penalty Cost Factorfor Exceeding ItemMaterial Capacity FlexfieldAttribute

Integer >= 0 Null Stores the flexfield column name that contains the valuein the corresponding table. Setup performed only duringapplication install. See Flexfield Attributesfor moreinformation.

MSO: Penalty Cost Factorfor Exceeding MaterialCapacity

Number >= 0 Null Defines a penalty cost factor for exceeding materialcapacity.

MSO: Penalty Cost Factorfor Exceeding OrgMaterial Capacity FlexfieldAttribute


MSO: Penalty Cost Factorfor Exceeding OrgResource CapacityFlexfield Attribute


MSO: Penalty Cost Factorfor Exceeding OrgTransportation CapacityFlexfield Attribute




22/26

MSO Profile Options


MSO: Penalty Cost Factorfor Exceeding ResourceCapacity FlexfieldAttribute


MSO: Penalty Cost Factorfor ExceedingTransportation CapacityFlexfield Attribute


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 safetystock. Can be defined at the site level.

MSO: Penalty Cost Factorfor Late Forecasts FlexfieldAttribute


MSO: Penalty Cost Factorfor Late Item DemandsFlexfield Attribute

Integer >= 0 Null Stores the flexfield column name that contains the valuein the corresponding table. Setup performed only duringapplication install. See Flexfield Attributesfor more

information.MSO: Penalty Cost Factorfor Late Org DemandsFlexfield Attribute


MSO: Penalty Cost Factorfor Late Sales OrdersFlexfield Attribute


MSO: PreprocessingAggregator Fill


Preprocessor aggregator fill.

MSO: PreprocessingAggregator Limit


Parameter to control preprocessing aggregator limit.

MSO: Preprocessing Flagfor LP Matrix

0 and 1 See AutomaticCalculations.

Contains the presolve indicator.

MSO: Preprocessor LPCompression


MSO: Primal SimplexParameter

-1, 0, 1, 2, 3, 4 See AutomaticCalculations.

Gradient parameter for primal simplex algorithm.

MSO: Primal/DualPreprocessing Reduction

0, 1, 2, 3 See AutomaticCalculations.

Used by optimization.

MSO: Queue Time Factor Number >= 0 None Increases item lead time in optimization, so that leadtime values are close to those used in the SchedulingEngine. Optimization lead time is padded to includequeue time.



23/26

MSO Profile Options


MSO: Reschedule SharedSupply to InfluenceBatching

Yes/No No Determines whether the Planning Engine schedulesshared supplies early to avoid item-based resourceconstraints prior to batch resources. Valid values are:

Yes: Considers whether scheduling shared suppliesearly will allow subsequent resource batching. AYes value improves the scheduled utilization of

batch resources by considering earlier constraints.

No: Schedules resource batching when supplies areavailable.

MSO: Resource BatchingStrategy

Nearest Date/Level Utilization

Nearest Date Selects order scheduling strategy used in resourcebatching. Valid values are:

Nearest Date: Schedules orders to load resourcesnearest the due date of the order.

Level Utilization: Schedules orders to levelutilization of the resource.

MSO: Resource Group forthe Line FlexfieldAttribute

Integer >= 0 Null Stores the name of the flexfield column that contains thevalue in the corresponding table. This setup is onlyperformed during application install. See FlexfieldAttributesfor more information.

MSO: Schedule AcrossBreaks

Yes/No Yes (canschedule across

break)

Determines whether the scheduling engine starts anactivity before a break and ends it after the break. If set toNo, verify that every activity has enough resource in oneshift (otherwise the activities are moved to the end of thehorizon). Can be defined at the site level.

MSO: schedule windowwidth

Integers >=0 8 days Defines time window (days) that the scheduling enginelooks for its primary resource. If the primary resource isnot in this window, the scheduling engine moves to an

alternate resource. Can be defined at the site level.

MSO: SCO Dual VariablesTolerance

Numeric 0.000000001 Parameter used internally for optimization. ConsultOracle Development and Oracle Support beforemodifying this profile option.

MSO: SCO Reduced CostTolerance

Numeric 0.000000001 Parameter used internally for optimization. ConsultOracle Development and Oracle Support beforemodifying 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 OptimalityTolerance

a number betweene-9 and e-4


Parameter to set the optimality tolerance for the simplexalgorithm.

MSO: SimplexPerturbation Constant

Number greaterthan e-8


Parameter to set the simplex perturbation constant.

MSO: SimplexPerturbation Limit


Parameter for the simplex perturbation limit.


MSR P fil O ti


24/26

MSR Profile Options


MSR Profile OptionsThe following table lists and defines the MSR profile options in Oracle AdvancedPlanning.

MSO: SimplexPerturbation Parameter

0,1 See AutomaticCalculations.

Provides a perturbation constant for the Planning Engine.Sets the amount by which the Planning Engine perturbsthe upper and lower bounds on the variables when aproblem is perturbed.

MSO: Simplex PresolveLimit

-1, 0, integer > 0 See AutomaticCalculations.

Parameter to set the limit on the number of pre-solves.

MSO: Simplex SingularityRepair Limit


Parameter to set the simplex singularity repair limit.

MSO: Solve Dual Problem 0 and 1 See AutomaticCalculations. Controls whether the Planning Engine solves the dualproblem or the primal problem.

MSO: Sourcing AllocationWindow

integer >= 1 7 Specifies the Allocation Percentages Satisfaction Period.The constraints are enforced in a rolling horizon manner.Used with Enforce Sourcing Constraints enabled inspecific plan options.

MSO: Substitute ItemPenalty

Number > 0 None Defines an internal penalty weight for substitute itemobjective in supply chain optimization.

MSO: Supply Window

Size

integer >= 0 Null During priority pegging, supplies are sorted based on

supply type, then smallest quantity, then by scheduledate. The highest priority demands from the firstdemand window will peg to the sorted supplies in thefirst window if possible. When the supplies from onewindow are all pegged, the demand will peg to thehighest sorted supply in the next window until alldemands are pegged. This is specified in the number ofworking days. Null is treated as 1 in the Planning Engine.

MSO: Use SCO TimeAggregation

True/False False Determines whether the Planning Engine should usedifferent aggregate time buckets than specified in the

aggregation settings of the plan options. The PlanningEngine use the values defined in the plan options. Youcan specify large values for daily and weekly buckets forPlanning Engine output, but this increases PlanningEngine calculation time. Valid values are:

True: The Planning Engine uses aggregate timebuckets specified in MSO: Optimization DailyAggregation Buckets and MSO: OptimizationWeekly Aggregation Buckets. The period time

bucket is derived.

False: The Planning Engine uses the same aggregatetime buckets as specified in the Aggregation tab ofthe Plan Options window.


INV Profile Options


25/26

INV Profile Options


INV Profile OptionsThe following table lists and defines the INV profile options in Oracle AdvancedPlanning.


MSR: PostponementFactor

Integers >= 0 10 Specifies maximum depth in the bill of materials and sourcingtree to which uncertainty must be postponed.

MSR: Safety StockHolding Strategy

DestinationOrganization orSourceOrganization

SourceOrganization

Specifies where safety stock should be held when the carryingcost is the same for an item in the destination organization anda source organization. A 0 value causes the safety stock to beheld at the destination organization. A 1 value causes thesafety stock to be held at the source organization.

MSR: ProbabilityDistribution Type

CumulativeProbabilities/Probabilities

Probabilities Determines probability distribution type associated withforecast sets as input to Oracle Inventory Optimization. ValidValues are:

Probabilities: Demand uncertainty is stated in terms of a(non-cumulative) probability distribution.

Cumulative Probabilities: Demand uncertainty is statedin terms of a cumulative probability distribution.


INV: Capable toPromise

ATP/CTP Basedon PlanningOutput, EnablePL/SQL based

ATP withPlanning Output

Null Set to ATP/CTP Based on Planning Output to performmultilevel order promising. Oracle Global Order Promisingcalculates promise dates on the basis of either planning outputor transaction data. The former is required for capable-to-

promise checks. When performing order promising inquiries onthe basis of planning output, Oracle Global Order Promisingautomatically reverts to an ATP inquiry on the basis oftransaction data.

INV: External ATP Not applicable Not applicable Only applicable for Oracle Global Order Promising fornon-Oracle Applications Release 11isource and to be set-up onlyon source instance. Do not set up for an Oracle ApplicationsRelease 11iinstance.

INV Profile Options


26/26

INV Profile Options


aps profile options 2205931

Documents