PRINT FROM SAP HELP PORTAL

Document: Derivation of Batch Data URL: http://help.sap.com/erp2005_ehp_06/helpdata/en/b7/582d38c4b3f205e10000009b38f8cf/content.htm Date created: July 04, 2013

2013 SAP AG or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Note This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.

PUBLIC 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 1 of 3

Derivation of Batch Data

Use
The batch derivation function enables you to transfer field values and characteristic values (attributes) from one or more batches to another batch during certain events. In this way, the field values or characteristic values of the receiving batch can be changed.

The shelf life expiration date of a component batch can determine the expiration date of a produced batch. Therefore, the expiration date of a component batch is transferred to that of the produced batch during a certain event.

Integration
The batch derivation function is designed to transfer data from component batches to produced batches. This means that only component batches used to produce another batch are included in the derivation process. In other words, the derivation works along the batch where-used list. 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 and batch determination. For further information, refer to the section SD - Introduction to the Condition Technique.

Prerequisites
The batch where-used list is activated.

Features
The data is always transferred from a component batch to a produced batch so that data transfer runs at the same time as the quantity flow. Events Batch derivation can be executed in the following 4 events: Recording a usage decision Creating or changing a process order Creating or changing a version of the EBR (electronic batch record) Performing shipping approval Derived attributes You can derive the following attributes: Fields of the batch master record (Classification) characteristics of the batch The following basic rules apply: Component batches may send data Produced batches may receive data Produced batches may send and receive if they send data to themselves. A derivation according to the pull principle always has one receiver, but can have several senders. The data is transferred to the receiving batch from batches in the batch where-used list of the receiving batch. Data that can not be transferred from batch master data or classification characteristics to the identical attribute in the receiver batch can be integrated using the customer exit EXIT_SAPLDRVN_001. This customer exit allows more flexibility as to where the data to be derived comes from.

Activities
To use the batch derivation function, you have to: Customize the condition technique for derivation Maintain condition records for derivation Pull derivation is carried out as follows: 01. When a pull derivation is called, the system first checks if a condition record exists for the receiving batch. This condition record contains the attributes that shall be transferred. The search for a condition record ends after the first condition record is found. 02. The batch where-used list is then analyzed to find all the batches that were used to produce this batch. To this end, the system performs a top-down analysis starting from the receiving batch. 03. For every component batch the system has to decide whether or not it is a sender. The condition record contains the attributes (fields, characteristics) that shall be sent from this component to the receiving batch. 04. The names of the sent attributes must match the names of the received attributes in order to be transferred. 05. The attributes of the sender batches are read. 06. The attributes are transferred to the sender batch using selection rules defined for each attribute.

Customizing Condition Technique for Derivation

You configure Customizing for the condition technique as described in the step Batch Derivation. You customize receiver records and sender records separately. 01. Condition tables A condition table defines the fields that make up the key for the condition record. In this step, you define how this key is to be put together. You later use these condition tables to specify the condition records for sender and receiver batches. 02. Access sequences You use access sequences to define the sequence in which the system searches for condition records via condition tables. 03. Strategy types One access sequence has to be assigned to each strategy type. When the condition technique is used in other functions, strategy types are used to store default values. This feature is not currently used by the derivation

PUBLIC 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 2 of 3

function. 04. Search strategies With the help of search strategies, you define the sequence in which the system uses the strategy types. 05. Assign search procedures to derivation events In this step, you assign your search strategies to the derivation events. Derivation can be carried out for the following events: Usage decision Process order (or production order) Electronic batch record (EBR) Shipping approval For more information, refer to the section SD Conditions and Pricing .

Maintaining Condition Records for Derivation

Use
You use condition records to define: Attributes and rules for receiver batches Attributes that sender batches send to the receiver batch You maintain the condition records for receiver batches and sender batches separately.

Prerequisites
You have configured the condition technique for derivation in the step Batch Derivation in Customizing. Create condition records 01. On the Derivation Create Search Strategy entry screen, enter a strategy type and choose Enter. The system prompts you to select a key combination if there are more than one. 02. Chose the key combination that your new condition record is to have. 03. Maintain the key fields. For example, in the Receiving material field, enter the material number of the batch that shall receive the data. 04. Choose Details. The Create (strategy type): Detail screen appears, where you maintain the attributes that shall be sent or received and the rules that shall apply for the derivation of every attribute. Attribute tab strip: 01. Select the indicator Fld if the attribute is a field from the batch master record. Select the Char. indicator if it is a classification characteristic. 02. Choose the required attribute via the F4 Help function. 03. Deletion indicator Using the deletion indicator, you determine whether or not the condition shall be used for the derivation. 04. Using the Save messages indicator, you determine whether warnings and error messages shall be stored with the derivation. Those messages are displayed in the derivation monitor. Rules tab strip: This tab strip is only relevant for receiver batches. In this step, you determine the rules that are used to process the attributes sent by the sender batches before they are transferred to the receiver batch. You will find explanations for each rule in the F1 help of the respective fields. Rules for controlling the derivation Comparative selection rules Boolean selection rules Selection rules for multiple-value characteristics 05. Close condition record maintenance by choosing Save. Change condition records You change condition records as described above in the section Create condition records.

PUBLIC 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 3 of 3