Upgrade and Update Guide

SAP ERP 6.0 Including Enhancement Package 7 Java

Target Audience
øC¹æè˜ System Administrators
øC¹æè˜ Technology Consultants

PUBLIC
øC¹ÍЗZø–<ÿ4@‘˚®péø�v5ýk>ŒÇ¨äJ&ú2'Üu>hп3¤Å0»˝•fiù¤öÕ\Ärjl��¶g§@q
Document History

CAUTION

Before you start the implementation, make sure you have the latest version of this document.
For the latest version, see http://service.sap.com/instguides.

The following table provides an overview of the most important document changes.
Version Date Description
1.0 2013-08-13 Final version
2013-09-26 ¨„��Â4 Section Preparation
Information on free space requirements for SUM directory updated
¨„��Â4 Section Planning
Information on dual-stack-split added
2013-10-16 Section Planning
Information on supported source releases updated
1.1 2013-10-31 Section Process:
Subsection Note about the Procees: Toolset version updated
1.2 2014-01-16 Cross-references to SL Toolset guides updated

2/38 PUBLIC 2014-01-16

Table of Contents

Chapter 1 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.1 Essential Information: Process and Documentation Overview . . . . . . . . . . . . . . 5
1.2 Important SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.3 Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Chapter 2 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.1 Supported Source Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.2 Dual-Stack Split . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.3 Upgrade Scope for ERP Java Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.4 Upgrade of Multiproduct Java Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 3 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.1 Free Space Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.2 EPC: Preparations for Universal Worklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 4 Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.1 Note About the Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Chapter 5 Follow-Up Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

5.1 SAP ECC: Activating SAP ECC Enterprise Extensions . . . . . . . . . . . . . . . . . . . . 17
5.2 Performing Follow-Up Activities for the E-Commerce User
Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.3 Additional Follow-Up Activities for SAP E-Commerce . . . . . . . . . . . . . . . . . . 18
5.3.1 Upgrading the Shop Management Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.3.2 Performing Adjustments to Java Class Changes . . . . . . . . . . . . . . . . . . . . . . . . 19
5.3.3 Checking the Login Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.3.4 Replacing the Catalog Replication Mechanism . . . . . . . . . . . . . . . . . . . . . . . . 22
5.3.5 Adjusting XCM Configuration and Creating Shops for New
Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.4 Adjusting the XCM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.5 Migrating XCM Configuration Data Manually . . . . . . . . . . . . . . . . . . . . . . . . 25

2014-01-16 PUBLIC 3/38

5.6 ADS: Performing Follow-Up Activities for Adobe Document
Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.7 Performing Follow-Up Activities for the System Landscape
Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.8 BI Java: Performing Follow-Up Activities for Business Warehouse . . . . . . . . . . 28

Chapter A Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
A.1 The Main SAP Documentation Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

4/38 PUBLIC 2014-01-16

 1 Getting Started
1.1 Essential Information: Process and Documentation Overview

Øîá»OG¢ ±/ö¹k³R˜Ts°ëº˙äƒR³néÍÏ9ºqp›%-Žú|•}ÃI犵¾ô¢/4£n¨Í3À)¹ł˚J,Ÿôì|=7Z”eU¬µý§ØD¼ê6ÇBg_K¦1,œšHÓUãkïøX¿¾§Ë¾õÔÿY#�„5ÞH˝õ© w½—×˙E9ÔıM˘Âñ

1 Getting Started

Øîá»OG¢ ±/ö¹k³R˜Ts°ëº˙äƒR³néÍÏ9ºqp›%-Žú|•}ÃI犵¾ô¢/4£n¨Í3À)¹ł˚J,Ÿôì|=7Z”eU¬µý§ØD¼ê6ÇBg_K¦1,œ†HÍU÷mïøX·¾®Ë�õÜ

This section of the guide contains important information that you need to read before starting your
update or upgrade process.
Øîë»OGª è/_ö©kèRST_°áºSä†R²nøÍLÏtºQp›%1Ž»|¾}ÁI炵ºô«/%£w¨Â3À)¹łJ%ŸµìA=0Z™eO¬ïýžØX¼ì6ÁBoTK�1·œ¨

Øîá»OG¢ ±/ö¹k³R˜Ts°ëº˙äƒR³néÍÏ9ºqp›%-Žú|•}ÃI犵¾ô¢/4£n¨Í3À)¹ł˚J,Ÿôì|=7Z”eU¬µý§ØD¼ê6ÇBg_K¦1,œšHÓUãkïøX¿¾§Ë¾õÔÿY#�„5ÞH˝õ© w½—×˙E9ÔıM˘Âñ

1.1 Essential Information: Process and Documentation

Overview
Øîá»OG¢ ±/ö¹k³R˜Ts°ëº˙äƒR³néÍÏ9ºqp›%-Žú|•}ÃI犵¾ô¢/4£n¨Í3À)¹ł˚J,Ÿôì|=7Z”eU¬µý§ØD¼ê6ÇBg_K¦1,œ†HÍU÷mïøX·¾®Ë�õÜ

This guide contains information specific to SAP ERP only, but you need additional information to
perform your update correctly.
Øîë»OGª è/_ö©kèRST_°áºSä†R²nøÍLÏtºQp›%1Ž»|¾}ÁI炵ºô«/%£w¨Â3À)¹łJ%ŸµìA=0Z™eO¬ïýžØX¼ì6ÁBoTK�1·œ¨

Øîá»OG¢ ±/ö¹k³R˜Ts°ëº˙äƒR³néÍÏ9ºqp›%-Žú|•}ÃI犵¾ô¢/4£n¨Í3À)¹ł˚J,Ÿôì|=7Z”eU¬µý§ØD¼ê6ÇBg_K¦1,œ†HÍU÷mïøX·¾®Ë�õÜ

Software Update Manager

In addition to the application-specific guide, you use the Software Update Manager (SUM) for the
upgrade or update.
The following table contains definitions of these terms:
Term Definition
Update Installation of an enhancement package in an existing SAP system.
Upgrade Upgrade to an SAP system including an enhancement package.

The Software Update Manager (SUM) guide contains information on the overall process, tools, the
operating system and the database, while this guide contains the application-specific information.
For the SUM guides, see SAP Service Marketplace at http://service.sap.com/sltoolset Software
Logistics Toolset 1.0 Documentation section: System Maintenance Updating SAP Systems Using Software Update Manager
<Version> .
Øîë»OGª è/_ö©kèRST_°áºSä†R²nøÍLÏtºQp›%1Ž»|¾}ÁI炵ºô«/%£w¨Â3À)¹łJ%ŸµìA=0Z™eO¬ïýžØX¼ì6ÁBoTK�1·œ¨

Master Guide

Øîž† Make sure that you also read the Master Guide for SAP Enhancement Package 7 for SAP ERP 6.0.
The Master Guide provides you with the overall view of the implementation process, meaning

2014-01-16 PUBLIC 5/38

 1 Getting Started
1.2 Important SAP Notes

installation, upgrade or update processes, and with references to important information during
implementation.
−Î2Î Make sure that you collect all the information about planning and implementation processes that
is contained in the Master Guide before starting your installation, upgrade, or update project.
−Î2Î Make sure that you have downloaded the latest version of the Master Guide SAP Enhancement Package
7 for SAP ERP 6.0 from SAP Service Marketplace at http://service.sap.com/erp-ehp7-
inst .

More Information
You can access documentation for all maintained product releases on SAP Help Portal at http://
help.sap.com/erp .

Target Release Documentation

The documentation for the target release is not available online in your system until you have
completed the upgrade and the installation procedure for the online documentation.
Before the upgrade, ensure that you can read the DVD offline. After the upgrade, you need to install
the documentation for the target release.
For SAP Library for SAP ERP 6.0 including SAP enhancement package 7, see SAP Help Portal at http://
help.sap.com/erp .

SAP Fiori Apps

For more information regarding SAP Fiori apps, see SAP Fiori for SAP ERP in the documentation of SAP
ERP on SAP Help Portal at http://help.sap.com/erp .
−Î×6B4¿Ý“ñ
ÅרñE˧ÔgÚ4ë⁄§ýôÆ”Þ˙óÿ˝¶0ß*øåïèu łž]¤äÔè—⁄g‹©>!=™°íÑflÂH«è¥P«Łz„úV5šÿłLõ+³DˆÄ‘Åf·C{i˜r^4<ÆTıpö]ßøÛ˘ŒâÀ

1.2 Important SAP Notes

−ÎÝ6B<¿KÝÂñÅ„¨½Eç§Þg™3냧ìôŽ”fi˙Óÿ÷0á*úåéès �žT¤õÔè—žg⁄©.!"™°íÚflËHêèŸP¬Łf„àVošÚŽLç+³LˆÇ‘ÇfX/·Zsi(o4)Æfiı~

Note Number Title Comment

1816819 Dual Stack support for Suite7i2013 Contains information about a dual-stack split
required for the upgrade to SAP Business Suite
7i2013 or SAP NetWeaver 7.4.
1815263 Upgrade to EHP7 for SAP ERP 6.0 Java (start release) Contains information about the upgrade to SAP
enhancement package 7 for SAP ERP 6.0 if Java
instances are installed.
1742750 Upgrade from SAP ERP 2004 to EHP7 for SAP ERP 6.0 Contains information about the upgrade to SAP
enhancement package 7 for SAP ERP 6.0 for
ABAP and Java standalone systems.
1815263 Upgrade to EHP7 for SAP ERP 6.0 Java (start release) Contains information about updating ERP 6.0
Java instances during the upgrade to SAP
enhancement package 7 for SAP ERP 6.0.

6/38 PUBLIC 2014-01-16

 1 Getting Started
1.2 Important SAP Notes

Note Number Title Comment

1737650 cþÙ˛¬ıôñ
¡Çª™=œòãffi6Í6yKWÞ\Å9̆ïö.+LsT@Ê>Wk—‰pª´¡i}¨äÁÅ&»3SNÖ›;@™U˚é‡ì¾„ßZ«¾V‘ºNÀÎïÄ£¯˜6Ëõ^ÈqKŸÂ-s® Contains information and references to SAP
– SP Stacks Notes for applying Support Package (SP) Stacks
of SAP enhancement package 7 for SAP ERP 6.0.
849887 Release Information Note SAP ERP 6.0 Contains a list of all SAP ERP 6.0 Release and
Information Notes (RIN) that have been issued
for SAP ERP 6.0.
998833 Release Restrictions SAP ERP 6.0 - Enhancement Provides information about the limitations for
Packages SAP enhancement packages for SAP ERP 6.0.
1818596 Enhancement package 7 for SAP ERP 6.0: Required SWC Describes the software components of your SAP
system that you need to update in order to use
enhancement package 7 functionality.
1820906 SAP Enhancement Package 7 for SAP ERP 6.0: Informs you about the points you have to
Compatible Add-ons consider when you plan to run SAP
enhancement package 7 for SAP ERP 6.0
together with an add-on in the same system.
156387 Composite Note on Upgrade Problems for the SAP This is an HR-specific SAP Note.
Component HR (Human Resources)
774615 Support Package Levels for SAP ERP / SAP ECC Contains information about the ABAP Support
Installations and Upgrades Package levels contained in the installations and
release upgrades.
1000009 ASU Toolbox Contains information about the ASU Toolbox.
The ASU Toolbox enables the customer to
recognize the steps before and after the update
that are required in addition to the actual
technical update. Furthermore, the ASU
Toolbox performs these steps in the system in a
controlled manner.
1468349 SAP Business Suite 7 for SAP NetWeaver 7.3 hub Describes which applications can run on a hub
system with SAP NetWeaver 7.3 and as of which
start release or SAP enhancement package this
is possible.
1600482 Hierarchical access functionality Contains upgrade SAP Note describing an
incompatible change.
1592495 Information for Portal Content Contains information about portal roles and
functions.
1790828 Central Note - Software Update Manager 1.0 SP08 Contains information about preparations for
the update.
1680045 Release Note for Software Provisioning Manager 1.0 Contains remarks, annotations, and
corrections discovered after the installation and
publication of the system copy guides.

cþÙ
¬‚ôù
äǤ™(œ�ãffi:Í6yEWÐ\Ù9†ëö7+@sU@Ð>×kı‰~ª£¡g}éäõÅ»CS'Ö¢;{™q˚¿‡€¾ƒßT«¸VƺrÀáﯣÚ*6þõ|È0KÊÂfs>žÎ

2014-01-16 PUBLIC 7/38

 1 Getting Started
1.3 Naming Conventions

1.3 Naming Conventions

œ¶°:×ö˜XKø_4]päł¢†ô−ÿ!Éj¶ÓŸávzîcu�ŸÒ…SK}³è\kÆøßÿBî"R)�È;²\ƒ’dS6„’Cµ¤êš@˝(‘ #6˚’g†“ÛéH@†ıœ˜·ž�&>Ë”cm¬Ê/S�RŠJ}ïž[q"n3ûi‹0Ú*$!z0Î=Š\˘7'™é

Instance Name

In this document, <instance_name> is used as a placeholder for the instance name in the instance
directory path of your system.
For standalone Java systems, <instance_name> is substituted with J<xx> for the central or dialog
instance, where <xx> stands for the instance number.

EXAMPLE

If your instance number is <00>, then the Java instance number is J00.

œ¶°0×ö
K·_$]+ä×¢�ô•ÿO!Îj·Ó›áLv7îCu�ŸÎ…KC³î\mÆüßöBî"R0�Ç;¢\Ž’dS=„ŽCô¤×šG˝4‘#l˚µg…“ÉéH@›ı�˜µž%&Ì”�m¶ÊuSFRˇŠL}éžSq)n8ûò‹ˇ
œ¶°0×ö
K·_$]+ä×¢�ô•ÿO!Îj·Ó›áLv7îCu�ŸÎ…KC³î\mÆüßöBî"R0�Ç;¢\Ž’dS=„ŽCô¤×šG˝4‘#l˚µg…“ÉéH@›ı�˜µž%&Ì”�m¶ÊuSFRˇŠL}éžSq)n8ûò‹ˇ

8/38 PUBLIC 2014-01-16

 2 Planning
2.1 Supported Source Releases

2 Planning

¡Û<AÌ˙Êi!aÙ§ˇ˝ÊPßî•‘F–³£¡ýæ\™Mı’öì{®;Îñq6g'CKâõÌy˧ˇ*aÞiB¬‘ân]¢b”èvC[3Ž»A $h˘_®›tS¥«n·©à^UÛ¹©j¢’Я¦/°©œkSˇ9þx©o

This section of the guide contains important information that you need to read before starting your
update or upgrade process.
¡Û<KÌ˙ÂixaŒ§ ˝‚PJß•–Fͳ£€ý÷\ÍM×’Öì{®'ΰO6e'EKäõÈy§*aÞpB£‘òn]¢b–è�CE[Ž¼A$r˘®°tO¥�n·¡àUUй2j‰

2.1 Supported Source Releases

This section provides an overview of the supported upgrade and update paths to SAP enhancement
package 7 for SAP ERP 6.0.
Before the update or upgrade, your SAP system must have one of the source releases that have been
released for this update and that apply to all databases.

CAUTION

If you have to apply Support Packages to your source release shortly before the upgrade or update,
check whether the equivalent Support Package for the target release is already available. Otherwise
this may delay your upgrade schedule.

Source Releases Target Release Upgrade Type

SAP ERP 6.0 SAP ERP 6.0 including SAP Enhancement package installation
enhancement package 7 (based on
SAP NetWeaver 7.3, SAP
enhancement package 1 for SAP
NetWeaver 7.3 or SAP NetWeaver
7.4)
SAP ERP 6.0 including SAP SAP ERP 6.0 including SAP Enhancement package update
enhancement package 2 – 6 enhancement package 7 (based on
SAP NetWeaver 7.3, SAP
enhancement package 1 for SAP
NetWeaver 7.3 or SAP NetWeaver
7.4)

¡Û<AÌ˙Êi!aÙ§ˇ˝ÊPßî•‘F–³£¡ýæ\™Mı’öì{®;Îñq6g'CKâõÌy˧ˇ*aÞiB¬‘ân]¢b”èvC[3Ž»A $h˘_®›tS¥«n·©à^UÛ¹©j¢’Я¦/°©œkSˇ9þx©o

Please note the following:

¡Û<KÌ˙ÂixaŒ§ ˝‚PJß•–Fͳ£€ý÷\ÍM×’Öì{®'ΰO6e'EKäõÈy§*aÞpB£‘òn]¢b–è�CE[Ž¼A$r˘®°tO¥�n·¡àUUй2j‰

2014-01-16 PUBLIC 9/38

 2 Planning
2.2 Dual-Stack Split

3¡$'Ä
ÓÀ˘’3˜ 86›Ë+®æo¦ÂW
¹{—Ósé/!9?ßâ‡æ€⁄›�Zî®ÑDbÀ<)*¯^[„_)$<Åo-=3:�ÊÈsÖ ´‹ÀÑ3˚,"“<ú˚b‡,ø4SI°ÉÏ0'þ�îôS†Úflû>Ý''

3¡$ÈáÄ To be able to upgrade or update to SAP enhancement package 7 for SAP ERP 6.0, your start systems
must have a minimum start SP of SAP NetWeaver 7.0 SPS14 (or Service Release 3). For more
information on the equivalent NW SPs, see SAP Note 1850327.
3¡$Èá« Based on the Landscape Pattern (HUB or SIDECAR) defined in SMSY for the Java system, the
Maintenance Optimizer will determine the corresponding SAP NetWeaver SP Stack. For more
information, see SAP Note 1620472.
3¡$ÈáÄ Note that if you upgrade to SAP enhancment package 7, you must also upgrade your Java Hubs to
SAP NW 7.30 or higher. This is to meet the interoperability requirements of SAP NetWeaver.
3¡$Èá« Bear in mind that SAP NetWeaver AS JAVA 7.3 is based on JAVA EE 5, which might require
additional migration effort for custom-specific application development based on former
JAVA EE versions.
3¡$Èá« For more information, refer to the SDN Best Practice blog http://scn.sap.com/
community/netweaver-portal/blog/2011/07/25/sap-netweaver-portal-73-top-10-
lessons-learned-from-ramp-up-you-should-know-before-getting-started.
3¡$ÈáÄ You do not need to apply any additional new SP Stack to the technical instance defined as HUB if
your JAVA instance is greater than or equal to the defined minimum SP Stack Level.
3¡$-Ä
ÓÈ˘É3P (6ÒËg®Êo¬Â˜
¾{–Óbép!t?ÿâ‡æ¼⁄ÈfiZî¨ÑBbÄ< *¯^B„P)4#Åo-633�‰ÈNÖ
´flÀË3D,˙“ ú˘b—,ð?SB°RÏˇ

3¡$'Ä
ÓÀ˘’3˜ 86›Ë+®æo¦ÂW
¹{—Ósé/!9?ßâ‡æ€⁄›�Zî®ÑDbÀ<)*¯^[„_)$<Åo-=3:�ÊÈsÖ ´‹ÀÑ3˚,"“<ú˚b‡,ø4SI°ÉÏ0'þ�îôS†Úflû>Ý''

2.2 Dual-Stack Split

Dual-stack systems are no longer supported for the upgrade target SAP enhancement package 7 for
SAP ERP 6.0. For more information, see SAP Note 1816819.
If your SAP ERP system is currently implemented as a dual-stack system, you need to perform a split
on your source system before starting the upgrade.
3¡$-Ä
ÓÈ˘É3P (6ÒËg®Êo¬Â˜
¾{–Óbép!t?ÿâ‡æ¼⁄ÈfiZî¨ÑBbÄ< *¯^B„P)4#Åo-633�‰ÈNÖ
´flÀË3D,˙“ ú˘b—,ð?SB°RÏˇ

3¡$'Ä
ÓÀ˘’3˜ 86›Ë+®æo¦ÂW
¹{—Ósé/!9?Ïâœæ¯⁄ı¢Zî®Ñ›bÙ

2.3 Upgrade Scope for ERP Java Components

The upgrade program detects which ERP Java components are installed in your source release system.
The versions of the ERP Java components in the target release system depend on your selections in SAP
Solution Manager Maintenance Optimizer. Based on your decision regarding the ERP usage types that
you want to bind with SAP enhancement package 7 into the upgrade, the upgrade program either
deploys the ordinary ERP 6.0 component versions, or the enhanced component versions. Since the
upgrade program always deploys complete usage types, you may have a larger amount of software
components installed in your target release system than in the source release system.

10/38 PUBLIC 2014-01-16

 2 Planning
2.4 Upgrade of Multiproduct Java Systems

NOTE

Since parts of SAP ERP 6.0, including SAP enhancement package 7 technical usage “Central
Applications” Java, are deployed in your system, ensure that the corresponding ABAP back end
is also enhanced.

Biller Direct

The deployment of the usage type Biller Direct includes the SAP Java Data Dictionary since it contains
the XCM database tables.
Dla/¼t‡
Œ_˛¯OmÞWTW2�·zL¸]h1>Æ.qÈÖïY
Dlk/¼t−
Ï_R¯_m–W˘W�£z¸Ih?>Ð..ÈVï`㯓~¢uº³l¼I¯ü’lY£·K,˙ˆŠ9Ýó•³]s_¶»ŒŸ?œ^X˝a¦šgùVAàc–˘§ùnÉþ’¼ —¯ù¼M[a¥iô¨⁄£üêùä

2.4 Upgrade of Multiproduct Java Systems

The upgrade program can now handle the upgrade of multiproduct Java systems based on SAP
NetWeaver 7.0.
For more information, see the Maintenance Planning Guide for SAP SolMan 7.1 SP05 on SAP Service
Marketplace at http://service.sap.com/erp-ehp6-inst .
Dla/¼t‡
Œ_˛¯OmÞWTW"�©zC¸Nh>>Á.qÈ˙ï@㯓b¢4º:³n¼O¯ú’hYª·Z,˙ˆ”9Òó’³Bs_¶°Œ‚~œcX˙aºš}ùAÙ�–˚§ ùfÉõ’· ˜¯Ð

2014-01-16 PUBLIC 11/38

This page is left blank for documents
that are printed on both sides.
 3 Preparation
3.1 Free Space Requirements

”þŠí ©˚Xƒ×−˙ÆÄ8˝&¦áÁ|f†·³˜]õÑÿ¯žá!®}Y´˝@ž}ÕkÓN§a(ѱþŸfl9£bÐÙ9˛aR6Áy3Oa°õ˜�´qyÿ¼Gœ%—³éòÜ¢w;˙a˚ÜgúA þòšœn

3 Preparation

This section of the guide contains important information about preparatory tasks that you need to
complete before starting your update or upgrade process.
”þŠí ©˚Xƒ×−˙ÆÄ8˝&¦áÁ|f†·³˜]õÑÿ¯žá!®}Y´˝@ž}ÕkÓN§a(ѱþŸfl9£bÐÙ9˛aR6Áy3Oa°õ˜�´qyÿ¼Gœ%—³éòÜ¢w;˙a˚ÜgúA þòšœn

3.1 Free Space Requirements

Make sure that the system that you want to update (upgrade) has at least the following amount of free
space:

Database-Independent
Software Update Manager (SUM) Directory Approximately 50 GB
Download Directory (temporary space requirement) Approximately 10 GB

Database-Dependent
Free space in the database Approximately 15 GB

”þší ©Xß×Å˙ÖÄcP&−áË4fƒ·²˜Lõ”ÿ[¯¾á!®}˘´"@œ}ÓkÕN£a(ѱþ†fl6£rÐÆ9˛aY6Èy¯€¦3HˆaªõE�+´myù¼Aœ-—³âòG¢^
”þŠí ©˚Xƒ×−˙ÆÄ8˝&¦áÁ|f†·³˜]õÑÿ¯žá˜®Z}{´˛@‘}ÕkžNêa-($ÑÒþáflø£}

3.2 EPC: Preparations for Universal Worklist

NOTE

This section applies only if your source release is lower than the following SAP NetWeaver releases:
”þxÈÃ SAP NetWeaver 7.0 SPS 18, patch level 6
”þxÈÃ SAP NetWeaver 7.0 SPS 19, patch level 5
”þxÈÃ SAP NetWeaver 7.0 SPS 20, patch level 4
”þxÈÃ SAP NetWeaver 7.0 SPS 21, patch level 1
”þxÈÃ SAP NetWeaver 7.0 SPS 22
”þxÈÃ SAP NetWeaver 7.0 including enhancement package 1 SPS 06, patch level 2
”þxÈÃ SAP NetWeaver 7.0 including enhancement package 1 SPS 07
”þxÈÃ SAP NetWeaver 7.0 including enhancement package 2 SPS 03, patch level 1
”þxÈÃ SAP NetWeaver 7.0 including enhancement package 2 SPS 04
”þxÈÃ SAP NetWeaver Composition Environment 7.2, patch level 1

2014-01-16 PUBLIC 13/38

 3 Preparation
3.2 EPC: Preparations for Universal Worklist

T”{#¢Š SAP NetWeaver Composition Environment 7.2 SPS 01, patch level 1
T”{#¢Š SAP NetWeaver Composition Environment 7.2 SPS 02, patch level 1
T”{#¢Š SAP NetWeaver Composition Environment 7.2 SPS 03

Before the update, make sure that there is no data in the database table KMC_WF_SUBSTITUTE,
otherwise the UWL database upgrade fails.

Prerequisites
This step is required only if Knowledge Management and Collaboration is installed in your source
release system.

Procedure
1. Export and back up the content of table KMC_WF_SUBSTITUTE, otherwise the UWL database
upgrade fails.
2. Delete this content from the table.
T”{Æ⁄Y®łtÀs„
7N¾)o/Ú™m>ÕÄÌúj£NØfiñ¿½�Mø2…⁄j趿
T”{Æ⁄Y®łtÀs„
7N¾)o/Ú¬mvÕæÌûj²NØÞñò½´MÜ2à⁄|j)¶€ÕÏ
JãVœ´„BÄýÑ+9{ÎIͱjYFð¯£bB�Îł1K§:çúø®‰áà¨1âJZíIƒ/r

14/38 PUBLIC 2014-01-16

 4 Process
4.1 Note About the Process

‰L?X|Jôüy@eõËDÈ.ýNS„EÙ•¨átłg—' êRÊHq>4”µš¿øl‹Š1Íb>$çs~ÒGúÛõ°¾µ ¼£b[£åç“g«ïñ=žLWmتÿØaPDÑ‹~-˝8œñ»zÓ¾V½°ù91“ëH}gÿP™F4

]¬
1îÜÉ••@»2|ËÕ$Ì‚Ž

4 Process

This section of the guide contains information about process-related application-specific tasks (in some
cases, there are no application-specific tasks).
‰L?X|Jôüy@eõËDÈ.ýNS„EÙ•¨átłg—' êRÊHq>4”µš¿øl‹Š1Íb>$çs~ÒGúÛõ°¾µ ¼£b[£åç“g«ïñ=žLWmتÿØaPDÑ‹~-˝8œñ§z;B½¶ù99“âH¼g÷

4.1 Note About the Process

The following table contains definitions of the terms “update” and “upgrade”:
Term Definition
Update Installation of an enhancement package in an existing SAP system.
Upgrade Upgrade to an SAP system including an enhancement package.

The update and upgrade processes are described in detail in the Software Update Manager (SUM) guide
Update Guide - Update of SAP Systems Using the Software Update Manager 1.0 SP09.
The corresponding toolset version is ToolSet 1.0 SPS09.
The SUM guide contains information on the overall process, tools, the operating system, and the
database, while this guide contains the application-specific information.
SAP ERP 6.0 enhancement package 7 requires application-specific steps for SAP HANA in the Process
section. All generic steps are documented in the SUM guides.
For the SUM guides, see SAP Service Marketplace at http://service.sap.com/sltoolset Software
Logistics Toolset 1.0 Documentation section: System Maintenance Updating SAP Systems Using Software Update Manager
1.0 SP09 .
‰L?R|JôôyˇeºËTÈuýS€EÓ•àáułv—x §RêHq>(”ô£¿úl”Š7Íf>-çb~Ò^úÔõ€¾ª ·£k[âåÚ“`«óñ'žWTضÿÞaVDÙ‹u-8ñ”
‰L?R|JôôyˇeºËTÈuýS€EÓ•àáułv—x §RêHq>(”ô£¿úl”Š7Íf>-çb~Ò^úÔõ€¾ª ·£k[âåÚ“`«óñ'žWHبÿÊaPDÙ‹}-˚8ÆñƒzÔ¾J½ªùc“÷H{gùPıF?
]7
˘

2014-01-16 PUBLIC 15/38

This page is left blank for documents
that are printed on both sides.
 5 Follow-Up Activities
5.1 SAP ECC: Activating SAP ECC Enterprise Extensions

5 Follow-Up Activities

This section of the guide describes application-specific steps that have to be performed after the update
or upgrade process is complete.
This section of the guide describes application-specific steps that have to be performed after the
installation process is complete.
{+ƒ$�nüE÷
ÁÆkgD£¥c’˚ö&:÷ïÓ¨©0M,tŁtå¾ëK‡~@”î.#ìÅøžNÔnöHí-v¡ó³BÕ4'©²Ð*§÷Êzt¬£%qº�'áÝfl-Y[zk÷Ö«gÖflCš8ü´,ìE
ã1x^ú—y

5.1 SAP ECC: Activating SAP ECC Enterprise Extensions

SAP ECC Enterprise Extension functions are activated by setting the activation switches. The activation
of the switches depends on the later use of the SAP system.

CAUTION

Before you activate a switch, you must discuss this with your business consultants and the project
team.
You cannot deactivate a switch once it has been activated.

Procedure
For more information about activating a switch and the possible restrictions, see SAP Note 816806.
{+ƒ.�nüM÷SÁ›kwDø¥/’2ö,:¿ïÔ¨¨0\,+Ł9žëKž~
”Ð.!ìÃøŸJÔgöYí-v¸ó¼BÅ48©²Ð!§þÊ;t/¬¤%mº–'»Ý�-Y[|kÿ Ö€gMflj
{+ƒ$�nüE÷
ÁÆkgD£¥c’˚ö&:÷ïÓ¨©0M,tŁtõ¾õK“~S”á.$ìÅøSWÔ ö�í_v¼óòBü4-©¥Ð,§²Êˇt4¬€%rº—'îÝš-Y[}k¾AÖ‘g®flDšüú,¥E.ã-x^?—k~:÷2úA+R¯I˝Á!2U˱ͼƒÿ„ð«÷9²[º0ÀP²£æ§)¬˝iQz˜Ð²#à§oÃî¬Ö³eõ¢º

5.2 Performing Follow-Up Activities for the E-Commerce User

Management
As of SAP E-Commerce 5.0, new user roles are provided. The old user roles are no longer supported.
For each Web application, a service user role and at least one Internet user role are available. For more
information about the available roles, see the documentation in the Solution Manager.
Due to these changes, you have to perform updates in the user management as outlined below.

Procedure

Updating Customized User Roles

Adjust your user role copies according to the authorizations provided in the new application user roles.
We recommend that you create role copies and refine authorizations with your own authorization
values.

2014-01-16 PUBLIC 17/38

 5 Follow-Up Activities
5.3 Additional Follow-Up Activities for SAP E-Commerce

Creating Service Users

It is now possible to have a service user for each application. You have to create service users and assign
them the appropriate service user role. You also have to create new customer JCO components in the
Extended Configuration Management (XCM) of your E-Commerce applications, which you can then
select in the user settings of your XCM application configurations.

Assigning Roles to Web-Based User Management

You have to assign new user roles to the Web-based user management using the following Customizing
activity:
CRM E-Commerce Basic Settings for E-Commerce Internet User Web-Based User Management Set Up Roles
for Web-based User Management
Furthermore, adjust the role mapping to Enterprise Portal roles if your E-Commerce applications run
in an Enterprise Portal. For more information, see SAP Note 713472.

Assigning Roles to the Reference User

You have to assign new user roles to the reference users created for the E-Commerce Business-to-
Consumer (B2C) application or for the Web-based user management application.

Internet User

You have to assign new user roles to your existing Internet users for the E-Commerce applications they
have to use. To apply mass user changes, use the User Mass Maintenance (transaction SU10).
§|r÷?÷`flxˇÎwàa/,zuÐYûºÊfi³>zÍN�+nõ‹ü ‘:´]¸>ÏZßhú8lTåe2
õœÉÝžújøÞ¡wŁ–½×h˘qßCΨC†/ä‚8pžz8„Éx5� ~§ò“w,¾èéŃ˜¨bõÅêŽOih1í˘5œIÁmÄ�^h �}ÉÉMøýßåÒíõ$¶ˆ~rv‰L
§|rý?÷`œx@Î8ðat`zIЈY¼ºÞfi½(z™Nÿ+WõÆü/ ¼:Š]û>àVßhõîü†[lkée!
ñœÆÝœúa¬ÞłwÛ–æ×V˘Sß}ΛCÉ`ä½8gž`N8·Éˆz5» C~*§º“—,§è¥Å¯˜¹bïÇê×ONh;í5ÌIëm⁄ł^c µ}É•M¾ýàå·íõ$Œˆ:r¦‰_8Á™Jª
òÈ—˚fi>ƒ%Aû”>¬H˚
ñg”ı

5.3 Additional Follow-Up Activities for SAP E-Commerce

In addition to adjusting the XCM configuration [page 23] and the user management [page 17], you have to
perform the following follow-up activities for SAP E-Commerce for SAP ERP:
§|rˆ9 Upgrading the Shop Management Data [page 18]
§|rˆ9 Performing Adjustments to the Java Class Changes [page 19]
§|rˆ9 Checking the Login Configuration [page 21]
§|rˆ9 Replacing the Catalog Replication Mechanism [page 22]
§|rˆ9 Adjusting XCM Configuration and Creating Shops for New Scenarios [page 22]
§|rý?÷`œx@Î8ðat`zIЈY¼ºÞfi½(z™Nÿ+GõØü ¯:Ÿ]ü>àłßˆ

5.3.1 Upgrading the Shop Management Data

In SAP E-Commerce 5.0, the Customizing data of the Shop Management Application is stored in the
database of SAP NetWeaver AS Java, while in previous releases the shop data was stored in the file system
in xml format.

18/38 PUBLIC 2014-01-16

 5 Follow-Up Activities
5.3 Additional Follow-Up Activities for SAP E-Commerce

Prerequisites
É°„˜˚à You have access to the files that contain the shop data from ISA (R/3 Edition) 4.0.
É°„˜˚à You have created an XCM application configuration for the Shop Management Web Application
(Shopadmin). The Shop Management Web Application is automatically installed with SAP E-
Commerce 5.0. The parameter object-path of the shop component must contain the path to the
XML files that contain the shop data from ISA (R/3 Edition) 4.0.

Procedure
1. Call the SAP E-Commerce Administration Console of the Web application Shopadmin in the
upgraded system. To do so, enter http://<hostname>:<port>/shopadmin/admin.
2. Choose the hyperlink Shop Data Migration (XML files to SAP J2EE Database).
3. Enter the name of the XCM application configuration that you created, as specified under
“Prerequisites”.
4. Choose Submit.
The shops are now uploaded to the database of SAP NetWeaver AS Java and you use the Shop
Management application to access them.

NOTE

The shops are stored in such a way that they depend on the ERP system ID and client. Therefore,
you might need to migrate the shop data from the file system to the NetWeaver Application Server
database more than once, depending on how many systems and clients you use in your landscape.

É°„ú;.ÏŽ|ŒÓ˛ð™öšî™#�©’Ò°C#Ú¾ŁÊ˜

5.3.2 Performing Adjustments to Java Class Changes

The following sections describe changes that have been made to Java classes. If you have modified these
classes in the source release, you have to adjust your modifications to the new developments.
As a prerequisite to run SAP E-Commerce 5.0, you must install the SAP R/3 Plug-In 2004 SP10 for SAP
R/3 4.6C and R/3 Enterprise. The former plug-in function modules are an integral part of mySAP ERP
2004 and SAP ERP 6.0.

Obsolete Classes

In SAP Internet Sales (R/3 Edition) 3.1 and 4.0, some specific back-end classes and algorithm classes had
been used if no SAP R/3 Plug-In was available or if the R/3 release was SAP R/3 4.6C or lower. These
classes are no longer used. However, the following classes are still delivered for documentation reasons:
É°„˜˚à com.sap.isa.backend.r3.shop.ShopR3

É°„˜˚à com.sap.isa.backend.r3.salesdocument.rfc.CCardStrategyR340b

É°„˜˚à com.sap.isa.backend.r3.salesdocument.rfc.CreateStrategyR340B

É°„˜˚à com.sap.isa.backend.r3.salesdocument.rfc.CreateStrategySimRFC

2014-01-16 PUBLIC 19/38

 5 Follow-Up Activities
5.3 Additional Follow-Up Activities for SAP E-Commerce

g¹�C com.sap.isa.backend.r3.salesdocument.rfc.DetailStrategyR340b

g¹�C com.sap.isa.backend.r3.salesdocument.rfc.DetailStrategyR3PI40

Incompatible Java Changes in Back-End Classes for SAP E-Commerce for SAP ERP

This section is relevant only if you have implemented extensions in the back-end classes for SAP E-
Commerce for SAP ERP. These back-end classes are included in the following packages (or subpackages
of these packages):

g¹�C com.sap.isa.backend.r3base

g¹�C com.sap.isa.backend.r3

g¹�C com.sap.isa.user.backend.r3

g¹�C com.sap.isa.businesspartner.backend.r3
The following classes are affected:

g¹�C Class ChangeStrategy
Method public boolean dequeueDocument has a new parameter of type SalesDocumentR3. In
releases SAP R/3 4.6C to mySAP ERP 2004, an update is performed for this sales document to remove
all locks. This was also performed in SAP Internet Sales (R/3 Edition) 4.0, but in a different place.
In SAP ERP 6.0, the ChangeStrategy class has been reimplemented. This new implementation is
com.sap.isa.backend.r3.salesdocument.rfc.ChangeStrategyERP. It enables a better lock
handling performance.

g¹�C Class Extension
The Extension class has been moved from com.sapmarkets.isa.backend.r3.salesdocument to
com.sapmarkets.isa.backend.r3base.

g¹�C Class ServiceR3IPC

g¹�, Method protected void customerExitBeforeDocumentCreation now uses the Map class
instead of the HashMap class.

g¹�, Method protected void customerExitAddKNVVParameters has been removed. Instead, a
new exit protected void customerExitBeforeHeaderAttributeCall is available. Note that
the function module ISA_PRICING_HDRDATA_GET is now used to read the header attributes.
This function module reads more attributes than those from table KNVV only.

g¹�C Class ShopBase
Method protected Set readSalesAreas() now returns the Set class instead of the Map class.

g¹�C Class StatusStrategyR3

g¹�, An additional parameter of type ReadStrategy has been introduced in the constructor of
StatusStrategyR3. This change also applies to the derived class StatusStrategyR3PI.

g¹�, ClassStatusStrategy is no longer used to search for sales documents, since a new search
framework has been implemented.

g¹�C Class WriteStrategyR3

20/38 PUBLIC 2014-01-16

5 Follow-Up Activities
5.3 Additional Follow-Up Activities for SAP E-Commerce

A new parameter of type JCoConnection has been introduced for method protected String
convertProductIds. This parameter was necessary because of a new back-end call that converts
material numbers from internal to external format and the other way round. The method also
issues a back-end exception now. This change also applies to method protected void
setItemProductInfo.

Changes in Functionality of Class WriteStrategyR3

•.æH# Method public void setPartnerInfo:

In 3.1 and 4.0, a manually entered ship-to address in B2B got the sold-to ID as key and not the
underlying ship-to ID. In SAP E-Commerce for SAP ERP 5.0, this behavior has been changed. If
you create a new ship-to address in the basket on the basis of an existing ship-to address, it gets the
ship-to ID as key in the ERP order.
EXAMPLE

Sold-to ID is 1000, ship-to ID is 1010. The ship-to address is “Becker Berlin, 12 Lagerhausstrasse”.
The end-user changes this address to “Becker Berlin, 20 Lagerhausstrasse”. As a result, a
manual address will appear in the ERP order (on header or on item level) with key 1010.
•.æH# Method protected void shipToDataToRFCSegment: A manually entered ship-to address gets its
language from the shop and not from the master data ship-to address (as in release 4.0).

5.3.3 Checking the Login Configuration

As of SAP E-Commerce 5.0, we recommend that you use the SU01-based login configurations. Check
the following sections if you have used an SU05-based login configuration in your source release.

Procedure

B2B XCM Default for Login Configuration

The default user configuration for ERP E-Commerce has changed from SU05
(R3_SU05Customer_LoginCustomerNo) to SU01 (R3_SU01UserContactPerson) in XCM. If you have not
changed the default setting, you will use the SU01-based configuration.
Review your login configuration settings in XCM (usertype) at Application configurations Customer <your
configuration> .

Role Assignment for Anonymous SU05 User

SAP E-Commerce 5.0 introduces special authorization roles. Authorization roles that contain the SD
authorization objects and new E-Commerce specific objects, for example, for viewing certain
documents in ERP E-Commerce, have been defined.
When ERP E-Commerce runs with an SU01-based login configuration, you have to assign certain roles
to the actual E-Commerce user (for example, SAP_ISA_B2B_FULL) and some to the anonymous user
that is defined in XCM (for example, SAP_ISA_B2B_RFC). For more information about the available

2014-01-16 PUBLIC 21/38

5 Follow-Up Activities
5.3 Additional Follow-Up Activities for SAP E-Commerce

roles, see the configuration documentation for ERP E-Commerce User Management in SAP Solution
Manager. You cannot assign authorization roles to SU05 users. In this case, all checks are performed
for the anonymous user.
Make sure that the anonymous user that you define in XCM has the corresponding role for the RFC
user (for example, SAP_ISA_B2B_RFC or SAP_ISA_B2C_RFC) and also the necessary application roles (for
example, SAP_ISA_B2B_FULL).

User Migration from SU05 to SU01

You can migrate your existing SU05 user accounts to SU01. After you have migrated the accounts, the
system generates an SU01 user the first time an SU05 user logs on to the upgraded ERP E-Commerce
application. For detailed information about the migration procedure, see the configuration
documentation for ERP E-Commerce User Management in SAP Solution Manager. Note that you must
assign the authorization role SAP_ISA_UADM_MANAGER to the anonymous RFC user for the migration
period in addition to the roles already assigned. Otherwise no new SU01 accounts can be created.

5.3.4 Replacing the Catalog Replication Mechanism

As of E-Commerce 5.0, an ABAP report replicates the ERP product catalogs to Search and Classification
(TREX). This replaces the trexr3 J2EE application. The report provides a Business Add-In (BAdI), which
you can use to adapt the retrieval and formatting of catalog data individually. The catalog data is
transferred directly from the ERP system to TREX using an RFC protocol. This means that the J2EE
Engine is not involved in the replication process and the running applications are not affected, neither
in terms of memory usage, nor in terms of CPU usage in the J2EE Engine.

Procedure
To start the report, call transaction ISA_CAT_REPLICATION. You can also schedule the report as a job.

5.3.5 Adjusting XCM Configuration and Creating Shops for

New Scenarios
If you are running the scenarios “Business-On-Behalf” and “Catalog and Order Management for
Internal Users”, you have to adjust the XCM configuration and create new shops. In both scenarios,
the sold-to party can be selected during the order creation process.

Procedure

Adjusting XCM Configuration

Change the parameter shopdata as follows:

¯‡q•ý4 If you run the “Business-On-Behalf” scenario, change it to r3shop_bob
¯‡q•ý4 If you run the “B2B for internal users”, change it to r3shop_agent

22/38 PUBLIC 2014-01-16

 5 Follow-Up Activities
5.4 Adjusting the XCM Configuration

Creating Shops

You cannot use existing shops for the two new scenarios. Instead, you have to create new shops as
follows:
1. Create a new shop.
2. Specify the scenario.
3. Copy the shop data from an existing shop that you have uploaded as described in Upgrading the Shop
Management Data [page 18].
rU/XÐûÞuŠr_+ëîVAÎ݉hL†úÜE4\1J—”Š:i«
N⁄7袇
¢‹¨õmS|‰ìù*A<ç·-‹ó˙!³ƒwÚp<ukÚX½¢œ“ùYr8²Ëã|o7öÚ SCšù
Já×V Mþüº.&na'DøÒŸ¡L⁄¶1�&;l:®…°~DM‘##—ºÿM^o&q¤M°bY<Ï•ØŠ´dQ´îi¾Z¸Òï�¢
rU/XÐóÞ,Š=_;ëµV Îñ‰b]LƒúÝE%\nJÉ”§:w«NÕ7Ù¢⁄
¤‹Û¨èm|¬ì°*d<å·-”óZ!łƒrÉp-u˛kÁXè¢ä“þYO8õËÛ|o7äÚ$SÚÆ
ÛßV Fþ÷º$&nv'Dø¿ŸÆLŠ¶�-&~lh®¨°aDˇ‘#–ºöMKo˜&?¤m°!Y˙ÏŒØÛ´UUQ�îM¾5¸¸ïb³Éÿı�:SÙÅ›+-Ç#,Kyoø%Þì⁄Ú$o¶(h´Ì

5.4 Adjusting the XCM Configuration

In SAP ERP 2004, the Extended Configuration Management (XCM) has been used to configure the
applications. The Customizing data was stored in XML files (scenario-config.xml and config-
data.xml) in the file system. As of SAP ERP 6.0, the Customizing data is stored in the database of SAP
NetWeaver AS Java. You have to check and adjust the configuration settings after the upgrade. For
information about using the Extended Configuration Management (XCM) Administration tool, see
the document Installation Guide - SAP ERP <Release> on <Operating System>: <Database>, section Using
Extended Configuration Management (XCM), or SAP Solution Manager.

Procedure

Entering Passwords

If you used the secure storage to encrypt passwords in the source release system, you need to reenter
each password after the upgrade. Whenever XCM data was modified, the secure storage was used.

Performing Adjustments to New Connection Concept

In the new release, each session is switched to https by default. To be able to log on to a Web application,
you have to check the XCM settings. Proceed as described below and adjust the XCM configuration:
1. Access the admin area of your Web application (http://<host>:<port>/<application name>/
admin).
2. Start the XCM Admin by following the link Extended Configuration Management (XCM) Administration.
3. Open the tree on the left by choosing Start General Application Settings Customer <Application
Name> <Application Name>config> .
4. Choose Edit.
5. Define the following parameters:
rU/é#Œ http.port.core: the http port of the NetWeaver Application Server
rU/é#Œ https.port.core: the https port of the NetWeaver Application Server
rU/é#Œ SSLEnabled:
rU/é#ù true = every session is switched to https

2014-01-16 PUBLIC 23/38

 5 Follow-Up Activities
5.4 Adjusting the XCM Configuration

ilGô−œ false = every session keeps the protocol that is currently used

NOTE

To be able to switch to the https connection, you need to enable https by using the Visual
Administrator of your SAP NetWeaver Application Server Java.

Checking the XCM Configuration

In the new release, some new parameters and components are required in the XCM configuration.
Furthermore, some of those that were used in the source release are no longer required. Those
parameters that are no longer used are highlighted in yellow and their description starts with
“OBSOLETE”. The description also contains information about what is used instead, or why the
parameter is no longer required.
You need to check the complete configuration of each web application and perform all required
configuration steps.

NOTE

You do not need to remove the obsolete parameters or components from the configuration.

ilG˙¯=Gõ#ùíß Ê.&$Št�ìˇ´:ÓÓØ¢œï2Ú\a%Q•rÇŁ\â>
€µóÓ“S>ÙÞÜ3.ªÆ´?uƒŸX‡µìá»°JxV¬"š˛xŽ{·ý[

E-Service Configuration Parameters

For E-Service, the table below provides you with an overview of all parameters that were used in CRM
4.0 and the parameters that are used in CRM 5.0 and higher:
CRM 4.0 CRM 5.0 and Higher
ATTACHMENTS attachments
— available_functions
COMPLAINT complaint
— email
FORGOT_PASSWORD_FORM forgot_password
IBASE ibase
ims ims
jco jco
— live_web_collaboration
— login
MINE_TYPES_ICONS mines_types_icons
PRODUCT_CATALOG product_catalog
PRODUCT_REGISTRATION product_registration
PRODUCT_SELECTION product_selection
REGISTER register
SERVICE_CONTRACT service_contract
SERVICE_REQUEST service_request
SOLUTION_SEARCH solution_search

24/38 PUBLIC 2014-01-16

 5 Follow-Up Activities
5.5 Migrating XCM Configuration Data Manually

CRM 4.0 CRM 5.0 and Higher

— store_locator
— transaction
— ui
SAP_API —
FIRST_FUNCTION —
IBASE_SELECTION —
ICSS_LWC_ENABLE —
REQUEST —
USER_ID —
EMAILSIZE —
FUNCTION_AVAILABLE —

õ-�±flleµf&NtEêgT½¹°>ł w®YûD„ ]"D
FˆÁu¿^:-•‰fl⁄>ûHkd ,àÉØ®Ýa4fi±FÓÌò

Replacing Component UI Configuration

The SAP configuration __backwardcompability_only__ for the component UI is no longer supported

as of SAP E-Commerce 5.0. If you are using this component configuration or your own customer
configuration that derives from this configuration, you need to create a new configuration for the
component UI derived from the SAP configuration default or default-hom.
õ-�±flleµf&NtEêgT«¹™>± Fw–YþD� œ"˘ bF7Áq£^9-‰‰…É>8ûRk6 aààØŽÝ~a:fiÊF>Ì®o…=*´ìÏ−ë/kfi'vìŸè²þX²9hËÞÀ³3†\ΤµéoQ@ÈyÔ4ÊuKõU3OÄŽDx„ø˚Z$ÒÅ%nx[,¢›OÁP>0ßg)žœ¿‹²˙8fiÇ;ŠCÞ÷/fnµÜüłx:ǼcGGˇºÿä
õ-u±fldeìfiNd˚ê+TŠ¹ƒ>ö Rw‰YèDÀ ˝"1 2FÁj®^1-‰‰QŁ>\ûyk- hàïØ‹Ý7aYfiÜFˆÌüo¬=(¶ìŁ−‹/zfi;ÖŸæ²þ\²whüÞܳO3Ù\뤟éXQcÈ$ÔF4¯u[KËU-3sÄ°D4„§˚?$ïÅ|nN['¢†OÈP30‚gž‚¿Ÿ²8™Ç'ŠEÞ÷-f ‡À±ł :ð:¼EGfˇçÿøٲ ’CAÙ‘^©¢j˛

5.5 Migrating XCM Configuration Data Manually

The Software Update Manager migrates the XCM configuration data automatically from the file system
to the database of SAP NetWeaver Application Server Java. If an error occurs, this data might not be
available after the upgrade and you will need to upload the data manually.

Prerequisites
You have access to the directory, in which the configuration files from the source release web
applications are stored.

Procedure
1. Access the SAP E-Commerce Administration Console of the Web application for which you want
to import the configuration (http://<HOST>:<PORT>/<APP-NAME>/Admin).
2. Follow the link Extended Configuration Management (XCM) Administration to access the XCM
Administrator.
3. Choose Start XCM Settings on the left-hand side.
4. Choose Edit (in the right upper corner). In the Edit mode, you can see two new text fields and
buttons below Upload configuration data from file-system.

2014-01-16 PUBLIC 25/38

 5 Follow-Up Activities
5.6 ADS: Performing Follow-Up Activities for Adobe Document Services

5. Enter the path to the corresponding files or use the Search button to select them from the wizard.
The file config-data.xml contains the component configuration data; file scenario-config.xml
contains the application configuration data.
NOTE

To locate the configuration files of your source release Web application, proceed as follows:
1. Access the XCM Administration application with the URL http://<HOST>:<PORT>/
<APP-NAME>/Admin/xcm/init.do.
2. Navigate to Start Options .
The path to the configuration files is displayed.
6. Choose Upload.
7. Choose Display to return to the display mode.
D�JŽgˆ½X¯@ß*1ı`ÜÜ&ëL‰L¹·†ÓX9¿›.úþÿ˘„ôíÔ−di8w¯kOÈÈ÷6”úÌı˛Ï]gıÝ¥ó)‡ÇÁ€ÈßZ= T¼˚ûR·`ˇýflØj£ØW−Ô©úƒ»’3−`CÏ�ø/¾ì£œ¶Ò_"
H#øŽ®²±xÔ~!1ò˛¯˚¿ˆxÖógD
åÕµµ)ß.íKÛ÷°f•˚œe¶˙½Y”ã=žSϘ-¤WÖ†s„—þ˛Ñ& kHïôx
D�Jfigˆ½P¯ˇße1−`⁄Üjëp‰X¹ð†ÇX7¿�.¥þ�˘£ô¢Ô½dr8x¯bO“È×6ËúäıÏNg„Ý£ó}‡ÁÁÃÈÞZ1 $¼}˚ÔR¤`ýrfl-Ød£ÃW�Ô´úÈ»Â3Ê$C⁄�‰/×친v¶Î_?"\HOø¹®«±zÔ~=1¶˛ý˚õˆhÖŒDˆåàµè)‹.×Kô÷⁄f•˚‚e¼ıS”ì=“SĘ+¤\WÖ⁄sä—ł˛×&'k1Ã=ô¤Y)s½ıGCp“IâÙÖ%›½$_~u14Ìñ>‡Ø,ZIÌ$˛fiN%Ú‚
D�J™g½H¯7ß 1š`’Ücëk‰˝¹ç†‘Xl¿M.ãþ�˘¥ô½Ô¯dr8z¯cOÈÈ%6Òú¨ı5ÏKg’ݤó8‡ÜÁ§ÈâZ
¼0˚ÿR¯`ýfl˙Ø`£ÇW„Ô¯ú‰»’3Š´CÀ

5.6 ADS: Performing Follow-Up Activities for Adobe Document

Services
To use Adobe Document Services (ADS) after the upgrade, you need to perform certain follow-up
activities. The follow-up activities mainly depend on the situation in your source release, meaning
whether ADS was configured in your source release.
The configuration information is available in SAP Library [external document] for your target release
under Function-Oriented View <Language> Adobe Document Services for Form Processing .

Procedure
D�J|BÔ ADS was not configured in your source release
Perform the complete ADS configuration as described in SAP Library [external document] for your
target release under Function-Oriented View <Language> Adobe Document Services for Form Processing .
In addition, check and define the Web Service Destination ConfigPort_Document. To do so, proceed
as described in SAP Note 1443819.
D�J|BÔ ADS was configured in your source release
Perform the following configuration steps:
D�J|B» D�Jfigˆ½P¯ˇße1−`⁄Üjëp‰X¹ð†ÇX7¿�.¥þ�˘£ô¢Ô½dr8x¯bO“È×6ËúäıÏNg„Ý£ó}‡ÁÁÃÈÞZ1 $¼}˚ÍR¤`ˆýfl ØV£ŁWÌÔèúÜ»Å3DhCœ�„/÷ìłœ1¶å_."HJø¹®¦±iÔ~<1ó˛ê˚æˆxÖåDå’µŠ)Ö.ðKâ÷²fÁ˚©e¼í
”£=ÈS
˜%

Create a new http destination to SAP NetWeaver Application Server ABAP with the name
FP_ICF_DATA_<SID>, where <SID> is your ABAP system ID.
For detailed information about the procedure, see SAP Library [external document] for your
target release under Function-Oriented View <Language> Adobe Document Services for Form Processing
Configuring Adobe Document Services for Form Processing (ABAP) Performing Basic ADS Configuration in
an ABAP Environment Creating the Destination Service for Communication with ADS .
D�JŽgˆ½X¯@ß*1ı`ÜÜ&ëJ‰S¹¥†ÓX;¿‹.¿þ ˘Łô¡Ô�da8h¯bO“ȸ6”úÛı5Ï�gßÝ‚ó8‡žÁÃÈÌZ# T¼k˚´Rõ`Hý–fl4Ø%£áWłÔ´ú‘»’3’4Cî�½/úì„œ7¶ó_?"H%øü®Ž±MÔ$~o1Ø˛¯˚¯ˆÖÓ+D$åÕµ«)fi.³Kł÷äf˚£

26/38 PUBLIC 2014-01-16

 5 Follow-Up Activities
5.7 Performing Follow-Up Activities for the System Landscape Directory

™üéXQ$ If you want to use Secure Socket Layer (SSL), perform the configuration steps as described in
SAP Library [external document] for your target release in the following:
™üéXQ- Function-Oriented View <Language> Adobe Document Services for Form Processing Configuring Adobe
Document Services for Form Processing (ABAP) Configuring the SSL Connection to ADS in an ABAP
Environment
™üéXQ- Function-Oriented View <Language> Adobe Document Services for Form Processing Configuring Adobe
Document Services for Form Processing (Java) Configuring the SSL Connection to ADS in a Java
Environment
™üéXQ$ After upgrading to SAP NetWeaver 7.4, you need to remove the Java parameter
Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.j
ts.ots.PortableInterceptor.JTSInitializer. To do so, proceed as described in SAP Note
1691054.
™üé½t–µÍĢ¥÷ŒN-=ˇjÞ[q½U8¥²òðõ˙„ò`,‰ :XîXúŸrÈp�ñ�6ˇtµçS}DQwh˘a#È
trΔP"Kpúô,ß¼Ez™áŸsjžø]çšbÏw@Ëù ¼Ýbí–„ÑÁÁ⁄×<ðm|÷C.“¸Kw˙¬Ð�+Êe[Øc¿r¬qé‚—A$À2Ë*`ú˛\˙hù7Ý0y¨<@Â6 §ÊB¼UÁ⁄²ÎOªõ—ô•NÒ1«"(ø!âɱ˜î׋œE¬×ŸÂ18É@=vÉG¢¿⁄’s¿ J,üÄ:^樫҂¯m%MUfi˧Žrñ+
™üéÏtŵšÄŸ¥äŒ-Rˇ:Þ0[l½A8³²ôð0˙Ðò,¯ 2XäXùŸdÈ5�Ł�dZtäµËSHD˜wR˘UaÈ3teÎŽP=Kvúã,„¼ÒzÀ
™üé·t–µÅÄA¥¸Œ^-fˇ&Þ>[z½8±²þðâ˙Œò,» &XìXéŸ`Èq�´�«E

5.7 Performing Follow-Up Activities for the System

Landscape Directory
The follow-up activities that you have to perform for the System Landscape Directory (SLD) depend
on the situation in your source release system, that is, whether SLD was configured or not.

Procedure
™üéXQK If the SLD was configured in your source release system, you must only perform the following two
actions to enable the use of SLD in the upgraded system:
™üéXQ$ Configure the user management
Define security roles and assign users to these roles.
Proceed as described in the SAP NetWeaver Library for your target release at: http://
help.sap.com/netweaver SAP NetWeaver 7.0 including Enhancement Package <n> Application Help
SAP Library <Language> SAP NetWeaver Administrator's Guide SAP NetWeaver Security Guide
Security Aspects for System Management Security Guide for the System Landscape Directory Configuring
SLD User Authorizations .
™üéXQ$ Update the SLD content and data model
We recommend that you download the latest SLD content from SAP Service Marketplace and
import it into the SLD. For more information, see SAP Note 669669.
™üéXQK If the SLD was not configured in your source release system but you want to use it in your target
release system, you must perform all configuration activities that are described in the document
User Guide - System Landscape Directory of SAP NetWeaver, section Changing the SLD Configuration available at
http://sdn.sap.com/irj/sdn/nw-sld.
In either situation, you also need to configure the following SLD components:

2014-01-16 PUBLIC 27/38

 5 Follow-Up Activities
5.8 BI Java: Performing Follow-Up Activities for Business Warehouse

×s%Í÷ SLD Data Supplier

Proceed as described in the SAP NetWeaver Library at:
http://help.sap.com/netweaver SAP NetWeaver 7.0 including Enhancement Package <n>
Application Help Function-Oriented View <Language> Solution Life Cycle Management by Key Capability
Software Life Cycle Management System Landscape Directory Configuring Systems to Connect to SLD
×s%ÍŸ For ABAP systems, navigate to: Connecting AS ABAP Systems to the SLD Configuring the SLD Data
Supplier: Default Settings
×s%ÍŸ For Java systems, navigate to: Connecting AS Java Systems to the SLD Setting Up the SLD Data Supplier
for Java-Based Systems
×s%Í÷ SLD Client
Proceed as described in the SAP NetWeaver Library at:
http://help.sap.com/netweaver SAP NetWeaver 7.0 including Enhancement Package <n>
Application Help Function-Oriented View <Language> Solution Life Cycle Management by Key Capability
Software Life Cycle Management System Landscape Directory Configuring Systems to Connect to SLD
Connecting AS Java Systems to the SLD Configuring the SLD Client
×sÀè9w¡xSæØo˝˙Â÷Ù˘•¿˙Ñ_í]Q—þ’s]
×sÊè9w©!S©ÈoGWÂËÙ•ø˙Å_ãKQÛþsr¢ÚŁ(jfó|Ô¹V„Ð
@rÐþ¢#¶˝¡ïïjõ]ª3F{W2Õ×õþ¬zo>˝fi˜QDT„¶ëÄ&Áj݆¨^ëÊ-f<1º-X}³íg”ŁϪòQ‡ÂÍkݳÓHì¸Âłñ¡=ˇdíáõÍ}í‘ícח˛éÀg¦hÚnł8JâWXxüà|ܵEú/©p±®�Hc0¼näÙ£º•ºflÜO'IžbD9gLËT˚�˝´,Õsó˝uÛ«fl�ªłÞX:E³Æà\×
×sËè2w±SìßoP^ÂÐÙH•ï˙“_¿Q²þqsq¢ŁŁjqókÔ‰VÉÐ8
Sr
Ðé¢b¶X¡¤ïyõ@ªq3]{F2uÕÌõã¬^oˆ˝qfi4Q@T”¶ÙÄ&•jJÝʨ˝ëÑIfS1Þ-Ø}†í"”´èªðQ‚ÂÚkܳÄHl¸›łÿ¡z=j|díÐõ−}Yí|í^

5.8 BI Java: Performing Follow-Up Activities for Business

Warehouse
If you have already used Information Broadcasting in the source release system, you only need to
perform configuration steps for Reporting and Analysis.
If you have not configured Information Broadcasting in the source release, you need to perform the
complete BI Java configuration, meaning the configuration of Information Broadcasting and Reporting
and Analysis.
To use relational BI Java connectors to integrate external data sources, you also need to complete the
necessary follow-up activities and configuration tasks for the Universal Data Integration (UDI).
To configure the required basic settings for portal and BI Java integration, perform the automated
configuration of BI Java.

Procedure

Configuration of Information Broadcasting

For information about the configuration of Information Broadcasting, see Customizing under SAP
NetWeaver Business Warehouse Settings for Reporting and Analysis Settings for Information Broadcasting .

Configuration of Reporting and Analysis

For information about the configuration of Reporting and Analysis, see Customizing under SAP
NetWeaver Business Warehouse Settings for Reporting and Analysis .

28/38 PUBLIC 2014-01-16

 5 Follow-Up Activities
5.8 BI Java: Performing Follow-Up Activities for Business Warehouse

Configuration of BI Print Service for Web Dynpro ABAP ALV

You need to create RFC destinations and Web Service destinations as described in Customizing under
Application Server SAP List Viewer (ALV) Set-Up Printing for Web Dynpro ABAP ALV
.

Configuration of UDI

For information about the configuration of UDI, see Customizing under SAP NetWeaver Business
Warehouse UDI Settings by Purpose. .
ilm|êÌù£ÞØ€[çWe—ˇz[}³^uŽÝ¿ýsÆû]˜ÊŒçáMaëxáÆ�ÛÌú᮫!Vãì�…sÎz’À¨ÈÅÉ^flûÕB"\RšãWO”%ïî−‡®dÙłmY.Š¢|˙−®§Õ8±jj0Ä kI`ãµ»NnÂqKe×G×ùc+åa�6çÑðÞÃØZxË“ÃÁ

Automated Configuration of BI Java

For information about the automated configuration of BI Java, see SAP Library [external document] for
your target release under Function-Oriented View <Language> Business Warehouse Configuration
Automatically Configuring BI Java .
ilg|êÌñ£⁄Øï[÷WO\e¹ˇ�[/³^�ŽÝ¥ý|s÷û
]Ê’ç÷Mpëxá©�žÌÅá−«V°ì´…6K¹z¦À‹ÈãÉ˙flÇÕ"˜Räã
”ïÃ−€®uÕłY\ŠÒ|~−¨§à8ôj0ò KIFãð»rn⁄qe®Gƒù¢+ï
ilg|êÌñ£⁄Øï[÷WO\e¾ˇq[(³^yŽÝ¥ý|s÷û
]Ê’ç÷Mpëxá©�žÌÅá−«V°ì´…6K¹z¦À‹ÈãÉ˙flÇÕ"˜Räã”ïÊ−€®d€ł&YiŠÕ|;−⁄§ó8åj#0· ˛I˚㥻 nâqweÐG…ù9+Àa›6ÅÑðÞºØ^Z8ËzÃØ™¯èèŬ=*_(“ò’^öQ!fi–$Q¬`2ÄúJ ‹ëÁÀÞM‚•ôŽÞılûŸÛ–òÑa‘bž“£–Å:)}Ø¥„]@‚µı»ë(ÛSyËs’˚¾ł½#j#
il|ªÌ¦£œØÓ[ÐW%\e£ˇ{[)³4^�ŽÝóýKsàûF]ZÊßç·M5ë˛áÜ�î̧áð«VÑ쪅sq‰z·À¾ÈðɘflÃÕB"ZRêã”gï+−„®d»ł3YzŠð|?−‡§à8 j-0· hIyãµ»JnÆqIeáGù~

2014-01-16 PUBLIC 29/38

This page is left blank for documents
that are printed on both sides.
A Reference
A.1 The Main SAP Documentation Types

A Reference

A.1 The Main SAP Documentation Types

The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software.

Cross-Phase Documentation

SAPterm is SAP’s terminology database. It contains SAP-specific vocabulary in over 30 languages, as

well as many glossary entries in English and German.
øßÕqò Target group:
øßÕqš Relevant for all target groups
øßÕqò Current version:
øßÕqš On SAP Help Portal at http://help.sap.com Glossary
øßÕqš In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes.
øßÕqò Target group:
øßÕqš Consultants
øßÕqš System administrators
øßÕqš Project teams for implementations or upgrades
øßÕqò Current version:
øßÕqš On SAP Help Portal at http://help.sap.com (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels. A collective security guide is available for SAP NetWeaver. This document contains
general guidelines and suggestions. SAP applications have a security guide of their own.
øßÕqò Target group:
øßÕqš System administrators
øßÕqš Technology consultants
øßÕqš Solution consultants
øßÕqò Current version:
øßÕqš On SAP Service Marketplace at http://service.sap.com/securityguide

Implementation

The master guide is the starting point for implementing an SAP solution. It lists the required installable
units for each business or IT scenario. It provides scenario-specific descriptions of preparation,

2014-01-16 PUBLIC 31/38

A Reference
A.1 The Main SAP Documentation Types

execution, and follow-up of an implementation. It also provides references to other documents, such
as installation guides, the technical infrastructure guide and SAP Notes.
¢ÐIfiÆœ Target group:
¢ÐIfiÆó Technology consultants
¢ÐIfiÆó Project teams for implementations
¢ÐIfiÆœ Current version:
¢ÐIfiÆó On SAP Service Marketplace at http://service.sap.com/instguides
The installation guide describes the technical implementation of an installable unit, taking into
account the combinations of operating systems and databases. It does not describe any business-related
configuration.
¢ÐIfiÆœ Target group:
¢ÐIfiÆó Technology consultants
¢ÐIfiÆó Project teams for implementations
¢ÐIfiÆœ Current version:
¢ÐIfiÆó On SAP Service Marketplace at http://service.sap.com/instguides
Configuration Documentation in SAP Solution Manager – SAP Solution Manager is a life-cycle
platform. One of its main functions is the configuration of business scenarios, business processes, and
implementable steps. It contains Customizing activities, transactions, and so on, as well as
documentation.
¢ÐIfiÆœ Target group:
¢ÐIfiÆó Technology consultants
¢ÐIfiÆó Solution consultants
¢ÐIfiÆó Project teams for implementations
¢ÐIfiÆœ Current version:
¢ÐIfiÆó In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system. The
Customizing activities and their documentation are structured from a functional perspective. (In order
to configure a whole system landscape from a process-oriented perspective, SAP Solution Manager,
which refers to the relevant Customizing activities in the individual SAP systems, is used.)
¢ÐIfiÆœ Target group:
¢ÐIfiÆó Solution consultants
¢ÐIfiÆó Project teams for implementations or upgrades
¢ÐIfiÆœ Current version:
¢ÐIfiÆó In the SAP menu of the SAP system under Tools Customizing IMG

Production Operation

The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver, and precedes the application operations guides of SAP Business Suite. The manual refers

32/38 PUBLIC 2014-01-16

A Reference
A.1 The Main SAP Documentation Types

users to the tools and documentation that are needed to carry out various tasks, such as monitoring,
backup/restore, master data maintenance, transports, and tests.
û3Ûú‹ Target group:
û3Ûú‹j System administrators
û3Ûú‹ Current version:
û3Ûú‹j On SAP Service Marketplace at http://service.sap.com/instguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed. It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks.
û3Ûú‹ Target group:
û3Ûú‹j System administrators
û3Ûú‹j Technology consultants
û3Ûú‹j Solution consultants
û3Ûú‹ Current version:
û3Ûú‹j On SAP Service Marketplace at http://service.sap.com/instguides

Upgrade

The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution. It provides scenario-specific descriptions of preparation, execution, and follow-up of
an upgrade. It also refers to other documents, such as upgrade guides and SAP Notes.
û3Ûú‹ Target group:
û3Ûú‹j Technology consultants
û3Ûú‹j Project teams for upgrades
û3Ûú‹ Current version:
û3Ûú‹j On SAP Service Marketplace at http://service.sap.com/instguides
The upgrade guide describes the technical upgrade of an installable unit, taking into account the
combinations of operating systems and databases. It does not describe any business-related
configuration.
û3Ûú‹ Target group:
û3Ûú‹j Technology consultants
û3Ûú‹j Project teams for upgrades
û3Ûú‹ Current version:
û3Ûú‹j On SAP Service Marketplace at http://service.sap.com/instguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release. Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG).
û3Ûú‹ Target group:

2014-01-16 PUBLIC 33/38

A Reference
A.1 The Main SAP Documentation Types

DQó¦Üy Consultants
DQó¦Üy Project teams for upgrades
DQó¦Ü Current version:
DQó¦Üy On SAP Service Marketplace at http://service.sap.com/releasenotes
DQó¦Üy In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)

34/38 PUBLIC 2014-01-16

Typographic Conventions

Example Description
<Example> Angle brackets indicate that you replace these words or characters with appropriate
entries to make entries in the system, for example, “Enter your <User Name>”.
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 Éæ:ºWÄ Words or characters quoted from the screen. These include field labels, screen titles,
pushbutton labels, menu names, and menu options.
Éæ:ºWÄ Cross-references to other documentation or published works
Example Éæ:ºWÄ Output on the screen following a user action, for example, messages
Éæ:ºWÄ Source code or syntax quoted directly from a program
Éæ:ºWÄ 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

2014-01-16 PUBLIC 35/38

 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

© Copyright 2013 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission
of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software
vendors.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission
of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software
vendors. National product specifications may vary.
These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only, without
representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP Group products and services are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP AG in Germany and other countries.
Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark
information and notices.

Disclaimer
Please see http://www.sap.com/corporate-en/legal/copyright/index.epx for disclaimer information and notices.

Documentation in the SAP Service Marketplace

You can find this document at the following address: http://service.sap.com/instguides

36/38 PUBLIC 2014-01-16

 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

© Copyright 2013 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained
herein may be changed without prior notice.