8/10/2017 Batch Derivation Overview with example | SAP Blogs

Products
Products Industries
Industries Support
Support Training
Training Community
Community Developer
Developer Partner
Partner

About
About

Home / Community / Blogs + Actions

Batch Derivation Overview with example

February 18, 2013 | 2,817 Views |

santosh sarda
more by this author

MAN Production Planning (PP)

Manufacturing | SAP ERP | batch | derivation | enterprise resource planning | management | sap erp manufacturing production
planning

share share tweet share 0

like

Follow

Purpose of Batch Derivation:

It enables you to do transfer/ display for batch master data and classification
data of the component batches of produced batches. Component batches may
send data and produced batches may receive data.

Derivation Event

https://blogs.sap.com/2013/02/18/batch-derivation-overview-with-example/# 1/10
 8/10/2017 Batch Derivation Overview with example | SAP Blogs

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).

Pull Derivation (1 receiver: n senders)

The deriva on is triggered from a transac on that affects the product. Here,
data from various senders can be collected, cumulated, and calculated.

Within a deriva on according to the pull principle, there can only be one
receiver, but there can be several senders (example usage: pick and pack for
pharmaceu cal products).

1. Pull deriva on can be triggered during usage decision through QM in

background.

2. When produc on order / process order is released.

3. When Goods receipt for produc on order / process order is posted.

4. Batch deriva on can be triggered manually with transac on DVMAN.

5. You can also call batch deriva on with user defined events in user
exits.

You have to maintain the required deriva on events in Customizing for

Batch Management under Deriva on of Batch Data -> Define Deriva on
Events.

Push derivation (1 sender n receivers)

Within a derivation according to the push principle, there can only be one
sender and several receivers.
This derivation is started from a transaction that affects the component
batch. Here, data from a sender batch can be derived onto several receiver
batches. You can trigger a push derivation at Usage decision or manual
derivation or with user defined derivation event.
Derivation Type
To fulfill the requirements that occur in various business processes, there
are generally two types of derivation:
· Static derivation
· Dynamic derivation
Static derivation is recommended if a batch is newly created or changed
and the values in the receiver batch(es) should be filled with the attributes
from the sender batch(es).
Dynamic derivation is used when

https://blogs.sap.com/2013/02/18/batch-derivation-overview-with-example/# 2/10
 8/10/2017 Batch Derivation Overview with example | SAP Blogs

the receiver batch must/should not be changed

the sender values should be used as the basis for a user decision

Prerequisites for batch Derivation:

1. The batch where-used list must be activated with the BaWU

synchron.posting indicator (synchronous posting of batch where-used
records).

You make the settings for the batch where-used list under

Batch Where-Used List ->Make Settings for Batch Where-

Used List :

Batch deriva on must be ac ve (Deriva on of Batch Data

Ac vate Batch Deriva on) in customizing of batch deriva on.

1. Sender and receiver search strategies must be assigned to the derivation

events in customizing.

If SAP standard condi on se ng for receiver / sender search are not enough
you can configure your own under Set Up Condi on Technique for Deriva on in
customizing.

https://blogs.sap.com/2013/02/18/batch-derivation-overview-with-example/# 3/10
 8/10/2017 Batch Derivation Overview with example | SAP Blogs

1. 5. Condition records should be maintained for receiver as well as sender

batches which we will demonstrate in example further.
Batch Derivation Example:

We will see how bulk red paint (CH-1110) transfers the characteristics to
Filled red canister CH-1100.

All prerequisite configurations is set as shown above.

Transaction CS03:

Receiver condition records: Transaction DVR1/DVR2:

https://blogs.sap.com/2013/02/18/batch-derivation-overview-with-example/# 4/10
8/10/2017 Batch Derivation Overview with example | SAP Blogs

Characteristics color_index_red & paint_viscosity should be received from

red paint.

Rules are set to determine batch derivation behavior as show below :

If multiple senders are sending chacateristcs values it will adopt the

minimum characteristics value. In case of Sender is empty or recipient has
the value it would provide the warning.

Sender condition record setting:

Transaction: DVS1/DVS2:

Sender condition records are maintained as shown below:

https://blogs.sap.com/2013/02/18/batch-derivation-overview-with-example/# 5/10
8/10/2017 Batch Derivation Overview with example | SAP Blogs

Derivation events are set in customizing to occur in all possible scenarios of

pull derivation. We would check It with goods receipt of filled red canister of
10KG (CH-1100).

Create and release process order to fill bulk red paint in 10 kg canister.

https://blogs.sap.com/2013/02/18/batch-derivation-overview-with-example/# 6/10
8/10/2017 Batch Derivation Overview with example | SAP Blogs

Transaction: MB31:

In next document I would explain how BADI DERIVATION can be used to

enhance batch derivation functionality.

https://blogs.sap.com/2013/02/18/batch-derivation-overview-with-example/# 7/10