ehs management: global label management

EHS Management: Global Label Management

SAP Best Practices for Environment, Health, and Safety Management

© 2011 SAP AG. All rights reserved. 2

Purpose, Benefits, and Key Process Steps

If you produce and sell products or purchase, store, and process raw materials in your enterprise, you have to print various labels and affix them to your goods and packaging. These labels include goods receipt labels, article labels, hazardous substance labels, danger labels, transportation labels, handling instructions, safety information, and labels tailored to suit your customers’ needs. Depending on the place of destination, the labels must be created in several languages and show graphics such as hazard symbols, use symbols, and company logos. The layout and content of labels can also be dependent on the jurisdiction for which the labels are destined. This means you have to observe numerous laws and regulations worldwide.

You can use this business process to label your products and bring them onto the market in compliance with the law. Integration in other processes in SAP ERP, for example, goods receipt, make-to-stock production, make-to-order production, and delivery allows the system to create legally compliant labels automatically and print the required number of labels. If you wish, you can number the labels with serial numbers. With the use of a partner product, you can control automatic labeling directly in the production line.


Purpose, Benefits, and Key Process Steps (Cont’d)

Benefits Automates labeling processes Legal Compliance for company-specific rules and regulations Customized planning and creation of labels Consistent data throughout the Product Life Cycle Supports high-performance printers and high-volume label printing.

Key Process Steps• Maintain Label Data in Material Master

• Create Label for Global Label Management – for Demonstration Only

• Maintain Generation Variant

• Creating Label Stock

• Trigger the Logistics Delivery order for Material H-4000

• Create Order

• Create Delivery

• Print and Preview Labels


Highlights

Types of Labels Primary container labels Over-pack labels, transport labels and address labels Additional labels for customers and internal use Waste labels Sample labels for products under development Inbound raw material bar code labels


Required SAP Applications and Company Roles

Required SAP Applications SAP ECC 6.0 enhancement package 5

Integration SAP EHS Management specification database Material Master WWI (Word-Windows Integration)

Company Roles Purchasing Administrator EHS Management: Warehouse Clerk Sales Administrator EHS Management: Clerk


Process Overview

Different labels are used for the development, production and distribution of products and substances. Different versions are required for the same product depending on the type of packaging, the country of destination and customer requirements. Data from the logistics supply chain/the ERP system is required to create a label. Automated Label printing is integrated in Global Label Management of SAP EHS Management. Only the material or production order number is required to provide the labeling data from the EHS Management specification database for the label.

Creation of labels requires the details of Dangerous Goods and Hazardous substances with accurate specification and material data. GLM automatically adjusts and determines the language based on the country to which it is being shipped. Supply chain staff can generate labels using a fully automated process or can quickly print labels manually. Label can be previewed before printing. Printing of label can be done remotely from any workplace or location for output on any printer. The system supports label printing on both standard Windows printers and special high-performance label printers.


Process Flow DiagramEHS Management: Global Label Management

Sal

es

Ad

min

istr

ato

r

Pu

rch

asi

ng

A

dm

inis

tra

tor

Maintain Label Data in Material Master

EH

S

Man

agem

ent:

W

areh

ou

se

Cle

rk

EH

S

Man

agem

ent

Cle

rk

Create Label for Global

Label Management –

for Demonstration

Only

Maintain Generation

Variant

Creating Label Stock

Trigger the Logistics

Delivery Order for Material

EH-4000

Print and Preview Labels


GLM Technical Process view

define the properties of the label stocks. Each label requires a special label stock viz: size, color, design.

create customer-specific l labeling requirements such as make-to-order production or delivery

use a label template to design the layout of the labels. You can print specification data.

system generates labels from report templates (label templates) and stores the labels in the EHS Management report database, generates and prints the labels from scratch each time

enter texts that have a standard character in the form of phrases

enter all environmentally relevant data and other data for substances (pure substances, preparations, mixtures, and residual substances), products, agents, packaging, etc.,

enter material-dependent data and texts for labeling and the packaging hierarchy.


Label Generation Business Process view


Trigger Label Generation

Check and validate label content

Create consignment fill-up order

Goods Receipt

Check Maintain Label relevant Data

Create Label Stocks

Create Delivery

Print Label for Delivery

Proof of Delivery

Goods Issue

Print Label Stocks

Print Label for Delivery


Following labeling scenarios are available

Make-to-Stock labeling scenario

Make-to-Order labeling scenario

Delivery labeling scenario

Goods Receipt labeling scenario

Generic labeling scenario

Sample labeling scenario

Make-to-Stock labeling scenario

In this labeling scenario you can print labels during the production process. Process order must be entered. Enter data in this labeling scenario that was already available during the production process. The system derives all other data required for label determination from the data entered or the standard values specified by you in Customizing for Global Label Management.

Make-to-Order labeling scenario

In this labeling scenario you can print labels during the production process. Process order must be entered. Enter data in this labeling scenario that was already available during the production process. The system derives all other data required for label determination from the data entered or the standard values specified by you in Customizing for Global Label Management.


Following labeling scenarios are available (Cont’d)

MakeDelivery labeling scenario

In this labeling scenario you can print labels for shipping or for a delivery. The system uses the material and batch, packaging, customer number, mode of transports and so on, specified in the delivery.

Goods Receipt Labeling scenario

In this labeling scenario you can print labels for purchased materials, for example, to label materials for production or the internal material flow.

Generic Labeling scenario

In this labeling scenario you can determine and print labels for a material. If you enter a customer, the system also determines customer-specific labels.

Sample Labeling scenario

In this labeling scenario you can determine and print labels of your choice for a material. You can also specify a label category and a label size for label determination that were not specified in the label data of the material. This enables you to create labels for a new sample.


GLM WWI Label Templates

Displaying labels Printing labels

The system Displays and Prints the labels found as follows in a label tree; The label is displayed using Microsoft Word. Set up Local printer for Printing Labels.

WWI (Windows Word processor Integration) Templates:

You define language-independent document templates using symbols and control objects in a modified version of Microsoft Word.


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


Budget Planning: Indicates a budget planning document


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.

Ext

erna

l to

SA

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.


Sub-Process Reference: If the scenario references another scenario in part, put the scenario number, name, and the step numbers from that scenario here


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

unct

ion>


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.