Professional Documents
Culture Documents
Target Audience
QÍ”ÝBe Technical Consultants
QÍ”ÝBe System Administrators
PUBLIC
QÍ”9gªiŒ˘ÿðÛ©Kšä^iQ(ÿõØrù ù%ÎãnÒ:Ãz€ÒjF„%@—Hû|˛ÍqMöùà-EJg•øN`r§öÿ‹
QÍ”0g¤i†˘ïïÛ¥K™äFiQ(çõÈmù˘ù)Îþnƒ:Yz5ÒkF™%M—]ÛZ˛Ú{
SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
www.sap.com
Disclaimer
Some 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.
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 `zG:q˘ Words or characters quoted from the screen. These include field labels, screen titles,
pushbutton labels, menu names, and menu options.
`zG:q˘ Cross-references to other documentation or published works
Example `zG:q˘ Output on the screen following a user action, for example, messages
`zG:q˘ Source code or syntax quoted directly from a program
`zG:q˘ 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
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 operation
Chapter 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.
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
1 Getting Started
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:
$�9gA Installation guides for single software units
$�9gA SAP Notes
$�9gA Configuration documentation
$�9gA 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:
$�9gA Getting Started
Contains valuable information about using this document and related information
(documentation and SAP Notes) crucial to the installation and upgrade.
$�9gA 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.
$�9g. 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.
$�9g. Software Component Matrix
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.
˛Ôß(™§ 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.
The following table lists further useful links on SAP Service Marketplace:
List of Further Useful Links
Content Location on SAP Service Marketplace
Information about creating error messages http://service.sap.com/message
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 http://service.sap.com/instguides SAP Business Suite Applications
(including SAP enhancement SAP SCM SAP Event Management
package 1)
SAP Event Management 7.0 http://service.sap.com/instguides SAP Business Suite Applications
SAP SCM SAP Event Management
SAP ERP 6.0 http://service.sap.com/erp-inst SAP ERP 6.0
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.
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
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.
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.
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
`³˘%Â3 RFID-Enabled Outbound Processing Without WM
`³˘%Â3 RFID-Enabled Inbound Processing and Receipt Confirmation
`³˘%Â3 Secure Tracking and Tracing
`³˘%Â3 IUID-Enabled Inbound/Outbound Processing
`³˘%Â3 RFID-Enabled LES with Centralized Warehouse Management System
`³˘%Â3 RFID-Enabled Kanban Processing
`³˘%Â\ RFID-Enabled Processes Without Back-end Integration
`³˘%Â3 RFID-Enabled Returnable Transport Items (RTI)
`³˘%Â3 Standalone RFID-Enabled Outbound Processing
`³˘%Â3 Standalone RFID-Enabled Inbound Processing
`³˘%Â3 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.
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.
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).
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].
information about items as they move through your supply chain and to automate your business
processes.
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.
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.
Implementation
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:
±¼.
ył Menu entries
±¼.
ył New screens
±¼.
ył New fields on the application user interfaces
±¼.
ył IMG activities required for the implementation
±¼.
ył New table entries in Customizing tables and system tables
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
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
fiðQDófi Install enhancement packages and Support Packages in one single step (this includes the
preconditioned Support Packages).
fiðQDófi SAP enhancement packages have Support Packages of their own that are equivalent to the Support
Package versions of the underlying SAP system.
fiðQDófi SAP enhancement packages have the same maintenance period as the underlying core application.
fiðQDófi The installation of an enhancement package is irreversible.
fiðQDófi 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.
fiðQDófi 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.
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
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
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
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.
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 .
Software Component
SAP Solutions for Auto-ID X = mandatory
and Item Serialization (X) = optional
Business Process – = not required
SAP Auto-ID SAP NetWeaver SAP NetWeaver SAP Event
Business Process Infrastructure Usage Type BI Usage Type PI Management SAP ERP
Standalone RFID- X (X) - - -
Enabled Inbound
Processing
Standalone IUID X (X) - - -
Processing
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.
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.
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.
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.
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.
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.
If you install SAP Auto-ID Infrastructure standalone, you have the option of installing the following:
Säþ(o SAP NetWeaver Business Intelligence
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:
Säþ(o 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.
Säþ(o 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
information about the required releases and support packages, see the respective sections about the
SAP Auto-ID Infrastructure business processes.
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.0
Step Action Remarks / Subsequent Steps
1 Installation of SAP enhancement package 5 For more information, see SAP Service
for SAP ERP 6.0 Marketplace at http://service.sap.com/
instguides SAP Business Suite Applications
SAP ERP SAP ERP 6.0 Installation
2 Installation of SAP Auto-ID Infrastructure 7.1 For more information, see SAP Note 1320442
SAP Auto-ID Infrastructure as Add-On for SAP Enhancement Package 5 for SAP ERP 6.0
Step Action Remarks / Subsequent Steps
Optional:
3 Installation/integration of SAP enhancement Hı±P¬> For more information about
package 2 for SAP NetWeaver Process installation or integration of an SAP
Integration 7.0 enhancement package on an existing
or SAP NetWeaver 7.0 or 7.1 system, see:
Installation/integration of SAP NetWeaver Hı±P¬Q Installation Guide – SAP Enhancement
Process Integration 7.0 including SAP Package 2 for SAP NetWeaver 7.0 on
enhancement package 2. 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
Hı±P¬Q 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
Hı±P¬> For more information about
installation or integration of an SAP
NetWeaver system including the SAP
enhancement package, see:
Hı±P¬Q 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
Hı±P¬Q 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 Hı±P¬> Download the XI content on SAP
the XI host Service Marketplace at http://
service.sap.com/swdc Download
Support Packages and Patches Entry by
Application Group SAP Application
SAP Auto-ID Infrastructure as Add-On for SAP Enhancement Package 5 for SAP ERP 6.0
Step Action Remarks / Subsequent Steps
Components SAP Auto-ID Infrastructure
SAP AII 7.1 Entry by Component XI
Content XI CONTENT AUTO-ID
7.1 .
©ñn†2Ç 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
Boxes
Step Action Remarks / Subsequent Steps
1 Installation/integration of SAP enhancement For more information, see:
package 2 for SAP NetWeaver 7.0 SP2 and ©ñn†2Ç Installation Guide – SAP Enhancement Package
higher as prerequisite for the SAP Auto-ID 2 for SAP NetWeaver 7.0 on SAP Service
Infrastructure 7.1 Add-On Marketplace at http://
or service.sap.com/installnw70, which
installation/integration of SAP NetWeaver 7.0 describes the installation of an SAP
SP2 and higher including SAP enhancement enhancement package on an existing
package 2 for SAP NetWeaver 7.0 as SAP NetWeaver 7.0 system.
prerequisite for the SAP Auto-ID ©ñn†2Ç Installation Guide – SAP NetWeaver 7.0
Infrastructure 7.1 Add-On 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 For more information, see SAP Note
Infrastructure 7.1 on the SAP NetWeaver 1320442 and on SAP Service Marketplace at
Application Server ABAP 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 .
3 Installation/Integration of back-end system ©ñn†2Ç For more information about the
backend system per business process,
see the respective business process
description in this guide.
©ñn†2Ç 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.
©ñn†2Ç 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
©ñn†2Ç For more information about SAP R/3
Enterprise 4.7x200, see Installation Guide
– SAP R/3 Enterprise on <OS>:<DB> –
Installation of SAP Auto-ID Infrastructure, SAP ERP, and SAP Enhancement Package 5 for SAP ERP on Separate
Boxes
Step Action Remarks / Subsequent Steps
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
“Ä@dþÌ 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 For more information, see SAP Service
enhancement package 5 for SAP ERP 6.0 Marketplace at http://service.sap.com/
instguides SAP Business Suite Applications
SAP ERP SAP ERP 6.0 Installation
5 If you use SAP R/3 Enterprise 4.7x200, apply at The Support Packages are available on SAP
least SAP BASIS SP 37 and SAP APPL Sp 09 for Service Marketplace at http://
the SAP R/3 Enterprise server. service.sap.com/swdc.
6 If you use SAP R/3 4.6C, apply at least SAP The Support Packages are available on SAP
BASIS SP 47, SAP ABA SP 47, and SAP APPL Service Marketplace at http://
SP 47 for the SAP R/3 server. service.sap.com/patches.
Installation of SAP Auto-ID Infrastructure, SAP ERP, and SAP Enhancement Package 5 for SAP ERP on Separate
Boxes
Step Action Remarks / Subsequent Steps
Marketplace at http://
service.sap.com/installNnw70,
which describes the installation of
an SAP NetWeaver Process
Integration 7.02 system
˝»FÊÍd 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 For more information, see SAP Note
Directory (SLD) content on the SLD host 669669.
(located on the SAP Exchange
Infrastructure)
9 Configuration of SAP enhancement package Configure the system as described in the
2 for SAP NetWeaver Process Integration 7.0. content below. You can check system
readiness as described in SAP Note 817920
For more information, see SAP Solution
Manager content Solutions/Applications
Basic Configuration Configuration Structures
SAP NetWeaver 7.0 (2004s) Usage Type
PI .
10 Installation of XI CONTENT AUTO-ID 7.1 on the 1. Download the XI content on SAP
XI host 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 If you use SAP enhancement package 5 for
system on the XI host SAP ERP 6.0, do the following:
1. Download the XI content XI CONTENT
EA-APPL_605 on SAP Service
Marketplace at http://
service.sap.com/swdc Download
Support Packages and Patches Entry by
Application Group SAP Application
Components SAP ERP
ENHANCEMENT PACKAGE SAP
Installation of SAP Auto-ID Infrastructure, SAP ERP, and SAP Enhancement Package 5 for SAP ERP on Separate
Boxes
Step Action Remarks / Subsequent Steps
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://
service.sap.com/swdc Download
Support Packages and Patches Entry by
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://
service.sap.com/swdc Download
Support Packages and Patches Entry by
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
Optional: Installation of SAP NetWeaver System with Usage Type Process Integration
Step Action Remarks / Subsequent Steps
1 Installation/integration of SAP enhancement For more information, see http://
package 2 for SAP NetWeaver Process service.sap.com/installnw70 or http://
Integration 7.0 or of SAP enhancement service.sap.com/installnwpi71.
package 1 for SAP NetWeaver Process
Integration 7.1
or
Installation/integration of SAP NetWeaver
Process Integration 7.0 including SAP
enhancement package 2 or of SAP NetWeaver
Optional: Installation of SAP NetWeaver System with Usage Type Process Integration
Step Action Remarks / Subsequent Steps
Process Integration 7.1 including SAP
enhancement package 1
2 Installation of SAP NetWeaver 7.0 BI Content For more information, see SAP Note
Add-On 5 (SAP NW 7.0 BI CONT ADDON 7.05) 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.05
For more information, see Installation Guide –
SAP NetWeaver 7.0 SR<X> on <OS>:<DB>
on SAP Service Marketplace at http://
service.sap.com/installnw70.
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.
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.
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.
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.
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.
If you install SAP Auto-ID Infrastructure as an add-on for SAP ERP, you have the option of installing
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:
GËÊey 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.
GËÊey 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.
The graphic shows an example of the technical infrastructure for SAP Auto-ID Infrastructure installed
on a separate box.
r²3¬;!Tö˘6−ç öª“ßïˇ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 X
r²3J˚Û AUTO-ID 7.1
r²3J˚Û SAP_BS_FOUNDATION_702
SAP EHP 5 for SAP ERP 6.0 X
SAP ERP 6.0 X
SAP NetWeaver PI X
r²3J˚Û XI CONTENT AUTO-ID 7.1
r²3J˚Û XI CONTENT EA-APPL 605
SAP NetWeaver BI X
r²3J˚Û BI_CONT 705
EHP 1 FOR SAP EM 7.0 X
SAP Event Management 7.0 X
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 X
ý»l6U AUTO-ID 7.1
ý»l6U SAP_BS_FOUNDATION_702
SAP EHP2 FOR SAP NETWEAVER 7.0 Support Package 2 (Application Server ABAP) X
SAP NetWeaver 7.0 X
SAP Backend System X
SAP R/3 4.6C and
higher
SAP NetWeaver PI X
ý»l6U XI CONTENT AUTO-ID 7.1
ý»l6U XI CONTENT EA-APPL 605
SAP NetWeaver BI X
ý»l6U BI_CONT 705
EHP 1 FOR SAP EM 7.0 X
SAP Event Management 7.0 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:
ý»l6U SAP Auto-ID Infrastructure as add-on for SAP ERP
ý»l6U 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 For process description information, see the RFID-Enabled Flexible Delivery Processing. The
Description 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 For configuration information, see the RFID-Enabled Flexible Delivery Processing: Configuration
Documentation 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 For more information, see the SAP Service Marketplace at http://service.sap.com/
Guide securityguide.
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.
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.
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 or higher as a backend system.
If you install SAP Auto-ID Infrastructure as an add-on for SAP ERP, you have the option of installing
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 maybe necessary.
The ASN IDoc (enriched DELVRYXX) is generated in SAP NetWeaver Process Integration as a result of
the outbound integration process:
óS˝ªQî 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.
óS˝ªQî 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 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.
The graphic shows an example of the technical infrastructure for SAP Auto-ID Infrastructure installed
on a separate box.
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 X
g6¥À} AUTO-ID 7.1
g6¥À} SAP_BS_FOUNDATION_702
SAP EHP5 for SAP ERP 6.0 X
SAP ERP 6.0 X
SAP NetWeaver PI X
g6¥À} XI CONTENT AUTO-ID 7.1
g6¥À} XI CONTENT EA-APPL 605
SAP NetWeaver BI X
g6¥À} BI_CONT 705
EHP 1 FOR SAP EM 7.0 X
SAP Event Management 7.0 X
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 X
éÂv�qp AUTO-ID 7.1
éÂv�qp SAP_BS_FOUNDATION_702
SAP EHP2 FOR SAP NETWEAVER 7.0 Support Package 2 (Application Server ABAP) X
SAP NetWeaver 7.0 X
SAP EHP4 and higher for SAP ERP 6.0 X
SAP ERP 6.0 X
SAP NetWeaver PI X
éÂv�qp XI CONTENT AUTO-ID 7.1
éÂv�qp XI CONTENT EA-APPL 605
SAP NetWeaver BI X
éÂv�qp BI_CONT 705
EHP 1 FOR SAP EM 7.0 X
SAP Event Management 7.0 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:
éÂv�qp SAP Auto-ID Infrastructure as add-on for SAP ERP
éÂv�qp SAP Auto-ID Infrastructure as add-on for SAPNetWeaver
Further Information
The following documents provide more information about the IUID-Enabled Inbound/Outbound
Processing implementation variant.
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.
Configuration For configuration information, see the IUID-Enabled Inbound/Outbound Processing: Configuration
Documentation Guide. The documentation is available as SAP Solution Manager content for the IUID-
Enabled Inbound/Outbound Processing business process. Choose tab page Configuration.
Scenario Security For more information, see the SAP Service Marketplace at http://service.sap.com/
Guide securityguide.
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
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 the following BAdI
implementations, to ensure that the inbound process works:
ÁÒ…−ó{ ABI_BADI_INBOUND_AII
ÁÒ…−ó{ ABI_BADI_SHP_DESADV_IN
ÁÒ…−ó{ ABI_BADI_DELY_PROC
Implementation Sequence
For more information about the implementation sequence, see Overall Implementation Sequence [page 30].
This business process supports the following system landscapes:
ÁÒ…−ó{ 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
Further Information
The following documents provide more information about the RFID-Enabled Flexible Delivery
Processing implementation variant.
Content Location
Process For process description information, see the following:
Description 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 For configuration information, see the following:
Documentation 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 For more information, see the SAP Service Marketplace at service.sap.com/
Guide securityguide.
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:
7µ ²G Product Tracking and Authentication
7µ ²G| Product Tracking by Delivery
7µ ²G| Product Tracking by EPC
7µ ²G| Product Authentication (EPCIS data capture and query capability)
7µ ²G| Cold Chain Monitoring
7µ ²G| electronic Pedegree (ePedegree) with interfaces in XI content
7µ ²G RFID-Enabled Inbound Processing and Receipt Confirmation
7µ ²G 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
(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
£¡–ñt• To use SAP object event repository, you have installed SAP Auto-ID Enterprise.
£¡–ñt• 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.
If you install SAP Auto-ID Infrastructure on a separate box, you also must install SAP NetWeaver Process
Integration and SAP Event Management.
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.
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].
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 maybe necessary.
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.
Example: Technical Infrastructure of Secure Tracking and Tracing (Using SAP ECC 6.0)
The graphic shows an example of the technical infrastructure for SAP Auto-ID Infrastructure installed
on a separate box.
ùð,ãÿÒ+!NЕægµ]ݼÑ.7Example: Technical Infrastructure of Secure Tracking and Tracing (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 X
îr·˘¬Ô AUTO-ID 7.1 We recommend that you install one (central) instance of AUTO-ID
îr·˘¬Ô SAP_BS_FOUNDATION_702 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.
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 X
îr·˘¬Ô AUTO-ID 7.1 We recommend that you install one
îr·˘¬Ô SAP_BS_FOUNDATION_702 (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 X
(Application Server ABAP)
SAP NetWeaver 7.0 X
SAP Backend System X
SAP ECC 6.0
SAP NetWeaver PI X
îr·˘¬Ô XI CONTENT AUTO-ID 7.1
îr·˘¬Ô XI CONTENT SCEMSRV 7.01
îr·˘¬Ô XI CONTENT EA-APPL 605
For more information about the installation of these components, see System Landscape [page 26].
Implementation Sequence
For more information about the implementation sequence, see Overall Implementation Sequence [page 30].
This business process supports the following system landscapes:
ëȘÅflł SAP Auto-ID Infrastructure as add-on for SAP ERP
ëȘÅflł SAP Auto-ID Infrastructure as add-on for SAPNetWeaver
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.
Configuration For configuration information, see the Secure Tracking & Tracing: Configuration Guide. The
Documentation documentation is available as SAP Solution Manager content for the Secure Tracking &
Tracing business process Choose tab page Configuration
Scenario Security For more information, see the SAP Service Marketplace at http://service.sap.com/
Guide securityguide.
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
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 [page 26].
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.
The graphic shows an example of the technical infrastructure for SAP Auto-ID Infrastructure installed
on a separate box.
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 X
;i<˚©» AUTO-ID 7.1
;i<˚©» SAP_BS_FOUNDATION_702
SAP EHP2 FOR SAP NETWEAVER 7.0 Support Package 2 (Application Server X
ABAP)
SAP NetWeaver 7.0 X
SAP Backend System X
SAP R/3 4.6C and
higher
SAP NetWeaver PI X
;i<˚©» XI CONTENT AUTO-ID 7.1
;i<˚©» XI CONTENT EA-APPL 605
SAP NetWeaver BI X
;i<˚©» BI_CONT 705
EHP1 FOR SAP EM 7.0 X
SAP Event Management 7.0 X
For more information about the installation of these components, see System Landscape [page 26].
Implementation Sequence
For more information about the implementation sequence, see Overall Implementation Sequence [page 30].
This business process supports the following system landscapes:
@ø‚€łł SAP Auto-ID Infrastructure as add-on for SAPNetWeaver
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.
Configuration For configuration information, see the RFID-Enabled RTI Processing: Configuration Guide. The
Documentation documentation is available as SAP Solution Manager content for the RFID-Enabled RTI
Processing business process. Choose tab page Configuration.
Scenario Security For more information, see the SAP Service Marketplace at service.sap.com/
Guide securityguide.
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.
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.
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 .
The graphic shows an example of the technical infrastructure for SAP Auto-ID Infrastructure used as
a standalone deployment
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 X
˘˜ï|‚¹ AUTO-ID 7.1
˘˜ï|‚¹ SAP_BS_FOUNDATION_702
SAP EHP2 FOR SAP NETWEAVER 7.0 Support Package 2 (Application Server ABAP) X
SAP NetWeaver 7.0 X
SAP NetWeaver BI X
˘˜ï|‚¹ BI_CONT 705
For more information about the installation of these components, see System Landscape [page 26].
Implementation Sequence
For more information about the implementation sequence, see Overall Implementation Sequence [page 30].
This business process supports the following system landscapes:
Further Information
The following documents provide more information about the Standalone RFID-Enabled Outbound
Processing implementation variant.
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.
Configuration For configuration information, see the RFID-Enabled Slap&Ship Outbound Processing: Configuration
Documentation 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.
Scenario Security For more information, see the SAP Service Marketplace at service.sap.com/
Guide securityguide.
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].
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
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].
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:
G›¯ Read handling unit or storage unit ID and storage bin tag (SAP Auto-ID Infrastructure)
G›¯ Move from goods receipt (with reference to inbound delivery) to putaway (SAP ERP)
or
G›¯ Move from picking to goods issue with homogeneous HU (SAP ERP)
or
G›¯ Transfer internal bin to bin warehouse (SAP ERP)
NOTE
Prerequisite
G›¯ The storage bins have been equipped with RFID tags. For a proposal of how to provide tags for
storage bins, see SAP Note 1372785.
G›¯ 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.
G›¯ The forklift is equipped with an RFID reader that is connected with SAP Auto-ID Infrastructure.
G›¯ You have activated the business function ERP_AIE_INTEGRATION AIE ERP 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 including
enhancement package 5 as a backend system.
If you install SAP Auto-ID Infrastructure as an add-on for SAP ERP, you have the option of installing
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 [page 26].
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.
The graphic shows an example of the technical infrastructure for SAP Auto-ID Infrastructure installed
on a separate box.
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 X
‚‰<Z„ AUTO-ID 7.1
‚‰<Z„ SAP_BS_FOUNDATION_702
SAP EHP 5 for SAP ERP 6.0 X
SAP ERP 6.0 X
SAP NetWeaver PI X
‚‰<Z„ XI CONTENT AUTO-ID 7.1
‚‰<Z„ XI CONTENT EA-APPL 605
SAP NetWeaver BI X
‚‰<Z„ BI_CONT 705
EHP 1 FOR SAP EM 7.0 X
SAP Event Management 7.0 X
The following table provides just one way to implement this business process. For other combinations,
see http://service.sap.com/scl.
SAP NetWeaver BI X
§qS;4fl BI_CONT 705
EHP 1 FOR SAP EM 7.0 X
SAP Event Management 7.0 X
For more information about the installation of these components, see System Landscape [page 26].
Implementation Sequence
For more information about the implementation sequence, see Overall Implementation Sequence [page 30].
This business process supports the following system landscapes:
§qS;4fl SAP Auto-ID Infrastructure as add-on for SAP ERP
§qS;4fl SAP Auto-ID Infrastructure as add-on for SAPNetWeaver
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.
Configuration The documentation is available as SAP Solution Manager content for the RFID-Enabled
Documentation LES with Centralized Warehouse Management System business process. Choose tab page Configuration
Scenario Security For more information, see the SAP Service Marketplace at http://service.sap.com/
Guide securityguide.
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
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
If you install SAP Auto-ID Infrastructure as an add-on for SAP ERP, you use SAP ECC 6.0 including SAP
enhancement package 2 and higher as a backend system.
If you install SAP Auto-ID Infrastructure as an add-on for SAP ERP, you have the option of installing
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 [page 26].
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.
Example: Technical Infrastructure of RFID-Enabled Kanban 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.
¢ãÄAœ‹;¤ˆƒþîñZÇí§øö˱�OOptional
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 X
irı AUTO-ID 7.1
irı SAP_BS_FOUNDATION_702
SAP EHP 5 for SAP ERP 6.0 X
SAP ERP 6.0 X
SAP NetWeaver PI X
irı XI CONTENT AUTO-ID 7.1
irı XI CONTENT EA-APPL 605
SAP NetWeaver BI X
irı BI_CONT 705
EHP 1 FOR SAP EM 7.0 X
SAP Event Management 7.0 X
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 X
irı AUTO-ID 7.1
irı SAP_BS_FOUNDATION_702
SAP EHP2 FOR SAP NETWEAVER 7.0 Support Package 2 (Application Server ABAP) X
SAP NetWeaver 7.0 X
SAP Backend System X
SAP EHP 2 FOR SAP
ERP 6.0
SAP NetWeaver PI X
irı XI CONTENT AUTO-ID 7.1
irı XI CONTENT EA-APPL 605
SAP NetWeaver BI X
irı BI_CONT 705
EHP 1 FOR SAP EM 7.0 X
SAP Event Management 7.0 X
For more information about the installation of these components, see System Landscape [page 26].
Implementation Sequence
For more information about the implementation sequence, see Overall Implementation Sequence [page 30].
This business process supports the following system landscapes:
%IfłV SAP Auto-ID Infrastructure as add-on for SAP ERP
%IfłV 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 Kanban Processing. The
documentation is available as SAP Solution Manager content for the RFID-Enabled Kanban
Processing business process. Choose tab page Documentation.
Configuration For configuration information, see the RFID-Enabled Kanban Processing: Configuration Guide. The
Documentation documentation is available as SAP Solution Manager content for the RFID-Enabled Kanban
Processing business process. Choose tab page Configuration.
Scenario Security For more information, see the SAP Service Marketplace at service.sap.com/
Guide securityguide.
4 Solution-Wide Topics
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.
implements enterprise service interfaces to ensure semantic harmonization and business relevance.
This section deals with the service-enablement of SAP Business Suite 7.
We recommend that you use the highest version of SAP NetWeaver Process Integration. For
more information, see SAP Note 1515223 and SAP Note 1388258
U�ßÐÊ 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.
U�ßÐÊ 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.
U�ßÐ¥ SAP NetWeaver CE 7.1 or higher
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.
1lfl*
ö SAP Solution Manager 7.0
The Solution Composer, shipped with SAP Solution Manager 7.0, is required to host the enterprise
service online documentation.
The following table describes the SAP applications required or recommended for different runtime and
design time use cases:
SAP Applications
SAP SAP SAP SAP SAP Solution SAP NetWeaver
Business NetWeaver NetWeaver NetWeaver Manager 7.0 7.1 Services
Suite PI 7.0 PI 7.1 (ES CE 7.1 (ES (Solution Registry
(Integration Repository) Repository) Composer)
Repository)
Runtime Usage:
Enterprise Service Required Optional
Provisioning
Process One option required
integration and
mediated
communication
Design Time Usage:
Create and Required One option required Recommended
enhance
enterprise service
definitions
View enterprise One Option Required Recommended
service models
Design and Required Recommended Recommended
develop
composite
applications
Enterprise service Required
online
documentation
Publications of Optional Required
enterprise service
end-points
features in SAP Business Suite. The selected technical usages will install the corresponding software
components that contain the enterprise services interfaces and implementations.
Êx•°“ 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 )
Êx•°“ 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)
Êx•°“ 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.
Êx•°“ 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.
5 Appendix
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 To analyze the effects of transports and support packages
enhancement package 1 for SAP Solution Manager as well as activation logs for business functions
7.0)
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.
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).
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:
ãÒqŸˇŽ Examples of reference system landscapes
ãÒqŸˇŽ Planning tools such as the business process repository
ãÒqŸˇŽ Deployment options
ãÒqŸˇŽ Typical implementation process
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.
To call up information about business scenarios, business processes, or implementable steps, navigate
the following paths in the BPR viewer:
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.
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.
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>”.
Example Arrows separating the parts of a navigation path, for example, menu options
Example
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
Disclaimer
Some 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.