Heuristics for Use with Descriptive Characteristics
Use
There are three standard heuristics that you can use together with descriptive characteristics and that are described here. Other heuristics can also be used, but there is no difference in the functionality to the standard situation.
Features
Ascertainment
This heuristic determines the open planned independent requirements, that is those requirements that have not been covered by a sales order. Planned orders must exist for the requirements before you can execute this heuristic. When you start the heuristic, you can make selections to limit the number of objects processed. On the initial screen you can also make entries for the offset to the opening horizon and the ascertainment horizon.
Note
The entry for the ascertainment horizon here only takes effect, if there is no entry in the product master.
Reorganization
There are two reorganization heuristics
Reorganize orders
This heuristic reduces or deletes open planned independent requirementsand associated planned orders for selected planned orders or purchase requisitions. Open planned independent requirements are those for which no corresponding sales orders exist.
Reorganize orders via product
This heuristic does the same as above, but starts its selection from a product.
In both cases dependent requirements are also adjusted.
Capacity Reservations
You can maintain capacity reservations on resources for the characteristics in the consumption group. The planning heuristics and Capable-to-Promise (CTP) consider these capacity reservations on the resource while scheduling the orders.
Propagation of Descriptive Characteristic Values
You can propagate descriptive characteristic values to dependent requirements in the procurement planning and CTP scenarios. The propagation occurs only if the relevant indicator has been selected in Global Customizing (/SAPAPO/RRPCUST1) at the client level or in the Product Master at product level. Descriptive characteristic values for the dependent requirements are evaluated using the values for all characteristics of the primary requirement and the location/product for the dependent requirement.
Pegging in LiveCache is not based on descriptive characteristic values. Therefore after a change in pegging, the descriptive characteristic values at the dependent requirement may not match those of the primary requirement to which it is pegged. In such a case, you can trigger a fresh propagation of descriptive characteristic values based on the new pegging values using heuristic SAP _PP_023.
For more details on these heuristics, refer to the online documentation (
icon beside heuristic) and the F1 help.