You are on page 1of 9

Handling Unit Management (HUM) for

Production
SAP Best Practices
2011 SAP AG. All rights reserved. 2
Purpose, Benefits, and Key Process Steps
Purpose
You use Handling Unit Management (HUM) to control logistical processes.
A handling unit represents a physical object in the SAP system. It consists of a load carrier, one or more packed products
and an unlimited quantity of packaging materials. Each handling unit has a unique identification number, which is typically
printed as a barcode on a material tag.
You can specify the material and the quantity that is to be packed in certain packaging, that is, in one handling unit. These
requirements are reproduced in a packing instruction. This packing instruction can be used to create handling units
automatically.
Benefits
Automatic packaging according to packing instructions
Track movements of groups of individual materials by tracking the handling units that contain them
Full integration into the logistic chain
The scenario offers you the possibility to demonstrate HUM with or without warehouse management

Key Process Steps
Creation and release of production order for handling unit (HU) production
HU packaging in production order
Goods receipt for produced HU
Monitoring of HU
Confirming production of HU
HU handling with WM or HU handling without WM
2011 SAP AG. All rights reserved. 3
Required SAP Applications and Company Roles
Required
Enhancement package 5 for SAP ERP 6.0
Company Roles
Production Planner
Warehouse Clerk
Manufacturing
Shopfloor Specialist
Warehouse monitoring
Sales administration

2011 SAP AG. All rights reserved. 4
Detailed Process Description
Handling Unit Management (HUM) for Production
This scenario describes the packaging process and goods receipt at the end of a
production order with HUM. The stock is posted directly into storage location and available
for picking with or without Warehouse Management.

The first step is the creation and processing of a production order (release, material
staging, printing of shop floor papers).
The produced material is automatically packed into Handling Units (HU)
Goods receipt of the HU of the production order to the storage location (varying due to the
use of Warehouse management or not)
Monitoring of HU in the HU monitor (creation, status and contents of the single HU can be
checked)
Confirmation of HU production order
Optional: Sales order and delivery processing with or without warehouse management

2011 SAP AG. All rights reserved. 5
Process Flow Diagram
Handling Unit Management (HUM) for Production
E
v
e
n
t

Beginning of
Planning
Cycle
M
a
n
u
f
a
c
t
u
r
i
n
g

Material
Requirements
Planning at Plant
Level & Evaluation of
Stock / Requirement
List
Purchase
Requi-
sition
P
r
o
d
u
c
t
i
o
n

P
l
a
n
n
e
r

Release
Production
Order
Material
Staging for
Production
Orders
HU Packaging
in production
order
Planned
Orders
Material
Available
?
B
u
y
e
r


S
h
o
p

F
l
o
o
r

S
p
e
c
i
a
l
i
s
t


Yes
Purchasing with
JIT Delivery
schedules (230)
Convert
Planned Order
to Production
Order for HU
production
Procurement
w/o QM
(130)
No
Monitor HU
HU Entering
goods receipt
for production
order
Confirming
production
order for HU
production
Planned
Independent
Requirements
2011 SAP AG. All rights reserved. 6
Process Flow Diagram
S
a
l
e
s

W
a
r
e
h
o
u
s
e

M
o
n
i
t
o
r
i
n
g

W
a
r
e
h
o
u
s
e

C
l
e
r
k


S
a
l
e
s

A
d
m
i
n
i
s
t
r
a
t
i
o
n



E
v
e
n
t

Check WM
stock for HU
Create Outbound
Delivery with Order
Reference (full WM)
Billing of
Sales Order
Create
Transfer Order
from stock
Confirm
Transfer Order
Confirming
production
order for HUM
with full WM
Create Sales
Order (full
WM)
Period End
Closing
General
Plant
(181)
P
l
a
n
t

C
o
n
t
r
o
-
l
l
e
r

Handling Unit Management (HUM) for Production:
Full Warehouse Management (WM) processing (option 1)
2011 SAP AG. All rights reserved. 7
Process Flow Diagram
Handling Unit Management (HUM) for Production:
Lean Warehouse Management (WM) processing (option 2)
S
a
l
e
s

A
d
m
i
n
i
s
t
r
a
t
i
o
n

S
a
l
e
s

W
a
r
e
h
o
u
s
e

C
l
e
r
k

E
v
e
n
t

Create Outbound
Delivery with Order
Reference (lean WM)
Billing of Sales
Order
Create Sales
Order
(lean WM)
Confirming
production
order for HUM
with lean WM
P
l
a
n
t

C
o
n
-
t
r
o
l
l
e
r
Period End
Closing
General
Plant
(181)
2011 SAP AG. All rights reserved. 8
Legend
Symbol Description Usage Comments
To next / From last Diagram: Leads
to the next / previous page of the
Diagram
Flow chart continues on the next /
previous page
Hardcopy / Document: Identifies a
printed document, report, or form
Does not correspond to a task
step in a document; instead, it is
used to reflect a document
generated by a task step; this
shape does not have any outgoing
flow lines
Financial Actuals: Indicates a
financial posting document
Does not correspond to a task
step in a document; instead, it is
used to reflect a document
generated by a task step; this
shape does not have any outgoing
flow lines
Budget Planning: Indicates a
budget planning document
Does not correspond to a task
step in a document; instead, it is
used to reflect a document
generated by a task step; this
shape does not have any outgoing
flow lines
Manual Process: Covers a task
that is manually done
Does not generally correspond to
a task step in a document;
instead, it is used to reflect a task
that is manually performed, such
as unloading a truck in the
warehouse, which affects the
process flow.
Existing Version / Data: This block
covers data that feeds in from an
external process
Does not generally correspond to
a task step in a document;
instead, this shape reflects data
coming from an external source;
this step does not have any
incoming flow lines
System Pass / Fail Decision: This
block covers an automatic
decision made by the software
Does not generally correspond to
a task step in the document;
instead it is used to reflect an
automatic decision by the system
that is made after a step has been
executed.
E
x
t
e
r
n
a
l

t
o

S
A
P

Business
Activity / Event
Unit Process
Process
Reference
Sub-
Process
Reference
Process
Decision
Diagram
Connection
Hardcopy /
Document
Financial
Actuals
Budget
Planning
Manual
Process
Existing
Version /
Data
System
Pass/Fail
Decision
Symbol Description Usage Comments
Band: Identifies a user role, such as Accounts
Payable Clerk or Sales Representative. This band
can also identify an organization unit or group,
rather than a specific role.
The other process flow symbols in this table go
into these rows. You have as many rows as
required to cover all of the roles in the scenario.
Role band contains
tasks common to that
role.
External Events: Contains events that start or end
the scenario, or influence the course of events in
the scenario.
Flow line (solid): Line indicates the normal
sequence of steps and direction of flow in the
scenario.
Flow line (dashed): Line indicates flow to
infrequently-used or conditional tasks in a
scenario. Line can also lead to documents involved
in the process flow.
Connects two tasks in
a scenario process or
a non-step event
Business Activity / Event: Identifies an action that
either leads into or out of the scenario, or an
outside Process that happens during the scenario
Does not correspond
to a task step in the
document
Unit Process: Identifies a task that is covered in a
step-by-step manner in the scenario
Corresponds to a task
step in the document
Process Reference: If the scenario references
another scenario in total, put the scenario number
and name here.
Corresponds to a task
step in the document
Sub-Process Reference: If the scenario references
another scenario in part, put the scenario number,
name, and the step numbers from that scenario
here
Corresponds to a task
step in the document
Process Decision: Identifies a decision / branching
point, signifying a choice to be made by the end
user. Lines represent different choices emerging
from different parts of the diamond.



Does not usually
correspond to a task
step in the document;
Reflects a choice to
be made after step
execution
<
F
u
n
c
t
i
o
n
>

2011 SAP AG. All rights reserved. 9
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, SAP BusinessObjects Explorer,
StreamWork, 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.
2011 SAP AG. All rights reserved
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 Business Objects Software Ltd. Business Objects is an SAP company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase
products and services mentioned herein as well as their respective logos are trademarks or
registered trademarks of Sybase, Inc. Sybase is an SAP company.
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.
The information in this document is proprietary to SAP. No part of this document may be
reproduced, copied, or transmitted in any form or for any purpose without the express prior
written permission of SAP AG.
This document is a preliminary version and not subject to your license agreement or any
other agreement with SAP. This document contains only intended strategies, developments,
and functionalities of the SAP product and is not intended to be binding upon SAP to any
particular course of business, product strategy, and/or development. Please note that this
document is subject to change and may be changed by SAP at any time without notice.
SAP assumes no responsibility for errors or omissions in this document. SAP does not
warrant the accuracy or completeness of the information, text, graphics, links, or other items
contained within this material. This document is provided without a warranty of any kind,
either express or implied, including but not limited to the implied warranties of
merchantability, fitness for a particular purpose, or non-infringement.
SAP shall have no liability for damages of any kind including without limitation direct,
special, indirect, or consequential damages that may result from the use of these materials.
This limitation shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. SAP has no
control over the information that you may access through the use of hot links contained in
these materials and does not endorse your use of third-party Web pages nor provide any
warranty whatsoever relating to third-party Web pages.