You use this heuristic to generate new receipt elements to cover product requirements. Here, the lot size parameters maintained in the product master are taken into consideration.

You use this heuristic to create new receipt elements in order to cover product requirements. Product requirements can be purchase requisitions, planned independent requirements, transfer requests or dependent requirements. Receipt elements are created for in-house production or external procurement, depending on transportation lanes, the PPM or the procurement type in the product master. Lot sizes defined in the product master are used to calculate the receipt quantities.

You use this heuristic to plan just the shortages and to reduce surpluses. Dynamic pegging relationships are taken into account with this heuristic.

You use this heuristic to define three planning horizons within which a different lot-sizing procedure can be used. You are able to choose between a procedure with lot-for-lot order quantities or various period lot sizes.

You use this heuristic to optimize setup and storage costs when calculating the lot size. Starting from the product shortage date, consecutive requirements quantities continue to be collected in a lot until total storage costs exceed the setup costs. Lot-sizing parameters are taken into account during this procedure.

You use this heuristic to calculate the quantities of external procurement orders for material bottlenecks of a product. The system specifies the unit costs for each manufacturer, taking into consideration storage costs, fixed order costs, quantity-dependent discounts and manufacturer-dependent dispatch times. Once the optimum discount scale is reached and the costs begin to rise again, no more lots are created.

You use this heuristic so that procurement is always triggered when the sum of the inventory levels and fixed receipts exceeds the so-called reorder point. The reorder point should cover the expected average material requirements during the replenishment lead-time.

You use this heuristic to plan products according to the heuristic defined in the Product Master for each product. The heuristic is carried out for the top level product using low-level coding, that is, if a component is not available on time, the top order is not rescheduled. The components that are defined as being planned automatically (both immediately or in planning run) are then planned using the heuristic defined in the Product Master. If you have not defined a heuristic for a product in the Product Master, the APO System uses the default heuristic you have entered for the Product heuristic in Customizing for Production Planning and Detailed Scheduling, under Global Settings ® Maintain Global Parameters and Defaults.

Components that are defined as being planned manually (both with and without availability check) are not taken into account during the production planning run. The availability check for components planned manually with check is not carried out.

You use the product heuristic to plan products according to the heuristic defined in the Product Master for each product. The heuristic is carried out for the top-level product. Components that are defined as being planned automatically and immediately are planned using a simple lot-sizing heuristic. Planning with this heuristic is carried out according to multi-level logic, that is, if a component is not available on time, the top-level order is rescheduled. For the components that are defined as being planned automatically in the planning run, planning file entries are created. The product heuristic can be executed in interactive planning and during the production planning run. If you have not defined a heuristic for a product in the Product Master, the APO System uses the default heuristic you have entered for the Product heuristic in Customizing for Production Planning and Detailed Scheduling, under Global Settings ® Maintain Global Parameters and Defaults.

The availability check is carried out for components that are defined as being planned manually with availability check.