Manage Order Promising Options

Use the Order Promising Options task to set up database promising.

The default values on the Order Promising Options page will meet most of your typical needs. Modify them only in consultation with your Oracle product team.

To set the options, go to the Global Order Promising work area, then click Tasks > Order Promising Options.

Locking Options

Promising might receive request y to promise an item while it's still processing an earlier request x to promise that item. You can specify how to lock inventory to make sure Promising doesn't consume the same inventory for these requests.

Assume Order Management sends request x, and then sends request y to Promising to promise an item.

Option	Description
Maximum Waiting Period for Inventory Lock	Specify how long the lock lasts. The default value is 10,000 milliseconds (10 seconds). Assume you set this option to 10. At run time, Promising receives request x from Order Management to promise an item, then Promising locks inventory for the item at 03:14:00 AM, where 03 is hours, 14 is minutes, and 00 is seconds. Promising will lock inventory until 03:14:11 AM. If Promising receives request y before 03:14:11 AM, then it will reject request y.
Wait Time to Retry Inventory Locking	Specify how long request y must wait before it tries again. The default value is 1,000 milliseconds (1 second). Assume you set: Maximum Waiting Period for Inventory Lock to 10 seconds Wait Time to Retry Inventory Locking to 2 seconds Request y will try again every two seconds until it reaches the maximum: 03:14:02 03:14:04 03:14:06 03:14:08 03:14:10 If Promising releases the lock before the maximum, then the retry is successful and Promising locks inventory for request y. For example, if Promising releases the lock for request x at 03:14:06 AM, then it will lock inventory for y at 03:14:08 AM.
Life Span for Unreleased Locks	If an error happens that causes the lock to remain in place, then use Life Span for Unreleased Locks to specify how long to keep the lock. Promising will permanently release the lock according to the value that you set. The default value is 1 minute. Assume you set: Maximum Waiting Period for Inventory Lock to 10 seconds Life Span for Unreleased Locks to 1 minute If Promising places a lock at 03:14:00 AM, and then an error happens that prevents Promising from releasing the lock at 03:14:11 AM, then Promising will release the lock at 03:15:00 AM. You must set Life Span for Unreleased Locks to a value that's higher than you set for Maximum Waiting Period for Inventory Lock. This makes sure Promising won't release the lock before the maximum expires.
Dependency Group Locking Policy	The default value is Enable Full Locking. Assume: Promising locks inventory for request x, and x includes item A and item B. Promising receives request y, y includes item B and item C, and y is waiting for Promising to release the lock. If you set this option to: Enable Full Locking. Promising will lock inventory for y only after it finishes processing request x for A and B. Enable Partial Locking. Promising will wait for the maximum to expire, and then lock inventory for C but not for B. It doesn't lock inventory for B because it's still processing x's request for B.

Time Zone Options

Specify how to handle differences in time zones. For more, see Examine Availability Dates.

Option	Description
Default Time Zone	If the request that Promising receives to promise an item doesn't include a time zone for the customer, supplier, or organization, then Promising will use the time zone that you specify in this option. The default value is UTC.
Time Period Tolerance for Upstream Searches	Specify the number days to adjust the time when you encounter time zone differences during an upstream search for supply. You can set this option to a value that's between 0.1 and 1. The default value is 0.5, which represents half a day. Assume you set Time Period Tolerance for Upstream Searches to 0.5. If the adjustment happens: Before 12 Noon. Promising assumes the request happens at the end of the previous time period. After 12 Noon. Promising assumes the request happens at the end of the current time period. For more, see Database Promising.

Model Analysis Options

Option	Description
Generate Replay Data Sets	Set a value: No. Don't create replay data. This is the default value. Yes. Create replay data while Promising promises each sales order in real time. Replay data includes diagnostic messages that you can use to troubleshoot problems. Yes, and Repromise. Create replay data, and also repromise the sales order each time you submit it to fulfillment. Generate replay data while Promising promises each sales order at run time, and also when Promising repromises sales orders that it collects at run time. For example: Set the Generate Replay Data Sets attribute to Yes, then click Save and Close. Go to the Order Management work area, then create and submit a sales order. Run the Extract Global Order Promising Replay Data scheduled process, then examine its log to help troubleshoot. For details, see Troubleshoot Setup Problems in Order Promising. Set the Generate Replay Data Sets attribute to No, then click Save and Close.
Life Span for Replay Data Sets	Specify how long to keep replay data. The default value is 24 hours.

General Options

Option	Description
Consider Infinite Supplier Capacity	If you enable this option, then Promising will assume supplier capacity is infinitely available even if you import it through file-based data import. Promising will ignore supplier capacity even if the request to promise includes that capacity.
Plans	If you enable this option, then Promising will include supply plans when it promises your item. Each supply recommendation will include a planned order, and Promising will assume that this supply is available to promise. The supply recommendation from Oracle Supply Planning provides the planned order.
Simulation Set	Select the simulation set that you want the Create Bills of Resourcesscheduled process to create. This set will contain the bills of resources that you need to build each capable-to-promise item in your make flow. For details, see Overview of Using Bills of Resources with Promising.
Enable Order Synchronization with Orders Promised Using The Memory-Resident Solution Synchronization Interval in Minutes	Don't use these options.