Update Data for Your Rules

If you change any assignment set, sourcing rule, ATP rule, or profile option, then you must run these scheduled processes:

Collect Planning Data
Collection Job Set

Select different parameters and entities when you run them, depending on what you changed.

For details, see Collect Data for Global Order Promising.

Example 1

Assume:

You keep inventory in the Denver warehouse and in the Seattle warehouse.
You remove one rule from an assignment set then add another one to it.
You create a global sourcing rule that transfers supply from Denver.
You don't have a sourcing rule for Seattle.
You have one ATP rule:
- Assignment level is Item
- Mode is Supply Chain Availability
Supply is currently available in Denver but not in Seattle.
You set the MSP_GOP_HORIZON_DAYS profile option to 30 days. For details, see Manage Promising Profiles.
You set the Warehouse attribute on the order line to Denver or Seattle, or leave it empty.

Here's what happens at run time for various scenarios.

Scenario	ATP Rule	Assignment	Warehouse	Catalog Availability	Estimate Order Availability	Scheduling
1	Yes	Yes	Denver	In Stock	On Time	Scheduled
2	Yes	Yes	Seattle	Out of Stock	Delay of 29 Days	Scheduled
3	Yes	Yes	Empty	In Stock	On Time	Scheduled
4	Yes	No	Denver	No Data Was Retrieved	On Time	Scheduled
5	Yes	No	Seattle	No Data Was Retrieved	Delay of 29 Days	Scheduled
6	Yes	No	Empty	No Data Was Retrieved	No Data Was Retrieved	You might see an error: `Order promising didn't schedule the fulfillment line. The sourcing rule or assignment is missing for the item, customer, and organization. Create a sourcing rule or assignment for the item, customer, and organization.`
7	No	Yes	Denver	No Data Was Retrieved	No Data Was Retrieved	You might see an error: `The item passed to order promising was not found in any organization. Verify the item definition.`
8	No	Yes	Seattle	No Data Was Retrieved	No Data Was Retrieved	Same as above
9	No	Yes	Empty	No Data Was Retrieved	No Data Was Retrieved	Same as above
10	No	No	Denver	No Data Was Retrieved	No Data Was Retrieved	Same as above
11	No	No	Seattle	No Data Was Retrieved	No Data Was Retrieved	Same as above
12	No	No	Empty	No Data Was Retrieved	No Data Was Retrieved	Same as above

Note

The ATP Rule column indicates whether you created an ATP rule that Promising can use given the order line details that Order Management sends.
The Assignment column indicates whether you created an assignment set that Promising can use given the order line details that Order Management sends.
The Warehouse column indicates whether you set the Warehouse attribute on the order line to Denver, Seattle, or didn't set any value.
The text in the Catalog Availability, Estimate Order Availability, and Scheduling columns is the status that the sales order displays.

Catalog Availability

Scenarios Description

1 and 3

Scenarios	Description
1 and 3	Catalog Availability examines your ATP rules and looks at supply for any global rule that matches the criteria from the order line. Denver is the only global sourcing rule that applies. You didn't set the Warehouse on the order line for scenario 3, so Promising applies the same global rule, Denver, and sets the status to `In Stock`.
2	If you specify the Warehouse on the order line, then Promising must use it, but Seattle doesn't have any supply, so the status is `Out of Stock`.
4 through 12	The status is `No Data Was Retrieved` because you didn't create an ATP rule and an assignment set. You need an ATP rule and an assignment set to determine Catalog Availability.

Catalog Availability examines your ATP rules and looks at supply for any global rule that matches the criteria from the order line.

Denver is the only global sourcing rule that applies. You didn't set the Warehouse on the order line for scenario 3, so Promising applies the same global rule, Denver, and sets the status to In Stock.

2 If you specify the Warehouse on the order line, then Promising must use it, but Seattle doesn't have any supply, so the status is Out of Stock.

4 through 12 The status is No Data Was Retrieved because you didn't create an ATP rule and an assignment set. You need an ATP rule and an assignment set to determine Catalog Availability.

For details, see How Catalogs Work Together.

Estimate Order Availability

Scenarios	Description
1 and 3	Similar to Catalog Availability, Estimate Order Availability examines your ATP rules and looks at supply for any global rule that matches the criteria. Denver is the only one that applies. You didn't set the Warehouse on the order line for scenario 3, so Promising applies the same rule, and sets the status to `On Time`.
2 and 5	You specify the Warehouse as Seattle, so Promising must use Seattle, Seattle doesn't have any supply, so Promising gets the value from the MSP_GOP_HORIZON_DAYS profile option and uses it to set the status to `Delay of 29 Days` (30 minus today).
4	You didn't set the Warehouse on the order line, so Promising applies the Denver global rule, and sets the status to `On Time`.
6 through 12	The status is `No Data Was Retrieved` because you didn't create an ATP rule and an assignment rule, or least an ATP rule and specify the warehouse on the order line. To get the estimate, you need an ATP rule and an assignment rule, or least an ATP rule and specify the warehouse.

Scheduling

Scenarios	Description
1 through 5	Promising was able to schedule the line, so it sets the status to `Scheduled`.
6 through 12	Scheduling displays an error because you didn't create an ATP rule and an assignment set, or least an ATP rule and specify the warehouse on the order line. To schedule, Promising needs an ATP rule and an assignment set, or least an ATP rule and the warehouse.

Example 2

Assume the scenarios are the same as example 1 but with these differences:

You create a global sourcing rule that transfers supply from Seattle.
You don't have a sourcing rule for Denver.

Here's what happens at run time.

Scenario	ATP Rule	Assignment	Warehouse	Catalog Availability	Estimate Order Availability	Scheduling
1	Yes	Yes	Denver	Out of Stock	On Time	Scheduled
2	Yes	Yes	Seattle	Out of Stock	Delay of 29 Days	Scheduled
3	Yes	Yes	Empty	Out of Stock	Delay of 29 Days	Scheduled

Catalog Availability

Scenarios Description

1 through 3

Scenarios	Description
1 through 3	Catalog Availability examines your ATP rules and looks at supply for any global rule that matches the criteria from the order line. Seattle is the only global sourcing rule that applies, but Seattle doesn't have any supply, and you don't have a sourcing rule for Denver, so the status is `Out of Stock`.

Catalog Availability examines your ATP rules and looks at supply for any global rule that matches the criteria from the order line.

Seattle is the only global sourcing rule that applies, but Seattle doesn't have any supply, and you don't have a sourcing rule for Denver, so the status is Out of Stock.

Estimate Order Availability

Scenarios	Description
1	You set the Warehouse on the order line to Denver, so Promising must use Denver. Denver has supply, so Promising sets the status to `On Time`.
2	You set the Warehouse on the order line to Seattle, so Promising must use Seattle. Seattle doesn't have any supply, so Promising sets the status to `On Time`.
3	You left the Warehouse empty, so Promising examines the only sourcing rule it has, which is for Seattle. Seattle doesn't have any supply, so Promising gets the value from the MSP_GOP_HORIZON_DAYS profile option and uses it to set the status to `Delay of 29 Days` (30 minus today).

Scheduling

Scenarios	Description
1 through 3	Promising was able to schedule the line, so it sets the status to `Scheduled`.

Example 3

Assume the scenarios are same as in example 1 but with these differences:

You have two global sourcing rules. One transfers supply from Denver and the other one from Seattle.
The assignment level for Denver is Global.
The assignment level for Seattle is Item, and the item is the AS54888 Computer.

The run time results are the same as they are for example 2.

Example 4

Assume the scenarios are same as in example 1 but with these differences:

You have one sourcing rule for Denver and another one for Seattle.
You have ATP rule x for Denver:
- Assignment level is Organization
- Mode is Supply Chain Search
You have ATP rule y for Seattle:
- Assignment level is Organization
- Mode is Infinite Availability
You have two global sourcing rules. One transfers supply from Denver and the other one from Seattle.
The assignment level for Denver is Global.
The assignment level for Seattle is Item, and the item is the AS54888 Computer.
You have two global rules and you assigned them, so Promising examines the assignment set to identify the rules it will use.

Here's what happens at run time for various scenarios.

Scenario	ATP Rule	Assignment	Warehouse	Catalog Availability	Estimate Order Availability	Scheduling
1	Yes	Yes	Denver	In Stock	On Time	Scheduled
2	Yes	Yes	Seattle	In Stock	On Time	Scheduled
3	Yes	Yes	Empty	In Stock	Delay of 29 Days	Scheduled

Catalog Availability

Scenarios Description

1 You specify the Warehouse as Denver, so Promising must use Denver. Denver has supply, so Promising sets the status to On Time.

2 and 3

Scenarios	Description
1	You specify the Warehouse as Denver, so Promising must use Denver. Denver has supply, so Promising sets the status to `On Time`.
2 and 3	Catalog Availability examines your ATP rules and looks at supply for any global rule that matches the criteria from the order line. Seattle is the only global sourcing rule that applies whether or not you specify Seattle as the warehouse on the order line. Seattle doesn't have any supply, but Seattle's mode is Infinite Availability. Promising always assumes supply is available in this mode, so it sends the status to `In Stock` even though Seattle doesn't have any supply.

Catalog Availability examines your ATP rules and looks at supply for any global rule that matches the criteria from the order line.

Seattle is the only global sourcing rule that applies whether or not you specify Seattle as the warehouse on the order line. Seattle doesn't have any supply, but Seattle's mode is Infinite Availability.

Promising always assumes supply is available in this mode, so it sends the status to In Stock even though Seattle doesn't have any supply.

Estimate Order Availability

Scenarios Description

1 You specify the Warehouse as Denver, so Promising must use Denver. Denver has supply, so Promising sets the status to On Time.

2 You specify the Warehouse as Seattle, so Promising must use Seattle. The mode on the ATP rule for Seattle is Infinite Availability, so Promising assumes supply is always available, and sets the status to On Time.

3

Scenarios	Description
1	You specify the Warehouse as Denver, so Promising must use Denver. Denver has supply, so Promising sets the status to `On Time`.
2	You specify the Warehouse as Seattle, so Promising must use Seattle. The mode on the ATP rule for Seattle is Infinite Availability, so Promising assumes supply is always available, and sets the status to `On Time`.
3	You didn't specify a Warehouse on the order line, so Promising looks at all the ATP rules that apply. The assignment level for Denver is Global, and the level for Seattle is Item. Item is more specific than Global, so Promising uses Seattle's ATP rule. Seattle doesn't have any supply, so Promising gets the value from the MSP_GOP_HORIZON_DAYS profile option and uses it to set the status to `Delay of 29 Days` (30 minus today).

You didn't specify a Warehouse on the order line, so Promising looks at all the ATP rules that apply.

The assignment level for Denver is Global, and the level for Seattle is Item. Item is more specific than Global, so Promising uses Seattle's ATP rule.

Seattle doesn't have any supply, so Promising gets the value from the MSP_GOP_HORIZON_DAYS profile option and uses it to set the status to Delay of 29 Days (30 minus today).

Scheduling

Scenarios	Description
1 through 3	Promising was able to schedule the line, so it sets the status to `Scheduled`.