Collect Planning Data for Your Configuration Model
Collect planning data at various points of your set up process, and also after you finish set up.
Collect Setup Data
Collect setup data each time you.
-
Create or modify a model.
-
Modify the item, item structure, catalog, or work definition.
- Collect Planning Data for Order Management
-
Set up a new item in the Product Information Management work area.
Collect data. For details, see Collect Planning Data for Order Management.
Attribute |
Value |
---|---|
Items Item Structures Work Definitions |
You must include these entities for each model. |
Collect Runtime Data
Periodically collect data for each new configured item your users add when they create a sales order. Collection gets the on-hand quantity for return orders and canceled order. The quantity affects planning. Specify attributes when you do the Supply Planning Data task.
Attribute |
Value |
---|---|
On Hand |
Promising uses this entity to get the inventory that's in stock for the model. If all components in the configured item aren't in stock, then Promising won't find availability for the model. For example, assume the schedule requires you to build the item within five days to meet the delivery date. Promising examines the build schedule for each component, the current backlog of purchase orders for component x, and determines component x isn't available for your order until the sixth day. |
Purchase Orders and Requisitions Transfer Orders Work Order Supplies |
Add these entities so Global Order Promising can get availability across the entire supply chain. |
Don't use templates that the dialog displays, such as Dynamic Data for Supply Planning. The templates don't apply for configure-to-order.
Make sure you refresh the server.