| Component CTP and capacity CTP for clusters |  |
| For clustered items the application of CTP checks is somewhat restricted. For clustered items, you can use three types of available-to-promise functionality: standard ATP check channel ATP check family CTP check For clustered items, the use of the following CTP functionality is restricted: component CTP check capacity CTP check Caution! If you have a cluster set-up with several clustered items and/or non-clustered items with the same item segment, the CTP functionality works correctly as long as you make sure that only one of these clustered or non-clustered items has a source Production. If multiple clusters have the source production, the capable-to-promise functionality produces erroneous results, because the system promises the same capacity and components to multiple orders: once for each cluster. This happens because a clustered item shares a bill of material, bill of critical material, routing operations, or bill of critical operations with clustered items that belong to the same item. If a clustered item has a valid sourcing strategy, ERP LN checks the component CTP and capacity CTP only if the sourcing strategy has a Production source (more than 0%). If a clustered item has no valid sourcing strategy, ERP LN checks the component CTP and capacity CTP only if the Default Supply Source is Production/Purchase and the Actual Supply Source at the requested date is Production. To define sourcing strategies, use the Sourcing Strategy (cprpd7110m000) session. To define a plan item's Default Supply Source, use the Items - Planning (cprpd1100m000) sesion. Related topics Clusters in Enterprise Planning Capable-to-promise, an overview Date-effective item data |