EHP5 for SAP ERP
6.0
July 2013
English
SAP ERP Subsidiary
Rollout rapid-deployment
solution: Software
Requirements
SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
© SAP AG
Page 2 of 10
SAP Rapid Deployment Solutions
Software Requirements
Copyright
© 2013 SAP AG or an SAP affiliate company. 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.
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/corporateen/legal/copyright/index.epx#trademark for additional trademark information and notices.
© SAP AG
Page 3 of 10
SAP Rapid Deployment Solutions
Software Requirements
Icons
Icon
Meaning
Caution
Example
Note
Recommendation
Syntax
External Process
Business Process Alternative/Decision Choice
Typographic Conventions
Type Style
Description
Example text
Words or characters that appear on the screen. These include field
names, screen titles, pushbuttons as well as menu names, paths and
options.
Cross-references to other documentation.
Example text
Emphasized words or phrases in body text, titles of graphics and tables.
EXAMPLE TEXT
Names of elements in the system. These include report names,
program names, transaction codes, table names, and individual key
words of a programming language, when surrounded by body text, for
example, SELECT and INCLUDE.
Example text
Screen output. This includes file and directory names and their paths,
messages, source code, names of variables and parameters as well as
names of installation, upgrade and database tools.
EXAMPLE TEXT
Keys on the keyboard, for example, function keys (such as F2) or the
ENTER key.
Example text
Exact user entry. These are words or characters that you enter in the
system exactly as they appear in the documentation.
<Example text>
Variable user entry. Pointed brackets indicate that you replace these
words and characters with appropriate entries.
© SAP AG
Page 4 of 10
SAP Rapid Deployment Solutions
Software Requirements
Contents
1
Required SAP Product and Software Component Versions ......................................................... 6
2
Required SAP Components .......................................................................................................... 6
2.1
Component Information....................................................................................................... 6
2.2
SAP Best Practices Add-ons and Transport ....................................................................... 8
2.3
System Status of Client Roles............................................................................................. 9
2.4
SAP Enterprise Extensions Sets and Business Functions ................................................. 9
2.5
SAP Notes and Messages .................................................................................................. 9
© SAP AG
Page 5 of 10
SAP Rapid Deployment Solutions
Software Requirements
SAP ERP Subsidiary Rollout rapid-deployment
solution: Software Requirements
1
Required SAP Product and Software Component
Versions
The table lists all software required to implement and run the solution:
Product
Product Version
Component
Comments
Required implementation tool
SAP Solution
Manager
SAP Solution
Manager 7.0
SAP EHP 1 for SAP
Solution Manager 7.0
SAP ERP
SAP ERP 6.0
SAP ERP 6.0
Application Server
ABAP
SAP ERP
Enhancement
Package
SAP Enhancement
Package 5 for SAP
ERP 6.0
* The logical component in SAP Solution Manager is an identifier provided by SAP for the
combination of product and product version. When selecting the SAP Solution Manager template
later on, the logical component provided by SAP will automatically be mapped with the logical
component in the customer system landscape with the same combination of product and product
version to set up access from SAP Solution Manager to the correct customer system.
The SAP ERP Subsidiary Rollout rapid-deployment solution is based on implementation
content of the SAP Best Practices package SAP Best Practices Subsidiary Integration in One
Client.
2
Required SAP Components
2.1 Component Information
2.1.1 SAP ERP Core Component 6.0 (SAP ECC 6.0)
You can find detailed information on Support Package Stack (SPS) definition for the Support
Releases of SAP ERP in SAP Note 774615 Support Package levels of ERP/ECC
installations/upgrades.
© SAP AG
Page 6 of 10
SAP Rapid Deployment Solutions
Software Requirements
2.1.2 SAP Enhancement Package 5 Support Package Stack 6 for
SAP ERP 6.0 Application Server ABAP ("SAP ERP 6.05
SPS06 AS ABAP")
SAP ERP 6.0-based SAP Best Practices packages focus mainly on the set of software components
bundled in SAP ECC 6.0. With the goal of a standardized installation process among baseline and
industry SAP Best Practices packages, a complete update of all ABAP software components of
Enhancement Package 5 for SAP ERP 6.0 is required.
You can find detailed information regarding the installation of Enhancement Package 5 for SAP ERP
6.0 in SAP Note 1298878 Installation of Enhancement Package 5 on SAP ERP 6.0.
To download Enhancement Package 5, go to the Software Distribution Center (SWDC) on the SAP
Service Marketplace at http://service.sap.com/swdc, choose Support Packages and Patches
Browse our Download Catalog SAP Application Components SAP ERP SAP ERP
ENHANCE PACKAGE EHP5 FOR SAP ERP 6.0
As per SAP Note 1064635, Support Package Stack (SPS) levels for SAP ERP are
synchronized across all Enhancement Package versions. Software components and
add-ons that are not touched within an Enhancement Package should have the support
package level assigned to the concurrent SPS of SAP ECC 6.0.
An overview (XLS) of all software components and their support package levels
combined in the various SPS is attached to note 1386389 SAP BAiO/BP: Stack
Information/Explanation for Used Products.
2.1.3 SAP Frontend Components (SAP GUI for Windows and SAP
NetWeaver Business Client)
Ensure that you have installed the latest and appropriate SAP frontend components.
The download path below leads you to an overview of how to install SAP frontend components and
how to apply patches. On the SAP Frontend Components navigation level, you can select the SAP
frontend components depending on your requirements.
To download the SAP frontend components, go to the Software Distribution Center (SWDC) on the
SAP Service Marketplace:
For SAP GUI at http://service.sap.com/swdc, choose Support Packages and Patches
Browse our Download Catalog SAP Frontend Components
For SAP NetWeaver Business Client at http://service.sap.com/swdc, choose Support
Packages and Patches Browse our Download Catalog SAP Frontend Components
NetWeaver Business Client NWBC NW Business Client 3.0
Regarding the SAP NetWeaver Business Client, DO NOT DOWNLOAD NWBC NW
Business Client 1.0 or NWBC NW Business Client 2.0. These versions are not
designed to be used with the current SAP Best Practices package Subsidiary Integration
in One Client.
Instead, download NWBC NW Business Client 3.0. This version is the correct one.
© SAP AG
Page 7 of 10
SAP Rapid Deployment Solutions
Software Requirements
You must use SAP NetWeaver Business Client 3.0 as the user interface connected to
your SAP ERP system. The minimum technical prerequisite is Enhancement Package 1
Support Package Stack 6 for SAP NetWeaver 7.0 Application Server ABAP (SAP NW
7.01 SPS06 AS ABAP).
In addition, you need to import the corrections referred to in note 1353538 SAP
NetWeaver Business Client 3.0 - Patch Collection.
Ensure that you have installed the latest versions of the SAP GUI and SAP Scripting
Engine. The use of older versions could result in serious activation errors.
2.1.4 SAP ERP 6.0: SAP Best Practices All-in-One Add-on and SAP
Best Practices Solution Builder Add-on
Software
Component
BP-ERP
(1)
BP-SOLBLD
(1)
Release
Version
Description
605
V[xy]
Use the latest version as
outlined in SAP Note
1301301 Release Strategy
for SAP Best Practices
Package ABAP Add-ons
SAP Best Practices All-in-One
based on SAP ERP 6.0 (SAP
ECC 600 EHP5)
70
V[yz]
Use the latest version as
outlined in SAP Note
1301301 Release Strategy
for SAP Best Practices
Package ABAP Add-ons
SAP Best Practices Solution
Builder on EHP5
(1)
You can find detailed information in the document Importing SAP Best Practices Add-ons
(ADDONINS.PDF) on the configuration DVD.
2.2 SAP Best Practices Add-ons and Transport
The following SAP Best Practices add-ons must be imported into the system:
BP-ERP 605V[xy]
This add-on contains the SAP Best Practices technical framework (e.g. BC-Sets, eCATTs,
print programs)
BP-SOLBLD 70V[yz]
This add-on contains the SAP Best Practices Solution Builder program
Always use the latest versions of the add-ons as outlined in SAP Note 1301301 Release
Strategy for SAP Best Practices Package ABAP Add-ons.
For more information, see the document Importing SAP Best Practices Add-ons (ADDONINS.PDF)
on the configuration DVD.
© SAP AG
Page 8 of 10
SAP Rapid Deployment Solutions
Software Requirements
Regular Updates Technical Environment
The technical add-ons provided by SAP Best Practices form the technical environment
required for the automated implementation of your SAP Best Practices version with the
SAP Best Practices Solution Builder. This technical framework is continuously updated,
providing enhanced, fixed, or additional technical objects that are required for the
technical implementation process.
SAP Best Practices is therefore offering updated versions of the add-ons on a regular
basis. Each updated add-on replaces the previous version in your system. You can find
more information about the currently available versions of the BP-ERP add-on and the
BP-SOLBLD add-on in SAP Note 1301301.
Since the solution scope file and the most current installation data files always
correspond to the current technical add-ons, you must always ensure you have the most
current versions in your system before the technical implementation of your SAP Best
Practices version begins.
The update of the technical framework has no impact on the scope or business content
of your SAP Best Practices version as it is described in the respective documentation.
2.3 System Status of Client Roles
The system cannot have any clients with the role productive client. If the system contains a
productive client, Extension Sets cannot be activated as required. Additionally, the automatic
installation of SAP Best Practices content using the SAP Best Practices Solution Builder is not
allowed, as BC Sets cannot be activated in the productive system. To check the settings of clients in
your system, use transaction SCC4.
2.4 SAP Enterprise Extensions Sets and Business
Functions
After installing SAP ERP, the following SAP ECC Extension Sets must be activated before the
activation of the SAP Best Practices Baseline package for the headquarters. Refer to the Quick
Guide of the SAP Best Practices Baseline package for the Headquarters’ country and ensure the
correct business functions have been activated.
2.5 SAP Notes and Messages
If issues become apparent after the shipment of this SAP ERP rapid-deployment solution for
subsidiary rollout (and hence of this document), a SAP Note exists to cover such eventualities.
Before you start the activation of the related SAP Best Practices scope, check the latest
version of the SAP Note below to obtain updates and corrections for problems that do
not become apparent until after shipment.
All SAP Notes have to be applied to the system via the SAP Note Assistant. All SAP
Notes mentioned below need to have the implementation status Completely
Implemented. Some SAP Notes require manual action before you set them to status
Completely Implemented.
To avoid activation errors as a result of generating loads, you must perform a mass
generation using transaction SGEN as described in SAP Note 481548.
© SAP AG
Page 9 of 10
SAP Rapid Deployment Solutions
Software Requirements
SAP Note
Description
Component
1650301
SAP Best Practices for Subsidiary Integration in One
Client V1.605
SV-SMB-AIO-BNT-SUB
In addition to the list of SAP Notes below, all SAP Notes mentioned in the Quick Guide of the SAP
Best Practices Baseline Package for the headquarters’ country must be implemented if still relevant
within the current SPS level (and if not stated otherwise in the SAP Note mentioned above), as well
as the SAP Notes mentioned in the Quick Guide of the SAP Best Practices Baseline Package for the
subsidiary’s country, as some notes might be country-specific:
SAP
Note #
Description
Comp
onent
Area
Remark
10560
Tax determination for plant
abroad
SD-BIL
Usage
Please refer to the configuration guide document
B10 for more details
459296
INTRASTAT/EXTRASTAT
: Triangular deals intercompany
SD-FTGOV
Usage
Please refer to the configuration guide document
B10 for more details
126192
Ext. Interfaces/BAPIs/ALE
FI-APAP-M
Usage
Please refer to the configuration guide document
B11 for more details
1432358
Starting application with
Loading Animation
BC-WDABA
Activation
1229004
Variances: Message KV
169 - no target costs
CO-PCOBJ
Usage
Cost objects belonging to a cross-company
controlling area with different company code
currencies.
1629093
IDOC - INVOIC: Tax
juristiction code TXJCD (3)
SD-EDIOM-IV
Usage
Transfer of tax jurisdiction code to E1EDP04
1638436
IDOC - INVOIC: Tax
juristiction code TXJCD (4)
SD-EDIOM-IV
Usage
Transfer of tax jurisdiction code to E1EDP04
Usage
Only implement the following SAP Note in addition to the SAP Notes as listed above if
you use SAP NWBC 3.0.
SAP Note
Description
Component
Area
1524776
Change purchase
order opens
purchase order in
display mode
EP-PCT-PUR-BP
Usage
© SAP AG
Remark
Page 10 of 10
