EHP4 for SAP ERP
6.0
June 2010
English
Batch Management (117)
Business Process Documentation
SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
SAP Best Practices
Batch Management: (117): BPD
Copyright
© 2010 SAP AG. 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.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z,
System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390,
OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+,
POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System
Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA,
AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of
IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of
Adobe Systems Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or
registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C ®, World Wide Web
Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented
and implemented by Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, Clear Enterprise, SAP BusinessObjects
Explorer, 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.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions,
Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP France in the United States and in
other countries.
All other product and service names mentioned are the trademarks of their respective companies. Data
contained in this document serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. 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 AG
Page 2 of 13
SAP Best Practices
Batch Management: (117): BPD
Icons
Icon
Meaning
Caution
Example
Note
Recommendation
Syntax
External Process
Business Process Alternative/Decision Choice
Typographic Conventions
Type Style
Description
Example text
Words or characters that appear on the screen. These include field
names, screen titles, pushbuttons as well as menu names, paths and
options.
Cross-references to other documentation.
Example text
Emphasized words or phrases in body text, titles of graphics and tables.
EXAMPLE TEXT
Names of elements in the system. These include report names,
program names, transaction codes, table names, and individual key
words of a programming language, when surrounded by body text, for
example, SELECT and INCLUDE.
Example text
Screen output. This includes file and directory names and their paths,
messages, source code, names of variables and parameters as well as
names of installation, upgrade and database tools.
EXAMPLE TEXT
Keys on the keyboard, for example, function keys (such as F2) or the
ENTER key.
Example text
Exact user entry. These are words or characters that you enter in the
system exactly as they appear in the documentation.
<Example text>
Variable user entry. Pointed brackets indicate that you replace these
words and characters with appropriate entries.
© SAP AG
Page 3 of 13
SAP Best Practices
Batch Management: (117): BPD
Contents
1
Purpose ................................................................................................................................... 5
2
Prerequisites............................................................................................................................ 5
2.1
Master Data and Organizational Data .............................................................................. 5
2.2
Business Conditions ......................................................................................................... 6
2.3
Roles ................................................................................................................................ 7
2.4
Preliminary Steps ............................................................................................................. 7
3
Process Overview Table ......................................................................................................... 9
4
Process Steps ......................................................................................................................... 9
5
4.1
Maintaining Batch Master Record .................................................................................... 9
4.2
Batch Information Cockpit .............................................................................................. 10
Appendix................................................................................................................................ 12
5.1
Reversal of Process Steps ............................................................................................. 12
5.2
SAP ERP Reports .......................................................................................................... 12
5.3
Frequently Asked Questions .......................................................................................... 13
© SAP AG
Page 4 of 13
SAP Best Practices
Batch Management: (117): BPD
Batch Management
1
Purpose
Document
The purpose of this document is to explain the business process of Batch Management in detail.
The target group for this document is a company’s logistics personnel.
Scenario
If materials were handled in batches it might be necessary to change the batch master data,or to
find out where a batch was used for example to perform a batch recall or report to government.
2
Prerequisites
2.1 Master Data and Organizational Data
SAP Best Practices Standard Values
Essential master and organizational data were created in your ERP system during the
implementation phase, such as the data that reflect the organizational structure of your company
and master data that suit their operational focus, for example, master data for materials,
vendors, and customers.
This master data usually consists of standardized SAP Best Practices default values, and
enables you to go through the process steps of this scenario.
Additional Master Data (Default Values)
You can test the scenario with other SAP Best Practices default values that have the
same characteristics.
Check your SAP ECC system to find out which other material master data exists.
Using Your Own Master Data
You can also use customized values for any material or organizational data for
which you have created master data. For more information on how to create master
data, see the Master Data Procedures documentation.
Use the following master data in the process steps described in this document:
Master /
Org. data
Value
Master / Org. data details
Comments
Material
H22
Trading Good for Reg.
Trading (reorder point
planning), batch
controlled (FIFO
strategy)
Only use if you have activated the
building blocks Batch Management
(117) or Serial Number
Management (126).
© SAP AG
See sections Business Conditions
and Preliminary Steps.
Page 5 of 13
SAP Best Practices
Batch Management: (117): BPD
Master /
Org. data
Value
Master / Org. data details
Comments
Material
H21
Trading Good for Reg.
Trading (reorder point
planning), batch
controlled (Exp. Date)
Only use if you have activated the
building blocks Batch Management
(117) or Serial Number
Management (126).
See sections Business Conditions
and Preliminary Steps.
Material
F29
Finished Good MTS for
Process Industry (PD
planning)
Only use if you have activated the
building blocks Batch Management
(117) and Make to Stock Production
– Process Industry (146)
See sections Business Conditions
and Preliminary Steps.
Material
F126
Finished Good MTS for
Discrete Industry (PD
planning)
Only use if you have activated the
building blocks Batch Management
(117) and Make to Stock Production
– Discrete Industry (145) with batch
management
See sections Business Conditions
and Preliminary Steps.
Material
R09, R19,
R30, R122
Raw materials for
Procurement to Stock
Only use if you have activated the
building blocks Batch Management
(117) and Procurement to Stock
(130)
See sections Business Conditions
and Preliminary Steps.
2.2 Business Conditions
The business process described in this Business Process Documentation is part of a bigger
chain of integrated business processes or scenarios. Consequently, you must have completed
the following processes and fulfilled the following business conditions before you are able to start
going through this scenario:
Business condition
Scenario
To run through this scenario, the materials must be
available in stock, and the batch master record must
have been created.
See Preliminary Steps to create initial
stock.
If you use finished goods (FERT) you can either:
Make-to-Stock Production - Discrete
Industry (145) (material F126)
Make-to-Stock Production - Process
Industry (146) (material F29)

run through the Make-to-Stock Production Discrete Industry (145) process (for material
F126) / the Make-to-Stock Production Process Industry (146) process (for material
F29) or

create stock using transaction MIGO (for
details see chapter Preliminary Steps).
If you use trading materials or raw materials, you
can either:

© SAP AG
Procurement without QM (130)
Run through the Procurement without QM
Page 6 of 13
SAP Best Practices
Batch Management: (117): BPD
Business condition
Scenario
(130) process, or

Create stock using transaction MIGO (for
details see chapter Preliminary Steps).
2.3 Roles
Use
The following roles must have been installed in order to test this scenario in the SAP NetWeaver
Business Client (NWBC). The roles in this Business Process Documentation must be assigned
to the user, or users, testing this scenario. You do not need these roles if you are not using the
NWBC interface. Instead, use the standard SAP GUI.
Prerequisites
The business roles have been assigned to the user who is testing this scenario.
Business role
Technical name
Process step
Employee
(Professional
User)
SAP_NBPR_EMPLOYEE-S
Assignment of this role is
necessary for basic functionality.
Warehouse Clerk SAP_NBPR_WAREHOUSECLERK-S
Posting the Goods Issue
Posting the Goods Receipt
Warehouse
Manager
SAP_NBPR_WAREHOUSEMANAGERM
Change Batch Master Record
Use Batch Management Cockpit
2.4 Preliminary Steps
In order to run through this scenario, the materials must be available in stock. Use transaction
MIGO to create the required data.
Use
The purpose of this activity is to post initial stock for materials in case there is not sufficient
material on stock.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Materials Management  Inventory
Management  Goods Movement  Goods Movement
(MIGO)
Transaction code
MIGO
2. On the initial screen, ensure that in the top left hand corner of the screen, the first field
shows Goods Receipt and the second field shows Other. In the field in the top right hand
corner, enter movement type 561 and choose Enter.
3. On the Goods Receipt Other - <> screen, make the following entries and choose Enter.
© SAP AG
Page 7 of 13
SAP Best Practices
Field name
Batch Management: (117): BPD
Description
User action and values
Comment
H21
Enter a material
number for a batchcontrolled material;
any material number
can be used.
Material tab
page
Material
Quantity tab
page
<Enter amount>
Amount
Where tab
page
Plant
1000
Storage
location
1050
4. On the Batch tab page, enter external batch number or leave empty for internal number
assignment.
5. If required, enter the date of production, then choose Enter:
Production date entry is only required for materials that are controlled according to
expiration date strategy.
6. If the material is serialized: On the Serial Numbers tab page, enter the serial number. If the
serial number is unknown, search for it by using the Find icon, or create a new one if none
exists.
7. Choose Item OK and then Post.
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Warehouse Clerk
(SAP_NBPR_WAREHOUSECLERK-S)
Business role menu
Warehouse Management  Consumption and Transfers  Other
Goods Receipts
1. On the Enter Other Goods Receipts: Initial screen, make the following entries and choose
Enter.
Field name
Description
User action and values
Movement Type
561
Plant
1000
Storage Location
1050
Comment
2. On the Enter Other Goods Receipts: New Item screen, make the following entries and
choose Enter.
Field name
© SAP AG
Description
User action and values
Comment
Page 8 of 13
SAP Best Practices
Batch Management: (117): BPD
Material
<Enter a batch
controlled material>
Quantity
<Enter a quantity>
Choose H21for FIFO
or H22for Expiration
Date.
3. Confirm the Automatic batch number allocation dialog box with by choosing YES.
4. If required, enter the date of production, then choose Enter:
Production date entry is only required for materials that are controlled according to
expiration date strategy.
5. To reverse the posting, repeat the steps using the reversal movement type 562.
6. If the material is serialized: On the Serial Numbers tab page, enter serial number. If the
serial number is unknown, search for it by using the Find icon, or create a new one if none
exists.
7. Choose Back and Save.
To reverse the posting, repeat the steps with reversal movement type 562.
Alternatively, cancel the material document using the transaction MBST.
Result
You have posted a material to stock and created a batch record.
3
Process Overview Table
Process Step
External
Process
Referenc
e
Business
Condition
Maintain Batch
Master Record
Batch
Information
Cockpit
4
Information
needed where
batch was
sold and
bought
Business Role
Transact
ion Code
Warehouse
Manager
MSC2N
Warehouse
Manager
BMBC
Expected
Results
Where-usedlists, batch
master data
Process Steps
4.1 Maintaining Batch Master Record
Use
Manual adjustment is needed for batch master data.
© SAP AG
Page 9 of 13
SAP Best Practices
Batch Management: (117): BPD
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Central Functions  Batch Management 
Batch  Change
Transaction code
MSC2N
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Warehouse Manager
(SAP_NBPR_WAREHOUSEMANAGER-M)
Business role menu
Warehouse Management  Batch  Change Batch
2. On the Change Batch screen, make the following entries and choose Enter:
Field name
Description
User action and values
Material
Material number
Enter material number, for
example, H21
Batch
Batch number
Enter batch number
Comment
Or search for the
batch number using
the input help.
3. Choose the Basic Data 1 tab page to change, for example, the batch status, production date,
shelf life or expiration date.
4. Choose Basic Data 2 tab page to change the batch description.
5. Choose the Classification tab page to set the classification status or to maintain class
characteristics.
6. Choose the Material tab page to display shelf life data and material classification.
7. Choose the Changes tab page to get an overview of the batch master changes. Choose
Display Changed Values to display changes in the bottom view.
Result
The batch is maintained.
4.2 Batch Information Cockpit
Use
When materials are handled in batches, there is sometimes a need to know where the batches
were used. Use the bottom-up batch search directed to customers or top-down batch search
directed to vendors.
Procedure
© SAP AG
Page 10 of 13
SAP Best Practices
Batch Management: (117): BPD
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Central Functions  Batch Management 
Batch Information Cockpit
Transaction code
BMBC
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Warehouse Manager
(SAP_NBPR_WAREHOUSEMANAGER-M)
Business role menu
Warehouse Management  Batch  Batch Information Cockpit
2. On the Batch Information Cockpit screen, enter the material, for example, TRADE21 (H21)
and choose Execute.
3. On the left hand side of the screen, in the Selection result for Batches list, open the context
menu by clicking on the relevant batch with the right mouse button. Choose the menu
Display Batch. On the right hand side of the screen the batch master data will now be
displayed.
4. On the left hand side of the screen, in the Selection result for Batches list, open the context
menu by clicking on the relevant batch with the right mouse button. Choose the menu Usage
(top-down). On the right hand side of the screen, a batch list will be displayed. The term ‘topdown’ means that the chosen batch was the last batch, and that all other displayed batches
were predecessors.
5. On the left hand side of the screen, in the Selection result for Batches list, open the context
menu by choosing the relevant batch with the right mouse button, and then choose Usage
(bottom-up). The result is that on the right side of the screen, a batch list is displayed. The
term ‘bottom-up’ means that the chosen batch was the original batch, and that all other
displayed batches are successors.
6. On the right hand side of the screen, select a batch number from the batch list. From this
batch, the following options are available by choosing the corresponding button:
Button
Action
Top-Down
Starts a new top-down batch list from the selected batch
Bottom-Up
Starts a new bottom-up batch list from the selected batch
Documents
Shows materials documents linked to the selected batch
Inspection Lots
Show all inspection lots with usage decisions linked to the selected batch.
Back
Moves one level back, for example, from the second list back to the first list.
Result
Different batch information is shown, such as batch master data, where-used-lists, material
documents, and inspection lots.
© SAP AG
Page 11 of 13
SAP Best Practices
5
Batch Management: (117): BPD
Appendix
5.1 Reversal of Process Steps
In the following section, you will find the most common reversal steps, which enable you to
reverse some of the activities described previously in this document.
Maintain Batch Master Record
Transaction code (SAP GUI)
MSC2N
Reversal:
Change Batch Master Record
Transaction code (SAP GUI)
MSC2N
Business role
Engineering Specialist (SAP_NBPR_ENGINEER-S)
Warehouse Manager
(SAP_NBPR_WAREHOUSEMANAGER-M)
Business role menu
Engineering  Batch Management  Change Batch
Warehouse Management  Batch  Change Batch
Comment
Correct previous entries.
5.2 SAP ERP Reports
Use
The table below lists the most frequently used reports that help you to obtain additional
information on this business process.
You can find detailed descriptions of the individual reports in the following BPD
documents, which provide a comprehensive compilation of all important reports:

Financial Accounting: SAP ERP Reports for Accounting (221)

Logistics Processes: SAP ERP Reports for Logistics (222)
Note that the descriptions of some reports, that are an indispensable part of the process flow,
may be located directly in the section where they belong.
Reports
Report title
Transaction code
Comment
Batch Analysis
MCBR
A list with summarized data
Integrity check for Batch Classification
BMCC
Shows whether batch
classification is maintained
consistently for the selected
materials
Expiration Date List
MB5M
Shows batches whose
expiration date has been
passed / the remaining shelf
life is shorter than the
selected period
© SAP AG
Page 12 of 13
SAP Best Practices
Batch Management: (117): BPD
5.3 Frequently Asked Questions
Questions
Answers
Can I delete batch records?
Yes, if you have run the archiving process.
Is it possible to change batch
management for a material?
Yes, if you have not yet posted any inventory for
this material.
Is it possible to change the batch class
of a material, which has existing
batches?
Yes. Refer to the SAP online documentation for how
to execute the process.
© SAP AG
Page 13 of 13