This component enables you to do the following for batch master data and classification data of the component batches of produced batches:

• Transfer
• Display for selection
• Display

The following basic rules apply:

• Component batches may send data.
• Produced batches may receive data.

In the following text, the term sender batch is used for component batches and receiver batch is used for produced batches.

To be able to derive batch data, you must have set up the batch where-used list. The derivation functions along the batch where-used list. In other words, only those component batches are included that were used in the produced batch.

The batch derivation function uses the condition technique to determine which batches of a batch where-used list take part in such a data transfer. Condition technique is also used in pricing or batch determination.

The derivation can be called and used in all areas of Logistics at fixed times (for example, when posting goods receipts for production orders, when releasing process and manufacturing orders, when making the usage decision).

To fulfill the requirements that occur in various business processes, there are generally two types of derivation:

• Static derivation
• Dynamic derivation

Depending on the situation, it might be useful to start the derivation of batch data from the component or the product. However, the data is always transferred from a component to a product, in other words in the same direction as the quantity flow.

• Pull derivation (1 receiver, n sender)

• Push derivation (n receiver, 1 sender)

Derivation of batch data can be implemented in the following scenarios:

1. Filling

A batch of a material is produced and is placed into various containers, before the results of the quality check are available. If the bulk batch is specified, these results should be transferred to the container batches.

2. Pick and pack activities