Profile Options

This appendix covers the following topics:

Oracle Global Order Promising Profile Options

Oracle Global Order Promising uses several types of profile options, including:

The following sections contain tables that list the profile option names, values, and descriptions.

MRP Profile Options

The following table lists and defines the MRP profile options used by Oracle Global Order Promising:

Profile Option Name Valid Values Default Value Description
MRP: ATP Assignment Set Text Null The assignment set name for use with Oracle Global Order Promising. When set to Null, Oracle Global Order Promising uses the assignment set from profile MSC: ATP Assignment Set from Oracle Advanced Planning Solution instance. Update this profile at site level on the source instance.
MRP: ATP Database Link Text Null Determines whether distributed Oracle Global Order Promising is used. Set this profile at the source instance. The value should equal the value you entered in the 'From Source to APS' of the source instance you defined in the Instance form. This is a site-level profile.
MRP: Calculate Supply Demand Yes
No		 Yes When set to Yes, this profile controls whether detailed supply / demand data is retrieved and retained for viewing during an ATP Inquiry. This data is viewed by selecting ATP Details in the Inquiry form. Performance can be slowed when the profile is set to Yes. For better performance, set it to Yes, run an ATP Inquiry and view the details, and thenset it back to No.
Set this profile to Yes only when you need to view the detailed supply demand and horizontal plan information for an ATP inquiry.
You can set the profile at the user level.
MRP: Include Substitute Components Yes
No		 No Indicates whether to include substitute components in the Oracle Global Order Promising calculation. Users can update at the site level. This setting is only applicable when ATP is based on Oracle Advanced Supply Chain Planning output.
MRP: Set Category for Backlog Form Text (varies) Use this profile option to indicate which items belonging to this category set appear in the Backlog Scheduling Workbench tree navigator. If no value is entered, no items appear in the Backlog Scheduling Workbench tree navigator. You can update this profile at the site level.

MSC Profile Options

The following table lists and defines the MSC profile options used by Oracle Global Order Promising:

Profile Option Name Valid Values Default Value Description
MSC: Action Allowed on ATP 24x7 Plan While Running Yes
No		 No Determines whether manual updates are allowed to the original plan when the plan copy is running.
Values are:

  • Yes: The ATP plan appears in the Workbench window while it is running. You can make changes to the plan. However, the changes will not appear in the refreshed plan.

  • No: The ATP plan appears only in the View Plan window.
MSC: Allocated ATP Forward Consumption Reduce future supply from lowest priority
Reduce available supply from any priority		 Null Determines the type of forward consumption that Oracle Global Order Promising can perform to accommodate the shortage faced by a demand class.
Values are:

  • Reduce future supply from lowest priority: Use the available supply from the lowest priority demand to account for the shortage of a demand class. If every demand class is at same priority, reduce the future supply to cover the shortage for a demand class.

  • Reduce available supply from any priority: A promised demand is the most important demand that you need to meet. Oracle Global Order Promising starts the adjustments from the higher priority demand class. That is, Oracle Global Order Promising reduces the availability of a lower priority demand class before a higher priority demand class to account for shortages from a previous period. Thus, it reduces the available supply to account for the shortage from lower priority demand classes.
MSC: ATP 24x7 Synchronization Downtime Any number between 0 and 999 Null Determines the approximate ATP downtime (in minutes) to cover the time required to synchronize and to switch over to the refreshed plan during the plan synchronization process. Oracle Global Order Promising internally translates this value into the number of orders to process.
You should set the value for this profile based on the sales order volume during the ATP 24x7 plan run.
This profile option also determines the duration of the extended synchronization process. This process is executed for the duration of the ATP downtime or 10 minutes, whichever is larger.
MSC: ATP Allocation Method User-Defined Allocation Percentage
Demand Priority		 Null This site-level profile determines the allocation method used by ATP. This is a site level profile. Values are:

  • User-Defined Allocation Percentage

  • Demand Priority
MSC: ATP Assignment Set Text Null Indicates name of the assignment set that Oracle Global Order Promising uses to identify all the possible shipping organizations. Oracle Global Order Promising uses this assignment set if the profile MRP: ATP Assignment Set is Null on the ERP instance. Users can update it at the site level in the Planning instance.
MSC: ATP Capacity Allocation Yes
No		 No Set it to No. You should only set it to Yes with 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. 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 a log file or a database trace file.
MSC: ATP Enforces Lead Time for ATO Models

  • Yes

  • No

 Yes Indicates whether ATP enforces lead time for ATO models or not.

  • Yes - Enforces lead time for ATO models.

  • No - Does not enforce lead time for ATO models.
MSC: Class Hierarchy Demand Class

  • Demand Class

  • Customer Class

 Demand Class
Customer Class		 Indicates which allocation hierarchy to use. Users can update it at the site level. Values are:

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

  • Customer Class: Has three levels: customer class, customer, and site.
MSC: Collection Window for Trading Partner Changes (Days) Integer >= 0 Null Use when collections for the trading partners entity is run in complete mode.
Specifies the number of days backwards for collecting changes in customer names, customer sites, vendors, and vendor sites. A Null value means all changes are collected.
MSC: Custom Allocation Yes
No		 No If set to Yes and MSC Class Hierarchy is set to Customer Class, Customer Allocated ATP performance is improved.
This profile can be used only in the following cases:

  • The item can be only an end item allocation, not a component allocation. That is, the item cannot be a component of another BOM.

  • No CTP exists. No planned order demand allocation and CTP suggested supply or demand allocation exists.
MSC: Display Order Rescheduling Supplies Yes
No		 No Determines whether the rescheduling supplies appear in the Planner Workbench.
Values are:

  • Yes: Displays the rescheduling supplies details in the Planner Workbench.

  • No: he rescheduling supplies details are hidden from the Planner Workbench


This profile is provided for debugging and analysis only. Therefore, you should set this profile to No in a production environment.
MSC: Enable Allocated ATP Yes
No		 No Use this profile option to indicate whether allocated order promising is used. Users can update this profile at the site level.
MSC: Enable ATP Summary Mode Yes
No		 No Enables the summarization of supply / demand data for improved performance. This is a site level profile. 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: Excess and Safety Stock by Demand Class Yes
No		 No 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.
Values are:

  • Yes: If such supply or demand has a demand class, and if the demand class exists on the allocation rule, then allocate the supply or demand to the demand class. If the supply or demand does not have a demand class or if the demand class does not exist on the allocation rule, then allocate the supply or demand to OTHER.

  • No: Allocate such supply or demand to OTHER.
MSC: Forward Stealing Logic & Enhanced Forward ATP Yes
No		 No When set to Yes, supply searches are more efficient in the forward pass. The software:

  • Considers multiple sources of supply (make, transfer, buy) together.

  • Considers component substitution in the forward pass.

Caution: Enabling this profile could significantly affect performance, and it must be enabled only after due analysis.
MSC: Horizontal Plan Demand Bucketing Preference Plan Recommended Date
Demand Due Date		 Demand Due Date Determines which date is used for bucketing demands.
Values are:

  • Plan Recommended Date: Demands are bucketed based on the dates recommended by the planning engine.

  • Demand Due Date: Demands are bucketed based on the schedule ship date on the sales orde.r
MSC: OTHER with Zero Allocation Percent is Valid Demand Yes
No		 No When set to Yes, demand classes with 0% allocation are considered as valid demand classes for allocated ATP calculations.
When set to No, demand classes with 0% allocations are not considered as valid demand classes for allocated ATP calculations.
MSC: Perform ATP Check for Internal Sales Orders Yes
No, only if
Destination Organization on ISO is not part of Plan		 No Determines if an ATP check is performed for internal sales orders.
MSC: Sales Orders Offset Days Integer >= 0 Null Collects completed sales orders 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 collected. Can be defined at the site level. A Null value means all closed sales orders are collected.
MSC:Select sourcing rules in ATP based on Sysdate, Request Date Sysdate Use this profile option to specify the basis of sourcing rule effectivity dates for available -to-promise. Valid values are:
- Sysdate: The sourcing rule effectivity date is based on the system date
- Request Date: The sourcing rule effectivity date is based on the greater of Request Date or Planning Time Fence Date
For example:
- MSC:Select sourcing rules in ATP based on = Request Date
- Item has five days leadtime and no on- hand
- Item currently sourced from supplier A
- Item will change sourcing to Supplier B on Dat 10
- Customer A calls today and requests item to ship on Day 20
- you would need to order the product on Day 14 to arrive on Day 19, then ship on Day 20
- Available-to-promise chooses Supplier B for this order based on Request Date
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 the following collections parameters:

  • Purge Sourcing History = Yes

  • Recalculate Sourcing History = Yes


These settings delete and then calculate Sourcing History (in months) from the Start date determined by the profile option value (in months). System performance might degrade when you set a high value for this profile option and the high volume of source transaction data is high.
MSC: Use Enhanced Forward ATP Yes/No No Use this profile option to specify whether the GOP engine should use enhanced forward ATP: Valid values are:
- Yes: Use enhanced forward ATP
- No: Do not use enhanced forward ATP
MSC: Use Shipping/Receiving Calendars Yes
No		 Yes Determines whether shipping/receiving/carrier calendars are used for order promising.
Values are:

  • Yes: Uses the shipping, receiving, and carrier calendars to schedule ship and arrival dates.

  • No: Uses only the organization's manufacturing calendar to schedule ship dates at each level.

INV Profile Options

The following table lists and defines the INV profile options used by Oracle Global Order Promising:

Profile Option Name Valid Values Default Value Description
INV: Capable to Promise ATP/CTP Based on Planning Output
ATP Based on Collected Data		 ATP Based on Collected Data This is a site-level profile. Values are:

  • ATP/CTP Based on Planning Output: Select this value if you want to use the Oracle Advanced Supply Chain Planning output for order promising.

  • ATP Based on Collected Data: Select this value if you want to use collected data for order promising.
INV: External ATP Global ATP Server
None		 - Only applicable for Oracle Global Order Promising for non-Oracle Applications on Release 11i source. Set up only on the source instance. Do not set this up for an Oracle Applications Release 11i instance. Set this profile to Global ATP Server if Oracle Global Order Promising is deployed. This is a site level profile.

BOM Profile Options

The following table lists and defines the BOM profile option used by Oracle Global Order Promising:

Profile Option Name Valid Values Default Value Description
BOM: Match To Existing Configuration

  • Yes

  • No

 No Determines whether Oracle Global Order Promising matches a sales order to an existing configuration.
Values are:

  • Yes: Attempts to match a sales order to an existing configuration.

  • No: Schedules a sales order without a match to existing configuration check.