Generic items in Enterprise PlanningA generic item represents an item structure that is configured according to a customer's preferences. This configuration takes place in the Product Configuration module. When an actual sales order is closed for a generic item, LN generates a project structure, and the demand is recorded for the corresponding project item. This means that for the generic item itself, no actual demand exists. Only the following types of demand can exist for a generic item:
Master-based planning Master-based planning for a generic item is similar to master-based planning for a normal item. You can maintain an item master plan for a generic item, and use BCMs and BCCs to explode critical requirements. As long as the configured (project) items involved are derived from the generic item (see the Derived-from Item field in the Item - General (tcibd0101s000) session), you can:
Order-based planning Order-based planning for a generic item differs from normal order-based planning in that it uses:
Generic BOM The following fields in the Generic BOMs (tipcf3110m000) session are relevant for planning in Enterprise Planning:
The planning percentage roughly indicates how often this particular material is actually used for a configured item. The required quantity for planning is computed as follows: The requirement date of a material in a generic BOM is determined as follows:
Generic routing The operations in a generic routing are not planned with regular backward planning, but each operation involved is planned with its own lead-time offset. The following fields in the Generic Routing (tipcf3120m000) session are relevant for planning in Enterprise Planning:
The planned production time is used to plan the operation involved. The planning percentage roughly indicates how often this particular operation is actually used for a configured item. The capacity use of the operation is computed as follows: The start date and finish date of an operation in a generic routing are determined as follows:
| |||