SAP Batch Derivation

 
 
Study Material Contributed by Ulhas Kavle - Senior SAP Consultant

SAP Batch Derivation

 

SAP Batch derivation

 

 

Definition

 
 

Transferring batch characteristics values or batch master fields from the sender batch to the receiving batch is called “Batch Derivation”. The component batches can pass on their Field values/characteristics values to the manufactured batch.

 

Events at which the copy of characteristics values to the manufactured batch is possible =

 

·         At Goods Receipt of the manufactured quantities

 

·         At Release of order

 

·         At Usage Decision

 

·         At Batch Creation

 

 


 

Batch Derivation Example

 

 

The following is an example of batch derivation at production order or process order release.

 

 

Production order / Process order = 1000120 for Material M1

 

 

Step 1: Define the transfer characteristics from the issued or sending component batches to the manufactured batch.

 

 

Issued Component

Batch

Concerned Characteristics

Value

Require Transfer

Logic

C1

B1

COLOR

RED

NO

 

 

 

WIDTH

2 M

YES

Move Average Value

 

 

LENGTH

10 M

YES

Move Average Value

 

 

HEAT NUMBER

H1

YES

Move the Minimum

 

 

 

 

 

 

 

B2

COLOR

RED

NO

 

 

 

WIDTH

3 M

YES

Move Average Value

 

 

LENGTH

10 M

YES

Move Average Value

 

 

HEAT NUMBER

H1

YES

Move the Minimum

 

 

 

 

 

 

                                   

 

 

Step 2: At Goods Receipt of the order or at Release of the manufacturing order or at usage decision, the transfer of characteristics can be triggered from the sending batch/es to the receiving batch/es.

 

Manufactured

Material

Batch

Concerned Characteristics

Value

Whether Copied over

M1

BX

DIAMETER

5 MM

 

 

 

WIDTH

2.5 M

Move Average Value

 

 

LENGTH

10 M

Move Average Value

 

 

HEAT NUMBER

H1

Move the Minimum

 

 

 

 

 

 

 

 


 

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.

 

 

Steps in setting up Batch Derivation Condition techniques

 

 

1. Create Sending Condition Tables

 

 

SAP provides a set of standard key combination sets or preconfigured sending condition tables. Conditions tables are created with a combination of conditions field all provided. You cannot add your own field. Each Condition table contains a key combination.

 

You can alternatively create your own sending key combination/condition tables other than that provided by SAP as shown above, by creating a custom sending condition table. Following set of sending conditions fields can be used to create your own sending key combination or sending condition table (Use configuration Transaction code DSC1):

 

Receiver Material

Receiver Material Type

Sender Material

Sender Material Type

Sender Plant

           

The key combinations or condition tables (for the sender) as provided by Standard SAP are as below:

 

Sender Material Number (Table 010)

Sender Material Type (Table 011)

Receiving material + sending material (Table 012)

Receiving material type + sending material type (Table 013)

Sending Plant (Table 502)

 

à You can create your own condition table – 901 with the following condition fields

 

     Sending material + Sending Plant (Table 901)

 

 

 

2. Create Receiving Condition Tables

 

 
SAP provides a set of standard key combinations set in preconfigured receiving condition tables. Conditions tables are created with a combination of conditions field all provided. You cannot add your own condition field. Each Condition table contains a key combination.

 

You can alternatively create your own receiving key combination/condition tables other than that provided by SAP as shown above, by creating a custom receiving condition table. Following set of receiving conditions fields can be used to create your own key combination or receiving condition table (Use configuration Transaction code DRC1):

 

Material Number

Material Type

            Receiving Plant

 

The key combinations or condition tables (for receiver) as provided by Standard SAP are as below:

 

Receiving Material Number (Table 001)

Receiving Material Type (Table 002)

Receiving Plant (Table 501)

 

à You can create your own condition table – 902 with the following condition fields

 

            Receiving material + Receiving Plant (Table 902)

 

 

 

3. Create Sender Access sequence,

 

 
Create Sender access sequence so as to help in searching the attributes of the sender batches. Some field key combinations or sending condition tables are already grouped together in priority sequence in the standard SAP Batch derivation access sequence “BDS1”.

 

The field combination which are set in a priority sequence in the configuration represent the field key combination that would be used to create the master data for sending party, which in-turn would help in searching the attributes of the sender batches.

 

If you choose to create your own access sequence, you may do so; when you do that you have to assign the sending condition tables in your own defined priority sequence. Transaction code is DSC5 to create access sequences in configuration.

 

SAP offers the following receiving condition tables (key combinations) for use in the access sequence BDS1 arranged in a priority:

 

10 Receiving material + sending material (Table 012)

20 Sender Material Numbers (Table 010)

30 Sending Plant (Table 502)

 

You can create your own sending access sequence arranged in a required access sequence: You can call this sending access sequence as “ZDS1”

 

10 Sending Plant (Table 502)

     20 Sending material + Sending Plant (Table 901)

 

 

 

4. Create Receiver Access sequence,

 

 

Create receiver access sequence to search for the attributes of the receiver batches. Some field key combinations or receiver condition tables are already set up in the standard SAP Batch derivation access sequence “BDR1”.

 

The receiver condition tables which are set in a priority sequence in the configuration represent the field key combination that would be used to create the condition record master data for receiving party, containing the characteristics and rules, which in-turn would help in searching the attributes of the receiver batches.

 

If you choose to create your own receiver access sequence, you may do so; when you do that you have to assign the receiver condition tables in your own defined priority sequence.

 

Transaction code is DRC5

 

SAP offers the following receiving condition tables for use in the access sequence BDR1 arranged in a priority sequence:

 

10 Receiving Material Number (Table 001)

20 Receiving Material Type (Table 002)

30 Receiving Plant (Table 501)

 

You can create your own receiving access sequence arranged in a required access sequence: You can call this sending access sequence as “ZDR1”

 

10 Receiving Plant (Table 501)

     20 Receiving material + Receiving Plant (Table 902)

 

 

 

5. Sending Condition Type (Strategy type)

 

 
Sending Condition types is created to assign the sending access sequence to it. Standard SAP already has done this for you.

 

In SAP, the standard sending condition type BDS1 is created and assigned to the standard sending access sequence BDS1.

 

 

Transaction code is DSC6.

 

 

6. Receiver Condition Type (Strategy type)

 

 

Receiver condition types are created to assign the receiving access sequence to it. Standard SAP already has done this for you.

 

In SAP, the standard receiving condition type BDS1 is created and assigned to the standard receiving access sequence BDS1.

 

 

Transaction code is DRC6.

 

 

 

7. Sending Batch Derivation Search Procedure

 

 

Sending Batch Derivation Search Procedure contains the sending Condition type.

 

Various condition types are assigned in a priority sequence for use for searching the sending batches and its data.

 

 

Note: You can choose to assign more than one condition type set in a priority while building a search procedure.   

 

Transaction code is DSC7.

 

 

 

 

8. Receiver Batch Derivation Search Procedure

 

 

Receiver Batch Derivation Search Procedure contains the receiving Condition type.

The various condition types are assigned in a priority sequence for use for searching the receiving batches.

 

Note: You can choose to assign more than one condition type set in a priority while building a search procedure.  

 

Transaction code is DRC7.

 
 

 

 

Step 4:

 

 

Define the Batch Derivation Event

 

 

Defining derivation event would tell the system of a business event to trigger batch derivation, i.e., a point in time to transfer batch characteristics values from a sender batches to a receiver batches.

 

The transaction code to configure the derivation events is DVC8.

 

To configure the batch derivation event, the following information is fed to the system:

 

A)    When do you want to trigger the batch derivation?

 

The answer to this question decides when you would wish to trigger the batch derivation

 

  • @ Release of production/process order
  • @ Goods receipt from production/process order
  • @ Usage Decision
  • @ Manual Batch Derivation
  • @ Batch Master creation

 

 

B)    What would be the Sender/Receiver Batch Determination Procedure?

 

 

The answer to this question decides the search of the sender batch and the receiver batches to copy/compute the batch characteristics values for the receiver batches.

 

 

  • Assign a Sender Batch Derivation Search Procedure
  • Assign a Receiver Batch Derivation Search Procedure

 

 

C)    What is the type of Batch Derivation?

 

 

The answer to this question decides what would be the type of Batch Derivation that is required for business use.

 

  • Static batch derivation transfers the characteristics values of the sender batches to the receiver batches. A derivation log is generated in the derivation Monitor.
  • Dynamic batch derivation does not transfer the characteristics values of the sender batches to receiver batches, it only simulates the transfer. The receiving batches are not automatically updated with the transferred values; you would have to manually change it.

 

 

D)    Do you want to display the batch derivation results

 

The answer to this question decides whether the derivation results are displayed.

 

  • Display in Errors
  • Hide when ok
  • Always Display
  • Always Hide

 

Following steps can be followed to implement batch derivation in your organization:

 

 


 

Step 5:

 

 

Creating Sending Condition Records or Sending Batch search Strategies

 

 

When you configure the system till the creation of batch derivation search procedures for both sending and receiving parties, you would eventually create the master data for the sending conditions. To create the sending condition records you should follow the process as below using the transaction code DVS1/DVS2/DVS3:

 

Choose the batch derivation strategy from the drop down >>> Then choose a key combination as set in access sequence >>> and then create the sending batch derivation strategy master data by entering values for the condition fields of the key combination >>> Enter the characteristics that you would want to transfer the values from the sending batches >>> Save.

 

There is not much of data entry when you create the sending condition record apart from assigning the characteristics for which values are to be transferred to the receiving batches.

 

You can set master data for more than one key combination (a key combination decides the master data level at which the master data is created), but the system at the time of execution would first access the first condition key combination and check whether the master data exists for the sending batches, if the sending batches are not found using the first sending condition record master data, the system would check whether the master data for the sending batches exists for the second key combination condition and if the batches are not found using the master data under the second sending condition records then it will go to the next key combination in the access sequence and search whether master data for the sending batches is created for the third key combination, so on and forth.

 

 


 

Step 6:

 

 

Creating Receiving Condition Records or Receiving Batch search Strategies

 

 

When you configure the system till the creation of batch derivation search procedures for both sending and receiving parties, you would eventually create the master data for the receiving conditions. To create the receiving condition records you should follow the process as below using the transaction code DVR1/DVR2/DVR3:

 

Choose the batch derivation strategy from the drop down >>> Then choose a key combination as set in access sequence >>> and then create the receiving batch derivation strategy master data by entering values for the condition fields of the key combination >>> Assign the characteristics for which you want to receive the characteristics values >>> Assign rules for the characteristics.

 

The Rules for the receiving characteristics are concerned with the following sending characteristics attributes:

 

 

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

 

 

You can set master data for more than one key combination (a key combination decides the master data level at which the master data is created), but the system at the time of execution would first access the first condition key combination and check whether the master data exists for the receiving batches, if a receiver batch derivation master data does not exists for the first key combination and the system fails to search the receiving batches using this condition record, it would further check whether the master data for the receiving batches is covered in the second key combination condition and if the master data does not exists under this given condition then it will go to the next key combination condition in the access sequence and search whether master data for the sending batches is created for the third key combination conditions, so on and forth.

 

 


 

Step 6:

 

 

The Actual Derivation

 

 

Once the batch derivation configuration is done and the master data is set, the derivation is triggered at the point where it is defined for.

 

SAP issues messages of success or error or information when the derivation finishes. You can define in transaction code DVC8 – Batch derivation Event configuration, if you want such messages to be popped-up after the derivation.