Database Promising
Use database promising to more quickly and accurately schedule some of your promising flows.
Use it with these flows and set ups:
- Standard flow when you set the source type to Buy From or Transfer From on your sourcing rule.
- Standard flow when you manufacture the item. For details, see Overview of Using Bills of Resources with Promising.
- Drop ship flow.
- Back-to-back flow.
- All other flows.
- Configured items.
Drop Shipments
You don't need to set up an ATP rule for a sales order that you promise in a drop shipment when you use database promising. However, if you use profitable-to-promise, then you must create an ATP rule and enable the Profitable to Promise option on that rule. For details, see Set Attributes on Your Supply Chain Search and Create Alternative Fulfillment Scenarios to Reduce Cost.
You must also assign the item to the Drop Ship Validation Organization. For details, see Promise Sales Orders in Your Drop Ship Flow.
For details, see Include Supplier Capacity When You Promise ATO Items.
Configured Items
Database promising considers the lead times in a drop ship flow or a buy flow when it promises a configured item.
Drop Ship Flow
- The supplier for an assemble-to-order item in a drop shipment typically uses the same capacity to supply different configuration for a configured item. It consumes capacity according to the supplier's calendar. Promising will consume the capacity that you specify for the configured item in the approved supplier list.
- Promising uses the lead time offset for a configure-to-order item when it calculates the scheduled ship date for the sales order. Promising also considers the item's processing lead time for each configure option.
- Promising considers each configure option that the user chooses when it calculates the schedule dates, then uses these dates to calculate the total lead time for the configured item.
Here's how Promising calculates the lead time for a configured item.
Total lead time equals the lead time of the root parent plus the longest lead time of the configure option at each level of the item hierarchy.Here are more details about how Promising uses lead times when it promises your item in a drop ship flow.
| Item | Where Promising Gets The Lead Times |
|---|---|
| Root Parent |
Preprocessing lead time and the supplier lead time that you specify in the approved supplier list for the root parent of the model. If you don't specify a supplier lead time, then Promising uses the processing lead time. |
| Configure Option | Supplier lead time that you specify in the approved supplier list for each configure option. |
Assume you sell the AS54888 desktop computer as a configured item, and it’s the root parent.
AS54888 Desktop Computer
Monitor configure option
24" Monitor
32" Monitor
Keyboard configure option
Business Keyboard
Gaming Keyboard
Assume you have these lead times.
| Item | Lead Time |
|---|---|
| AS54888 | 5 Days |
| 24" Monitor | 4 Days |
| 32" Monitor | 2 Days |
| Business Keyboard | 1 Days |
| Gaming Keyboard | 3 Days |
Assume you order the AS54888 with the 32" Monitor and the Business Keyboard. The lead time for the 32" monitor is 2 days, the lead time for the Business Keyboard is 1 day, so Promising uses the 32" monitor's lead time when it calculates the total lead time.
Here's the calculation for all configurations.
| Configuration | Configure Option That Has the Longest Lead Time | Lead Time of the Root Parent | Total Lead Time |
|---|---|---|---|
|
24" Monitor Business Keyboard |
4 days | 5 days | 9 days |
|
24" Monitor Gaming Keyboard |
4 days | 5 days | 9 days |
|
32" Monitor Business Keyboard |
2 days | 5 days | 7 days |
|
32" Monitor Gaming Keyboard |
3 days | 5 days | 8 days |
Buy Flow
Promising uses the same lead times and calculations that it uses in a buy flow, but with a few differences.
- It also looks at the postprocessing lead time from the approved supplier list for the root parent.
- If the approved supplier list includes the lead time for the configured item and lead time for the assemble-to-order item, then Promising uses the configured item's lead time.
- If you don't specify the processing lead time for the root model or for any of the configure options, the Promising assumes the lead time is zero.
- You can also specify the processing lead time in the receiving organization.
Related Topics
You can enable the Search Components and Resources attribute when you promise a configured item. For details, see Set Attributes on Your Supply Chain Search.
Back-to-Back
- Promising considers the item's postprocessing lead time from the Product Information Management work area when it recommends supply in a back-to-back flow. The requested delivery date corresponds to the dock date on the purchase order or transfer order, or to the completion date on the work order.
- Promising applies the postprocessing lead time to the dock date or to the completion date when it calculates the scheduled ship date for the sales order.
- Promising can consider the work order, transfer order, or purchase order as soon as you collect it.
- Promising doesn't consider your ATP rule's Infinite Availability attribute at the ship-from organization. If Promising can't identify a supply source by the end of the promising horizon, then it returns an error that say's inventory isn't available.
Bill of Resources
Standard Items
You can use a bill of resources to identify a subset of the manufacturing components and resources in the bill of materials that are most likely to affect manufacturing's lead time. Promising then examines only the subset instead of all the manufacturing components when it promises in a capable-to-promise flow. For details, see Overview of Using Bills of Resources with Promising.
Configured Items
Promising uses your bill of resources to identify the required components and resources that you need to build an assemble-to-order configured item. Promising will consider the lead time for each configure option regardless of whether you enable the Search Components and Resources option on your ATP rule.
If the pick-to-order item or if the component in a kit is an assembled item, then Promising will use your bill of resources the same way that it does when it promises a standard item.
Process Work Definitions
- Promising uses your bill of resources for the primary item to create capable-to-promise supply for the primary item.
- If you modify an attribute on the order line, such as the quantity or date, then Promising will update the supply and demand for the primary item in your downstream fulfillment applications.
If you collect work orders, then Promising will consider supply from:
- Any work order that you have for the primary item, and will use it as available-to-promise supply.
- The work orders, and use it as available-to-promise supply to meet demand for each coproduct and byproduct. Promising doesn't recommend new supply for coproducts and byproducts, but it can consider existing supply to meet demand.
For details, see Use Work Definitions with Your Bill of Resources.
Product Information Management
Promising considers the Create Supply attribute and the Create Supply After attribute that you specify for the item in the Product Information Management work area. It does this when available-to-supply supply isn't available and it needs to make supply or buy supply in your capable-to-promise flow.
| Value of the Create Supply Attribute | Description |
|---|---|
| No | Promising won't make supply or buy supply for the item even if you have a sourcing rule for the item. |
| Yes | If you also set the Create Supply After attribute, then Promising will use your sourcing rule to make supply or buy supply. |
For details about this behavior, go to Oracle Cloud Application Update Readiness. In the Essential Content area, under What's New, click HTML in the Supply Planning row. On the What's New page, click Update 22B, then search for Create New Supplies Based on Earliest Date Constraint.
Consume Transfers at the Same Time
If you transfer supply from an upstream organization to the ship-from organization, then Promising will adjust the upstream organization’s supply so it happens at the end of the previous day or at the end of the day that the upstream organization receives the request.
If the upstream organization and the ship-from organization are in different time zones, then you might find it helpful to specify when to consume supply.
Assume the upstream organization is in Eastern Standard Time (UTC minus 5) and the ship-from organization is in Pacific Standard Time (UTC minus 8). Set up Promising so it consumes supply on the same day for both time zones.
- Go to the Global Order Promising work area, then click Tasks > Order Promising Options page. For details, see Manage Order Promising Options.
-
Set the Time Period Tolerance for Upstream Searches parameter.
If you use the default value of 0.5, and if the request for supply at the upstream organization arrives before 12 PM, then Promising will consume supply on the previous day. If it arrives after 12 PM, then Promising will consume supply on the current day.
The value is a fraction of a 24 hour day. For example, 0.5 equals 12 hours because 0.5 is one half of a 24 hour day, which is 12 PM. For another example, 0.8 equals 19.2 hours into a 24 hour day, which is 7:20 PM.
Allocate Supply in a Hierarchy
You can allocate supply in a hierarchy to improve the way you distribute supply for an item that's in high demand and when you have only a limited amount of supply to distribute. For details, see Allocate Supply in a Hierarchy.
Profitable to Promise
If you need to use profitable to promise in a drop shipment, then enable the Profitable to Promise option on the ATP rule that you use to assign the item in the drop ship validation organization.
The bill of resources doesn't contain cost for the item even if you enable the Capable to Promise option on your bill of resources to promise an item that you manufacture. Instead, Promising determines cost when it promises the item according to the:
- Items and resources that you specify are critical
- Items and resources that Promising actually consumes
- Supply that Promising consumes from your supply sources
For background details, see the Profitable to Promise section in Set Attributes on Your Supply Chain Search.
Substitute the Item
Promising substitutes the item differently depending on the features that you use.
| You Enable the Constraint-Based Planning Feature | You Enable the Respect Organization-Specific Item Substitution Rules Feature | Promising Will |
|---|---|---|
| Yes | Yes | Use a substitute item from the organization that you specify for the item in the Product Information Management work area. |
| No | Yes | Use the item substitutes that you specify in the master organization, and Promising won't consider any item substitutes that you specify in each organization. |
For details, see Overview of Constraint-Based Supply Planning. Also, go to Oracle Cloud Application Update Readiness. In the Essential Content area, under What's New, click HTML in the Supply Planning row. On the What's New page, click Update 22B, then search for Respect Organization-Specific Item Substitution Rules.
Earliest Acceptable Date
You can use the Earliest Acceptable Date attribute on the order line to specify a date before the requested date. Set the Request Type attribute on the line to Ship On to specify the earliest acceptable ship date, or set it to Arrive On to specify the earliest arrival date.
Promising considers the Earliest Acceptable Date attribute when it calculates the scheduled ship date and the scheduled arrival date, but it puts a priority on meeting the requested date. If you specify the Requested Arrival Date attribute and the Earliest Acceptable Date attribute on the order line, then Promising promises the sales order so it arrives on or after the Earliest Acceptable Date. For details, see Examine Availability Dates.
Promising Horizon and Other Order Promising Options
Promising doesn't use the promising horizon with database promising, so you don't need to worry about setting it when you use database promising.
You can also set some of the promising options to specify how to handle supply searches that happen at the same time, how to consider time zones, how to use supplier capacity that's infinitely available, how to use troubleshooting details, and so on.
For details, see Manage Promising Profiles.
REST API and SOAP
Use the Supply Allocation Availability REST API to get details about your allocation hierarchy. For details, see the Test Your Setup section in Allocate Supply in a Hierarchy.
Use the Quick Availability Check REST API to get details about the supply that's currently available in your supply chain. For details see Allocate Supply Through REST API.
Suppliers and Supplier Capacity
If you set up and collect supplier and supplier site details, then Promising uses that information during planning.
You can set up Promising so it considers supplier capacity as infinitely available. If necessary, you can use the Order Promising Options page to tell Promising to use this capacity even after you upload capacity data through file-based data import (FBDI).
Source Promising
Use source promising when you have a large volume of items and organizations in a back-to-back flow. Also, you don't need to collect transactional entities when you use source promising. For details, see Schedule Sales Orders for Back-to-Back Items.
You can also use source promising when you don't use a back-to-back flow. For details, see Get Promising Dates in Real Time.
Guidelines
Apply these guidelines when you use database promising:
- You don't need to refresh the server after you collect data.
-
If the MSP_ENABLE_GOP_WITH_NEW_ARCH profile is Yes, then you're using database promising. For details, see Manage Planning Profile Options.