Batch Management Overview

8/8/2019
Batch Management (LO-BM)

Generated on: 2019-08-08
SAP S/4HANA | 1809.002
PUBLIC
Warning
This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not re ect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.
For more information, please visit the SAP Help Portal.
https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=21766606&topics=8efeb753128eb44ce10000000a1… 1/23
8/8/2019
Batch Derivation
Purpose
This component enables you to do the following for batch master data and classi cation data of the component batches of
produced batches:
Transfer
Display for selection
Display
The following basic rules apply:
Component batches may send data.
Produced batches may receive data.
In the following text, the term sender batch is used for component batches and receiver batch is used for produced batches .
Integration
To be able to derive batch data, you must have set up the batch where-used list. The derivation functions along the batch where-
used list. In other words, only those component batches are included that were used in the produced batch.
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 or batch determination.
For more information, see Prerequisites for Batch Derivation .
Features
Derivation Event
The derivation can be called and used in all areas of Logistics at xed times (for example, when posting goods receipts for
production orders, when releasing process and manufacturing orders, when making the usage decision).
For more information on derivation events, see Pull Derivation .
Derivation Type
To ful ll the requirements that occur in various business processes, there are generally two types of derivation:
Static derivation
Dynamic derivation
For more information on derivation types, see Derivation Type: Static/Dynamic .
Derivation Direction
Depending on the situation, it might be useful to start the derivation of batch data from the component or the product. However,
the data is always transferred from a component to a product, in other words in the same direction as the quantity ow.
8/8/2019
Pull derivation (1 receiver, n sender)
For more information, see Pull Derivation .
Push derivation (n receiver, 1 sender)
For more information, see Push Derivation .
Constraints
You cannot transfer from a produced batch to a component batch.
In connection with order networks, you cannot generally perform derivations, since the batch where-used list cannot
evaluate the links.
Example
Derivation of batch data can be implemented in the following scenarios:
1. Filling
2. A batch of a material is produced and is placed into various containers, before the results of the quality check are available.
If the bulk batch is speci ed, these results should be transferred to the container batches.
3. Pick and pack activities
The SLED of the unpacked material should be transferred to the packed material.
See also:
Push Derivation (n Receiver, 1 Sender)
Prerequisites for Batch Derivation
Condition Record Maintenance for Bills of Material
Derivation Monitor
Manual Derivation
Ensuring Consistency when Changing the Derivation
Derivation Type: Static/Dynamic

De nition
For each derivation event you can specify whether the derivation is performed statically or dynamically.
Static Derivation
For a static derivation, the attributes determined for the sender batch(es) are transferred to the receiver batch(es).
Dynamic Derivation
8/8/2019
For a dynamic derivation, no attributes are transferred to the receiver batch(es), in other words, the derivation is simulated and
the values are merely displayed. The derivation is saved, but the receiver batch(es) are not automatically changed.
Purpose
Static derivation is recommended if a batch is newly created or changed and the values in the receiver batch(es) should be lled
with the attributes from the sender batch(es).
Dynamic derivation is used when
the receiver batch must/should not be changed
the sender values should be used as the basis for a user decision
Integration
Specifying the Derivation Type
You specify the derivation type in Customizing for Batch Management under Derivation of Batch Data De ne Derivation
Events
Derivation Log
A log is created for both static and dynamic derivations.
When you perform derivation, the following are logged:
Derivation type
Derivation event
Derivation status
Result of the derivation, as well as the sender batches and the data sent
Messages that arose during a derivation (for example, error messages when a derivation fails, due to a sender eld being
non-valuated)
During a dynamic derivation, you can therefore see which data was used as the basis for making a decision.
Note
Any existing values that are overwritten by the change documents for the receiver batch are stored in the batch master
(Logistics Central Functions Batch Management Batch Change/Display ) on the Changes tab page.
Displaying Derivation Logs
You can evaluate derivation logs using the Derivation Monitor
Deleting Derivation Logs
Choose Logistics Central Functions Batch Management Batch Derivation Delete Delete Derivation Logs to delete any
derivation logs that you no longer require from the database.
8/8/2019
Pull Derivation (1 Receiver, n Sender)

Purpose
The derivation is triggered from a transaction that affects the product. Here, data from various senders can be collected,
cumulated, and calculated. Within a derivation according to the pull principle, there can only be one receiver, but there can be
several senders (example usage: pick and pack for pharmaceutical products).
Prerequisites
Features
Range of the Derivation
You can derive the following elds:
Fields of the batch master record
Classifying Attributes
In order that the eld and characteristic values can be successfully transferred, the master elds and the characteristics of the
batches involved in the derivation must be identical.
Data that cannot be displayed using these elds with regards to having the same names (for example, different characteristics),
but which should still be transferred, can be integrated into the derivation using the Business Add-In Derivation (method
SENDER_VALUES_CHANGE ). This gives you more exibility when constructing the type and range of the data to be derived,
depending on the information required.
For more information, see Customizing for Batch Management under Derivation of Batch Data Business Add-In: Derivation.
You specify the elds and characteristic values that to derive in the condition records.
Derivation Rules for Receiver Batches
When maintaining receiver condition records, you can specify whether, during a derivation, you want to allow sender attributes
without content, or overwriting of already lled receiver attributes.
The system also offers several rules for the attributes, which enable an automatic, rule-based derivation where there are
con icting sender values.
You can maintain receiver condition records by choosing:
Logistics Central Functions Batch Management Batch Derivation Condition Record Maintenance for Bills of
Material ( Maintain Condition Records for a Bill of Material )
Logistics Central Functions Batch Management Batch Derivation Recipient Condition Records Display/Change (
Maintain Condition Records without a Bill of Material )
Derivation Events
A pull derivation can be triggered at the following events:
8/8/2019
Usage decision
When you make the usage decision, the derivation is triggered in the background.
Caution
The event "usage decision" does not include the Automatic Usage Decision
Release process/production order
After you have released the process/production order, you can trigger the derivation by choosing on the Goods Receipt tab
page. If a header batch exists, the derivation occurs automatically.
Batch record
When you create or change a version, a derivation is triggered automatically.
Goods receipt for process/production order
When you post the production order, the derivation is triggered in the background.
Note
A derivation is also triggered when you post a goods receipt for a run schedule header.
Manual derivation
You perform a manual derivation by choosing Logistics Central Functions Batch Management Batch Derivation Manual
Derivation .
For more information, see Manual Derivation .
User-de ned event
You can use this derivation event if you do not want to run the derivation as for one of the standard events. To do this, you can, for
example, call the derivation in a suitable user exit.
You maintain the required derivation events in Customizing for Batch Management under Derivation of Batch Data De ne
Derivation Events.
See also:
Deriving the Production Date in Orders - Example
Deriving the Production Date in Orders -

Example
Deriving Production Date and Expiration Date - Example
In this example, in the rst derivation (highlighted red on the screen), the system determines the production date of batch B from
the minimum production dates of batches D and G. Afterwards, the system uses this production date and the expiration date from
the material master data for B to calculate the shelf life expiration date for B.
8/8/2019
This derivation is executed in the event process order. The production dates forDandGhave already been maintained at this point.
In the second derivation (green), both dates are transferred from batchBto batchA.This derivation takes place in a further order.
Activities
Customizing
To assign the standard search procedures BDR001 for receiver search and BDS001 for sender search to the derivation event
process order, choose Batch Derivation → Condition Technique → Assign Search Procedures to Derivation Events .
When the system subsequently searches for a receiver condition record during derivation, it uses the search procedure BDR001,
and therefore searches:
Using the material number of the batch that is currently being processed
Then, using the material type
When it looks for a sender condition record using search procedure BDS001, it searches
Using the material number of the component batch and the material number of the batch that is currently being processed
Then, using only the material number of the component batch
That means that when checking in the rstderivation whetherDis a sender batch, the system would search for a condition record:
Using material number_D+ material number_B
Then, using only material number_Das a key
Maintaining Condition Records

Create two receiver condition records for the strategy type BDR1 and key combination receiver material number using Create
(receiver condition type): Fast Entry
8/8/2019
Key = material number_A
On the Detail screen, maintain the attributes HSDAT and VFDAT.
The following rules are de ned for the attributes:
Attribute HSDAT Attribute VFDAT
Sender eld empty = Error Sender eld empty = Error
Selection rule = Minimum Selection rule = Minimum
Levels in BWU List = 2 Levels in BWU List = 2
Key = material number_B
On the Detail screen, maintain the attribute HSDAT that is to be received.
The following rules are de ned for the attribute:
Attribute HSDAT
Sender eld empty = Error
Selection rule = Minimum
Create three sender condition records for the strategy type BDS1 using Create (sender condition type): Fast Entry.
Two of those sender condition records are created with the key combination sender material number:
Key Attribute
Material number_D HSDAT
Material number_G HSDAT
A third sender condition record is created with the key combination receiver material number + sender material number.
Key Attribute
Material number_B | Material number_A HSDAT
If thisrecord was created with the key combination sender material number , it would already send to itself in the rstderivation.
In order to restrict this condition record to thesecondderivation, the material number of the receiver batch is also used as key to
the condition record.
Order Processing
A manufacturing order is created in order to produce batch B. After batch B in the display has been booked in for goods receipt,
the derivation is performed after each save of the order.
8/8/2019
During the derivation for batch B, the system nds the second receiver condition record, as described above. This condition record
speci es that the production date should be derived.
Special functionality when deriving the production date:
If the shelf life data is maintained in the material master, the expiration date will be calculated.
To derive the production date for batch B, the system searches for sender batches in the extended batch where-used list of batch
B. During this search, the system uses condition technique to look for a sender condition record for each of the batches from the
extended batch where-used list.
The extended batch where-used list is not only based on posted goods movements but also on expected goods movements.
The condition technique nds condition records for batchesDandG.
The system uses the contents of both HSDAT elds to determine the minimum, and checks that none of the sender elds was
empty. If the production date is successfully derived, and if the shelf life data is maintained for batch B, then the system also
calculates the shelf life expiration date.
A dialog box informs the user that a derivation has been carried out.
(In Customizing for Batch Management under Derivation of Batch Data → De ne Derivation Events , you de ne whether a dialog
box appears.)
You can display the result of the derivation in detail.
The derivation is saved along with the order, unless the user does not save the order.
Changes are only made to batch B if the derivation is successful, or has ended with a warning. If an error has occurred, for
example because a sender eld was empty, then batch B is not changed, but the derivation is saved.
In a similar way, the expiration date and the production date are transferred from batchBto batchAin the order that produces
batchA.In this derivation, the batch where-used list is only evaluated down to the second level. Therefore, batchesDandGwill not
send again in this derivation.
Push Derivation (n Receiver, 1 Sender)

Purpose
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 (Example usage: Filling bulk batches in the Chemicals industry).
Prerequisites
8/8/2019
Caution
You must have set the Push Derivation indicator for the condition record of the sender batch.
Features
You can trigger a push derivation at the following events:
Usage decision
Manual Derivation
User-de ned derivation event
For more information on derivation events and the scope of the derivation, see Pull Derivation (1 Sender, n Receiver) .
Prerequisites for Batch Derivation

To successfully perform batch derivation, the following prerequisites must be ful lled:
Both sender and receiver must be materials subject to a batch management requirement.
Customizing
The following settings are required in Customizing for Batch Management :
a) Batch where-used list
The batch where-used list must be activated with the BaWU synchron.posting indicator (synchronous posting of batch
where-used records).
Using the batch where-used list, the system determines the component batches (sender batches) and the batches that resulted
from them (receiver batches). When evaluating the batch where-used list, both existing and planned goods movements are taken
into account.
You make the settings for the batch where-used list under Batch Where-Used List Make Settings for Batch Where-Used List .
b) Derivation of Batch Data
Batch derivation must be active ( Derivation of Batch Data Activate Batch Derivation ).
Sender and receiver search strategies must be assigned to the derivation events ( Derivation of Batch Data De ne
Derivation Events ).
If you do not want to use the SAP standard settings for condition technique, you must de ne your own under Set Up
Condition Technique for Derivation .
Maintaining Condition Records
Condition records must be maintained for sender and receiver batches.
There are two options for condition record maintenance:
https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=21766606&topics=8efeb753128eb44ce10000000a… 10/23
8/8/2019
1. Logistics Central Functions Batch Management Batch Derivation Condition Record Maintenance for Bills of
Material.
2. Logistics Central Functions Batch Management Batch Derivation Receiver Condition Records/Sender Condition
Records Create.
For more information on maintaining condition records, see Condition Record Maintenance for Bills of Material , Creating
Condition Records for a Bill of Material , Maintaining Condition Records without a Bill of Material .
Condition Record Maintenance for Bills of

Material
Purpose
For materials subject to a batch management requirement that are assigned to a bill of material, you can use this function to
simultaneously maintain receiver and sender condition records.
Integration
As well as this transaction, you also have the option of maintaining condition records separately by choosing Logistics Central
Functions Batch Management Batch Derivation Recipient Condition Records/Sender Condition Records.
For more information, see Maintaining Condition Records without Bill of Material .
Prerequisites
A sender search strategy and a receiver search strategy must be assigned to the derivation event.
Features
Choose Logistics Central Functions Batch Management Batch Derivation Condition Record Maintenance for Bills of Material
to access the initial screen for maintaining condition records with reference to a bill of material.
Initial Screen
Select a derivation event and a bill of material.
Note
In the derivation events Release Process/Manufacturing Order and Goods Receipt for Process/Production Order , you can
derive to a co- or by-product.
After you execute the selection, a screen with three subareas appears.
Selection Result
In the left screen area, the system displays a list of the material to produce (receiver) and the necessary components (sender).
Note
8/8/2019
The material to produce is always listed as the sender material.
If you have maintained attributes for these materials, these are also listed.
Detail Area
When you choose a material or an attribute, a detail area in the lower right screen area.
When you choose a material, the system displays the header data of the condition record. You can also maintain the validity
period, the deletion ag, and the logging type. You can also delete the condition record by choosing . When you click on an
attribute of an receiver, the system displays the derivation rules for this attribute so that you can maintain them.
Attribute Worklist
In the attribute worklist , you create attributes to which you want to assign the materials. This attribute worklist is available for
maintaining condition records for bills of material.
Choose to create attributes. You can use Drag&Drop to assign attributes to the receiver and the senders.
For more information on the processing functions in the attribute worklist , choose .
Maintaining Condition Records for a Bill of

Material
Purpose
You use this single function to maintain condition records for a receiver batch and several sender batches.
Procedure
Creating Condition Records
1. Choose Logistics Central Functions Batch Management Batch Derivation Condition Record Maintenance for Bills of
Material.
The initial screen Condition Record Maintenance for Bills of Material appears.
2. On the initial screen Condition Record Maintenance with Bill of Material , select the required derivation event.
Note
In the derivation events Release Process/Manufacturing Order and Goods Receipt for Process/Production Order ,
you can derive to a co- or by-product. Enter the material number of the co- or by-product in the Co-/By-Product eld,
as well as the key for the bill of material.
3. Enter the key values for the required bill of material.
Note
The validity date is used to select the bill of material, to determine condition records, and as the default value for the
start of the validity period for the condition records.
4. Choose .
8/8/2019
The initial screen Condition Record Maintenance for Time “XXX” .
5. If you do not yet have an attribute worklist, or if the attributes that you want to derive are not yet included in your attribute
worklist, add them by choosing or .
6. Specify which attributes are received and sent by moving the attributes via Drag&Drop from the attribute worklist to the
materials in the bill of material tree.
7. If there is no condition record exists yet for the selected material to which you are adding an attribute, and if there are
several possible key combinations for this derivation event, you must select the key combination you want to use from the
dialog box.
Note
The number of key combinations depends on the condition tables that are assigned to the search strategy using the
access sequence and the strategy type.
You make settings in Customizing for Batch Management under Derivation of Batch Data Set Up Condition
Technique for Derivation .
Deleting Condition Records
You have two options in the detail area for deleting condition records:
1. You can set the deletion ag for the condition record. This means that the record is not considered during the next
derivation, and is deleted during the next reorganization run.
2. You can choose to delete the condition record directly from the database.
Maintaining Condition Records without Bills

of Material
Purpose
You maintain condition records without reference to a bill of material if you
create a new condition record and therefore want to automatically restrict the validity of the existing condition record with
the same key
want to create several condition records for the same material and derivation events with different key combinations
Procedure
You maintain the condition records for receiver and sender materials separately.
1. Logistics Central Functions Batch Management Batch Derivation Receiver Condition Records
Create/Change/Display.
2. Logistics Central Functions Batch Management Batch Derivation Sender Condition Records
Create/Change/Display.
Creating Receiver Condition Records
1. Choose Logistics Central Functions Batch Management Batch Derivation Receiver Condition Records Create.
8/8/2019
2. The Derivation – Create Search Strategy: Initial screen appears.
3. Enter the desired strategy type and choose Enter .
1. Chose the key combination that your new condition record is to have.
2. The fast entry screen appears.
3. Maintain the key elds.
4.
In the Receiving material eld, enter the material number of the batch that shall receive the data.
5. Select an entry and choose Details .
The Create (Strategy Type): Details screen appears. Here you maintain the attributes (on the Attributes tab page) and rules (on
the Rules tab page) according to which the derivation should be performed.
1. Close condition record maintenance by choosing Save.
Creating Sender Condition Records
1. Choose Logistics Central Functions Batch Management Batch Derivation Sender Condition Records Create.
The Derivation – Create Search Strategy: Initial screen appears.
1. Enter the desired strategy type and choose Enter .
1. Chose the key combination that your new condition record is to have.
Caution
If you want to create this sender condition record for a Push Derivation , you must select a key combination without receiver
information.
The fast entry screen appears.
1. Maintain the key elds.
1. Select an entry and choose Details .
1. Make your entries on the detail screen.
2. Save your entries.
Deleting Condition Records
In these transactions you can only set the deletion ag.
Selecting Condition Records
In the transactions for changing and display receiver and sender condition records, you can choose Strategy Info on the initial
screen to select by existing condition records in the system.
Derivation Monitor
8/8/2019
Use
The derivation monitor is used to:
Control previously performed derivations (receiver batches, attributes and their values, messages)
Change the status of the invalidated derivations
The derivation logs form the basis of the derivation monitor.
Prerequisites
Derivations have already been performed in your system.
Features
To go to the selection screen containing the following selection criteria, choose Logistics Central Functions Batch
Management Batch Derivation Derivation Monitor to access the selection screen for the derivation monitor.
Selection Screen
On the selection screen, you enter the criteria for selecting the derivations that are to be displayed.
Example
For example, you can display all derivations of batches with a certain expiration date, or all derivations for a batch or derivation
event.
You can change the display of the derivations. You can choose whether the display focuses on the batches or on the derivation
status.
Derivation Monitor
The derivation monitor displays all derivations that match the given selection criteria.
There are nine derivation statuses:
Status of New Derivation Status After Change in Order or Status After Manual
Batch Master Con rmation
OK Derivation OK Derivation OK, but data changed OK, data change con rmed
manually
Warning Carried out with warning Warning and data change Warning, (data change)
con rmed manually
Error Terminated with error Error and data change Warning, (data change)
con rmed manually
After a derivation is performed for the rst time, it can have one of three statuses:
Derivation OK
The derivation was performed without errors.
Carried out with warning
8/8/2019
For at least one attribute, one of the rules in the condition record is set to Warning , and the corresponding situation has
occurred (for example, a sent attribute was empty). The system displays a warning for this derivation, but the derivation is
still carried out. In other words, the receiver batch is changed.
Terminated with error
For at least one attribute, one of the rules in the condition record is set to Error , and the corresponding situation has
occurred (for example, the receiving attribute already contained a different value). The derivation is canceled, that is, no
attributes for the receiver batch are changed – not even the attributes where no error occurred.
Changing the Derivation Status
You can manually con rm an invalidated derivation in the derivation monitor by choosing Edit Set derivation status o.k. The
derivation then receives one of the following statuses:
OK, data change con rmed manually
Warning, (data change) con rmed manually
Error, (data change) con rmed manually
For more information about status changes after changes in the order or to the batch, see Consistency Check for Changes .
Additional Information
The derivation monitor offers you the following additional information using the context menu (right mouse button):
Material
Display the material master
Plant
Display the plant master
Batch
Display the batch master
Batch where-used list
The batch where-used list shows:
Sender batches that sent attributes
Sender batches that did not send attributes
Component batches that are not sender batches
Derivation status
Detail view: Derivation
The system displays all sender batches for a derivation, which sent attributes to the receiver batch.
Manual Derivation
Purpose
You use this function if you want to perform a derivation for the event Manual Derivation .
8/8/2019
Integration
The following functions are integrated into manual derivation :
Batch master (change, display)
Batch worklist
Features
To go to the selection screen containing the following selection criteria, choose Logistics Central Functions Batch
Management Batch Derivation Manual Derivation to access the selection screen for the manual derivation .
Selection Criteria
The following selection criteria are available:
Material
Plant
Batch
You can restrict the number of batches to display using the parameter Maximum Number of Batches .
Batch Worklist
The Batch Worklist is completely integrated into the Manual Derivation function.
If you set the Display Worklist indicator on the selection screen, the batch worklist is empty when it is displayed after you carry
out the selection. In other cases, you can open and close the worklist by choosing .
You can add batches to the Batch Worklist using Drag&Drop, the context menu (right mouse button), or using Selection in
Folder from the selection results area.
You call the batch master by clicking or choosing the context menu for a batch.
Selection Result
After performing the selection, the system displays the batches according to the selection criteria.
You call the batch master by clicking or choosing the context menu for a batch.
Batch Master – Switch Mode
You can switch between display mode and change mode by choosing .
Perform Manual Derivation
After you have selected a batch from the selection result or from the batch worklist, you can choose to trigger manual
derivation.
Derivation Result
After you have triggered the derivation, the system displays a popup with the messages that occurred for the derivation.
8/8/2019
Consistency Check for Changes

Purpose
If changes relevant to the derivation are made to the order or batch after the derivation has been performed, the validity of this
derivation is no longer guaranteed. The consistency of a derivation is no longer guaranteed, since the derivation might have
different results using the new conditions.
For this reason, a dialog box informs the user who changes the data about the derivations that are affected by the change.
Caution
The consistency check is not integrated into the old batch master transaction (MSC2).
The consistency check is not performed if components are added to orders, or when additional batches are posted, than were
originally planned in the order.
Features
The consistency becomes questionable when you make the following changes:
Changes in the Order:
You exchange a component batch that has sent attributes to a produced batch in a previous derivation.
You exchange a component batch that has sent attributes to a produced batch in a past derivation. One of the batches that
was included in this component batch, was a sender batch. When the component batch is exchanged, the subsequent
levels of the batch where-used list become obsolete.
You exchange the produced batch of an order that was used as a component batch of a subsequent order. One of the
component batches was a sender batch for the produced batch in one of the subsequent orders. This means that part of
the batch where-used list is now invalid.
See Consistency Check in the Derivation - Example .
Changes to Batches
If you change an attribute of a batch that was involved in a derivation, this derivation becomes obsolete.
Derivation Status
If you make changes in the order or to the batch that are relevant for this derivation, the status of the derivation also changes, as
follows:
O.k., but data changed
Warning and data change
Error and data change
Consistency Check in the Derivation -

Example
8/8/2019
The following examples explain the different situations that are recognized by the derivation’s consistency check:
Starting point:
Order 123 produces batch C using component batches D and E .
Order 124 produces batch A using component batches B and C .
Derivation:
Batch A receives the expiration date.
The selection rule for the expiration date is minimum.
A derivation took place, in which the batches B and E each sent their expiration date. The expiration date of batch B has been
transferred, since it is smaller than that of batch E.
Result:
Batch A ’s expiration date is now 04.20.
Example 1:
Change:
Batch E is replaced by batch X in order 123.
The consistency check converts the status of this derivation due to the change.
8/8/2019
Example 1.1:
The expiration date of batch X is 4.1 :
The expiration date 04.20 of batch A is now incorrect and must be corrected to by the new value 04.01. After this correction, the
status of the derivation can be set to manually con rmed.
Example 1.2:
The expiration date of batch X is 5.1 :
The 04.20 in A is still correct. The status of the derivation can be set to manually con rmed without any further corrections.
Example 2:
Change:
Batch C is replaced by batch X in order 124.
8/8/2019
Batch X was produced from batches Y and Z . Batch Z would also be a sender for a new derivation.
Example 2.1:
The expiration date of batch Z is 4.1:
The 04.20 in A is incorrect and must be corrected (new value 04.01). After this correction, the status of the derivation can be set
to manually con rmed.
Example 2.2:
The expiration date of batch Z is 05.1:
The 04.20 in A is still correct. The status of the derivation can be set to manually con rmed without any further corrections.
Example 3:
Change
Batch C is replaced by batch X in order 123.
8/8/2019
Batch C is still entered as a component in order 124. Batch E is no longer contained in the batch where-used list for batch A . You
can only make the necessary correction after you adjust order 124. Until then, in this example, the 04.20 in batch A would formally
be correct.
Business Add-Ins (BAdIs) for Batches

In Batch Management, you can use the BAdIs described below.
Batch Master
You can nd these BAdIs in Customizing for Logistics - General under Batch Management Batch Master :
Enhancements for Batch Master Transactions (BATCH_MASTER)
You can use this BAdI to do the following:
Perform additional checks for batch data and for batch classi cation
De ne the input attributes of individual elds using the eld selection control
In uence the locking of the batch master when goods movements are posted (MIGO) so that, under speci c
conditions, multiple goods movements can be posted in parallel to the same batch.
BAdI: Additional Custom Fields and Tab in Batch Master Transactions (VB_BM_ADD_SCREEN_FIELDS)
You can use this BAdI to add customer-speci c elds to a customer-speci c tab or to the Basic Data 2 tab in the batch
master.
Batch Determination
You can nd the BAdI Preselection of Batches Within Batch Determination (VB_BD_SELECTION) in Customizing for Logistics
- General under Batch Management Batch Determination and Batch Check .
Batch Where-Used List

8/8/2019
You can nd these BAdIs in Customizing for Logistics - General under Batch Management Batch Where-Used List :
Access to Customer-Speci c Batch Usage Data (VB_GET_EXT_BATCHES)
You can use this BAdI to integrate additional data sources into the batch where-used list.
Enhancement to Automatic Plant Determination in transaction MB56 (VB_GET_POS_PLANT)
You can use this BAdI to adjust the automatic plant selection for material number and batch to suit your requirements.
Shelf Life Expiration Date

You can nd the BAdI Control of Shelf Life Expiration Date Processing (VB_SLED_MANAGEMENT) in Customizing for Logistics -
General under Batch Management Shelf Life Expiration Date (SLED) .
You can use this BAdI to in uence the control of shelf life expiration date processing when goods movements take place.
Batch Derivation
You can nd the BAdI Derivation (DERIVATION) in Customizing for Logistics - General under Batch Management Derivation of
Batch Data .
Batch Information Cockpit

You can nd these BAdIs in Customizing for Logistics - General under Batch Management Batch Information Cockpit :
Batch Information Cockpit - Additional Data/Columns (BIC_ADDITIONAL_DATA)
You can use this BAdI to add customer-speci c columns to the Selection Result: Batches and the Selection Result: Stock
in the Batch Information Cockpit. You can ll these columns with additional information about batches; for example, with
WM data (such as warehouse number or storage bin) or stock values.
Follow-Up Actions in the Batch Information Cockpit (BIC_FOLLOW_UP_ACTION)
You can use this BAdI to trigger follow-up actions for batches, either by choosing a pushbutton or using the context menu,
that have been selected in the navigation area (Selection Result: Batches, Selection Result: Stock, and Worklist).
Selection Enhancement in the Batch Information Cockpit (BIC_SELECTION)
You can use this BAdI to de ne a customer-speci c selection tab page and to add elds to the Selection Result: Batches.

Batch Management Overview

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Batch Management Overview

Uploaded by

Copyright:

Available Formats

8/8/2019

Batch Management (LO-BM)

SAP S/4HANA | 1809.002

For more information, please visit the SAP Help Portal.

Display for selection

The following basic rules apply:

Component batches may send data.

Produced batches may receive data.

For more information, see Prerequisites for Batch Derivation .

For more information on derivation events, see Pull Derivation .

For more information on derivation types, see Derivation Type: Static/Dynamic .

For more information, see Pull Derivation .

Push derivation (n receiver, 1 sender)

For more information, see Push Derivation .

3. Pick and pack activities

Push Derivation (n Receiver, 1 Sender)

Prerequisites for Batch Derivation

Condition Record Maintenance for Bills of Material

Ensuring Consistency when Changing the Derivation

Derivation Type: Static/Dynamic

Dynamic derivation is used when

the receiver batch must/should not be changed

A log is created for both static and dynamic derivations.

When you perform derivation, the following are logged:

Displaying Derivation Logs

You can evaluate derivation logs using the Derivation Monitor

Deleting Derivation Logs

Pull Derivation (1 Receiver, n Sender)

You can derive the following elds:

Fields of the batch master record

Derivation Rules for Receiver Batches

You can maintain receiver condition records by choosing:

A pull derivation can be triggered at the following events:

Release process/production order

When you create or change a version, a derivation is triggered automatically.

Goods receipt for process/production order

For more information, see Manual Derivation .

User-de ned event

Deriving the Production Date in Orders - Example

Deriving the Production Date in Orders -

Then, using the material type

Then, using only the material number of the component batch

Using material number_D+ material number_B

Then, using only material number_Das a key

Maintaining Condition Records

On the Detail screen, maintain the attributes HSDAT and VFDAT.

The following rules are de ned for the attributes:

Attribute HSDAT Attribute VFDAT

Sender eld empty = Error Sender eld empty = Error

Selection rule = Minimum Selection rule = Minimum

Levels in BWU List = 2 Levels in BWU List = 2

Key = material number_B

On the Detail screen, maintain the attribute HSDAT that is to be received.

The following rules are de ned for the attribute:

Sender eld empty = Error

Selection rule = Minimum

Material number_D HSDAT

Material number_G HSDAT

Material number_B | Material number_A HSDAT

Special functionality when deriving the production date:

The condition technique nds condition records for batchesDandG.

You can display the result of the derivation in detail.

Push Derivation (n Receiver, 1 Sender)