SAP Solutions for RFID 2007 powered by SAP NetWeaver™

Master Guide

SAP Solutions for RFID 2007 powered by SAP NetWeaver™ Using SAP Auto-ID Infrastructure 5.1, SAP Event Management 5.1, and SAP Object Event Repository Document Version 1.3 – November, 2011 Material Number 50083260

© Copyright 2011 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, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, 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.

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 24 F +49/18 05/34 34 20 www.sap.com

Typographic Conventions Type Style Represents Example Text Words or characters quoted from

the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Cross-references to other documentation.

Example text Emphasized words or phrases in body text, graphic titles, and table titles.

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

Example text Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.

Icons Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Master Guide SAP Solutions for RFID

November 2011 4

Contents

1 GETTING STARTED ..................................................................................................... 6

1.1 History of Changes ............................................................................................... 7

1.2 Related Information............................................................................................... 8 1.2.1 Related Documentation ....................................................................................... 8

1.3 Important SAP Notes ............................................................................................ 9

2 SAP SOLUTIONS FOR RFID: OVERVIEW.................................................................. 10

2.1 System Infrastructure ......................................................................................... 10

3 BUSINESS PROCESSES IN SAP SOLUTIONS FOR RFID ......................................... 12

3.1 RFID-Enabled Outbound Processing Without WM ............................................ 12 3.1.1 Overview ........................................................................................................... 12 3.1.2 Implementation Variant: RFID-Enabled Flexible Delivery Processing.................. 13

3.1.2.1 Technical System Landscape ......................................................................... 13 3.1.2.2 Overview of Implementation Sequence........................................................... 15 3.1.2.3 Implementation Sequence .............................................................................. 15 3.1.2.4 Configuration.................................................................................................. 16

3.1.3 Implementation Variant: RFID-Enabled Delivery Processing .............................. 16 3.1.3.1 Technical System Landscape ......................................................................... 16

3.1.4 Overview of Implementation Sequence .............................................................. 21 3.1.4.1 Backend Option SAP ECC 6.0: Implementation Sequence ............................. 21 3.1.4.2 Backend Option SAP ECC 5.0: Implementation Sequence ............................. 22 3.1.4.3 Backend Option SAP R/3 Enterprise: Implementation Sequence .................... 24 3.1.4.4 Backend Option SAP R/3 4.6C: Implementation Sequence ............................. 26 3.1.4.5 Implementation Sequence: Optional SAP Event Management (SAP EM) ........ 28

3.1.5 Configuration ..................................................................................................... 28

3.2 RFID-Enabled Inbound Processing and Receipt Confirmation ......................... 29 3.2.1 Overview ........................................................................................................... 29

3.3 Product Tracking and Authentication ................................................................ 30 3.3.1 Overview ........................................................................................................... 30 3.3.2 Technical System Landscape ............................................................................ 30 3.3.3 Overview of Implementation Sequence .............................................................. 32

3.4 RFID-Enabled RTI Processing ............................................................................ 34 3.4.1 Overview ........................................................................................................... 34 3.4.2 Technical System Landscape ............................................................................ 34 3.4.3 Overview of Implementation Sequence .............................................................. 36

3.4.3.1 Configuration.................................................................................................. 36

3.5 Standalone RFID-Enabled Outbound Processing ............................................. 37 3.5.1 Overview ........................................................................................................... 37 3.5.2 Technical System Landscape ............................................................................ 37 3.5.3 Overview of Implementation Sequence .............................................................. 39

3.5.3.1 Configuration.................................................................................................. 39


November 2011 5

3.6 Standalone RFID-Enabled Inbound Processing ................................................ 40 3.6.1 Overview ........................................................................................................... 40

4 ENTERPRISE SERVICES IN SAP AII ......................................................................... 41

4.1 Technical Landscape .......................................................................................... 41

4.2 Installation Information ....................................................................................... 42

5 SAP COMPONENTS ................................................................................................... 44

5.1 Application Components .................................................................................... 44 5.1.1 OLTP System .................................................................................................... 44 5.1.2 SAP Auto-ID Infrastructure ................................................................................. 44 5.1.3 SAP Event Management (Optional) ................................................................... 44 5.1.4 SAP EM - Web Communication Layer (Optional) ............................................... 45

5.2 Technology Components ................................................................................... 46 5.2.1 SAP Basis / SAP NetWeaver Application Server ................................................ 46 5.2.2 SAP NetWeaver Process Integration (PI/XI) ....................................................... 46 5.2.3 SAP GUI ............................................................................................................ 47 5.2.4 SAP Basis Plug-Ins ............................................................................................ 47

6 REFERENCES: RELATED IMPLEMENTATION / CONFIGURATION GUIDES ........... 48


November 2011 6

1 Getting Started This documentation was developed to provide a central starting point for the technical implementation of SAP Solutions for RFID. It contains all activities for installation and configuration of SAP Solutions for RFID.

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.

To facilitate the implementation process, all information within this document is sorted according to this distinction. Upgrade information is available in separate upgrade documentation that is referenced within the Master Guide in the respective sections. This Master Guide provides the information about which components and which guides are required during this process. In this section, you get valuable information about using this document and related

information (documentation and SAP Notes) crucial for the installation and upgrade. In section SAP Solutions for RFID Overview [page 10], a short introduction is given to the

offerings as part of SAP Solutions for RFID. In section Business Processes and Scenarios in SAP Solutions for RFID, you get a short

description the business processes and scenarios that you can run using this solution. An overview of the processes including their technical components (mandatory and

optional components) and technical 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.

Depending on the specific processes to be implemented, many different installation and configuration guides are required during the implementation process. In section References: Related Implementation / Configuration Documentation [page 48], you can find an overview of all required documentation referenced in this Master Guide.


November 2011 7

1.1 History of Changes The Master Guide is regularly updated on SAP Service Marketplace at service.sap.com/instguides.

Make sure you have the latest version of the Master Guide by checking SAP Service Marketplace immediately before starting the installation.

The following table provides an overview of the most important changes that were made in the latest versions. Master Guide Version 1.0 First Customer Shipment 1.1 Path to XI content on the software download corner

updated. 1.2 Caution section regarding implementation of an SAP

object event repository added in chapter 2 SAP Solutions for RFID: Overview.

1.3 Chapter 1 Getting Started: Enhancement regarding supported SAP enhancement packages. Chapter 1.3 Important SAP Notes: Enhancement regarding SAP notes 1144099, 1612879, and 1641200.


November 2011 8

1.2 Related Information 1.2.1 Related Documentation The following list contains links to crucial information for implementing SAP Solutions for RFID.

Content Location on SAP Service Marketplace Latest versions of installation and upgrade guides

service.sap.com/instguides

General information about SAP Solutions for RFID

service.sap.com/rfid

SAP Business Maps - information about applications and business scenarios

service.sap.com/businessmaps

Sizing, calculation of hardware requirements - such as CPU, disk and memory resource - with the Quick Sizer tool

service.sap.com/quicksizer

Released platforms and technology-related topics such as maintenance strategies and language support

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

Network security service.sap.com/securityguide High Availability service.sap.com/ha Performance service.sap.com/performance Information about Support Package Stacks, latest software versions and patch level requirements

service.sap.com/sp-stacks

Information about Unicode technology service.sap.com/unicode@sap


November 2011 9

1.3 Important SAP Notes

Read the installation notes before beginning the installation. These notes contain the most recent information regarding the installation, as well as corrections to the installation documentation. Make sure that you have the most recent version of each note. You can find the SAP Notes in SAP Service Marketplace (service.sap.com/notes) or by using SAPNet - R/3 Front end.

List of Related SAP Notes

SAP Note Number

Title Description

1022171 Installation/Upgrade AUTO-ID 5.1 to SAP NetWeaver 7.0

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

1033669 Installing SCEMSRV 510 on SAP Netweaver 04s

Contains installation information for SAP Event Management 5.1

1025452 Master Guide SAP Solutions for RFID (Using SAP AII 5.1)

Contains: Any information relating to SAP Solutions for

RFID when the Master Guide was published (for example, latest component version requirements),

Corrections to this Master Guide. 1052281 Release Restrictions for

SAP AII 5.1

1058421 Corrections for the online documentation for SAP AII 2007

Contains information about changes to the SAP Library documentation for SAP AII 2007

1144099 Own activity methods when upgrading SAP Event Management

1612879 Upgrade to EhP3 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.

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=DISPL_TXT&_NNUM=1022171&









November 2011 10

2 SAP Solutions for RFID: Overview SAP Solutions for RFID enable the 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 RFID consist of the following offerings:

SAP Auto-ID Infrastructure (SAP AII) SAP AII 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 RFID-enable basic logistics processes, but also provides 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 AII 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.

If you implement an SAP object event repository, you have to install SAP Auto-ID Infrastructure and SAP Event Management on the same box. o 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.

SAP Event Management (SAP EM) SAP Event Management (SAP EM) allows you to track and query events across your supply chain and 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 EM is an optional component in SAP AII processes. If you install SAP object event repository, it is also possible to use the standalone functionality of SAP EM.

If you implement an SAP object event repository, you have to install SAP Auto-ID Infrastructure and SAP Event Management on the same box.

2.1 System Infrastructure Planning the Technical Infrastructure The design of the technical infrastructure for your system determines to a large degree the cost-effectiveness of the implementation. You have to determine the requirements that your system must fulfill. The following questions can help you to identify the requirements that influence the design of the technical infrastructure most:


November 2011 11

Purpose of the system Is it a non-production system such as a demo system or is it a development or test

system? (Development and test systems should also be considered as “production” systems in the sense that failure of a system could result in loss of money.).

Or is it a “true” production system in the sense that your actual business processes run in this system? (In the following, we will refer only to this kind of system as “production system”.)

Number of users How many users do you expect? Do you expect to be able to control the number of users (as in the case of a pure

intranet scenario), or do you have no control over the number of users (as in the case of an internet enabled “Outbound Order Fulfillment”)?

Scalability We recommend that you plan the system to be scalable right from the start. This way you can react to increasing demands more easily without major redesigns.

Availability What are the availability requirements of the system? It is desirable to have as little downtime as possible, but guaranteeing certain service levels (such as 99.9% uptime) is costly.

Security / Manageability How do you assess the security risks of the system? Security is a requirement that influences the infrastructure design quite heavily, because security considerations often demand exactly the opposite of what is required to retain the manageability of the system. For example, manageability would demand that you keep your software together as much as possible, while network security demands that you separate your software into network segments connected only over firewall systems. Some general design principles include keeping the system as simple as possible to ensure manageability and being flexible so that you can modify the system in response to new demands.

High Availability To make your system highly available, you need to set up at least two copies of each software component of the system, so that one component can take over when the other one fails. This does not necessarily mean that you have to double the hardware, but in practice this is usually the case. You have to take great care not to omit any part of the software or hardware (servers, network, firewalls) from the high availability concept. If the failure of one component causes the entire system to fail, that component is called a single point of failure (SPOF). Note that a high availability concept should also include planned downtimes for software and server maintenance, upgrades and the possibility of software stability problems. We do not discuss these topics in depth here, but you should keep in mind implementing concepts to keep these downtimes under control.


November 2011 12

3 Business Processes in SAP Solutions for RFID

This section contains information about the following business processes that you can run using SAP Solutions for RFID: RFID-Enabled Processes with Backend Integration RFID-Enabled Outbound Processing Without WM RFID-Enabled Inbound Processing and Receipt Confirmation Product Tracking and Authentication

RFID-Enabled Processes Without Backend Integration RFID-Enabled Returnable Transport Items (RTI) Standalone RFID-Enabled Outbound Processing Standalone RFID-Enabled Inbound Processing

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.

3.1 RFID-Enabled Outbound Processing Without WM

3.1.1 Overview 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 the ERP system

Commission RFID tags in SAP Auto-ID Infrastructure (SAP AII)

Pack and load in SAP AII

Post goods issue in the ERP system

Send ASNs together with EPCs

This process has two possible implementation variants: RFID-Enabled Flexible Delivery Processing

o In this implementation variant, SAP AII and the ERP system communicate via SAP NetWeaver usage type Process Integration (PI/XI). ERP is updated at loading.

RFID-Enabled Delivery Processing o This implementation variant requires an add-on (details below). ERP is

updated at packing and loading.


November 2011 13

3.1.2 Implementation Variant: RFID-Enabled Flexible Delivery Processing

This section contains information about the technical infrastructure of the RFID-Enabled Flexible Delivery Processing implementation variant, including its components and the communication between them.

3.1.2.1 Technical System Landscape General Considerations For the sake of simplicity and clearness the figure contains icons for whole SAP systems, not for single hosts. Remember that every 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.

XI Content Considerations XI Content is a special application content that must be installed on the XI host where each shared application needs its own content.

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 AII 5.1. The relationship is one to one with every Support Package.

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


November 2011 14

FlexibleDelivery Processing-

Backend Environment

SAP ECC 6.0

Database

SAP Basis Plug-In 2005.1 (optional)

ABAPSchema

FlexibleDelivery Processing- Core Environment

Database

JavaSchema

ABAPSchema

SAP NetWeaver 2004s Usage Type Process

Integration (PI/XI)

Integration Server

Integration Builder

XI Content AUTOID 5.1

XI ContentEA_APPL_600

Database

JavaSchema

ABAPSchema

SAP Net-Weaver2004s Usage

Type AS-ABAP


Type AS-Java

Add-On SAP Auto-ID

Infrastructure 5.1


Type AS-Java


Type AS-ABAP

Optional:SAP NetWeaver

Business Intelligence(BI) with BI Content

Add-On 2

Systems withUsage Types

Standalone Engines

LiveCache

Search and Classification

(TREX)

Pre-calculation Server (BI)

AS-Java

EP

BI-Java

AS-ABAP

BI

IGS comprised

Adobe document services

comprised

Clients/Tools

Web Browser SAP GUI Visual

Composer

BI Add-On, Business Explorer

comprised

The following components are mandatory or optional, as indicated below, for the technical implementation of the process.

Table of Software Components

Component Mandatory Optional

AUTO-ID 5.1 X

AUTO-ID UI 5.1 X

XI CONTENT AUTO-ID 5.1 X

XI CONTENT EA_APPL_600 X

BI CONT 7.03 X

SAP NETWEAVER 2004S Application Server ABAP

X As of SAP NetWeaver 2004s

SP11

SAP WEB AS 7.00 X

SAP Backend System X SAP R/3 4.6C or higher


November 2011 15

3.1.2.2 Overview of Implementation Sequence This section lists the sequence of steps (installation, technical configuration, application configuration) that are required to implement the business process.

3.1.2.3 Implementation Sequence No Action [Corresponding Documentation]

1 Installation/Integration of backend system (SAP R/3 4.6C or higher): [Installation Guide – SAP ECC 6.0 on <Operating System>: <Database>, available at: service.sap.com/instguides]

2 Installation/Integration of an SAP NetWeaver 2004s Application Server ABAP+Java SP011 or higher as prerequisite for the XI system. [SAP NetWeaver 2004s Installation Guide - SAP NetWeaver 2004s ABAP+Java on <OS>:<DB> available at: service.sap.com/installNW2004s]

3 Installation/Integration of SAP NetWeaver 2004s Process Integration (PI/XI) SP11 or higher [SAP NetWeaver 2004s Installation Guide - SAP NetWeaver 2004s ABAP+Java on <OS>:<DB> available at: service.sap.com/installNW2004s]

4 Installation of the current System Landscape Directory (SLD) content on the SLD host (located on the SAP Exchange Infrastructure host) as described in SAP Note 669669.

5 Configuration of SAP NetWeaver 2004s Process Integration (PI/XI) SP11 or higher Configure the system as described in the content below. System readiness can be checked as described in SAP Note 817920. [SAP Solution Manager Content Solutions Basic Configuration Configuration Structures SAP NetWeaver 2004s Usage Type PI]

6 Installation of XI Content AUTO-ID 5.1 on the XI host. a. Download this XI Content at: service.sap.com/swdc Download

Support Packages and Patches Entry by Application Group SAP Application Components SAP Auto-ID Infrastructure SAP AII 2007 Entry by Component XI Content XI CONTENT AUTO-ID 5.1

b. Import the downloaded XI Content files as described in SAP Note 836200.

7 Installation of XI Content EA_APPL_600 on the XI host. a. Download this XI Content at: service.sap.com/swdc Download

Support Packages and Patches Entry by Application Group SAP Application Components SAP ERP SAP ERP 2005 SAP NW - XI XI Content EA-APPL 600

c. Import the downloaded XI Content files as described in SAP Note 705541.

8 Installation/Integration of an SAP NetWeaver 2004s Application Server ABAP +Java SP11 or higher as prerequisite for the SAP Auto-ID Infrastructure 5.1 Add-On. [SAP NetWeaver 2004s Installation Guide - SAP NetWeaver ABAP+Java on <OS>:<DB> available at: service.sap.com/installNW2004s]

9 Installation of Add-On SAP Auto-ID Infrastructure 5.1 on the AS-ABAP and on the AS-Java systems. [See SAP Note 1022171 and the SAP Server Marketplace at service.sap.com/instguides -> SAP Components -> SAP Solutions for RFID -> Using SAP Auto-ID Infrastructure 2007]

10 Optional: Installation of SAP NetWeaver 2004s Business Intelligence (BI) SP07 or higher with BI Content Add-On 3. [SAP NetWeaver 2004s Installation Guide - SAP NetWeaver 2004s ABAP+Java on <OS>:<DB> available at: service.sap.com/installNW2004s]


November 2011 16

3.1.2.4 Configuration For configuration information, see the RFID-Enabled Flexible Delivery Processing: Configuration Guide. The documentation is available on SAP Service Marketplace at service.sap.com/rfid Detailed Information.

3.1.3 Implementation Variant: RFID-Enabled Delivery Processing

This section contains information about the technical infrastructure of the RFID-Enabled Delivery Processing implementation variant, including its components and the communication between them.

3.1.3.1 Technical System Landscape This section describes the technical system landscape of RFID-Enabled Delivery Processing depending on the different backend options, including its components and the communication between them. You have the following backend options:

Backend Options and related components for RFID-Enabled Delivery Processing (X = mandatory / (X) = optional)

Backend Options for RFID-Enabled Delivery Processing

Backend Option: SAP R/3 4.6C SAP R/3 4.6C with SAP BASIS SP 47/SAP ABA SP 47/SAP APPL SP 47

X

Add-On AUTOID_INT_200_46C X XI Content AUTOID_INT_200_46C X Backend Option: SAP R/3 Enterprise 4.7 Extension Set 200 SAP R/3 Enterprise 4.7 Extension Set 200 with SAP BASIS SP 37/SAP APPL SP 09 X

Add-On AUTOID_INT_200_470 X XI Content AUTOID_INT_200_470 X SAP Basis Plug-In 2005.1 (or higher) If SAP EM is used Backend Option: SAP ERP Central Component 5.0 SAP ECC 5.0 X XI Content EA_APPL_500 X SAP Basis Plug-In 2005.1 (or higher) If SAP EM is used Backend Option: SAP ERP Central Component 6.0 SAP ECC 6.0 XI Content EA_APPL_600 SAP Basis Plug-In 2005.1 (or higher) If SAP EM is used

General Considerations For the sake of simplicity and clearness the graphics contain icons for whole SAP systems, not for single hosts. Remember that every 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.


November 2011 17


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 the SAP Auto-ID Infrastructure and the corresponding XI Content for SAP AII 5.1. The relationship is one to one with every Support Package.

Integration with SAP Event Management When using SAP R/3 4.6C or SAP R/3 4.7, Extension Set 2.0, as backend component, the application interface to SAP Event Management needs to be configured in the project.




AUTO-ID 5.1 X

AUTO-ID UI 5.1 X


BI CONT 7.03 X



SP11

SAP WEB AS 7.00 X

SAP Backend System X See the following figures for

the different backend options.

SCEMSRV 5.1 (SAP Event Management)

X

SAP EM-WCL 5.1 X


November 2011 18

Technical Infrastructure of RFID-Enabled Delivery Processing (Using SAP ECC 5.0 or SAP ECC 6.0)

RFID-EnabledDelivery Processing

Backend Environment

SAP ECC 5.0 orSAP ECC 6.0

Database

Optional:Event Management

5.1

SAP EM 5.1

Database

SAP Event Management

SAP EM WCL5.1

DatabaseJava

Schema

SAP NetWeaver 2004s UsageType AS-Java


ABAPSchema

RFID-EnabledDelivery Processing - Core Environment

Database

JavaSchema

ABAPSchema

SAP NetWeaver 2004s Usage Type Process

Integration (PI/XI)

Integration Server

Integration Builder


XI ContentEA_APPL_500 or

EA_APPL_600

Database

JavaSchema

ABAPSchema


Type AS-ABAP


Type AS-Java

Add-On SAP Auto-ID

Infrastructure 5.1


Type AS-Java


Type AS-ABAP



Add-On 2


Standalone Engines

LiveCache


(TREX)


AS-Java

EP

BI-Java

AS-ABAP

BI

IGS comprised


comprised

Clients/Tools


Composer


comprised


November 2011 19

Technical Infrastructure of RFID-Enabled Delivery Processing (Using SAP R/3 Enterprise 4.7x200)

RFID-EnabledDelivery Processing

Backend Environment

SAP R/3 Enterprise 4.7x200

Database


ABAPSchema

SAP BASIS SP 37

SAP APPL SP 09

Add-On AUTOID_INT_200_4

70



Add-On 2


Standalone Engines

LiveCache


(TREX)


AS-Java

EP

BI-Java

AS-ABAP

BI

IGS compris

ed

Adobe document services comprise

d

Clients/Tools


Composer

BI Add-On,

Business

Explorer compris

ed

Database

JavaSchema

SAP Net-

Weaver 2004s

AS-Java

Add-On SAP Auto-ID Infrastructure

5.1

ABAPSchema

SAP Net-

Weaver 2004s

AS-ABAP

Database

JavaSchema

ABAPSchema

SAP NetWeaver Usage Type

ProcessIntegration (PI/XI)

Integration Server

Integration Builder


XI ContentAUTOID_INT_200_4

70

SAP Net-

Weaver 2004s

AS-Java

SAP Net-

Weaver 2004s

AS-ABAP


5.1

SAP EM5.1

Database

SAP Event

Management

SAP EM WCL 5.1

Database

JavaSchema



November 2011 20

Technical Infrastructure of RFID-Enabled Delivery Processing (Using SAP R/3 4.6C)

RFID-Enabled Delivery Processing

Backend Environment

SAP R/3 4.6C

DatabaseABAP

Schema

SAP APPL SP 47

Add-On AUTOID_INT_200_46C

SAP BASIS SP 47

SAP ABA SP 47

RFID-Enabled Delivery Processing Core Environment

Database

JavaSchema

ABAPSchema

Net-Weave

r2004s AS-

ABAP

Net-Weave

r2004s AS-Java

Add-On SAP Auto-ID

Infrastructure 5.1

Database

JavaSchema

ABAPSchema

SAP NetWeaver

2004s ProcessIntegration

(PI/XI)Integration

ServerIntegration

Builder

XI ContentAUTOID 2.1XI Content

AUTOID_INT_200_46C

Net-Weav

er2004s AS-Java

Net-Weav

er2004s AS-

ABAP



Add-On 2


Standalone Engines

LiveCache


(TREX)


AS-Java

EP

BI-Java

AS-ABAP

BI

IGS comprised


comprised

Clients/Tools


Composer

BI Add-On,

Business Explorer

comprised


5.1SAP EM 5.1

Database


SAP EM WCL5.1

DatabaseJava

Schema



November 2011 21

3.1.4 Overview of Implementation Sequence This section lists the sequence of steps (installation, technical configuration, application configuration) required to implement the business scenario. Depending on the backend you use different implementation sequences are necessary.

3.1.4.1 Backend Option SAP ECC 6.0: Implementation Sequence No Action [Corresponding Documentation]

1 Installation/Integration of SAP ECC 6.0: [Installation Guide – SAP ECC 6.0 on <Operating System>: <Database>, available at: service.sap.com/instguides]

2 Installation/Integration of an SAP NetWeaver 2004s Application Server ABAP+Java as prerequisite for the XI system. [SAP NetWeaver 2004s Installation Guide - SAP NetWeaver 2004s ABAP+Java on <OS>:<DB> available at: service.sap.com/installNW2004s]

3 Installation/Integration of SAP NetWeaver 2004s Process Integration (PI/XI) [SAP NetWeaver 2004s Installation Guide - SAP NetWeaver 2004s ABAP+Java on <OS>:<DB> available at: service.sap.com/installNW2004s]


5 Configuration of SAP NetWeaver 2004s Process Integration (PI/XI) Configure the system as described in the content below. System readiness can be checked as described in SAP Note 817920. [SAP Solution Manager Content Solutions Basic Configuration Configuration Structures SAP NetWeaver 2004s Usage Type PI]

6 Installation of XI Content AUTO-ID 5.1 on the XI host. a) Download this XI Content at: service.sap.com/swdc Download Support Packages and Patches Entry by Application Group SAP Application Components SAP Auto-ID Infrastructure SAP AII 2007 Entry by Component

XI Content XI CONTENT AUTO-ID 5.1 b) Import the downloaded XI Content files as described in SAP Note 836200.

7 Installation of XI Content EA_APPL_600 on the XI host. a) Download this XI Content at: service.sap.com/swdc Download Support Packages and Patches Entry by Application Group SAP Application Components SAP ERP SAP ERP 2005 SAP NW - XI XI Content EA-APPL 600 b) Import the downloaded XI Content files as described in SAP Note 705541.



10 Optional: Installation of SAP NetWeaver 2004s Business Intelligence (BI) with BI Content Add-On 2. [SAP NetWeaver 2004s Installation Guide - SAP NetWeaver 2004s ABAP+Java on <OS>:<DB> available at: service.sap.com/installNW2004s]


November 2011 22

11 Optional: Installation of SAP Event Management environment. See section Implementation Sequence: Optional SAP Event Management [on page 28]

3.1.4.2 Backend Option SAP ECC 5.0: Implementation Sequence No Action [Corresponding Documentation]

1 Installation/Integration of SAP ECC 5.0: [Installation Guide – SAP ERP Central Component 5.0 on <Operating System>: <Database>, available at: service.sap.com/instguides]

2 Installation/Integration of an SAP NetWeaver 2004s Application Server ABAP+Java as prerequisite for the XI system. [SAP NetWeaver 2004s Installation Guide - SAP NetWeaver 2004s ABAP+Java on <OS>:<DB> available at: service.sap.com/installNW2004s]



5 Configuration of SAP NetWeaver 2004s Process Integration (PI/XI) Configure the system as described in the guide below. System readiness can be checked as described in SAP Note 817920. [SAP Solution Manager Content Solutions Basic Configuration Configuration Structures SAP NetWeaver 2004s Usage Type PI]

6 Installation of XI Content AUTO-ID 5.1 on the XI host. a) Download this XI Content at: service.sap.com/swdc Download Support Packages and Patches Entry by Application Group SAP Application Components SAP Auto-ID Infrastructure SAP AII 2007 Entry by Component

XI Content XI CONTENT AUTO-ID 5.1 b) Import the downloaded XI Content files as described in SAP Note 836200.


8 Installation/Integration of an SAP NetWeaver 2004s Application Server ABAP+Java SP11 or higher as prerequisite for the SAP Auto-ID Infrastructure 5.1 Add-On. [SAP NetWeaver 2004s Installation Guide - SAP NetWeaver 2004s ABAP+Java on <OS>:<DB> available at: service.sap.com/installNW2004s]




November 2011 23



November 2011 24

3.1.4.3 Backend Option SAP R/3 Enterprise: Implementation Sequence

No Action [Corresponding Documentation]

1 Installation/Integration of SAP R/3 Enterprise 4.7x200: [Installation Guide - SAP R/3 Enterprise on <OS>:<DB> - Using SAP R/3 Enterprise Core 4.70, SAP R/3 Enterprise Extension Set 2.00- available at: service.sap.com/instguides]

2 Applying at least SAP BASIS SP 37 and SAP APPL SP 09 for the SAP R/3 Enterprise Server. The Support Packages are available at service.sap.com/swdc

3 Install Add-On AUTOID_INT_200_470 on the SAP R/3 Enterprise Server: a. Install Add-On according to SAP Note 728372. b. Apply SAP Note 689793.

4 Installation/Integration of an SAP NetWeaver 2004s Application Server ABAP+Java system as prerequisite for XI system. [SAP NetWeaver 2004s Installation Guide - SAP NetWeaver 2004s ABAP+Java on <OS>:<DB> available at: service.sap.com/installNW2004s]







9 Installation of XI Content AUTOID_INT_200_470 on the XI host. a. Download this XI Content at: service.sap.com/swdc Download

Support Packages and Patches Entry by Application Group SAP Application Components SAP Auto-ID Infrastructure SAP AII 2007 Entry by Component XI Content XI CONTENT AUTOID_INT 200_470


10 Installation/Integration of an SAP NetWeaver 2004s Application Server ABAP+Java system SP 11 or higher as prerequisite for the SAP Auto-ID Infrastructure 5.1 Add-On. [SAP NetWeaver 2004s Installation Guide - SAP NetWeaver 2004s ABAP+Java on <OS>:<DB> available at: service.sap.com/installNW2004s]



November 2011 25




November 2011 26

3.1.4.4 Backend Option SAP R/3 4.6C: Implementation Sequence No Action

[Corresponding Documentation]

1 Installation/Integration of SAP R/3 4.6C: [Installation Guide - SAP R/3 4.6C on <OS>:<DB> available at: service.sap.com/instguides]

2 Applying at least SAP BASIS SP 47 / SAP ABA SP 47 / SAP APPL SP 47 for the SAP R/3 Server. The Support Packages are available at service.sap.com/patches

3 Install Add-On AUTOID_INT_200_46C on the SAP R/3 Enterprise Server: a. Install Add-On according to SAP Note 725064 b. Apply SAP Note 689793

4 Installation/Integration of an SAP NetWeaver 2004s Application Server ABAP+Java system as prerequisite for XI system. [SAP NetWeaver 2004s Installation Guide - SAP NetWeaver 2004s ABAP+Java on <OS>:<DB> available at: service.sap.com/installNW2004s]






a. Import the downloaded XI Content files as described in SAP Note 836200.

9 Installation of XI Content AUTOID_INT_200_46C on the XI host. a. Download this XI Content at: service.sap.com/swdc Download

Support Packages and Patches Entry by Application Group SAP Application Components SAP Auto-ID Infrastructure SAP AII 2007 Entry by Component XI Content XI CONTENT AUTOID_INT 200_46C


10 Installation/Integration of an SAP NetWeaver 2004s Application Server ABAP+Java system SP 11 or higher as prerequisite for the SAP Auto-ID Infrastructure 5.1 Add-On. [SAP NetWeaver 2004s Installation Guide - SAP NetWeaver 2004s ABAP+Java on <OS>:<DB> available at: service.sap.com/installNW2004s]



November 2011 27



November 2011 28

3.1.4.5 Implementation Sequence: Optional SAP Event Management (SAP EM)

No Action


1 Installation of SAP Basis Plug-In 2006 SP01 (or higher) on the Backend: See SAP Note 1007796 (Installation / Upgrade of Basis Plug in 2006.1) and SAP Service Marketplace at: service.sap.com/r3-plug-in

2 Installation of SAP Event Management 5.1 [SAP Note 1033669]

4 Installation of SAP EM - Web Communication Layer 5.1 For more information, see the SAP Service Marketplace under service.sap.com/instguides -> SAP Components -> SAP Solutions for RFID -> Using SAP Auto-ID Infrastructure 2007.

When using SAP R/3 4.6C or SAP R/3 4.7, Extension Set 2.0, as backend component, the application interface to SAP Event Management needs to be configured in the project.

3.1.5 Configuration For configuration information, see the RFID-Enabled Delivery Processing: Configuration Guide. The document is available on SAP Service Marketplace at service.sap.com/rfid

Detailed Information.


November 2011 29

3.2 RFID-Enabled Inbound Processing and Receipt Confirmation

3.2.1 Overview 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 the ERP system

Unload inbound deliveries in SAP AII

Confirm the inbound delivery in the ERP system

Post goods receipt in the ERP system

This process has two possible implementation variants: RFID-Enabled Flexible Delivery Processing

o In this implementation variant SAP AII and the ERP system communicate via SAP NetWeaver usage type Process Integration (PI/XI). ERP is updated at loading. For more information about this implementation variant, see RFID-Enabled Flexible Delivery Processing.

RFID-Enabled Delivery Processing o This implementation variant requires an add-on (details below). ERP is

updated at packing and loading. For more information about this implementation variant, see RFID-Enabled Delivery Processing.


November 2011 30

3.3 Product Tracking and Authentication 3.3.1 Overview Product Tracking and Authentication is a business process that uses SAP object event repository to track product flow and trace business events across your enterprise and your extended supply chain network, and thereby to ensure the safe production and secure distribution of your product by creating visibility and traceability. It comprises business process variants:

Product tracking and authentication o Product tracking by delivery o Product tracking by EPC o Product authentication

3.3.2 Technical System Landscape General Considerations For the sake of simplicity and clearness the graphics contain icons for whole SAP systems, not for single hosts. Remember that every 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.


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 the SAP Auto-ID Infrastructure and the corresponding XI Content for SAP AII 5.1. The relationship is one to one with every Support Package.

The following figure shows an example of the technical infrastructure of Product Tracking and Authentication, including its components and the communication between them. Example: Technical Infrastructure of Product Tracking and Authentication


November 2011 31

Backend Env.: Customer

Backend Env.: Supplier

SAP ECC 6.0(Customer)

SAP AII 5.1(Customer)

Core Environment (Supplier)

SAP N

etWeaver 2004s Process Integration (PI/X

I)

SAP ECC 6.0(Supplier)

SAP AII 5.1(Supplier)

Database

JavaSchema

ABAPSchema

SAP Object Event Repository

SAP Net-Weaver2004s AS- ABAP

SAP Net-Weaver2004s AS- Java

SAP EM WCL 5.1

SAP EM

SAP AII 5.1

SAP Basis Plug-In 2006




X

SAP EM-WCL 5.1 X

XI CONTENT SCEMSRV 5.1 X

AUTO-ID 5.1 X We recommend that you install one (central) instance of AUTO-ID 5.1

together with SCEMSRV 5.1 to form the SAP object event repository. You

may install one or more additional (local) instances of AUTO-ID 5.1.

AUTO-ID UI 5.1 X



X As of SAP NetWeaver 2004s SP11

SAP WEB AS 7.00 X

SAP Backend System X SAP ECC 6.0


November 2011 32

3.3.3 Overview of Implementation Sequence This section lists the sequence of steps (installation, technical configuration, application configuration) that are required to implement the Product Tracking and Authentication business process. No Action [Corresponding Documentation]

Installation of SAP Object Event Repository (Core Environment) 1 Installation/Integration of an SAP NetWeaver 2004s Application Server ABAP

+Java SP11 or higher as prerequisite for the SAP Auto-ID Infrastructure 5.1 Add-On. [SAP NetWeaver 2004s Installation Guide - SAP NetWeaver ABAP+Java on <OS>:<DB> available at: service.sap.com/installNW2004s]




5 Installation of XI Content SAP EM 5.1 on the XI host. Download this XI Content at: service.sap.com/swdc Download Support Packages and Patches Entry by Application Group SAP Application Components SAP Auto-ID Infrastructure SAP AII 2007 Entry by Component

XI Content XI CONTENT SCEMSRV 5.1 Import the downloaded XI Content files as described in SAP Note 836200.

6 Installation of XI Content AUTO-ID 5.1 on the XI host. Download this XI Content at: service.sap.com/swdc Download Support Packages and Patches Entry by Application Group SAP Application Components SAP Auto-ID Infrastructure SAP AII 2007 Entry by Component

XI Content XI CONTENT AUTO-ID 5.1 Import the downloaded XI Content files as described in SAP Note 836200.



9 Installation of SAP Basis Plug-In 2006 SP01 (or higher) on the Backend: See SAP Note 1007796 (Installation / Upgrade of Basis Plug in 2006.1) and SAP Service Marketplace at: service.sap.com/r3-plug-in

10 Installation of SAP EM 5.1 as of SP01 [see SAP Note 1033669]


November 2011 33

11 Installation of SAP EM - Web Communication Layer 5.1 For more information, see the SAP Service Marketplace under service.sap.com/instguides -> SAP Components -> SAP Solutions for RFID -> Using SAP Auto-ID Infrastructure 2007.

Installation of Backend Envionment (Supplier or Customer) 1 Installation/Integration of SAP ECC 6.0:

[Installation Guide – SAP ECC 6.0 on <Operating System>: <Database>, available at: service.sap.com/instguides]




November 2011 34

3.4 RFID-Enabled RTI Processing 3.4.1 Overview 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. SAP supports 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 Service Marketplace at service.sap.com/rfid Detailed Information.

3.4.2 Technical System Landscape The following figure shows the technical infrastructure of RFID-Enabled RTI Processing, including its components and the communication between them.



November 2011 35

Technical Infrastructure

Optional:SAP Event

Management5.1

SAP EM 5.1

Database


SAP WCL 5.1

Database

JavaSchema


RFID-Enabled RTI ProcessingCore Environment

Database

JavaSchema

ABAPSchema


Type AS-ABAP


Type AS-Java

Add-On SAP Auto-ID

Infrastructure 5.1



Add-On 2


Standalone Engines

LiveCache


(TREX)


AS-Java

EP

BI-Java

AS-ABAP

BI

IGS comprised


comprised

Clients/Tools


Composer


comprised




AUTO-ID 5.1 X

AUTO-ID UI 5.1 X

BI CONT 7.03 X



SP11

SAP WEB AS 7.00 X


X

SAP EM-WCL 5.1 X


November 2011 36

3.4.3 Overview of Implementation Sequence This section lists the sequence of steps (installation, technical configuration, application configuration) required to implement the business processes. No Action


1 Installation/Integration of an SAP NetWeaver 2004s Application Server ABAP+Java system SP11 or higher as prerequisite for the SAP Auto-ID Infrastructure 5.1 Add-On. [SAP NetWeaver 2004s Installation Guide - SAP NetWeaver 2004s ABAP+Java on <OS>:<DB> available at: service.sap.com/installNW2004s]


3 Optional: Installation of SAP NetWeaver 2004s Business Intelligence (BI) with BI Content Add-On 2 [SAP NetWeaver 2004s Installation Guide - SAP NetWeaver 2004s ABAP+Java on <OS>:<DB> available at: service.sap.com/installNW2004s]

4 Optional: Installation of SAP Event Management environment (for RFID-Enabled RTI Processing). See section Implementation Sequence: Optional SAP Event Management [on page 28]

3.4.3.1 Configuration For configuration information, see the RFID-Enabled RTI Processing: Configuration Guide. The documentation is available on SAP Service Marketplace at service.sap.com/rfid

Detailed Information.


November 2011 37

3.5 Standalone RFID-Enabled Outbound Processing 3.5.1 Overview The stand-alone deployment option of SAP AII 5.1 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 stand-alone SAP AII 5.1 provides users with the ability to execute the process sequence: tag commissioning (to write and validate written tags), packing, and loading.

3.5.2 Technical System Landscape The following figure shows the technical infrastructure of Standalone RFID-Enabled Outbound Processing, including its components and the communication between them.



November 2011 38

Technical Infrastructure

Standalone RFID-EnabledOutbound Processing

Core Environment

Database

JavaSchema

ABAPSchema


Type AS-ABAP


Type AS-Java

Add-On SAP Auto-ID

Infrastructure 5.1



Add-On 2


Standalone Engines

LiveCache


(TREX)


AS-Java

EP

BI-Java

AS-ABAP

BI

IGS comprised


comprised

Clients/Tools


Composer


comprised




AUTO-ID 5.1 X

AUTO-ID UI 5.1 X

BI CONT 7.03 X



SP11

SAP WEB AS 7.00 X


November 2011 39

3.5.3 Overview of Implementation Sequence This section lists the sequence of steps (installation, technical configuration, application configuration) required to implement the business processes. No Action


1 Installation/Integration of an SAP NetWeaver 2004s Application Server ABAP+Java system SP11 or higher as prerequisite for the SAP Auto-ID Infrastructure 5.1 Add-On. [SAP NetWeaver 2004s Installation Guide - SAP NetWeaver 2004s ABAP+Java on <OS>:<DB> available at: service.sap.com/installNW2004s]


3 Optional: Installation of SAP NetWeaver 2004s Business Intelligence (BI) with BI Content Add-On 2 [SAP NetWeaver 2004s Installation Guide - SAP NetWeaver 2004s ABAP+Java on <OS>:<DB> available at: service.sap.com/installNW2004s]

3.5.3.1 Configuration For example information about configuring standalone RFID-enabled processes, see the RFID-Enabled Slap&Ship Outbound Processing: Configuration Guide. The documentation is available on SAP Service Marketplace at service.sap.com/rfid Detailed Information.


November 2011 40

3.6 Standalone RFID-Enabled Inbound Processing 3.6.1 Overview The stand-alone deployment option of SAP AII 5.1 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 stand-alone SAP AII 5.1 provides users with the ability to perform inbound delivery processing and unloading. For information about the technical system landscape, the components required for this process and their installation, see Standalone RFID-Enabled Outbound Processing.


November 2011 41

4 Enterprise Services in SAP AII You can use enterprise services in SAP AII to service-enable automated logistic processes by using labels that can be automatically identified by IDs. The enterprise services are grouped by the following business objects, which manage the lifecycle of the label, the RFID device that is used to read the label, and observations recorded by the RFID device:

AutomaticIdentificationLabel The enterprise services (operations) belonging to this business object are used to manage tag IDs.

AutomaticIdentificationLabelDevice The enterprise services (operations) belonging to this business object are used to create and modify master data for devices.

AutomaticIdentificationLabelDeviceObservation The enterprise services (operations) belonging to this business object are used to create and search for observations, that is events that have occurred to objects identified by an automatically identifiable label.

4.1 Technical Landscape As a prerequisite for running enterprise services for SAP AII, you must install the same system landscapes as described in the previous chapters of this master guide. The following diagram provides an overview of a possible system landscape for SAP AII enterprise services. Example: Possible System Landscape for SAP AII Enterprise Services


November 2011 42

SAP AII Enterprise Services

Database

JavaSchema

ABAPSchema

SAP Net-Weaver 2004s Usage Type

AS-ABAP

SAP Net-Weaver 2004s Usage Type

AS-Java

Add-On SAP Auto-ID Infrastructure 5.1

SAP NetWeaver usage type Process Integration

(PI/XI)

The following software components are either mandatory or optional, as indicated below, for the technical implementation of enterprise services for SAP AII 5.1: Component Mandatory Optional SAP AII 5.1 X SAP NetWeaver 2004s usage type XI X

4.2 Installation Information No. Action [Corresponding Documentation]

1 Installation/Integration of an SAP NetWeaver 2004s Application Server ABAP+Java system as prerequisite for the SAP Auto-ID Infrastructure 5.1 Add-On. [SAP NetWeaver 2004s Installation Guide - SAP NetWeaver 2004s ABAP+Java on <OS>:<DB> available at: service.sap.com/installNW2004s]


3 Installation of XI Content AUTO-ID 5.1 on the XI host. Download this XI Content at: service.sap.com/swdc Download Support Packages and Patches Entry by Application Group SAP Application Components

SAP Auto-ID Infrastructure SAP AII 2007 Entry by Component XI Content


November 2011 43

XI CONTENT AUTO-ID 5.1 Import the downloaded XI Content files as described in SAP Note 836200.


November 2011 44

5 SAP Components 5.1 Application Components

5.1.1 OLTP System 5.1.1.1.1.1 Definition OnLine Transaction Processing system (for example, SAP R/3 system, SAP R/3 Enterprise, SAP ECC) that is used in the SAP Solutions for RFID environment as backend system.

5.1.1.1.1.2 Use Data is exchanged between the SAP Solutions for RFID environment and a connected OLTP system.

5.1.2 SAP Auto-ID Infrastructure This component, optionally together with adapters for SAP backend systems and/or SAP Event Management, supports the integration of RFID interrogators and other hardware for automatic identification with backend systems. It could be described as a kind of 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 XI - from ERP systems 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, 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 XI 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.

5.1.3 SAP Event Management (Optional) SAP Event Management offers the possibility 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. Use SAP Event Management (SAP EM) 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 to control events SAP Event Management checks the Supply Chain Event Management-relevant

objects as soon as they are saved in the application system.


November 2011 45

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)

5.1.4 SAP EM - Web Communication Layer (Optional) Java-based SAP front end which offers information access and full supply chain visibility for SAP EM via the Internet.


November 2011 46

5.2 Technology Components 5.2.1 SAP Basis / SAP NetWeaver Application Server Definition SAP NetWeaver Application Server (SAP NetWeaver AS) provides the technological foundation for all other mySAP.com components. In a sense, SAP NetWeaver AS is the "operating system" of mySAP.com. Until SAP R/3 4.6D, SAP NetWeaver AS was named SAP Basis. 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 mySAP.com, SAP now offers multiple components that build on SAP NetWeaver AS. As a result, there is no tight naming relation between SAP NetWeaver AS and SAP R/3 any more. An SAP System consists of a database server, (optional) additional application servers, and a number of front-end computers. 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.

Use 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 vice versa. In addition, the Internet Communication Framework (ICF) of SAP NetWeaver AS enables ABAP-written programs 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.

5.2.2 SAP NetWeaver Process Integration (PI/XI) Based on a native Web infrastructure that leverages open standards, SAP NetWeaver Process Integration (SAP NetWeaver XI) makes it possible to manage the broad diversity of highly heterogeneous components from a multitude of vendors and running in various technology environments. The integration capabilities capture shared business semantics and act as a mediator between the services and their technical realizations. It includes technical functions, such as Web service discovery, queuing, mapping, and routing. 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 instant plug-in of new components once per component. This provides the future flexibility needed in today’s fast-changing business world, and it reduces integration costs compared to the direct connection approach.


November 2011 47

5.2.3 SAP GUI Generally, the latest release of the SAP GUI software can be used with all previous SAP R/3 releases (such as 4.0B). As a result, older SAP systems can also benefit from the features that are only available in the newer SAP GUI releases - for example, the look and feel of EnjoySAP and support for Windows 2000. The benefit of this downward compatibility is that you can simply install a new SAP GUI release instead of patching an old one. The SAP GUI maintenance strategy takes advantage of this feature. In many problem situations, the recommendation is to install a new SAP GUI release, because patches cannot always be provided for older SAP GUI releases even if SAP still maintains the SAP R/3 System with the same release number.

5.2.4 SAP Basis Plug-Ins 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 mySAP SCM or mySAP CRM together with certain SAP industry-specific application components. All SAP industry-specific application components based on SAP R/3 4.6B or higher SAP R/3 releases require an SAP Basis Plug-In. SAP Basis Plug-Ins are shipped with SAP application components (mySAP SCM, SAP BW, mySAP SRM EB, mySAP CRM, and SAP SEM) and with industry-specific SAP application components based on SAP R/3 4.6B or higher SAP R/3 releases. You can order the most recent SAP Basis Plug-In releases free of charge or download them from the SAP Service Marketplace. 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 for download, see SAP Service Marketplace at the Internet address service.sap.com/r3-plug-in.


November 2011 48

6 References: Related Implementation / Configuration Guides

List of implementation and configuration documentation for SAP Solutions for RFID Title Purpose Where to find

Installation Specific –Core Installation SAP NetWeaver 2004s Installation Guide - SAP NetWeaver 2004s ABAP+Java on <OS>:<DB>

Installation of an SAP NetWeaver Application Server ABAP+Java system as a prerequisite for SAP Auto-ID Infrastructure 5.1

service.sap.com/ instguides

SAP NetWeaver 2004s Installation Guide - SAP NetWeaver 2004s ABAP+Java on <OS>:<DB>

Installation of SAP XI 7.0 as dedicated server

SAP Note 1022171: Installation SAP Auto-ID Infrastructure 5.1

Installation of SAP Auto-ID Infrastructure 5.1

service.sap.com/notes

SAP Note 836200: SAP NetWeaver 2004s: Import of Process Integration Content

Applying XI Content AUTO-ID 5.1 on the SAP XI server

service.sap.com/notes

Installation Specific – Backend (OLTP) Installation Backend (OLTP) Option SAP ECC 6.0 Installation Guide - SAP ERP Central Component 6.0 on <Operating System>: <Database> Installing the OLTP SAP

ECC 6.0 server


mySAP Business Suite Solutions mySAP ERP

Backend (OLTP) Option SAP ECC 5.0 Installation Guide - SAP ERP Central Component 5.0 on <Operating System>: <Database> Installing the OLTP SAP

ECC 5.0 server


mySAP Business Suite Solutions mySAP ERP

Backend (OLTP) Option SAP R/3 Enterprise 4.70x200 Installation Guide - SAP R/3 Enterprise on <Operating System>: <Database>- Using SAP R/3 Enterprise Core 4.70, SAP R/3 Enterprise Extension Set <Release>

Alternative OLTP server installation


SAP Components

SAP Note 728372: AUTOID_INT 200_470 installation

Applying Add-On AUTOID_INT_200_470 on SAP R/3 4.70x200 service.sap.com/

notes SAP Note 836200: SAP NetWeaver 2004s: Import of Process Integration Content



November 2011 49

Backend (OLTP) Option SAP R/3 4.6C R/3 Installation on <Operating System>: <Database>- Release 4.6C

Alternative OLTP server installation


SAP Note 728372: AUTOID_INT 200_470 installation

Applying Add-On AUTOID_INT_200_46C on SAP R/3 4.6C service.sap.com/

notes SAP Note 836200: SAP NetWeaver 2004s: Import of Process Integration Content


Installation Specific – SAP NetWeaver 2004s Usage Type Business Intelligence (Optional) SAP NetWeaver 2004s Installation Guide - SAP NetWeaver 2004s ABAP+Java on <OS>:<DB>

Installing SAP NetWeaver 2004s Usage Type Business Intelligence


Installation Specific – SAP Event Management (Optional) SAP Note 1033669: Installation SAP EM 5.1 service.sap.com/

notes Installation Guide – SAP EM WCL 5.1

Installing the SAP EM WCL on a SAP NetWeaver AS-Java


SAP Note 836200: SAP NetWeaver 2004s: Import of Process Integration Content

XI Content SAP EM 5.1 on the SAP XI server service.sap.com/

notes SAP Note 1007796: Installation / Upgrade of Basis Plug in 2006.1

Applying plug-in on the OLTP backend system.

Configuration Specific RFID-Enabled Flexible Delivery Processing: Configuration Guide

Detailed configuration information

service.sap.com/rfid Detailed Information

RFID-Enabled Outbound Processing: Configuration Guide



RFID-Enabled Delivery Processing: Configuration Guide



RFID-Enabled Slap&Ship Outbound Processing: Configuration Guide



RFID-Enabled RTI Processing: Configuration Guide



SAP NetWeaver 2004s Process Integration (PI/XI)


SAP Solution Manager

Solutions Basic Configuration Configuration Structures SAP NetWeaver 2004s Usage Type PI


November 2011 50

System Landscape Directory (SLD) Detailed configuration information

service.sap.com/installNW2004s

Post-Installation Guide – System Landscape Directory SAP NetWeaver 2004s

SAP Solutions for RFID 2007 powered by SAP NetWeaver™

Documents

Transcript of SAP Solutions for RFID 2007 powered by SAP NetWeaver™