SAP Solutions for Auto-ID and Item Serialization 2010 ... · PDF fileMaster Guide SAP...

Master GuideSAP Solutions for Auto-ID and Item Serialization 2010 Powered by SAP NetWeaver®

Using SAP Auto-ID Infrastructure 7.1, SAP Event Management 7.0 Including SAP Enhancement Package 1, SAP Object Event Repository, SAP NetWeaver® 7.0 Including SAP Enhancement Package 2, and SAP Enhancement Package 5 for SAP ERP 6.0

Target Audience ■ Technical Consultants ■ System Administrators

PUBLICDocument version: 1.4 – 2012-04-02Material number: 50095578

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +49/18 05/34 34 34F +49/18 05/34 34 20

www.sap.com

© Copyright 2012 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, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.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.MaxDB is a trademark of MySQL AB, Sweden.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, 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 in several other countries all over the world. 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.

DisclaimerSome components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components.Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way.

Documentation in the SAP Service MarketplaceYou can find this document at the following address: http://service.sap.com/instguides

2/82 PUBLIC 2012-04-02

http://service.sap.com/instguides

Typographic Conventions

Example Description

<> Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, “Enter your <User Name>”.

Arrows separating the parts of a navigation path, for example, menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in the documentation

Example Textual cross-references to an internet address, for example, http://www.sap.com

/example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web

123456 Hyperlink to an SAP Note, for example, SAP Note 123456

Example ■ Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options.

■ Cross-references to other documentation or published works

Example ■ Output on the screen following a user action, for example, messages ■ Source code or syntax quoted directly from a program ■ File and directory names and their paths, names of variables and parameters, and

names of installation, upgrade, and database tools

EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, database table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE

EXAMPLE Keys on the keyboard

2012-04-02 PUBLIC 3/82

http://www.sap.com

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=123456&_NLANG=en&_NVERS=0


Document History

CAUTION

Before you start the implementation, make sure you have the latest version of this document.

You can find the latest version on SAP Service Marketplace http://service.sap.com/

instguides.

The following table provides an overview on the most important document changes:

Version Date Description

1.0 2010-12-20 First Customer Shipment

1.1 2011-01-25 Chapter 3.2 RFID-Enabled Inbound Processing and Receipt Confirmation: Enhancement regarding over and under unloading operationChapter 3.3 Secure Tracking and Tracing: Enhancement regarding quantity events

1.2 2011-05-23 Chapter A Reference was deleted.

1.3 2011-11-08 Chapter 1.1 About this Document: Enhancement regarding supported SAP enhancement packages.Chapter 1.3 Important SAP Notes: Enhancement regarding SAP notes 1144099, 1612879, and 1641200.

1.4 2012-04-02 Chapter 5.1 List of Documents: Enhancement regarding update guides.

4/82 PUBLIC 2012-04-02



Table of Contents

Chapter 1 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.1 About this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.2 Related Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.3 Important SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 2 SAP Solutions for Auto-ID and Item Serialization Overview . . . . . . . . . . 13

2.1 Introduction to SAP Solutions for Auto-ID and Item Serialization . . . . . . . . . 13

2.2 Software Units of SAP Solutions for Auto-ID and Item

Serialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.2.1 Application Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.2.1.1 SAP Solutions for Auto-ID and Item Serialization . . . . . . . . . . . . . . . . . . . . . . 15

2.2.1.2 SAP Auto-ID Infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2.2.1.3 SAP ERP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2.2.1.4 OLTP System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2.2.1.5 SAP Event Management (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2.2.2 Technology Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2.2.2.1 SAP Basis and SAP NetWeaver Application Server . . . . . . . . . . . . . . . . . . . . . . 17

2.2.2.2 SAP NetWeaver Process Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

2.2.2.3 SAP Basis Plug-In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

2.2.2.4 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

2.3 Enhancement Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2.3.1 Enhancement Package Key Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2.3.2 Key Facts About Enhancement Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

2.3.3 Enhancement Package Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

2.4 Software Component Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

2.5 System Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

2.6 Overall Implementation Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Chapter 3 Business Processes of SAP Solutions for Auto-ID and Item

Serialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

3.1 RFID-Enabled Outbound Processing Without WM . . . . . . . . . . . . . . . . . . . . . 39

2012-04-02 PUBLIC 5/82

3.1.1 Implementation Variant: RFID-Enabled Flexible Delivery

Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

3.1.2 Implementation Variant: IUID-Enabled Inbound/Outbound

Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

3.2 RFID-Enabled Inbound Processing and Receipt Confirmation . . . . . . . . . . . . . 48

3.3 Secure Tracking and Tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

3.4 RFID-Enabled RTI Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

3.5 Standalone RFID-Enabled Outbound Processing . . . . . . . . . . . . . . . . . . . . . . . 56

3.6 Standalone RFID-Enabled Inbound Processing . . . . . . . . . . . . . . . . . . . . . . . . 58

3.7 Standalone IUID Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

3.8 RFID-Enabled LES with Centralized Warehouse Management

System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

3.9 RFID-Enabled Kanban Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Chapter 4 Solution-Wide Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

4.1 SAP Solution Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

4.2 Upgrade Roadmap and Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

4.3 Service-Oriented Architecture (SOA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

4.3.1 Service Enablement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

4.3.2 Installation of the Service-Oriented Architecture (SOA) . . . . . . . . . . . . . . . . . 70

4.3.3 Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Chapter 5 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

5.1 List of Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

5.2 List of SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

5.3 Media List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

5.4 Tools and Resources for Planning Your System Landscape . . . . . . . . . . . . . . . 75

5.4.1 Business Process Repository (BPR) Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

5.4.2 Using the BPR Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

5.4.3 Scenario and Process Component List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

5.4.4 Using the SCL/PCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

6/82 PUBLIC 2012-04-02

1 Getting Started

1.1 About this Document

This Master Guide is the central starting point for the technical implementation of SAP solutions for

auto-ID and item serialization. You can find cross-scenario implementation information as well as

scenario-specific information in this guide.

NOTE

The central starting point for the technical upgrade of your SAP application is the Upgrade

Master Guide, which you can find on SAP Service Marketplace at http://service.sap.com/

instguides.

If you deploy SAP Auto-ID Infrastructure as an add-on, we recommend to use SAP Auto-ID

Infrastructure with the SAP enhancement package combinations mentioned in this guide. In

principle, you can deploy SAP Auto-ID Infrastructure also on a higher enhancement package for

SAP NetWeaver or SAP ERP than mentioned in this guide.

Use the Master Guide to get an overview of SAP solutions for auto-ID and item serialization, its software

units, and its scenarios from a technical perspective. The Master Guide is a planning tool that helps

you to design your SAP solutions for auto-ID and item serialization system landscape. It refers you to

the required detailed documentation, mainly:

■ Installation guides for single software units

■ SAP Notes

■ Configuration documentation

■ SAP Library documentation

For a general overview of the available SAP documentation, see The Main SAP Documentation Types.

The Master Guide consists of the following main sections:

■ Getting Started

Contains valuable information about using this document and related information

(documentation and SAP Notes) crucial to the installation and upgrade.

■ SAP Solutions for Auto-ID and Item Serialization Overview

Contains a short introduction to the offerings of SAP solutions for auto-ID and item serialization.

● Software Units of SAP Solutions for Auto-ID and Item Serialization

Contains a short description of the software components that are part of SAP solutions for

auto-ID and item serialization.

● Software Component Matrix

1 Getting Started


2012-04-02 PUBLIC 7/82



Provides the information about which business processes use which component and whether

the corresponding component is mandatory or optional.

● System Landscape for SAP Solutions for Auto-ID and Item Serialization

Provides an overview of a possible system landscape and overall installation information.

■ Business Processes of SAP Solutions for Auto-ID and Item Serialization

Contains the following information for each business process of SAP solutions for auto-ID and

item serialization:

● Business process overview

● Information about the required technical components (mandatory and optional

components) and technical system landscape

● Examples of how the different components interact and what protocols and interfaces are

used (technical infrastructure examples)

Depending on the actual business processes that have to be implemented and other aspects

(such as security or performance), the real infrastructure might be different.

● Information about the component's software releases

● Information about the overall installation sequence and subsequent steps

● References to related installation and configuration guides

■ Solutions-Wide Topics

■ Appendix

■ References

Depending on the specific business process, different installation and master guides are required

during the business process implementation. You can find an overview of all required

documentation referenced in this Master Guide.

NOTE

You can find the most current information about the technical implementation of SAP solutions

for auto-ID and item serialization and the latest installation and configuration guides on SAP

Service Marketplace at http://service.sap.com/instguides.

We strongly recommend that you use the documents available here. The guides are regularly

updated.

Constraints

■ The business scenarios that are presented here serve as examples of how you can use SAP software

in your company. The business scenarios are only intended as models and do not necessarily run

the way they are described here in your customer-specific system landscape. Ensure to check your

requirements and systems to determine whether these scenarios can be used productively at your

site. Furthermore, we recommend that you test these scenarios thoroughly in your test systems

to ensure they are complete and free of errors before going live.

1 Getting Started


8/82 PUBLIC 2012-04-02


■ This Master Guide primarily discusses the overall technical implementation of SAP solutions for

auto-ID and item serialization, rather than its subordinate components. This means that additional

software dependencies might exist without being mentioned explicitly in this document. You can

find more information on component-specific software dependencies in the corresponding

installation guides.

1.2 Related Information

The following table contains links to crucial information for implementing SAP solutions for auto-ID

and item serialization:

List of Related Documentation

Content Location on SAP Service Marketplace

Information about the latest versions of installation and upgrade guides


General information about SAP solutions for Auto-ID and item serialization

http://service.sap.com/rfid

Information about applications/solutions and business scenarios – SAP Business Maps

http://service.sap.com/businessmaps

Information about sizing, calculation of hardware requirements – such as CPU, disk and memory resource – with the Quick Sizer tool

http://service.sap.com/sizing

Information about released platforms and technology-related topics, such as maintenance strategies and language support

http://service.sap.com/platforms

To access the Platform Availability Matrix directly, enter http://service.sap.com/pam

Information about network security http://service.sap.com/securityguide

Information about network integration http://service.sap.com/securityguide

Information about high availability http://service.sap.com/ha

Information about performance http://service.sap.com/performance

Information about Support Package Stacks, latest software versions and patch level requirements

http://service.sap.com/sp-stacks

Information about the installation of SAP NetWeaver http://service.sap.com/instguidesnw70

Information about the upgrade of SAP NetWeaver http://service.sap.com/upgradenw70

Documentation on SAP Help Portal http://help.sap.com

Further Useful Links

The following table lists further useful links on SAP Service Marketplace:

List of Further Useful Links


Information about creating error messages http://service.sap.com/message

Information about SAP Notes http://service.sap.com/notes

1 Getting Started


2012-04-02 PUBLIC 9/82


http://service.sap.com/rfid

http://service.sap.com/businessmaps

http://service.sap.com/sizing

http://service.sap.com/platforms

http://service.sap.com/pam

http://service.sap.com/securityguide


http://service.sap.com/ha

http://service.sap.com/performance


http://service.sap.com/instguidesnw70

http://service.sap.com/upgradenw70

http://help.sap.com

http://service.sap.com/message

http://service.sap.com/notes


SAP Software Download Center (software download and ordering software)

http://service.sap.com/swdc

SAP Online Knowledge Products (OKPs) – role-specific Learning Maps

http://service.sap.com/rkt

Installation Guide: SAP Enhancement Package Installation Using SAP Enhancement Package Installer (SAPehpi) 7.02


Troubleshooting and Administration for Installations Using SAPehpi (ABAP)


Troubleshooting for Installations Using SAPehpi (Java) http://service.sap.com/instguides

How to Install SAP Enhancement Package 5 for SAP ERP 6.0: A Practical Guide


How to Install SAP Enhancement Package 1 for SAP SCM 7.0: A Practical Guide


Related Master Guides

This Master Guide is based on Component Master Guides. The following documents contain detailed

information about the relevant components:

List of Related Master Guides

Content Location

SAP Event Management 7.0 (including SAP enhancement package 1)

http://service.sap.com/instguides SAP Business Suite ApplicationsSAP SCM SAP Event Management

SAP Event Management 7.0 http://service.sap.com/instguides SAP Business Suite ApplicationsSAP SCM SAP Event Management

SAP ERP 6.0 http://service.sap.com/erp-inst SAP ERP 6.0

SAP NetWeaver 7.0 (including SAP enhancement package 2)

http://service.sap.com/instguides SAP NetWeaver SAP NetWeaver 7.0 (2004s) Installation Master Guide

SAP Solution Manager

SAP provides the SAP Solution Manager as a platform to efficiently support the implementation of

your solution. Using SAP Solution Manager significantly accelerates the implementation process and

helps you to achieve your business goals. At the same time, SAP can deliver Support Services based on

the business scenarios designed and documented in SAP Solution Manager. Implementation content

for your solution may further accelerate the implementation process. For information about availability

of content specifically tailored to your solution, see SAP Service Marketplace at http://

service.sap.com/solutionmanager.

Dependencies Between the Technical Usage of a System, the Activation of Business Functions, and Specific Functions

For more information about dependencies between the technical usage of a system, the activation of

business functions, and specific functions, see the ERP_AIE_INTEGRATION AIE ERP Integration business

1 Getting Started


10/82 PUBLIC 2012-04-02


http://service.sap.com/rkt








http://service.sap.com/erp-inst


http://service.sap.com/solutionmanager


function description. Start the transaction for displaying the business function status in the Switch

Framework (transaction SFW5) and display the documentation for the ERP_AIE_INTEGRATION business

function in the Display Document column.

1.3 Important SAP Notes

You must read the following SAP Notes before you start the installation or upgrade. These SAP Notes

contain the most recent information on the installation or upgrade, as well as corrections to the

installation or upgrade documentation.

Make sure that you have the up-to-date version of each SAP Note, which you can find on SAP Service

Marketplace at service.sap.com/notes.

SAP Note Number Title Description

1320442 Installation/Upgrade AUTO-ID 7.01 on SAP NetWeaver 7.0 EHP2

Contains installation and upgrade information for SAP Auto-ID Infrastructure 7.1

1320497 Installing/Upgrade SCEMSRV 701

Contains installation and upgrade information for SAP enhancement package 1 for SAP Event Management 7.0. If you want to run an SAP object event repository, the installation of SAP Event Management is required.

677373 Release Information Visibility Processes

Contains information about the availability of visibility processes

1344660 SAP Auto-ID Infrastructure 7.1: Online Documentation

Contains information about changes to the SAP Library documentation for SAP Auto-ID Infrastructure 7.1

1224284 Enterprise Services, Installing and Accessing the SOA Documentation

Lists business-related grouping of Enterprise Services

1342173 SAP AII: SOA Documentation Corrections

Contains information about changes to the documentation for SAP Auto-ID Infrastructure Enterprise Services

1350818 Consulting note for archiving configuration

Contains information about the configuration to display archived data in the Web interface

1515223 SAP NetWeaver Process Integration: Release Recommendation

This SAP note sets out our recommendation on which release of SAP NetWeaver PI you should use

1612879 Upgrade to EhP 3 for Netweaver 7.0 - new syntax check

Contains information about syntax errors in some programs after the upgrade to SAP enhancement package 3 for SAP NetWeaver 7.0.

1641200 New Start Authorization Check for Web Dynpro Applications

Contains information about missing authorizations to access the Web Dynpro applications in SAP Auto-ID Infrastructure.

1 Getting Started


2012-04-02 PUBLIC 11/82












1144099 (only for SAP object event repository)

Own activity methods when upgrading SAP Event Management

1 Getting Started


12/82 PUBLIC 2012-04-02


2 SAP Solutions for Auto-ID and Item Serialization Overview

2.1 Introduction to SAP Solutions for Auto-ID and Item Serialization

SAP solutions for auto-ID and item serialization enable you to use of radio frequency identification

(RFID) and other means of automatic identification such as barcodes to provide accurate, real-time

information about items as they move through your supply chain and to automate your business

processes. SAP solutions for auto-ID and item serialization consist of the following:

■ SAP Auto-ID Infrastructure

SAP Auto-ID Infrastructure is a flexible and customizable infrastructure that integrates RFID

technology with existing SAP logistics systems. It provides:

● Standard content that enables you to automate and enable RFID for basic logistics processes

● Extensible capabilities that allow you to easily adapt the standard content to implement your

own customer-specific processes

■ SAP Auto-ID Enterprise

You can install multiple local instances of the component SAP Auto-ID Infrastructure and

implement an SAP object event repository to collect data centrally from across your enterprise

and from your business partners. You can use the repository to query, manage, and monitor your

processes centrally.

CAUTION

To implement an SAP object event repository, you must install SAP Auto-ID Infrastructure

and SAP Event Management on the same box. Furthermore, make sure that you have installed

your ERP system on a separate box.

SAP Object Event Repository

You can use SAP object event repository (the repository) to capture, store, and query data about

uniquely identified objects centrally in a disparate system landscape. You can automatically capture

information about object-level events that occur across your supply chain, from both within your

enterprise and from your business partners. You can access the data in the repository and your

business partner can use XML messages to query it. By enabling disparate applications to exchange

information about uniquely identified objects, the repository provides visibility and traceability of

the objects throughout their respective lifecycles. Furthermore, you can use the repository to

monitor business documents related to the objects.



2012-04-02 PUBLIC 13/82

■ SAP Event Management

SAP Event Management allows you to track and query events across your supply chain. It thereby

provides or improves visibility within your logistics processes, both in planning and in execution.

The flexibility of the application allows you to map, control, and check all required business

processes. SAP Event Management is an optional component in SAP Auto-ID Infrastructure

processes. If you install SAP object event repository, it is also possible to use the standalone

functionality of SAP Event Management.

NOTE

For SAP Event Management, the installation of SAP Event Management Communication

Layer (SAP EM-WCL) based on SAP NetWeaver Application Server Java is optional. As of SAP

enhancement package 1 for SAP Event Management SAP EM-WCL is not required. For more

information about SAP EM-WCL, see the Master Guide for SAP Event Management 7.0.

This Master Guide provides a central starting point for the technical implementation of the following

business processes:

■ RFID-Enabled Processes with Back-end Integration

● RFID-Enabled Outbound Processing Without WM

● RFID-Enabled Inbound Processing and Receipt Confirmation

● Secure Tracking and Tracing

● IUID-Enabled Inbound/Outbound Processing

● RFID-Enabled LES with Centralized Warehouse Management System

● RFID-Enabled Kanban Processing

■ RFID-Enabled Processes Without Back-end Integration

● RFID-Enabled Returnable Transport Items (RTI)

● Standalone RFID-Enabled Outbound Processing

● Standalone RFID-Enabled Inbound Processing

● Standalone IUID Processing

CAUTION

The technical landscapes described here show one of several ways to distribute the components

among hosts. Distribution of components depends on many factors, such as performance, sizing,

available hardware and so on. In practice, other distributions are possible.

Supported SAP NetWeaver Process Integration Releases

All business processes described here support SAP NetWeaver Process Integration 7.0 up to SAP

enhancement package 2 and SAP NetWeaver Process Integration 7.1 up to SAP enhancement package

1. In the single business process descriptions, for example, in the implementation sequence, only SAP

enhancement package 2 for SAP NetWeaver Process Integration 7.0 is mentioned.



14/82 PUBLIC 2012-04-02

SAP NetWeaver Process Integration is only needed if you install SAP Auto-ID Infrastructure on a

separate box or together with SAP object event repository. For more information, see the description

of the relevant business process.

NOTE

For an overview of the entire functionality of SAP solutions for auto-ID and item serialization,

see the solution map on SAP Service Marketplace at http://service.sap.com/bmet SAP

Business Maps Cross Industry Maps Supply Chain Management

RECOMMENDATION

The business processes that are presented here serve as examples of how you can use SAP software

in your company. The business processes are only intended as models and do not necessarily run

the way they are described here in your customer-specific system landscape. Check your

requirements and systems to determine whether you can use these processes productively at your

site. Furthermore, we recommend that you test these processes thoroughly in your test systems

to ensure they are complete and free of errors before going live.

NOTE

This Master Guide provides just one way to implement each business process. This is the

implementation valid for SAP solutions for auto-ID and item serialization. For other ways to

implement business processes, see the Scenario Component List Viewer on SAP Service

Marketplace (http://service.sap.com/scl).

2.2 Software Units of SAP Solutions for Auto-ID and Item Serialization

This section provides additional information about the most important software components of SAP

solutions for Auto-ID and Item Serialization.

NOTE

Only a subset of these components is required for the installation of a specific business process.

For a process-specific overview of components, see Business Processes of SAP Solutions for Auto-ID and

Item Serialization [external document].

2.2.1 Application Components

2.2.1.1 SAP Solutions for Auto-ID and Item Serialization

SAP solutions for auto-ID and item serialization enable you to use of radio frequency identification

(RFID) and other means of automatic identification such as barcodes to provide accurate, real-time



2012-04-02 PUBLIC 15/82

http://service.sap.com/bmet

http://service.sap.com/scl

information about items as they move through your supply chain and to automate your business

processes.

2.2.1.2 SAP Auto-ID Infrastructure

This component, optionally together with adapters for SAP backend systems or SAP Event

Management, supports the integration of RFID interrogators and other hardware for automatic

identification, with backend systems. It could be described as middleware for RFID and automatic

identification integration. In contrast to the adapters this component is implemented as an independent

system. It is connected to the device controllers of the readers. SAP Auto-ID Infrastructure receives

business-related information – indirectly through Process Integration (PI) - from SAP ERP and translates

it into technical information for the readers, handles the actions to be executed, receives messages about

read tags, decides on the reaction to read information or missing reads, persist the observation of tags

and tags related data, and delivers filtered information back to the backend system. Instead of connecting

SAP Auto-ID Infrastructure directly with different backend systems, it is integrated using PI systems.

This makes it possible to use an open XML message interface on the SAP Auto-ID Infrastructure side

and to easily connect backend systems.

2.2.1.3 SAP ERP

SAP ERP 6.0 consists of different product instances and software components, each representing a

particular functional piece of the software. For more information, see the Master Guide for SAP ERP

on SAP Service Marketplace at http://service.sap.com/instguides SAP Business Suite Applications

SAP ERP SAP ERP 6.0 Planning .

For information about the SAP enhancement packages for SAP ERP that are relevant for the business

process that you want to implement, see SAP Service Marketplace at http://service.sap.com/

instguides SAP Business Suite Applications SAP ERP SAP ERP 6.0 SAP enhancement packages for SAP ERP

6.0 .

2.2.1.4 OLTP System

The OnLine Transaction Processing (OLTP) system , for example, SAP R/3 system, SAP R/3

Enterprise, or SAP ECC, that is used in the SAP solutions for auto-ID and item serialization environment

as backend system. Data is exchanged between an SAP solutions for auto-ID and item serialization

environment and a connected OLTP system.



16/82 PUBLIC 2012-04-02




2.2.1.5 SAP Event Management (Optional)

SAP Event Management enables you to process application objects in various application systems and

thereby to track events for individual objects, processes, or parts of these throughout the entire supply

chain

The Web Dynpro ABAP-based Web interface and the Java-based Web interface (classic) offer information

access and full supply chain visibility for SAP Event Management. For example, you can access all your

supply chain information over the internet.

SAP Event Management can link, update, and evaluate the event messages with the application data

from the supply chain network.

It allows you to:

■ Monitor, measure and evaluate business processes

● SAP Event Management automatically monitors events that occur and those that have not

been reported, for example, goods issue, purchase order transfer, production end, or

unreported proof of delivery.

● SAP Event Management can automatically transfer data to a data warehouse system that uses

key performance indicators to create performance data for the quality of execution and

notification.

■ Employ checking processes and notify persons responsible for control events

● SAP Event Management checks objects that are relevant for Supply Chain Event Management

as soon as they are saved in the application system.

● SAP Event Management can automatically inform the decision maker in critical situations

that action is required, for example, automatic re-scheduling of the subsequent process step

when a delay has occurred.

■ Exchange and query information between partners, for example, e-mail or Internet

2.2.2 Technology Components

2.2.2.1 SAP Basis and SAP NetWeaver Application Server

SAP NetWeaver Application Server (SAP NetWeaver AS) provides the technological foundation for all

other SAP.com components. In a sense, SAP NetWeaver AS is the "operating system" of SAP.com. SAP

Basis became known as SAP NetWeaver AS from SAP R/3 4.6D on.

In the past, SAP Basis was used and shipped exclusively as an integral part of SAP R/3. This was also

reflected by the fact that SAP Basis and SAP R/3 had identical release names and shared support packages.

With the introduction of SAP.com, we now offer multiple components that build on SAP NetWeaver

AS. As a result, there is no longer a close naming relationship between SAP NetWeaver AS and SAP R/

3.

An SAP System consists of a database server, optional additional application servers, and a number of

front-end computers.



2012-04-02 PUBLIC 17/82

The database server is the computer on which the database is installed. This server can also

accommodate the central instance (the SAP instance that includes the message server and enqueue

server processes). If the central instance is installed on a separate application server, the database server

is called a standalone database server. Additional dialog instances (SAP instances including only dialog,

batch, spool, or update processes) are installed on application servers.

SAP NetWeaver AS provides a platform for quickly developing and deploying dynamic and collaborative

Web applications or other thin-client applications (WAP, PDA, and so on) and includes all proven SAP

programming models and technologies. With SAP NetWeaver AS, SAP natively supports open Internet

standards, including such protocols as HTTP, HTTPS, and SMTP, as well as Internet document

standards like HTML and XML.

Open integration capabilities provide access to existing SAP and non-SAP applications. All integration

facilities supported by SAP are available with SAP NetWeaver AS. The Java Connector or the DCOM

Connector give ABAP applications access to Java or .NET components and the other way round. In

addition, the Internet Communication Framework (ICF) of SAP NetWeaver AS enables programs

written in ABAP to process and distribute HTTP requests directly.

As a consequence, SAP NetWeaver AS can serve both as an HTTP server and client. It serves as an HTTP

server for bringing applications to the user via a Web browser either directly or via a standard Web

server. It serves as an HTTP client to access other Web applications for collecting information and data.

To complete Web connectivity, SAP NetWeaver AS provides full support for sending and receiving e-

mails via SMTP.

2.2.2.2 SAP NetWeaver Process Integration

Based on a native Web infrastructure that leverages open standards, SAP NetWeaver Process Integration

makes it possible to manage the broad diversity of highly heterogeneous components from a multitude

of vendors and to run in various technology environments. The integration capabilities capture shared

business semantics and act as a mediator between the services and their technical implementations. It

includes technical functions, such as Web service discovery, queuing, mapping, and routing. It also

establishes an infrastructure for business process management and high-performance execution within

and across organizational boundaries.

Exchange-based process integration removes the problems of direct connections by extracting shared

collaboration knowledge. These shared business semantics ease the integration of both external and

internal components. Instead of directly coding point-to-point interfaces for each new component,

the exchange infrastructure allows you to instantly plug in of new components once for each

component. This provides the flexibility you needed in today’s fast-changing business world, and it

reduces integration costs compared to the direct connection approach.



18/82 PUBLIC 2012-04-02

2.2.2.3 SAP Basis Plug-In

The SAP Basis Plug-In is an interface that enables the exchange of data between one or several SAP R/

3 systems and other SAP application components. The SAP Basis Plug-In supplies SAP application

components with transaction data and master data in real time. It also makes it possible to use SAP

application components like SAP Supply Chain Management (SAP SCM) or SAP Customer

Relationship Management (SAP CRM) together with certain SAP industry-specific application

components. All SAP industry-specific application components based on SAP R/3 4.6B and higher SAP

R/3 releases require an SAP Basis Plug-In.

SAP Basis Plug-Ins are shipped with SAP application components (SAP SCM, SAP NetWeaver Business

Intelligence, SAP Enterprise Buyer, SAP CRM, and SAP Strategic Enterprise Management) and with

industry-specific SAP application components based on SAP R/3 4.6B and higher SAP R/3 releases. You

can order the most recent SAP Basis Plug-In releases or download them from the SAP Service

Marketplace free of charge. Depending on the combination of the SAP R/3 Plug-In release and version

and the SAP R/3 release, certain SAP R/3 Support Package levels are required to install the SAP R/3 Plug-

In. For more information and to download, see SAP Service Marketplace at http://

service.sap.com/r3-plug-in.

2.2.2.4 User Interface

As of release 7.1, the mobile user interface based on Java Web Dynpro is no longer supported. The mobile

user interface as of release 7.1 uses the ITSmobile technology.

For more information about the user interface based on Java, see the Application Operations Guide for

SAP Auto-ID release 7.0 on SAP Service Marketplace at http://service.sap.com/instguides SAP

Business Suite Applications SAP SCM SAP Solutions for Auto-ID and Item Serialization SAP Solutions for Auto-ID

and Item Serialization 7.0 .

For more information about ITSmobile technology, see SAP Help Portal at http://help.sap.com/

nw70 SAP NetWeaver 7.0 including EHP2 SAP NetWeaver 7.0 Library (including Enhancement Package 2) SAP

NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key Capability ABAP Technology

UI Technology Web UI Technology SAP ITS in SAP NetWeaver Application Server Creating Mobile Applications

with ITSmobile .

NOTE

We highly recommend that you implement mobile integration with SAP consultants or

experienced SAP partners on a project by project basis, to ensure that the devices you deploy are

supported for SAP Auto-ID Infrastructure.



2012-04-02 PUBLIC 19/82

http://service.sap.com/r3-plug-in



http://help.sap.com/nw70


2.3 Enhancement Packages

2.3.1 Enhancement Package Key Concept

We have adapted our major release strategy to better fit your adoption cycle. To ensure that you benefit

from new developments and innovations while minimizing the impact on your core operational

systems, SAP uses enhancement packages to speed up the delivery of new functions.

With SAP enhancement packages, you can install and activate new functions depending on your

business needs without having to perform a system upgrade.

Implementation

There are three different scenarios to implement an enhancement package:

■ Installation of an enhancement package on an existing SAP system

■ New installation of an SAP system including an enhancement package

■ Upgrade of an SAP system including an enhancement package

The installation process of enhancement packages consists of two different steps:

■ Technical installation of an enhancement package

■ Activation of new functions using the switch framework technology

From a business point of view, functional enhancements are grouped into business functions (BFs).

The technical installation of the business functions does not change the system behavior. The new

functions are available in the system, but are not active. After the installation, no user interface or

process change takes place. You must explicitly activate new functions so that they become visible in

the system. As a result, changes are predictable and there are no side effects as only the activated areas

change.

With the switch framework technology (transaction SFW5), it is possible to control the activation of

new SAP objects in ABAP-based SAP systems. The activation process triggers a background job that

automatically performs all changes in the SAP system.

CAUTION

You cannot reverse most business function once they are activated. Due to technical restrictions,

only a limited number of business functions are reversible.

After you have activated a business function, you can see the changes and new developments in the

SAP system, for example:

■ Menu entries

■ New screens

■ New fields on the application user interfaces

■ IMG activities required for the implementation

■ New table entries in Customizing tables and system tables



20/82 PUBLIC 2012-04-02

You can create a transport request with the current settings of the switch framework. You can check

functional changes and the impact of an activated business function in advance in the business function

documentation.

RECOMMENDATION

Test the installation and activation on a sandbox system.

Maintenance

SAP enhancement packages have Support Packages of their own that are equivalent to the Support

Package versions of the underlying SAP system. We highly recommend installing the enhancement

package in combination with the latest available Support Package stack. This approach reduces

installation, modification adjustment, and testing effort. Using this strategy, you can install SAP

enhancement packages as a normal maintenance activity together with Support Package stacks.

An enhancement package requires a specific Support Package stack level in the source release SAP

system. If the SAP system is on a lower Support Package stack level, all relevant Support Package stacks

are automatically included into the download queue, as well as the latest available Support Packages

for the enhancement package.

Tools

The enhancement package installation requires the following tools:

■ SAP Solution Manager Maintenance Optimizer

■ Installation or upgrade tools (depending on your scenario)

The SAP Solution Manager Maintenance Optimizer (transaction DSWP) supports the download of a

consistent queue that includes all necessary support packages and enhancement packages. In addition,

SAP Solution Manager calculates a valid import queue for the selected SAP system and generates the

enhancement package stack configuration file that you require for the installation.

For the new installation of an SAP system including enhancement package you use the standard

installation tool (SAPinst)

To install an enhancement package on an existing SAP system, as well as for the upgrade of an SAP

System to a higher release including an enhancement package, you use the Software Update Manager

(SUM)

2.3.2 Key Facts About Enhancement Packages

The following list summarizes important facts about the enhancement package concept and

recommended approaches:

■ SAP enhancement packages are cumulative, meaning that each new enhancement package

includes new innovations of its own as well as all innovations delivered with prior packages.

■ We recommend installing the latest available enhancement package version.



2012-04-02 PUBLIC 21/82

■ Install enhancement packages and Support Packages in one single step (this includes the

preconditioned Support Packages).

■ SAP enhancement packages have Support Packages of their own that are equivalent to the Support

Package versions of the underlying SAP system.

■ SAP enhancement packages have the same maintenance period as the underlying core application.

■ The installation of an enhancement package is irreversible.

■ As long as you do not activate a business function, the installation of an enhancement package has

no impact on existing business processes or user interfaces.

You can only activate business functions in ABAP-based systems, not in Java-based SAP systems.

■ The activation of most business functions and extension sets is irreversible. Only a small number

of business functions is reversible.

Test the installation process and activation of new functions in advance on a sandbox system.

Ensure that you evaluate the runtime and the SAP system behavior, its dependencies and impacts.

Make sure that your SAP system is free of errors before going live.

2.3.3 Enhancement Package Implementation

In the following, you will find an overview of the steps involved in the three different enhancement

package implementation scenarios.

Process

Enhancement Package Installation in an Existing SAP System

Process

1. You find out, which of the new functions are interesting for your business.

2. You analyze the landscape dependencies.

3. You identify the enhancement package you want to install.

4. You make sure that you have set up your SAP Solution Manager system for the download of

packages and that the Maintenance Optimizer is configured.

5. You download the installation queue.

6. You perform the installation.

7. You analyze the impact of the business function activation with the dependency analyzer and

impact analyzer (transaction SFW5).

8. You activate the business functions.

9. You perform additional Customizing, if necessary.

10. You test the new functions.

Tools

■ SAP Solution Manager Maintenance Optimizer (mandatory)



22/82 PUBLIC 2012-04-02

■ Software Update Manager (SUM)

■ Switch framework with Dependency Analyzer and Impact Analyzer in SAP Solution Manager

(transaction SFW5)

New Installation of an SAP System with Enhancement Packages

Process

1. You install the SAP system. This includes the installation of the enhancement package.

2. You activate the business functions using the switch framework (transaction SFW5).

3. You perform the Customizing for the SAP system.

4. You test the SAP system.

Tools

■ Standard Installation tool SAPinst

■ Switch framework with Dependency Analyzer and Impact Analyzer in SAP Solution Manager

(transaction SFW5)

Upgrade to an SAP System Including an Enhancement Package Installation

Process

1. You plan the upgrade to the new release.

If you want to include Support Package stacks in your release upgrade, you require the SAP Solution

Manager Maintenance Optimizer. Make sure that you have set up an SAP Solution Manager system

and configured the Maintenance Optimizer for the download of the Support Packages.

2. You perform the upgrade to the new release. The upgrade includes the enhancement package.

3. You activate the business functions using the switch framework (transaction SFW5).

4. You perform the delta Customizing for the SAP system.

5. You test the SAP system.

Tools

■ Standard upgrade tool Software Update Manager (SUM)

■ SAP Solution Manager Maintenance Optimizer

2.4 Software Component Matrix

This section provides an overview of which business scenario uses which software unit.

NOTE

Note that there are software requirements for each component below that are not explicitly

mentioned in this documentation. They are documented in the relevant installation guides.

NOTE

This Master Guide provides just one way to implement each business scenario. For other ways to

implement business scenarios, see the Scenario & Process Component List in SAP Service



2012-04-02 PUBLIC 23/82

Marketplace at service.sap.com/scl. The Scenario & Process Component List helps you to find

realization alternatives for SAP solutions, business scenarios, and processes. It shows you which

application components are needed to realize a business scenario or process.

SAP Auto-ID Infrastructure 7.1 as Add-On for SAP ERP

SAP Solutions for Auto-ID and Item Serialization Business Process

Software ComponentX = mandatory(X) = optional– = not required

Business ProcessSAP Auto-ID Infrastructure

SAP NetWeaver Usage Type BI

SAP NetWeaver Usage Type PI

SAP Event Management SAP ERP

RFID-Enabled Processes With Backend Integration:

RFID-Enabled Outbound Processing Without WM, implementation variant RFID-Enabled Flexible Delivery Processing

X (X) (X) (X) X

RFID-Enabled Outbound Processing Without WM, implementation variant IUID-Enabled Inbound/Outbound Processing

X (X) (X) (X) X

RFID-Enabled Inbound Processing and Receipt Confirmation: RFID-Enabled Flexible Delivery Processing

X (X) (X) (X) X

Secure Tracking and Tracing

X (X) X X X

RFID-Enabled LES with Centralized Warehouse Management System

X (X) (X) (X) X

RFID-Enabled Kanban Processing

X (X) (X) (X) X

RFID-Enabled Processes Without Backend Integration:

RFID-Enabled Returnable Transport Items (RTI)

Business Process does not support this deployment option.

Standalone RFID-Enabled Outbound Processing

X (X) - (X) -

Standalone RFID-Enabled Inbound Processing

X (X) - (X) -

Standalone IUID Processing

X (X) - (X) -



24/82 PUBLIC 2012-04-02

NOTE

When SAP Auto-ID Infrastructure is deployed as an add-on for SAP ERP, and you want to use

Global Returnable Asset Identifiers (GRAIs), you have to create your own application to maintain

the relationship of the GRAI to the material number. You also have to implement Business Add-

In (BAdI) /AIN/DM_PRODUCT BAdI: Product Master-Specific Data Retrieval in Customizing for SAP Auto-

ID Infrastructure. For more information, see Customizing for SAP Auto-ID Infrastructure under

Business Add-Ins (BAdIs) BAdI: Product Master Specific Enhancements .

SAP Auto-ID Infrastructure 7.1 as Add-On for SAP NetWeaver







RFID-Enabled Processes With Backend Integration:

RFID-Enabled Outbound Processing Without WM, implementation variant RFID-Enabled Flexible Delivery Processing

X (X) X (X) X

RFID-Enabled Outbound Processing Without WM, implementation variant IUID-Enabled Inbound/Outbound Processing

X (X) X (X) X

RFID-Enabled Inbound Processing and Receipt Confirmation: RFID-Enabled Flexible Delivery Processing

X (X) X (X) X

Secure Tracking and Tracing

X (X) X X X

RFID-Enabled LES with Centralized Warehouse Management System

X (X) X (X) X

RFID-Enabled Kanban Processing

X (X) (X) (X) X

RFID-Enabled Processes Without Backend Integration:

RFID-Enabled Returnable Transport Items (RTI)

X (X) - (X) -

Standalone RFID-Enabled Outbound Processing

X (X) - - -



2012-04-02 PUBLIC 25/82







Standalone RFID-Enabled Inbound Processing

X (X) - - -

Standalone IUID Processing

X (X) - - -

2.5 System Landscape

CAUTION

We strongly recommend that you use a minimal system landscape for test and demo purposes

only. For performance, scalability, high availability, and security reasons, do not use a minimal

system landscape as your production landscape.

CAUTION

The technical landscapes described here show one of several ways to distribute the components

among hosts. Distribution of components depends on many factors, such as performance, sizing,

available hardware, and so on. In practice, other distributions are possible.

Since SAP Auto-ID Infrastructure can either be used as an add-on based on SAP ERP or together with

SAP NetWeaver in a separate box from SAP ERP, the following sections provide an overview of a possible

system landscape for all implementations of SAP solutions for auto-ID and item serialization. We do

not recommend installing all components on one host. Instead, you can distribute the components

among several hosts, as shown in the diagram below. The diagram provides just one example; there

are several ways to distribute the components. The distribution depends on many factors, such as sizing,

security, available hardware, and so on. In practice, any distribution of components among hosts is

possible.

Supported SAP NetWeaver Process Integration Releases

All business processes described here support SAP NetWeaver Process Integration 7.0 up to SAP


1. In the single business process descriptions, for example, in the implementation sequence, only SAP

enhancement package 2 for SAP NetWeaver Process Integration 7.0 is mentioned.

SAP NetWeaver Process Integration is only needed if you install SAP Auto-ID Infrastructure on a

separate box or together with SAP object event repository. For more information, see the description

of the respective business process.



26/82 PUBLIC 2012-04-02

General considerations

If you install SAP object event repository in your system landscape, you also have to install SAP

NetWeaver Process Integration.

CAUTION

If you install SAP Auto-ID Infrastructure as an add-on for SAP ERP, you also receive SAP Event

Management. In this case, its usage as an SAP object event repository is not supported by SAP.

CAUTION

If you install SAP Auto-ID Infrastructure on a separate box, you have the option of installing SAP

Event Management for local visibility or to use it as an SAP object event repository. In the latter

case, you install a separate SAP Auto-ID Infrastructure including SAP Event Management as a

separate instance in the same box. Furthermore, make sure that you have installed your ERP

system on a separate box. You must also install SAP NetWeaver Process Integration.

NOTE

For more information about possible deployment options, see the Master Guide for SAP Event

Management.

SAP Auto-ID Infrastructure as Add-On for SAP ERP

Figure 1: SAP Auto-ID Infrastructure as Add-On for SAP ERP

If you install SAP Auto-ID Infrastructure as an add-on for SAP ERP, you have the option of installing

SAP Event Management for local visibility.

Furthermore you have the option of connecting SAP Auto-ID Infrastructure to a separate instance of

SAP NetWeaver Business Intelligence.



2012-04-02 PUBLIC 27/82

SAP Auto-ID Infrastructure Installed on a Separate Box

Figure 2: SAP Auto-ID Infrastructure Installed on a Separate Box

If you install SAP Auto-ID Infrastructure on a separate box, you have the option of installing SAP Event

Management for local visibility or to use it as an SAP object event repository. In the latter case, you

install a separate SAP Auto-ID Infrastructure including SAP Event Management as a separate instance

in the same box. Furthermore, make sure that you have installed your ERP system on a separate box.

You must also install SAP NetWeaver Process Integration.

Furthermore, you have the option of connecting SAP Auto-ID Infrastructure directly to a separate

instance of SAP NetWeaver Business Intelligence and also optionally to a separate instance of SAP ERP

using SAP Netweaver Process Integration.



28/82 PUBLIC 2012-04-02

SAP Auto-ID Infrastructure Standalone

Figure 3: SAP Auto-ID Infrastructure Standalone

If you install SAP Auto-ID Infrastructure standalone, you have the option of installing the following:

■ SAP NetWeaver Business Intelligence

Additional Information Regarding Enterprise Services

You can use enterprise services in SAP Auto-ID Infrastructure to enable automated logistics processes

for services by using labels that IDs can automatically identify. The enterprise services are grouped by

business objects that manage the lifecycle of the label. The enterprise services are also grouped by the

RFID device that is used to read the label, and observations recorded by the RFID device. The enterprise

services are shipped with SAP Auto-ID Infrastructure. There are two technical scenarios for enterprise

services:

■ Using asynchronous enterprise services (SAP Auto-ID Infrastructure services):

To run asynchronous enterprise services, you must install SAP NetWeaver Process Integration (PI).

Note that SAP Auto-ID Infrastructure services run with an SAP ERP system for message exchange.

■ Using synchronous enterprise services:

There are two ways to run synchronous enterprise services, either by accessing the back-end system

via WSDL/SOAP runtime directly or access the back-end system via SAP NetWeaver PI runtime

(synchronous mediated). The latter requires an SAP NetWeaver PI integration server.

At the moment, SAP Auto-ID Infrastructure only uses synchronous enterprise services.

For more information about the installation of SAP NetWeaver, see the Master Guide for SAP

NetWeaver 7.0 on SAP Service Marketplace at http://service.sap.com/instguides . For more



2012-04-02 PUBLIC 29/82


information about the required releases and support packages, see the respective sections about the

SAP Auto-ID Infrastructure business processes.

2.6 Overall Implementation Sequence

The following tables describe the overall installation sequence for SAP Auto-ID Infrastructure and are

valid for SAP enhancement package 5 for SAP ERP 6.0.

All business processes described in this guide support SAP NetWeaver Process Integration 7.0 up to SAP


1. For reasons of simplification in this overall implementation sequence, we only cover SAP

enhancement package 2 for SAP NetWeaver Process Integration 7.0. For more information about

importing Enterprise Services Repository content, see SAP Help Portal at http://help.sap.com

SAP NetWeaver SAP NetWeaver PI/Mobile/IdM 7.1 SAP NetWeaver Process Integration 7.1 Including

Enhancement Package 1 SAP NetWeaver Process Integration Library Administrator's Guide Configuration of SAP

NetWeaver Configuration of SAP NetWeaver Systems Process Integration (PI) Wizard-Based Configuration

Importing ESR Content .

NOTE

Before you start the installation, you must know the components, and releases of components,

that you need for your business scenarios. We do not recommend installing all components. Only

install those components that are required for the business scenarios you want to use. For more

information about the required components, see the software component matrix for each business

scenario at Business Processes of SAP Solutions for Auto-ID and Item Serialization [page 39].

These tables contain all available software units. However, to implement a specific scenario, you need

a subset of the available software units. Some are only required for special processes. For information

about the software you need to implement a specific scenario, see SAP Service Marketplace at http://

service.sap.com/sp-stacks.

For the latest component version and patch level requirements, see quick link /sp-stacks in SAP Service

Marketplace.

For documentation listed in the following table, see List of Documents.

Process

SAP Auto-ID Infrastructure as Add-On for SAP Enhancement Package 5 for SAP ERP 6.0Step Action Remarks / Subsequent Steps

1 Installation of SAP enhancement package 5 for SAP ERP 6.0

For more information, see SAP Service Marketplace at http://service.sap.com/

instguides SAP Business Suite ApplicationsSAP ERP SAP ERP 6.0 Installation

2 Installation of SAP Auto-ID Infrastructure 7.1 For more information, see SAP Note 1320442



30/82 PUBLIC 2012-04-02

http://help.sap.com







Optional:

3 Installation/integration of SAP enhancement package 2 for SAP NetWeaver Process Integration 7.0orInstallation/integration of SAP NetWeaver Process Integration 7.0 including SAP enhancement package 2.

■ For more information about installation or integration of an SAP enhancement package on an existing SAP NetWeaver 7.0 or 7.1 system, see: ● Installation Guide – SAP Enhancement

Package 2 for SAP NetWeaver 7.0 on SAP Service Marketplace at http://service.sap.com/

installnw70, which describes the installation of an SAP enhancement package on an existing SAP NetWeaver Process Integration 7.0 system

● Installation Guides - SAP NetWeaver PI 7.1 on SAP Service Marketplace at http://service.sap.com/

installnwpi71, which describes the installation of an SAP enhancement package on an existing SAP NetWeaver Process Integration 7.1 system

■ For more information about installation or integration of an SAP NetWeaver system including the SAP enhancement package, see: ● Installation Guide – SAP NetWeaver 7.0

Including SAP Enhancement Package 2 on <OS>:<DB> on SAP Service Marketplace at http://service.sap.com/installNnw70, which describes the installation of an SAP NetWeaver Process Integration 7.02 system

● Installation Guide SAP NetWeaver Process Integration 7.1 including SAP Enhancement Package 1 on <OS>:<DB> on SAP Service Marketplace at http://service.sap.com/installnwpi71, which describes the installation of an SAP NetWeaver Process Integration 7.11 system.

4 Installation of XI Content Auto-ID 7.1 on the XI host

■ Download the XI content on SAP Service Marketplace at http://

service.sap.com/swdc DownloadSupport Packages and Patches Entry by

Application Group SAP Application



2012-04-02 PUBLIC 31/82

http://service.sap.com/installnw70


http://service.sap.com/installnwpi71


http://service.sap.com/installNnw70







Components SAP Auto-ID InfrastructureSAP AII 7.1 Entry by Component XI

Content XI CONTENT AUTO-ID 7.1 .

■ Import the downloaded XI content files as described in SAP Note 836200.

Installation of SAP Auto-ID Infrastructure, SAP ERP, and SAP Enhancement Package 5 for SAP ERP on Separate BoxesStep Action Remarks / Subsequent Steps

1 Installation/integration of SAP enhancement package 2 for SAP NetWeaver 7.0 SP2 and higher as prerequisite for the SAP Auto-ID Infrastructure 7.1 Add-Onorinstallation/integration of SAP NetWeaver 7.0 SP2 and higher including SAP enhancement package 2 for SAP NetWeaver 7.0 as prerequisite for the SAP Auto-ID Infrastructure 7.1 Add-On

For more information, see: ■ Installation Guide – SAP Enhancement Package

2 for SAP NetWeaver 7.0 on SAP Service Marketplace at http://service.sap.com/installnw70, which describes the installation of an SAP enhancement package on an existing SAP NetWeaver 7.0 system.

■ Installation Guide – SAP NetWeaver 7.0 Including SAP Enhancement Package 2 on <OS>:<DB> on SAP Service Marketplace at http://service.sap.com/installnw70, which describes the installation of an SAP NetWeaver 7.02 system.

2 Installation of Add-On SAP Auto-ID Infrastructure 7.1 on the SAP NetWeaver Application Server ABAP

For more information, see SAP Note 1320442 and on SAP Service Marketplace at http://service.sap.com/instguides

SAP Business Suite Applications SAP SCMSAP Solutions for Auto-ID and Item SerializationUsing SAP Auto-ID Infrastructure 7.1 .

3 Installation/Integration of back-end system ■ For more information about the backend system per business process, see the respective business process description in this guide.

■ For more information about SAP ERP 6.0, see Installation Guide – SAP ECC 6.0 on <OS>:<DB> on SAP Service Marketplace at http://service.sap.com/instguides.

■ For more information about SAP ERP 5.0, see Installation Guide – SAP ERP Central Component (ECC) 5.0 on <OS>:<DB> on SAP Service Marketplace at http://service.sap.com/instguides

■ For more information about SAP R/3 Enterprise 4.7x200, see Installation Guide – SAP R/3 Enterprise on <OS>:<DB> –



32/82 PUBLIC 2012-04-02













Using SAP R/3 Enterprise Core 4.70, SAP R/3 Enterprise Extension Set 2.00 on SAP Service Marketplace at http://service.sap.com/instguides

■ For more information about SAP R/3 4.6C, see Installation Guide – SAP R/3 4.6C on <OS>:<DB> on SAP Service Marketplace at http://service.sap.com/instguides

4 If you use SAP ERP 6.0, installation of SAP enhancement package 5 for SAP ERP 6.0

For more information, see SAP Service Marketplace at http://service.sap.com/

instguides SAP Business Suite ApplicationsSAP ERP SAP ERP 6.0 Installation

5 If you use SAP R/3 Enterprise 4.7x200, apply at least SAP BASIS SP 37 and SAP APPL Sp 09 for the SAP R/3 Enterprise server.

The Support Packages are available on SAP Service Marketplace at http://service.sap.com/swdc.

6 If you use SAP R/3 4.6C, apply at least SAP BASIS SP 47, SAP ABA SP 47, and SAP APPL

SP 47 for the SAP R/3 server.

The Support Packages are available on SAP Service Marketplace at http://service.sap.com/patches.

7 Installation/integration of SAP enhancement package 2 for SAP NetWeaver Process Integration 7.0orInstallation/integration of SAP NetWeaver Process Integration 7.0 including SAP enhancement package 2.

■ For more information about installation or integration of an SAP enhancement package on an existing SAP NetWeaver 7.0 or 7.1 system, see: ● Installation Guide – SAP Enhancement

Package 2 for SAP NetWeaver 7.0 on SAP Service Marketplace at http://service.sap.com/

installnw70, which describes the installation of an SAP enhancement package on an existing SAP NetWeaver Process Integration 7.0 system

● Installation Guides - SAP NetWeaver PI 7.1 on SAP Service Marketplace at http://service.sap.com/

installnwpi71, which describes the installation of an SAP enhancement package on an existing SAP NetWeaver Process Integration 7.1 system

■ For more information about installation or integration of an SAP NetWeaver system including the SAP enhancement package, see: ● Installation Guide – SAP NetWeaver 7.0

Including SAP Enhancement Package 2 on <OS>:<DB> on SAP Service



2012-04-02 PUBLIC 33/82







http://service.sap.com/swdc.

http://service.sap.com/swdc.

http://service.sap.com/patches.

http://service.sap.com/patches.






Marketplace at http://service.sap.com/installNnw70, which describes the installation of an SAP NetWeaver Process Integration 7.02 system

● Installation Guide SAP NetWeaver Process Integration 7.1 including SAP Enhancement Package 1 on <OS>:<DB> on SAP Service Marketplace at http://service.sap.com/installnwpi71, which describes the installation of an SAP NetWeaver Process Integration 7.11 system.

8 Installation of the current System Landscape Directory (SLD) content on the SLD host (located on the SAP Exchange Infrastructure)

For more information, see SAP Note 669669.

9 Configuration of SAP enhancement package 2 for SAP NetWeaver Process Integration 7.0.

Configure the system as described in the content below. You can check system readiness as described in SAP Note 817920For more information, see SAP Solution Manager content Solutions/Applications

Basic Configuration Configuration StructuresSAP NetWeaver 7.0 (2004s) Usage Type

PI .

10 Installation of XI CONTENT AUTO-ID 7.1 on the XI host

1. Download the XI content on SAP Service Marketplace at http://

service.sap.com/swdc Support Packages and Patches Entry by Application Group SAP Application Components SAP Auto-ID Infrastructure SAP AII 7.1

Entry by Component XI Content XI CONTENT AUTO-ID 7.1 .

2. Import the downloaded XI content files as described in SAP Note 836200.

11 Installation of the XI content of the backend system on the XI host

If you use SAP enhancement package 5 for SAP ERP 6.0, do the following:1. Download the XI content XI CONTENT

EA-APPL_605 on SAP Service Marketplace at http://


Application Group SAP Application Components SAP ERP ENHANCEMENT PACKAGE SAP



34/82 PUBLIC 2012-04-02













EHP5 FOR ERP 6.0 XI Content XI CONTENT EA-APPL 605 .

2. Import the downloaded XI content files as described in SAP Note 836200 or 1152640.

If you use SAP ERP 6.0, do the following:1. Download the XI content XI CONTENT

EA_APPL_600 on SAP Service Marketplace at http://


Application Group SAP Application Components SAP ERP SAP ERP 6.0

Entry by Component XI Content XI CONTENT EA-APPL 600 .

2. Import the downloaded XI content files as described in SAP Note 836200 or 1152640.

If you use SAP ERP 5.0, do the following:1. Download the XI content XI CONTENT

EA_APPL_500 on SAP Service Marketplace at http://


Application Group SAP Application Components SAP ERP SAP ERP 2004

Entry by Component XI Content XI CONTENT EA-APPL 500 .

2. Import the downloaded XI content files as described in SAP Note 836200, 1152640 or 705541

SAP Auto-ID Infrastructure Used as Standalone Deployment OptionStep Action Remarks / Subsequent Steps

1 Installation/Integration of SAP enhancement package 2 for SAP NetWeaver 7.0 SP2 and higher, as prerequisite for the SAP Auto-ID Infrastructure 7.1 Add-Onorinstallation/integration of SAP NetWeaver 7.0 SP2 and higher including SAP enhancement package 2 for SAP NetWeaver 7.0 as prerequisite for the SAP Auto-ID Infrastructure 7.1 Add-On

For more information, see: ■ Installation Guide – SAP Enhancement Package 2 for SAP NetWeaver

7.0 on SAP Service Marketplace at http://service.sap.com/installnw70, which describes the installation of an SAP enhancement package on an existing SAP NetWeaver 7.0 system.




2012-04-02 PUBLIC 35/82















SAP Auto-ID Infrastructure Used as Standalone Deployment OptionStep Action Remarks / Subsequent Steps

2 Installation of Add-On SAP Auto-ID Infrastructure 7.1 on the SAP NetWeaver Application Server ABAP

For more information, see SAP Note 1320442 and on SAP Service Marketplace at http://service.sap.com/

instguides SAP Business Suite Applications SAP SCM SAP Solutions for Auto-ID and Item Serialization Using SAP Auto-ID Infrastructure 7.1 .

Optional: Installation of SAP Object Event RepositoryStep Action Remarks / Subsequent Steps

1 Installation of SAP Basis Plug-In 7.02 on the back-end if it is not already installed

See SAP Note 1007796 (Installation/Upgrade of Basis Plug in 2006.1) and SAP Service Marketplace at http://service.sap.com/r3-plug-in.

2 Installation/integration of SAP enhancement package 2 for SAP NetWeaver 7.0 SP2 and higher as prerequisite for the SAP Auto-ID Infrastructure 7.1 Add-Onorinstallation/integration of SAP NetWeaver 7.0 SP2 and higher including SAP enhancement package 2 for SAP NetWeaver 7.0 as prerequisite for the SAP Auto-ID Infrastructure 7.1 Add-On

For more information, see: ■ Installation Guide – SAP Enhancement Package

2 for SAP NetWeaver 7.0 on SAP Service Marketplace at http://service.sap.com/installnw70, which describes the installation of an SAP enhancement package on an existing SAP NetWeaver 7.0 system.


3 Installation/integration of SAP enhancement package 1 for SAP Event Management 7.0orInstallation/integration of SAP Event Management 7.0 including SAP enhancement package 1 for SAP Event Management 7.0


4 Installation of SAP Auto-ID Infrastructure 7.1 For more information, see SAP Note 1320442

Optional: Installation of SAP NetWeaver System with Usage Type Process IntegrationStep Action Remarks / Subsequent Steps

1 Installation/integration of SAP enhancement package 2 for SAP NetWeaver Process Integration 7.0 or of SAP enhancement package 1 for SAP NetWeaver Process Integration 7.1orInstallation/integration of SAP NetWeaver Process Integration 7.0 including SAP enhancement package 2 or of SAP NetWeaver

For more information, see http://service.sap.com/installnw70 or http://service.sap.com/installnwpi71.



36/82 PUBLIC 2012-04-02

















Optional: Installation of SAP NetWeaver System with Usage Type Process IntegrationStep Action Remarks / Subsequent Steps

Process Integration 7.1 including SAP enhancement package 1

Optional: Installation of SAP Business IntelligenceStep Action Remarks / Subsequent Steps

1 Installation of SAP NetWeaver 7.0 Usage type BI

For more information, see SAP Service Marketplace at http://service.sap.com/installnw70

2 Installation of SAP NetWeaver 7.0 BI Content Add-On 5 (SAP NW 7.0 BI CONT ADDON 7.05)

For more information, see SAP Note 1321293. You can download the BI content for SAP Auto-ID Infrastructure from SAP Service Marketplace at http://

service.sap.com/swdc Download Support Packages and Patches Entry by Application Group

SAP Application Components SAP Auto-ID Infrastructure SAP AII 7.1 Entry by Component

BI CONT 7.05For more information, see Installation Guide – SAP NetWeaver 7.0 SR<X> on <OS>:<DB> on SAP Service Marketplace at http://service.sap.com/installnw70.

Optional: Installation of SAP Event ManagementStep Action Remarks / Subsequent Steps

1 Installation of SAP Basis Plug-In 2006 SP01 and higher on the Backend

For more information, see SAP Note 1007796. Installation/Upgrade of Basis Plug in 2006.1 on SAP Service Marketplace at http://service.sap.com/notes.. For more information about SAP R/3 Plug-In, see http://service.sap.com/r3-plug-in.

2 Installation/integration of SAP enhancement package 1 for SAP Event Management 7.0orInstallation/integration of SAP Event Management 7.0 including SAP enhancement package 1 for SAP Event Management 7.0


NOTE

When using SAP R/3 4.6C or SAP R/3 4.7, Extension Set 2.0, as a backend component, you must

configure the application interface to SAP Event Management in the project.



2012-04-02 PUBLIC 37/82









http://service.sap.com/notes.



This page is left blank for documents that are printed on both sides.

3 Business Processes of SAP Solutions for Auto-ID and Item Serialization

This section contains short process descriptions and information about the technical landscape of the

business processes.

NOTE

A detailed process description and configuration documentation are part of SAP Solution Manager

implementation content ST-ICO 150 L022 (SP25). For more information about SAP Solution

Manager, see http://service.sap.com/solutionmanager.

For a description of business processes that are related to other deployments, see the respective

Master Guide under List of Documents.

3.1 RFID-Enabled Outbound Processing Without WM

Description

You can use this business process to automate outbound processing without the need for a warehouse

management (WM) system. You can either use it as a standalone outbound delivery process, or combine

it with the RFID-Enabled Inbound Processing and Receipt Confirmation process to create an integrated

delivery process between two business partners. This process allows you to:

■ Create outbound deliveries in SAP ERP

■ Commission RFID tags in SAP Auto-ID Infrastructure

■ Pack and load in SAP Auto-ID Infrastructure

■ Post goods issue in SAP ERP

■ Send ASNs together with EPCs

This process has the following implementation variants:

■ RFID-Enabled Flexible Delivery Processing

In this implementation variant, SAP Auto-ID Infrastructure and SAP ERP communicate via SAP

NetWeaver Process Integration. SAP ERP is updated at loading.

■ IUID-Enabled Inbound/Outbound Processing

In this implementation variant, SAP Auto-ID Infrastructure allows you to process deliveries using

standard SAP ERP interfaces. SAP Auto-ID Infrastructure supports the process for multilevel

hierarchies. The process supports the use of UIIs (Unique Item Identifiers) to identify material

items.



2012-04-02 PUBLIC 39/82


3.1.1 Implementation Variant: RFID-Enabled Flexible Delivery Processing

Description

This section contains information about the technical infrastructure of the RFID-Enabled Flexible

Delivery Processing implementation variant, including the components and the communication

between the components.

Prerequisite

If SAP Auto-ID Infrastructure and SAP ERP are installed on separate boxes, you can activate the business

function ERP_AIE_INTEGRATIONAIE ERP Integration in SAP ERP. Then you can activate the Business Add-

In (BAdI) implementation ABI_BADI_V56K_AIIFLX to get the correct due date of the delivery document.

If SAP Auto-ID Infrastructure is deployed on SAP ERP, you must activate the business function

ERP_AIE_INTEGRATION AIE ERP Integration in SAP ERP. Then you must activate BAdI implementation

ABI_BADI_V56K_AII71 or ABI_BADI_V56K_AIIECN, to ensure that the outbound process works.

Technical System Landscape

Software Components

If you install SAP Auto-ID Infrastructure as an add-on for SAP ERP, you use SAP ECC 6.0 including SAP

enhancement package 5 as a backend system.


SAP NetWeaver Process Integration.

If you install SAP Auto-ID Infrastructure on a separate box, you also must install SAP NetWeaver Process

Integration.

General Considerations

For simplicity, the graphic for the technical infrastructure contains icons for whole SAP systems, not

for single hosts. Remember that each SAP system may consist of several hosts with different tasks. Use

the internal features of the SAP NetWeaver Application Server ABAP+Java to provide high availability

and load balancing between the SAP systems.

NOTE

For more information about possible system landscapes, see System Landscape [external document].

Deployment Considerations

The content of the advanced shipping notification (ASN) differs depending on the deployment option.

If the partners of this implementation variant, for example, a supplier and a customer, use different

deployment options, adjustments may be necessary.

The ASN IDoc (enriched DELVRYXX) is generated in SAP NetWeaver Process Integration as a result of

the outbound integration process:



40/82 PUBLIC 2012-04-02

■ When SAP Auto-ID Infrastructure is deployed on SAP ERP, the ASN IDoc can contain hierarchical

information, which can be transferred from supplier to customer.

■ When SAP Auto-ID Infrastructure is not deployed on SAP ERP, the ASN IDoc can contain

hierarchical information. For this a handling unit is required for all levels or all but the lowest level

of the hierarchy. If you use the DespatchDeliveryNotification message, this limitation does not

apply.

For example, the partners work in a mixed deployment scenario where they have deployed SAP

Auto-ID Infrastructure separately from SAP ERP on the supplier side and directly on SAP ERP on

the customer side. They must have a handling unit at all levels or all but the lowest level of the

hierarchy to transfer the hierarchy from supplier to customer.

When SAP Auto-ID Infrastructure is not deployed as an add-on for SAP ERP (thus, it is deployed as an

add-on for SAP NetWeaver in a box separate from SAP ERP), the following applies: Handling units

(HUs) that were prepacked in SAP Auto-ID Infrastructure can only be manually assigned to an

outbound delivery in SAP ERP. This should be done before you load the HUs in SAP Auto-ID

Infrastructure to generate an advanced shipping notification (ASN) with the HUs.

XI Considerations

XI content is a special application content that must be installed on the XI host where each shared

application needs its own content.

NOTE

For each ABAP Support Package for SAP systems, there is a corresponding XI Content Binary

Patch Package that you must apply each time you upgrade your Support Package. This also applies

for SAP Auto-ID Infrastructure and the corresponding XI Content for SAP Auto-ID

Infrastructure 7.1. There is a one-to-one relationship between each Support Package.

Identity Management Considerations

For an overview of the planning and installation information necessary for implementing SAP

NetWeaver Identity Management, see the Installation Overview available on the SAP Help Portal at

http://help.sap.com/nw71 SAP NetWeaver Identity Management 7.1 .

Example: Technical Infrastructure of RFID-Enabled Flexible Delivery Processing (Using SAP ECC 6.0)

The graphic shows an example of the technical infrastructure for SAP Auto-ID Infrastructure installed

on a separate box.



2012-04-02 PUBLIC 41/82


Figure 4: Example: Technical Infrastructure of RFID-Enabled Flexible Delivery Processing (Using SAP

ECC 6.0)

Software Units for SAP Auto-ID Infrastructure as an Add-On for SAP ERP Using SAP ECC 6.0

The following software components are either mandatory or optional, as shown in the table below,

for the technical implementation of this process.

The following table provides just one way to implement this business process. For other combinations,

see http://service.sap.com/scl.

Component Mandatory Optional

SAP Auto-ID Infrastructure 7.1 ■ AUTO-ID 7.1 ■ SAP_BS_FOUNDATION_702

X

SAP EHP 5 for SAP ERP 6.0 X

SAP ERP 6.0 X

SAP NetWeaver PI ■ XI CONTENT AUTO-ID 7.1

■ XI CONTENT EA-APPL 605

X

SAP NetWeaver BI ■ BI_CONT 705

X

EHP 1 FOR SAP EM 7.0 X

SAP Event Management 7.0 X

Software Units for SAP Auto-ID Infrastructure Installed on a Separate Box





42/82 PUBLIC 2012-04-02






X

SAP EHP2 FOR SAP NETWEAVER 7.0 Support Package 2 (Application Server ABAP) X

SAP NetWeaver 7.0 X

SAP Backend System XSAP R/3 4.6C and higher



X


X



For more information about the installation of these components, see System Landscape [external

document].

Implementation Sequence

For more information about the implementation sequence, see Overall Upgrade Sequence [external

document].

This business process supports the following system landscapes:

■ SAP Auto-ID Infrastructure as add-on for SAP ERP

■ SAP Auto-ID Infrastructure as add-on for SAPNetWeaver

Further Information

The following documents provide more information about the RFID-Enabled Flexible Delivery

Processing implementation variant.

Content Location

Process Description

For process description information, see the RFID-Enabled Flexible Delivery Processing. The documentation is available as SAP Solution Manager content for the RFID-Enabled Inbound Processing & Receipt Confirmation business process or for the RFID-Enabled Outbound Processing Without WM business process. Choose tab page Documentation.

Configuration Documentation

For configuration information, see the RFID-Enabled Flexible Delivery Processing: Configuration Guide. The documentation is available as SAP Solution Manager content for the RFID-Enabled Inbound Processing & Receipt Confirmation business process or for the RFID-Enabled Outbound Processing Without WM business process. Choose tab page Configuration.

Scenario Security Guide

For more information, see the SAP Service Marketplace at http://service.sap.com/securityguide.



2012-04-02 PUBLIC 43/82




3.1.2 Implementation Variant: IUID-Enabled Inbound/Outbound Processing

Description

This section contains information about the technical infrastructure of the IUID-Enabled Inbound/

Outbound Processing implementation variant, including the components and the communication

between the components.

Prerequisite

If SAP Auto-ID Infrastructure and SAP ERP are installed on separate boxes, you can activate the business

function ERP_AIE_INTEGRATION AIE ERP Integration in SAP ERP. Then you can activate the Business Add-

In (BAdI) implementation ABI_BADI_V56K_AIIFLX to get the correct due date of the delivery document.


ERP_AIE_INTEGRATION AIE ERP Integration in SAP ERP. Then you must activate BAdI implementation

ABI_BADI_V56K_AII71 or ABI_BADI_V56K_AIIECN, to ensure that the outbound process works.


Software Components


enhancement package 5 or higher as a backend system.




Integration.






NOTE

For more information about possible system landscapes, see System Landscape [external document].




deployment options, adjustments maybe necessary.

The ASN IDoc (enriched DELVRYXX) is generated in SAP NetWeaver Process Integration as a result of

the outbound integration process:



44/82 PUBLIC 2012-04-02

■ When SAP Auto-ID Infrastructure is deployed on SAP ERP, the ASN IDoc can contain hierarchical

information, which can be transferred from supplier to customer.

■ When SAP Auto-ID Infrastructure is not deployed on SAP ERP, the ASN IDoc can contain

hierarchical information. For this a handling unit is required for all levels or all but the lowest level

of the hierarchy. If you use the DespatchDeliveryNotification message, this limitation does not

apply.

For example, the partners work in a mixed deployment scenario where they have deployed SAP

Auto-ID Infrastructure separately from SAP ERP on the supplier side and directly on SAP ERP on

the customer side. They must have a handling unit at all levels or all but the lowest level of the

hierarchy to transfer the hierarchy from supplier to customer.

When SAP Auto-ID Infrastructure is not deployed as an add-on for SAP ERP (thus, it is deployed as an

add-on for SAP NetWeaver in a box separate from SAP ERP), the following applies: Handling units

(HUs) that were prepacked in SAP Auto-ID Infrastructure can only be manually assigned to an

outbound delivery in SAP ERP. This should be done before you load the HUs in SAP Auto-ID

Infrastructure to generate an advanced shipping notification (ASN) with the HUs.

XI Considerations



NOTE

For each ABAP Support Package for SAP systems there is a corresponding XI Content Binary Patch

Package that must be applied every time you upgrade your Support Package. This also applies for

SAP Auto-ID Infrastructure and the corresponding XI Content for SAP Auto-ID Infrastructure

7.1. The relationship is one to one with every Support Package.





Business Function in Backend System

SAP enhancement package 5 for SAP ERP 6.0 with business function ERP_UID_02 is a prerequisite to use

this implementation variant.

Example: Technical Infrastructure of IUID-Enabled Inbound/Outbound Processing (Using SAP ECC 6.0)


on a separate box.



2012-04-02 PUBLIC 45/82


Figure 5: Example: Technical Infrastructure of IUID-Enabled Inbound/Outbound Processing (Using

SAP ECC 6.0)








X

SAP EHP5 for SAP ERP 6.0 X

SAP ERP 6.0 X

SAP NetWeaver PI ■ XI CONTENT AUTO-ID 7.1 ■ XI CONTENT EA-APPL 605

X


X








46/82 PUBLIC 2012-04-02






X


SAP NetWeaver 7.0 X

SAP EHP4 and higher for SAP ERP 6.0 X

SAP ERP 6.0 X

SAP NetWeaver PI ■ XI CONTENT AUTO-ID 7.1 ■ XI CONTENT EA-APPL 605

X


X



For more information about the installation of these components, see System Landscape [external

document].


For more information about the implementation sequence, see Overall Upgrade Sequence [external

document].




Further Information

The following documents provide more information about the IUID-Enabled Inbound/Outbound


Content Location

Process Description For process description information, see the IUID-Enabled Inbound/Outbound Processing. The documentation is available as SAP Solution Manager content for the IUID-Enabled Inbound/Outbound Processing business process. Choose tab page Documentation.


For configuration information, see the IUID-Enabled Inbound/Outbound Processing: Configuration Guide. The documentation is available as SAP Solution Manager content for the IUID-Enabled Inbound/Outbound Processing business process. Choose tab page Configuration.





2012-04-02 PUBLIC 47/82




3.2 RFID-Enabled Inbound Processing and Receipt Confirmation

Description

You can use this business process to automate inbound processing and receipt confirmation. You can

either use it as a standalone inbound delivery process or combine it with the RFID-Enabled Outbound

Processing Without Warehouse Management process to create an integrated delivery process between

two business partners. This business process allows you to:

■ Receive ASNs together with EPCs

■ Create inbound deliveries in SAP ERP

■ Unload inbound deliveries in SAP Auto-ID Infrastructure

■ Confirm the inbound delivery in SAP ERP

■ Post goods receipt in SAP ERP

Over and under unloading operation can only be supported for unpacked inbound deliveries.

This process has the following possible implementation variant:

■ RFID-Enabled Flexible Delivery Processing

In this implementation variant SAP Auto-ID Infrastructure and SAP ERP communicate via SAP

NetWeaver Process Integration (SAP NetWeaver PI). SAP ERP is updated at loading. For more

information about this implementation variant, see RFID-Enabled Flexible Delivery Processing [external

document].

Prerequisite


ERP_AIE_INTEGRATION AIE ERP Integration in SAP ERP. Then you must activate the following BAdI

implementations, to ensure that the inbound process works:

■ ABI_BADI_INBOUND_AII

■ ABI_BADI_SHP_DESADV_IN

■ ABI_BADI_DELY_PROC


For more information, see RFID-Enabled Flexible Delivery Processing.


For more information about the implementation sequence, see Overall Implementation Sequence [page 30].


■ Implementation variant RFID-Enabled Flexible Delivery Processing:

● SAP Auto-ID Infrastructure as add-on for SAP ERP

● SAP Auto-ID Infrastructure as add-on for SAPNetWeaver


3.2 RFID-Enabled Inbound Processing and Receipt Confirmation

48/82 PUBLIC 2012-04-02

Further Information



Content Location

Process Description

For process description information, see the following:RFID-Enabled Flexible Delivery ProcessingThe documentation is available as SAP Solution Manager content for the RFID-Enabled Inbound Processing & Receipt Confirmation business process or for the RFID-Enabled Outbound Processing Without WM business process. Choose tab page Documentation.


For configuration information, see the following:RFID-Enabled Flexible Delivery Processing: Configuration GuideThe documentation is available as SAP Solution Manager content for the RFID-Enabled Inbound Processing & Receipt Confirmation business process or for the RFID-Enabled Outbound Processing Without WM business process. Choose tab page Configuration


For more information, see the SAP Service Marketplace at service.sap.com/securityguide.

3.3 Secure Tracking and Tracing

Description

You can use this business scenario to track product flow and trace business events across your enterprise

and your extended supply chain network. This ensures the safe production and secure distribution of

your product by creating visibility and traceability. To enable this, Secure Tracking and Tracing uses

SAP object event repository. It comprises the following business processes:

■ Product Tracking and Authentication

● Product Tracking by Delivery

● Product Tracking by EPC

● Product Authentication (EPCIS data capture and query capability)

● Cold Chain Monitoring

● electronic Pedegree (ePedegree) with interfaces in XI content

■ RFID-Enabled Inbound Processing and Receipt Confirmation

■ RFID-Enabled Outbound Processing Without WM

SAP NetWeaver Process Integration is used to integrate the inbound and outbound processing.

SAP Auto-ID Infrastructure cannot send quantity events in an EPCIS Event Capture Notification

Message. A consequence of this is that SAP Auto-ID Infrastructure cannot send information about

untagged objects to SAP object event repository. Compared with this SAP object event repository can

handle quantity events.

CAUTION

If you have already installed SAP Auto-ID Enterprise and are using SAP object event repository,

do not activate the business function OER, Performance-Optimized PTA and Cold Chain



2012-04-02 PUBLIC 49/82

(AIE_OER_PTACOLDCHAIN) because the data is incompatible. If you activate this business function,

you can no longer use existing data in SAP object event repository in your business processes.

Prerequisite

■ To use SAP object event repository, you have installed SAP Auto-ID Enterprise.

■ You have activated the business function ERP_AIE_INTEGRATION AIE ERP Integration and the business

function LOG_LE_INTEGRATION LE, Extended Warehouse Management Integration in SAP ERP.


Software Components

If you install SAP Auto-ID Infrastructure as an add-on for SAP ERP, you use SAP ECC 6.0 as a backend

system.

If you install SAP Auto-ID Infrastructure as an add-on for SAP ERP, you also must install SAP NetWeaver

Process Integration.


Integration and SAP Event Management.






If you use the process variant for cold chain monitoring for the Product Tracking and

Authentification process, make sure that your data base capacity meets the expected data volume. The

data volume may increase because of the possible attachments to event messages.

SAP Object Event Repository Considerations

To implement an SAP object event repository, you must install SAP Auto-ID Infrastructure and SAP

Event Management on the same box. Furthermore, make sure that you have installed your ERP system

on a separate box.

If you install SAP Auto-ID Infrastructure on a separate box, you have the option of installing SAP Event

Management for local visibility or to use it as an SAP object event repository. In the latter case, you

install a separate SAP Auto-ID Infrastructure including SAP Event Management as a separate instance

in the same box. Furthermore, make sure that you have installed your ERP system on a separate box.

You must also install SAP NetWeaver Process Integration.

NOTE

For more information about possible system landscapes, see System Landscape [page 26].




50/82 PUBLIC 2012-04-02



deployment options, adjustments maybe necessary.

XI Considerations



NOTE









Example: Technical Infrastructure of Secure Tracking and Tracing (Using SAP ECC 6.0)


on a separate box.

Figure 6: Example: Technical Infrastructure of Secure Tracking and Tracing (Using SAP ECC 6.0)



2012-04-02 PUBLIC 51/82









XWe recommend that you install one (central) instance of AUTO-ID 7.1 together with SCEMSRV 7.0 to form SAP object event repository. You may install one or more additional (local) instances of AUTO-ID 7.1.

SAP EHP5 for SAP ERP 6.0 X

SAP Backend System XSAP ECC 6.0


■ XI CONTENT SCEMSRV 7.01


X

EHP1 FOR SAP EM 7.0 X







XWe recommend that you install one (central) instance of AUTO-ID 7.1 together with SCEMSRV 7.0 to form SAP object event repository. You may install one or more additional (local) instances of AUTO-ID 7.1.

SAP EHP2 FOR SAP NETWEAVER 7.0 Support Package 2 (Application Server ABAP)

X

SAP NetWeaver 7.0 X

SAP Backend System XSAP ECC 6.0


■ XI CONTENT SCEMSRV 7.01


X



For more information about the installation of these components, see System Landscape [page 26].



52/82 PUBLIC 2012-04-02








Further Information

The following documents provide more information about the Secure Tracking and Tracing

implementation variant.

Content Location

Process Description For process description information, see the Secure Tracking & Tracing. The documentation is available as SAP Solution Manager content for the Secure Tracking & Tracing business process. Choose tab page Documentation.


For configuration information, see the Secure Tracking & Tracing: Configuration Guide. The documentation is available as SAP Solution Manager content for the Secure Tracking & Tracing business process Choose tab page Configuration



3.4 RFID-Enabled RTI Processing

Description

You use this business scenario to manage, load, and unload returnable transport items (RTIs) as well

as to track their current location and evaluate stocks and cycle times. You can use this process for both

standardized containers and special containers. We support both plant-internal processes as well as

cross-plant and cross-business-partner processes. This process provides you with transparency across

your stocks of RTIs. This enables you to automate processes, reduce stocks, shorten cycle times, and

recognize bottlenecks early on. For more information, see SAP Solution Manager under RFID-Enabled

RTI Processing.


Software Components


Integration.








2012-04-02 PUBLIC 53/82



NOTE


XI Considerations



NOTE









Example: Technical Infrastructure of RFID-Enabled RTI Processing


on a separate box.

Figure 7: Example: Technical Infrastructure of RFID-Enabled RTI Processing



54/82 PUBLIC 2012-04-02


Figure 8: Optional







SAP Auto-ID Infrastructure 7.1 ■ AUTO-ID 7.1

■ SAP_BS_FOUNDATION_702

X


X

SAP NetWeaver 7.0 X

SAP Backend System XSAP R/3 4.6C and higher



X


X





2012-04-02 PUBLIC 55/82







Further Information

The following documents provide more information about the RFID-Enabled RTI Processing

implementation variant.

Content Location

Process Description For process description information, see the RFID-Enabled RTI Processing. The documentation is available as SAP Solution Manager content for the RFID-Enabled RTI Processing business process. Choose tab page Documentation.


For configuration information, see the RFID-Enabled RTI Processing: Configuration Guide. The documentation is available as SAP Solution Manager content for the RFID-Enabled RTI Processing business process. Choose tab page Configuration.



3.5 Standalone RFID-Enabled Outbound Processing

Description

The standalone deployment option of SAP Auto-ID Infrastructure enables customers to perform basic

outbound processing while providing the platform to migrate to a solution that is integrated with a

backend and expert system and scale the solution in a later roll-out following, for instance, a pilot.

Outbound processing with the standalone SAP Auto-ID Infrastructure provides users with the ability

to execute the process sequence: tag commissioning to write and validate written tags, packing, and

loading.













56/82 PUBLIC 2012-04-02


Example: Technical Infrastructure of Standalone RFID-Enabled Outbound Processing

The graphic shows an example of the technical infrastructure for SAP Auto-ID Infrastructure used as

a standalone deployment

Figure 9: Example: Technical Infrastructure of Standalone RFID-Enabled Outbound Processing

Software Units for SAP Auto-ID Infrastructure Used as a Standalone Deployment








X


SAP NetWeaver 7.0 X


X







2012-04-02 PUBLIC 57/82


■ SAP Auto-ID Infrastructure as standalone deployment option

Further Information

The following documents provide more information about the Standalone RFID-Enabled Outbound


Content Location

Process Description For process description information, see the RFID-Enabled Slap and Ship Outbound Processing. The documentation is available as SAP Solution Manager content for the RFID-Enabled Slap and Ship Outbound Processing business process. Choose tab page Documentation.


For configuration information, see the RFID-Enabled Slap&Ship Outbound Processing: Configuration Guide. The documentation is available as SAP Solution Manager content for the RFID-Enabled Slap and Ship Outbound Processing business process. Choose tab page Configuration.



3.6 Standalone RFID-Enabled Inbound Processing

Description

The standalone deployment option of SAP Auto-ID Infrastructure enables customers to perform basic

inbound processing while providing the platform to migrate to a solution that is integrated with a

backend and expert system and scale the solution in a later roll-out following, for instance, a pilot.

Inbound processing with the standalone SAP Auto-ID Infrastructure provides users with the ability to

perform inbound delivery processing and unloading.

For information about the technical system landscape, and the software units required for this process

and the implementation sequence, see Standalone RFID-Enabled Outbound Processing [page 56].

3.7 Standalone IUID Processing

Description

If you use item unique identification (IUID) to manage items marked with a unique item identifier

(UII), you can use this business process to execute standalone delivery processing for these items. IUID

is a system of identification developed by the US Department of Defense (DoD) that allows you to track

identical assets. If you use SAP Auto-ID Infrastructure in standalone mode for delivery processing, you

can perform the following process steps for objects marked with UIIs:

■ Tag commissioning

■ Internal movement

■ Packing

■ Loading

■ Unloading


3.6 Standalone RFID-Enabled Inbound Processing

58/82 PUBLIC 2012-04-02

This business process describes standalone outbound delivery processing, including tag commissioning

and packing.

For information about the technical system landscape, the software units required for this process and

the implementation sequence, see Standalone RFID-Enabled Outbound Processing [page 56].

3.8 RFID-Enabled LES with Centralized Warehouse Management System

Description

You can use this business process to automate the movement of handling units (HUs) and storage units

(SUs) resulting in the creation and confirmation of transfer orders (TOs) in SAP ERP (WM). The process

supports the following steps:

■ Read handling unit or storage unit ID and storage bin tag (SAP Auto-ID Infrastructure)

■ Move from goods receipt (with reference to inbound delivery) to putaway (SAP ERP)

or

■ Move from picking to goods issue with homogeneous HU (SAP ERP)

or

■ Transfer internal bin to bin warehouse (SAP ERP)

NOTE

The HandlingUnitERPLogisticsAreaChangeRequestConfirmation service operation can move

a HU or SU in a warehouse. It always moves a complete HU or SU and never does a partial stock

withdrawal or placement. It can find and confirm open transfer orders that were created to move

the HU or SU from one warehouse internal storage bin to another warehouse internal storage

bin. Goods receipt and goods issue do not fit in this scheme of HU or SU movement in a warehouse.

■ The operation only supports goods receipt for HU-managed storage locations.

■ The operation supports goods issue for any kind of storage location.

However, it only supports a goods issue for a homogeneous HU or SU, that is, an HU or SU

that has just one quant.

Prerequisite

■ The storage bins have been equipped with RFID tags. For a proposal of how to provide tags for

storage bins, see SAP Note 1372785.

■ The HUs and SUs are equipped with RFID tags. For a proposal of how to provide tags in the case

of HUs and usage of the field VEKP-EPC1 (that is, our default way of tag assignment), see SAP Note

1371453.

■ The forklift is equipped with an RFID reader that is connected with SAP Auto-ID Infrastructure.

■ You have activated the business function ERP_AIE_INTEGRATION AIE ERP Integration in SAP ERP.



2012-04-02 PUBLIC 59/82




Software Components

If you install SAP Auto-ID Infrastructure as an add-on for SAP ERP, you use SAP ECC 6.0 including

enhancement package 5 as a backend system.




Integration.






NOTE


XI Considerations



NOTE









Example: Technical Infrastructure of RFID-Enabled LES with Centralized Warehouse Management System (Using SAP ECC 6.0)


on a separate box.



60/82 PUBLIC 2012-04-02


Figure 10: Example: Technical Infrastructure of RFID-Enabled LES with Centralized Warehouse

Management System (Using SAP ECC 6.0)









X


SAP ERP 6.0 X



X


X








2012-04-02 PUBLIC 61/82






X


X

SAP NetWeaver 7.0 X

SAP Backend System X ■ SAP ERP 6.0 ■ SAP enhancement package

5 for SAP ERP 6.0



X


X









Further Information

The following documents provide more information about the RFID-Enabled LES with Centralized

Warehouse Management System process.

Content Location

Process Description The documentation is available as SAP Solution Manager content for the RFID-Enabled LES with Centralized Warehouse Management System business process. Choose tab page Documentation.


The documentation is available as SAP Solution Manager content for the RFID-Enabled LES with Centralized Warehouse Management System business process. Choose tab page Configuration



3.9 RFID-Enabled Kanban Processing

Description

You use this business process to integrate the kanban replenishment procedure in SAP ERP with radio

frequency identification (RFID) technology. By using RFID tags and devices to monitor the movements



62/82 PUBLIC 2012-04-02



and establish the status of kanban containers, RFID-enabled kanban automates and enhances the

visibility of your kanban replenishment procedure, resulting in a more accurate overview of your stock.

If SAP Auto-ID Infrastructure is deployed as an add-on for SAP ERP, you cannot use the manual

transactions to update the Kanban status and write tags.

Prerequisite

You use SAP enhancement package 2 or higher for SAP ERP 6.0.


Software Components


enhancement package 2 and higher as a backend system.








NOTE


XI Considerations



NOTE









Example: Technical Infrastructure of RFID-Enabled Kanban Processing (Using SAP ECC 6.0)


on a separate box.



2012-04-02 PUBLIC 63/82


Figure 11: Example: Technical Infrastructure of RFID-Enabled Kanban Processing (Using SAP ECC

6.0)

Figure 12: Optional



64/82 PUBLIC 2012-04-02








X


SAP ERP 6.0 X



X


X










X


SAP NetWeaver 7.0 X

SAP Backend System XSAP EHP 2 FOR SAP ERP 6.0



X


X






2012-04-02 PUBLIC 65/82








Further Information



Content Location

Process Description For process description information, see the RFID-Enabled Kanban Processing. The documentation is available as SAP Solution Manager content for the RFID-Enabled Kanban Processing business process. Choose tab page Documentation.


For configuration information, see the RFID-Enabled Kanban Processing: Configuration Guide. The documentation is available as SAP Solution Manager content for the RFID-Enabled Kanban Processing business process. Choose tab page Configuration.





66/82 PUBLIC 2012-04-02

4 Solution-Wide Topics

4.1 SAP Solution Manager

We highly recommend SAP Solution Manager as a platform to efficiently support the implementation

of your solution. Using SAP Solution Manager significantly accelerates the implementation process

and helps you achieve your business goals. We also deliver Support Services based on the business

scenarios designed and documented in SAP Solution Manager. Implementation content for your

solution can further accelerate the implementation process. For information about availability of

content specifically tailored to your solution, see SAP Service Marketplace at http://

service.sap.com/solutionmanager.

NOTE

In the installation or upgrade process, an SAP Solution Manager system is required to generate

the SAP Solution Manager Key. Without the SAP Solution Manager Key, you cannot continue

the installation process. The generation of the required key is implemented into SAP Solution

Manager as of release 3.2 support package 8. For more information, see SAP Note 811923.

4.2 Upgrade Roadmap and Shared Services

■ The Upgrade Roadmap provides methodologies for planning and executing an upgrade project.

For information, see SAP Solution Manager.

■ Shared services are provided by SAP NetWeaver and are required to run a system landscape, such

as SAP Solution Manager, System Landscape Directory, or Software Lifecycle Manager. For

information, see the current Master Guide and Upgrade Master Guide for SAP NetWeaver on SAP

Service Marketplace at http://service.sap.com/instguides SAP NetWeaver SAP NetWeaver

7.0 (2004s) Installation Master Guide or SAP NetWeaver SAP NetWeaver 7.0 (2004s) Upgrade

Upgrade Master Guide .

4.3 Service-Oriented Architecture (SOA)

SAP´s delivery on SOA (service-oriented architecture) differs from the pure architectural concept of

SOA in the delivery of ready-to use enterprise services. Enterprise services are SAP-defined Web services

which provide end-to-end business processes or individual business process steps that can be used to

compose business scenarios while ensuring business integrity and ease of reuse. SAP designs and


4.1 SAP Solution Manager

2012-04-02 PUBLIC 67/82





implements enterprise service interfaces to ensure semantic harmonization and business relevance.

This section deals with the service-enablement of SAP Business Suite 7.

4.3.1 Service Enablement

The service enablement of SAP Business Suite consists of one or more of the following SAP components:

■ SAP Business Suite 7

Enterprise services are an integral part of the software components of the SAP Business Suite

applications. Enterprise services are the technical interfaces to the functionality available in the

business application.

■ SAP NetWeaver PI 7.0 or higher

SAP NetWeaver Process Integration (SAP NetWeaver PI) is an open integration and application

platform that provides tools enabling you to set up a service-oriented architecture for business

applications. You can use the platform for providing, discovering, and consuming services,

integrating applications using the integration server, and managing business processes. Process

integration is required in a runtime environment to consume enterprise services in a mediated

scenario.

NOTE

Most asynchronous services can only be consumed in a mediated scenario.

NOTE

We recommend that you use the highest version of SAP NetWeaver Process Integration. For

more information, see SAP Note 1515223 and SAP Note 1388258

● Enterprise Services Repository

The Enterprise Services Repository (ES Repository) is the central repository that contains the

definition of all enterprise services and models. ES Repository is shipped with SAP NetWeaver

PI 7.1 and with SAP NetWeaver CE 7.1 or higher. The Enterprise Services Repository is a design

time environment that enables you to create and enhance enterprise service definitions and

to view enterprise service models.

NOTE

In a SAP NetWeaver 7.0 landscape you will require the Integration Repository to create

and enhance enterprise service definitions in a design time environment.

● Services Registry

The Services Registry is shipped with SAP NetWeaver PI 7.1 and SAP NetWeaver CE 7.1 or

higher and is required for the publication of enterprise service end-points (Web services) that

have been configured and activated in the SAP Business Suite.

■ SAP NetWeaver CE 7.1 or higher



68/82 PUBLIC 2012-04-02



The SAP NetWeaver Composition Environment (SAP NetWeaver CE) provides a robust

environment for the design and implementation of composite applications.

The design time environment of SAP NetWeaver CE can be used for the model-driven design and

development of composite applications based on enterprise services. SAP NetWeaver CE offers the

tools and the environment necessary for running composite applications fast and efficiently in a

runtime environment.

■ SAP Solution Manager 7.0

The Solution Composer, shipped with SAP Solution Manager 7.0, is required to host the enterprise

service online documentation.

Figure 13: Overview: SAP's Applications for SOA Enablement

The following table describes the SAP applications required or recommended for different runtime and

design time use cases:

SAP Applications

SAP Business Suite

SAP NetWeaver PI 7.0 (Integration Repository)

SAP NetWeaver PI 7.1 (ES Repository)

SAP NetWeaver CE 7.1 (ES Repository)

SAP Solution Manager 7.0 (Solution Composer)

SAP NetWeaver 7.1 Services Registry

Runtime Usage:

Enterprise Service Provisioning

Required Optional

Process integration and

One option required



2012-04-02 PUBLIC 69/82

mediated communication

Design Time Usage:

Create and enhance enterprise service definitions

Required One option required Recommended

View enterprise service models

One Option Required Recommended

Design and develop composite applications

Required Recommended Recommended

Enterprise service online documentation

Required

Publications of enterprise service end-points

Optional Required

4.3.2 Installation of the Service-Oriented Architecture (SOA)

The installation of service interfaces, and therefore the service enablement of SAP Business Suite,

consists of one or more of the following phases:

■ Identification of software components and required business functions

You use the technical data section of the enterprise service documentation to identify the following

data for each enterprise service:

● the software component version with which the service was shipped

● the business function(s) required to be activated

■ Identification of technical usages

SAP Note 1324838 provides a mapping of business functions and software component versions to

technical usages. You use this documentation to identify the required technical usages for your

list of software component versions and business functions.

■ Installation of the software component ECC-SE

The software component ECC-SE contains service implementations for ECC (the ERP Central

Component). This component must be explicitly installed if you intend to use enterprise services

for ECC functionality. In this case you must also select the technical usage “ESA ECC-SE” during

the enhancement package installation.

■ Selection and installation together with the other parts of the enhancement package

In the enhancement package installation process you must select all the technical usages you have

identified for service enablement together with the technical usages you identified for enhanced



70/82 PUBLIC 2012-04-02


features in SAP Business Suite. The selected technical usages will install the corresponding software

components that contain the enterprise services interfaces and implementations.

■ Enterprise service definitions for SAP NetWeaver PI 7.0 or ES Repository (SAP NetWeaver

7.1) (optional)

To install the content required for the enterprise service definitions you must select the technical

usage “XI Content” in the enhancement package installation process. This usage type downloads

the content files for both SAP NetWeaver 7.0 and 7.1 versions. Unpack the ZIP file and copy the tpz

files corresponding to your SAP NetWeaver version into the import directory of your Integration

Repository (for SAP NetWeaver PI 7.0) or Enterprise Services Repository (for SAP NetWeaver ES

Repository 7.1). Use the import function to import the content files into the corresponding

repository (Integration Repository or Enterprise Services Repository). (Choose Tools Import

Design Objects )

■ Enterprise service models for ES Repository (SAP NetWeaver 7.1) (optional)

To install the content required for the enterprise service models you must select the technical

usage “ESR Content” in the enhancement package installation process. This usage type downloads

the content files for SAP NetWeaver ES Repository 7.1. Unpack the ZIP file and copy the tpz files

into the import directory of your Enterprise Services Repository. Use the import function to import

the content files into the Enterprise Services Repository. (Choose Tools Import design objects )

NOTE

The enterprise service models are not available for the Integration Repository (SAP NetWeaver

PI 7.0)

■ Enterprise service online documentation for Solution Composer (optional)

To install the content required for the enterprise service online documentation you must

download the content file for the corresponding Business Suite application product version from

the Service Marketplace. Then you must import the content file into your Solution Composer.

Refer to SAP Note 1224284 for further information.

■ Services Registry (optional)

The services registry is shipped with SAP NetWeaver PI 7.1 and CE 7.1. You must install the services

registry and then publish the enterprise services from the Business Suite application to the registry

using the transaction SOAMANAGER in the backend.

For further information regarding the installation of SAP NetWeaver PI, CE and ES Repository,

refer to the corresponding SAP NetWeaver Installation and Master Guides.

4.3.3 Related Documentation

For more information about the service-oriented architecture (SOA), see the following information

sources:



2012-04-02 PUBLIC 71/82


■ SDN Community in the SAP Network at https://www.sdn.sap.com/irj/sdn/soa (registration

required)

■ The SAP Enterprise Service Workplace at http://ESWorkplace.sap.com

■ The Enterprise Services Wiki in the SAP Network at https://wiki.sdn.sap.com/wiki/x/LQ0

(registration required)

■ SAP Note 1224284: Enterprise Services, Installing and Accessing the SOA Documentation

■ SAP Note 1359215: Technical prerequisites for using enterprise services

■ SAP note 838402: Problems with non-Unicode system landscapes



72/82 PUBLIC 2012-04-02

https://www.sdn.sap.com/irj/sdn/soa

http://ESWorkplace.sap.com

https://wiki.sdn.sap.com/wiki/x/LQ0




5 Appendix

5.1 List of Documents

The following table lists all documents mentioned in this Master Guide.

Title Location on SAP Service MarketplaceInstallation Guides

Installation Guide of SAP ERP 6.0 http://service.sap.com/instguides SAP Business Suite Applications SAP ERP SAP ERP 6.0 Installation

Installation Guide – SAP Supply Chain Management 7.01

http://service.sap.com/instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP SCM Server 7.0 Master Guide for SAP SCM 7.0 Including SAP Enhancement Package 1

Installation Guide – SAP NetWeaver 7.0 http://service.sap.com/installNW71

Installation Guide – SAP Solution Manager http://service.sap.com/instguides SAP ComponentsSAP Solution Manager

Title Location on SAP Service MarketplaceMaster Guides

SAP ERP 6.0 http://service.sap.com/instguides SAP Business Suite Applications SAP ERP SAP ERP 6.0 Planning

SAP NetWeaver 7.0 http://service.sap.com/installNW70

SAP Supply Chain Management 7.01

http://service.sap.com/instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP SCM Server 7.0 Master Guide for SAP SCM 7.0 Including SAP Enhancement Package 1

SAP Event Management 7.0 (including SAP enhancement package 1)

http://service.sap.com/instguides SAP Business Suite Applications SAP SCM SAP Event Management SAP EM Server Using SAP EM Server 7.0 Master Guide for SAP Event Management 7.0 Including SAP Enhancement Package 1

Title Location on SAP Service MarketplaceUpdate Guides

SAP Supply Chain Management 7.01

http://service.sap.com/instguides SAP Business Suite Applications SAP SCMSAP SCM Server Using SAP enhancement package 1 for SAP SCM Server 7.0 Upgrade GuidesUpgrade Guides SAP SCM 7.0 EHP1

Software Update Manager 1.0

Update Guide - Update of SAP Systems Using Software Update Manager 1.0. You can download the latest version of this guide from SAP Service Marketplace at http://

service.sap.com/sltoolset .

5.2 List of SAP Notes

The following table lists all SAP Notes mentioned in this Master Guide.

5 Appendix

5.1 List of Documents

2012-04-02 PUBLIC 73/82



http://service.sap.com/installNW71



http://service.sap.com/installNW70




http://service.sap.com/sltoolset

http://service.sap.com/sltoolset


669669 Updating the SAP Component Repository in the SLD

Contains information about the update of the SAP Component Repository in the SLD

677373 Release Information Visibility Processes

Contains information about the availability of visibility processes

705541 XI 3.0 (SP1 and higher): Importing XI Content

Description of the import of downloaded XI content files

811923 Generating the SAP Solution Manager key

Description of the generation of the required SAP Solution Manager key

817920 XI Readiness Check 3.0/7.0, 7.1 Description for system readiness check.

836200 SAP NetWeaver 7.0: Importing Process Integration

Description of import of downloaded XI content files

1007796 Installation/Upgrade Basis Plug-In (PI_BASIS) 2006.1

Installation of SAP Basis Plug-In 7.01 SP02 on the back-end if it is not already installed

1152640 SAP NetWeaver 7.1: Import ESR-Content

Description of the import of downloaded XI content files

1224284 Enterprise Services, Installing and Accessing the SOA Docu

Lists business-related grouping of Enterprise Services

1320442 Installation/Upgrade AUTO-ID 7.1 on SAP NetWeaver 7.0 EHP2

Contains installation and upgrade information for SAP Auto-ID Infrastructure 7.1

1320497 Installing/Upgrade SCEMSRV 701 Contains installation and upgrade information for SAP enhancement package 1 for SAP Event Management 7.0

1321293 BI_CONT 705 Delta Upgrade (NW/ERP Enh.Pack )

Installation of SAP NetWeaver 7.0 BI Content Add-On 5 (SAP NW 7.0 BI CONT ADDON 7.05)

1342173 SAP AII: SOA Documentation Corrections

Contains information about changes to the documentation for SAP Auto-ID Infrastructure Enterprise Services

1344660 SAP Auto-ID Infrastructure 7.1: Online Documentation

Contains information about changes to the SAP Library documentation for SAP Auto-ID Infrastructure 7.1

1350818 Consulting note for archiving configuration

Contains information about the configuration to display archived data in the Web interface

1515223 SAP NetWeaver Process Integration: Release Recommendation

This SAP note sets out our recommendation on which release of SAP NetWeaver PI you should use

5.3 Media List

Installable Software Unit Media Name

AIN 710 SAP AII 7.1 (51036907)

SCEMSRV 701 SAP AII 7.1 (51036907)

SAP_BS_FND 702 SAP AII 7.1 (51036907)

5 Appendix

5.3 Media List

74/82 PUBLIC 2012-04-02

















Installable Software Unit Media Name

EM_WCL 700 SAP AII 7.1 (51036907)

XI/ESR Content SAP AII 7.1 (51036907)

5.4 Tools and Resources for Planning Your System Landscape

To plan your system landscape, you can use a few tools and resources that are available to you as SAP

customer.

Tools

On SAP Service Marketplace, we provide some tools that allow you to look up more detailed

information about business scenarios, business processes, and implementable steps. These tools include

the following:

Tools for Looking Up Information about Business Processes, Scenarios, and Implementable Steps

Tool Purpose

Business process repository (BPR) viewer To look up descriptions of business scenarios, business processes, and implementable steps

Scenario and process component list To look up the required components and releases for a business scenario, business process, or implementable step

In addition, there are tools in SAP Solution Manager that support you before, during, or after the

installation of your SAP product or SAP enhancement package. These tools include:

Tools for Supporting Installations and Upgrades

Tool Purpose

Solution Manager System Landscape To model and set up your system landscape

SAP Solution Manager Maintenance Optimizer To install support packages and SAP enhancement packages

Business process repository To access configuration documentation, links to Customizing activities and master data transactions, specifically tailored for individual business processes, business scenarios, or implementable steps

Business process change analyzer (available with SAP enhancement package 1 for SAP Solution Manager 7.0)

To analyze the effects of transports and support packages as well as activation logs for business functions

NOTE

As of SAP Solution Manager 7.0 with support package 23, these tools have been enhanced to

provide a better support for the setup of your system landscape and for installing and activating

business functions. For more information, see SAP Library for SAP Solution Manager on SAP Help

Portal at http://help.sap.com under SAP Solution Manager.

5 Appendix


2012-04-02 PUBLIC 75/82

http://help.sap.com

SAP Solution Manager: Implementation Content

To get implementation content that supports you during the configuration of your business processes,

business scenarios, and implementable steps, you need the SAP Solution Manager add-on Implementation

Content ST-ICO 155 L022 (SP25).

SAP Business Suite: Landscape Implementation — Technical Planning Guide

To get an overview of the necessary steps for planning a system landscape, use the Landscape Implementation

— Technical Planning Guide on SAP Service Marketplace at http://service.sap.com/instguides under

SAP Business Suite Applications . The guide also provides you with more information about the

following:

■ Examples of reference system landscapes

■ Planning tools such as the business process repository

■ Deployment options

■ Typical implementation process

5.4.1 Business Process Repository (BPR) Viewer

The business process repository viewer (BPR viewer) is a tool on SAP Service Marketplace that allows

you to preview the existing business scenarios, business processes, and implementable steps that are

shipped as part of SAP Solution Manager content. You can make use of the information in SAP Solution

Manager during your implementation project by taking the pre-delivered implementation content as

the starting point for your project scope. The implementation content is delivered with the following

assigned information:

■ Description of the business scenario, process, or implementable step

■ Configuration content (Customizing activities or configuration documentation)

5.4.2 Using the BPR Viewer

Procedure

Calling Up the BPR Viewer

You can call up the BPR viewer directly using the Internet address https://

implementationcontent.sap.com/bpr. Alternatively, you can also call up the Internet address http://

service.sap.com/bpr first, to see more background information about the BPR viewer and additional

material on SAP Service Marketplace.

Working with the BPR Viewer

To call up information about business scenarios, business processes, or implementable steps, navigate

the following paths in the BPR viewer:

5 Appendix


76/82 PUBLIC 2012-04-02


https://implementationcontent.sap.com/bpr

https://implementationcontent.sap.com/bpr

http://service.sap.com/bpr

http://service.sap.com/bpr

BPR Object Location

Business scenario Under Solutions/Applications

Business process Under Organizational Areas

Implementable step Under Solutions/Applications

For each business scenario, business process, or implementable step, you can select between different

versions that depend on varying components and releases. To display the descriptions of a business

scenario, business process, or implementable step, choose the Documentation tab page. To display

configuration documentation, choose the Configuration tab page.

NOTE

The BPR Viewer displays all descriptions, but only a selection of the configuration documentation.

To view all configuration documentation, install and use SAP Solution Manager at your customer

site.

5.4.3 Scenario and Process Component List

The scenario and process component list (SCL/PCL) is a tool on the SAP Service Marketplace that allows

you to find realization alternatives for SAP solutions, business scenarios, and processes for your SAP

enhancement package installation. You find the tool at http://service.sap.com/scl.

The SCL/PCL helps you to bridge the gap between the business view and the technical view in SAP's

products. It shows you which application components are needed to realize a business scenario or a

process and which business scenarios are possible with a given set of application components.

5.4.4 Using the SCL/PCL

Procedure1. Go to SAP Service Marketplace at http://service.sap.com/scl.

2. To start the SCL/PCL, choose Start Application.

The following selection options are provided:

■ SAP Scenarios and Realization Alternatives

With this option you can browse SAP's solutions, business scenarios, and processes. You can

find out which components are needed and the available alternatives.

■ SAP Components and Possible Scenarios

This option allows you to browse SAP's products and components and to find out, which

business scenarios and processes you can realize using the components.

For more information on how to use the tool, refer to the Help section.

3. Select SAP Scenarios and Realization Alternatives.

Select one or several scenarios, processes, and variants you want to realize. You can make your

selection by using an alphabetical index or a full-text search. It is also possible to see all scenarios

5 Appendix


2012-04-02 PUBLIC 77/82



for a certain solution. You will then get a list of the alternative ways to realize these scenarios. You

can also search for the identified business functions of a SAP enhancement package.

In the following steps we chose the scenario Billing Analysis in ERP as an example.

4. Add the scenario Billing Analysis in ERP to the Selected Scenarios/Processes/Variants list and choose Show

Realization Alternatives. The SCL/PCL then lists the different possibilities. With options like Validity

you can switch between possible and impossible realization alternatives. TheOptional Comp.

dropdown list helps you to find the minimum required SAP product versions.

5 Appendix


78/82 PUBLIC 2012-04-02

Typographic Conventions

Example Description

<Example> Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, “Enter your <User Name>”.

ExampleExample

Arrows separating the parts of a navigation path, for example, menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in the documentation

http://www.sap.com Textual cross-references to an internet address

/example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web

123456 Hyperlink to an SAP Note, for example, SAP Note 123456

Example ■ Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options.

■ Cross-references to other documentation or published works

Example ■ Output on the screen following a user action, for example, messages ■ Source code or syntax quoted directly from a program ■ File and directory names and their paths, names of variables and parameters, and

names of installation, upgrade, and database tools

EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, database table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE

EXAMPLE Keys on the keyboard

2012-04-02 PUBLIC 79/82

http://www.sap.com



SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +49/18 05/34 34 34F +49/18 05/34 34 20

www.sap.com

© Copyright 2012 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, PowerPoint, Silverlight, and Visual Studio 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, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation.Linux is the registered trademark of Linus Torvalds in the United States and other countries.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countries.Oracle and Java are registered trademarks of Oracle and its affiliates.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.Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc.IOS is a registered trademark of Cisco Systems Inc.RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World are trademarks or registered trademarks of Research in Motion Limited.Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are trademarks or registered trademarks of Google Inc.INTERMEC is a registered trademark of Intermec Technologies Corporation.Wi-Fi is a registered trademark of Wi-Fi Alliance.Bluetooth is a registered trademark of Bluetooth SIG Inc.Motorola is a registered trademark of Motorola Trademark Holdings LLC.Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, 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 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.

80/82 PUBLIC 2012-04-02

Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate 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.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.

DisclaimerSome components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited, as is any decompilation of these components.Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way.

Documentation in the SAP Service MarketplaceYou can find this document at the following address: http://service.sap.com/instguides

2012-04-02 PUBLIC 81/82


SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 34F +49/18 05/34 34 20www.sap.com

© Copyright 2012 SAP AG. All rights reserved.© Copyright 2012 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.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.

SAP Solutions for Auto-ID and Item Serialization 2010 ... · PDF fileMaster Guide SAP...

Documents

Transcript of SAP Solutions for Auto-ID and Item Serialization 2010 ... · PDF fileMaster Guide SAP...