Activating Requirements

Use

Use this function to determine when the system should create purchase requisitions for material components (and service activities) or when reservations should become relevant for MRP.

The following options are available in the Reservation/Purch.Req. field:

  • The system activates requirements immediately

  • The system activities requirements when you release the network or activity

  • You prevent requirements from being activated, even after release.

This is useful for instance, if you want to cost components but do not want to trigger MRP or purchasing. Another case is if you have copied assemblies from a standard network, but want to activate requirements for subordinate components first.

Activities

You can control the activation of requirements from various hierarchy levels.

  • The system copies the default value for the Reservation/Purch.Req. field from the network profile to the network. You can change this value in the network header on the Control tab page. This setting is then valid for all the network activities and their assigned components.

  • Irrespective of the setting in the network header, you can activate all requirements for individual activities, WBS elements or the whole network manually. See Activating all Requirements in a Hierarchy

If you activate requirements for the whole network, this has - as opposed to changing the field in the network header- no effect on activities or component assignments that are created later.

  • You can also change the Reservation/Purch.Req. field when you assign a component to an activity or later. You can do this in either the component overview or on the detail screen for the individual component assignment.

If the system has already created a purchase requisition for a component, you can go directly from the component assignment detail screen to this purchase requisition.

The reservation number is displayed on the component assignment detail screen, even if the reservation is not relevant to MRP: