Show TOC

 Treatment of Individual Customer Requirements

As a rule, you should always have specified collective requirements for the components of an RPM product. You may nevertheless want to plan certain key assemblies/components as individual customer requirements.

The system determines the dependent requirements for the components that are to be treated as individual customer requirements immediately the planned order is created for the end product and saves the requirements in the order as input nodes.

The dependent requirements for the components that are marked as collective requirements are not determined until the RPM run.

However, after the RPM run the planning matrix also contains the components with individual customer requirements. This is necessary so that the system can determine any master data or configuration errors.

Restrictions

  • If a component is part of a phantom assembly and is to be planned as an individual customer requirement, the individual customer requirement indicator must also be set for the phantom assembly. This is checked at the time of PDS generation.

  • If you change a component from individual customer to collective requirement and later change it back to individual customer requirement, it may happen that the dependent requirement determined is deleted.

    Example Example

    You have specified individual customer requirement for the component K1. You generate a production data structure (PDS). The system creates a planned order P1 for a newly received sales order A1. At the same time, the system also generates an input node in the order for the component K1.

    You then change the component K1 by setting the collective requirement indicator. The PDS is regenerated. You then carry out an RPM run. The order P1 now contains two dependent requirements for K1. A collective requirement identified as a dependent requirement in the make-to-stock segment and an individual customer requirement in the individual customer segment.

    If you then change the component back to individual customer requirement, the system will delete both types of dependent requirements at the time of the next RPM run. Because the input node for the individual customer requirement is only generated when the order is created, the system has not generated any further dependent requirement.

    End of the example.