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.