Create Promising Rules for Your Configuration Model

Use an available-to-promise (ATP) rule and sourcing rule to promise your configured item in different ways.

At runtime, Order Promising determines the lead time for the model and components, depending on the option classes and options your customer chooses. Here's how Promising does it.

Examines various paths in the item structure and determines the longest path.
Considers fixed and variable lead times for items across the structure. The lead time for the model influences order promising behavior. For example, if a sales order requests a model but no supply exists, then Promising makes sure it promises the sales order only on or after the model lead time.

Set up Order Promising to promise a pick-to-order model.

Make sure you set the Ship Model Complete attribute to Yes on the model in Product Information Management.
Make sure all components will be available on a specific date in the specified warehouse so Promising can promise the model for the date.
If a delay happens in receiving a component in the warehouse at some later time, then a person in shipping might decide to ship only the parts of the configured item that are available. You might need to do more processing to ship the remaining part of the configured item that doesn't involve promising.

This section describes how to set up rules for a configured item. For details, see Assignments and Promising Rules.

Assume you must create an available-to-promise rule for the CTO_474000 model. For details, see Create Your Configuration Model.

Try it.

Go to the Global Order Promising work area, then click Tasks > Manage ATP Rules.

On the Manage ATP Rules page, click Actions > Create, then set the values.

Attribute	Value
Name	ATP rule for Build My Laptop
Promising Mode	Choose a value. Supply Chain Availability Search. Consider supply for the configuration components in your model when promising availability. Choose this value for most configured items. You must use this value for a back-to-back flow. Lead Time Based. Use this value when the supply chain for your item is reliable and predictable. Infinite Availability Based. Use when your item is always available.
Search Components and Resources	Enable it. Allow Promising to consider components and resources when promising an assemble-to-order model. If you source the item through a back-to-back flow, then you must enable this option. Enabling produces the planning recommendation that the flow needs to create the supply order.
User Defined Fence in Days	Specify the point in time when the flow can consider that the configured item is always available. To make sure processing for an advance order is timely, set your time fence to a lead time that exceeds your typical lead time.

For this example, enable all attributes in the Supply Types area and Demand Types area. Global Order Promising will consider each type you chose when it analyzes your supply chain.

In your actual deployment, disable attributes you know aren't viable.

Click ATP Rule Assignment, click Actions > Add Row, then set the values. Add a separate row for the model, for each option class, and each configure option.

Assignment Basis	Assigned-to Item
Item	CTO_474000
Item	CTO_474101
Item	CTO_474102
Item	CTO_474201
Item	CTO_474202
Item	CTO_474301
Item	CTO_474302
Item	CTO_474100
Item	CTO_474200
Item	CTO_474300

Note

You must assign a rule to the model, each option class, and each configure option in your model at some hierarchical level.
You typically assign at the Item level.
You typically use the same rule for model, classes, and options. You can use different rules, but using the same rule simplifies set up, maintenance, and troubleshooting.

Click Actions > Add Row, then set the values.

Assignment Basis	Assigned-to Item Category
Category	GOP_Category

Note

This step assigns your rule at the Category level so the same rule can recognize each instance of your configured item that Product Information Management creates at runtime, such as CTO_474000-100 and CTO_474000-101.
Supply Orchestration associates the configured item that it creates at runtime with the same category you set for the configuration model in Product Information Management at design time. Downstream processes also use the same catalog at runtime.