As per my impression, “User requirements” is missed-out function. It is able to be used to keep parent component/model’s BOM line and Route operations simple and legible. User requirement function acts like “Phantom component” of configuration model. Once BOM is created by configuration model, system explodes the BOM line(s) or/and route operation(s) which is/are defined under “User requirement” component. Let me explain the function step by step: Initially, a component needs to be defined for the use of “User requirement”. Afterwards, BOM lines and/or route operations need to be defined under the regarding component.

Once all the setup is done, the other step is to define related component as User requirement on parent model/component. Once user requirement is defined, system creates the user requirement as a component.

Note: User requirement component does not need to be related with the product master like component or model (Under “Components” tab, user has to select Product master and under “Versions” button, user has to define a product master).

  Once configuring line on any of the order line, system adds the BOM line(s), which is/are defined under “User requirements” component, to its parent model’s BOM line.