SAP Batch Derivation Types

 There are 2 types of Batch Derivations, Pull and Push Batch Derivation.

 Pull Derivation

 Pull derivation exists when there are multiple sender batches and one receiver batch.

 Batch Master Characteristic’s values or Batch Master Field values can be transferred
to the receiver batch from the sender batch.

 For a given characteristics either its value from the first batch can be copied over or
an average value can be copied over to the receiver batch.

Pull Derivation = Many Senders >>TRANSFERRED>> One Receiver

                       = n senders  – 1 Receiver

 Push Derivation

 When there are many receivers and 1 sender. You have to choose whether the batch
derivation is a push derivation in the sender condition record.

 An example of Push derivation can be:

 When you procure a component batch and use it to produce chemical products which
are produced in bulk and stored in various bulk containers marked with unique batch
numbers, in this case you if you want to transfer a component batch characteristics
value or component batch master fields to the receiver batches, then you can do so
using “Push Batch Derivation”.

 Push Derivation = One Senders >>TRANSFERRED>> Many Receiver

                           = 1  senders – n Receiver

Steps in Settings up SAP Batch Derivation

 One can use the following steps to set up batch derivation in SAP.
Step 1:

 Activate Batch Where used list

 One should activate the Batch where used list, in the configuration with the BaWU
Synchron.posting indicator on– Allowing the system to figure out the sending batches
and the sending characteristics values. There is no Transaction code for this, you have
go to Logistic General >>> Batch >>> Batch Where Used List.

 Step 2:

 Batch Derivation Activation

 Batch Derivation should be active in configuration so as to use this functionality. Use

transaction code DVSP.

 Step 3:

Setting Batch Derivation Search Procedure Techniques

It becomes really impossible for us to inform the system about the sending batch
number (for each and every batch) and the characteristics/rules to transfer to the
receiving batch number/s. Thus we use the batch search procedures and conditions
records to direct the system so that for all the sending material batches at the “plant”
level should be considered in the search and its data should be transferred to the
receiving material batches. A similar condition record should be set for the receiving
side so that all the material batches at the “receiving plant” level should be considered
in the search and they should receive the characteristics data. Setting the sending
condition on “sending plant” and the receiving condition on the “receiving plant” is
just an example. You could define the levels at which condition records should be
defined through the standard condition table and access sequence configuration

 SAP makes it easier for the users to make various combinations of levels for the
sending party and the receiving party, to do this you should choose the condition
fields as supplied by SAP and create a condition table and use these tables or key
combinations to assign them in an access sequence with priorities. This suggests that
you can make use of more than one key combination assigned in priorities so that if
the condition record for one combination is not found, the system can make use of the
next condition record to search for the sending batches and the receiving batches
involved in the transfer.

 Once the Condition tables, access sequences, strategy types, and search procedures
are configured for the sending party and the receiving party, you should then create
condition records at the defined levels or defined key combination, for the sending
party and the receiving party.

 For example

 If the sending key combination or sending condition record is to be defined at the
“sending material-plant” level, then you should define the “actual sending material
and the “sending plant” in the condition records and the characteristics involved in the
transfer.

 On the other hand you should also define the condition records key combination for
the receiving party, for example if you make a definition at the “receiving material-
receiving plant level”; you should enter the actual receiving material and the receiving
plant involved in the derivation, to help the system to search for the receiving batches.

 While you create the receiving condition records, you should maintain a set of
transfer specific rules i.e., if the sender field/characteristics value is empty or the
sender is overwriting any existing characteristics values in the receiving batch then
should it error out the transfer or issue an warning or do nothing and on the other hand
you can direct the system to send minimum/maximum/average value of the sender
characteristics if there are more than one sender batches or more than one value is
defined for the characteristics in the sending batch.

 The Batch derivation procedures and the condition records, for the sending party and
the receiving party, which are set, it helps the search for all the concerned sending
batches and the receiving batches, and identifies the rules defined in them, so that the
characteristics values can be transferred to the receiving batches.