Check Control of Requirements Type Determination

In the standard system, requirements types are determined according to a specific search strategy beginning with the material strategy group.

Strategy for Determining the Requirements Type

1. First, an attempt is made to find a requirements type using the strategy group in the material master.
2. If the strategy group has not been maintained, the system will determine it using the MRP group.
3. If the MRP group has not been defined, the system uses the material type instead of the MRP group when accessing the corresponding control tables.
4. If no requirements type is found here, the system assumes a special rule and attempts to find a requirements type with the aid of the item category and the MRP type.
5. If this is not possible, a last attempt is made to find a requirements type with the item category only.
6. If the last attempt fails, the system declares the transaction as not relevant for the availability check or transfer of requirements.


You can select an alternative search strategy in the 'Source' field, for example a transaction-related procedure for determining requirements type (source = 1 or 2).


There are business transactions, such as consignment stock processing, in which the material with its planning characteristics is not important, rather the transaction itself. An issue from the customer's consignment stock should not trigger an availability check against planning at the plant as layed down by the planning strategy but rather against special stock.


1. Assign the item categories and MRP type to the requirements types.
2. Select an alternative search strategy in the 'Source' field if necessary.

Notes for determining requirements types in releases previous to 3.0

Up to and including Release 2.0, requirements types were determined using the document item category and MRP type of the material in the relevant plant.

As of release 2.1, this specification is carried out identically for Logistics by means of the MRP group of the material which specifies a strategy from which the requirements type is determined.