RE Quick Guide

EHP5 for SAP ECC 605 July 2012 English

Quick Guide for Implementing the SAP Real Estate Management Rapid-Deployment Solution (RDS)

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany

SAP Best Practices

Quick Guide for Implementing SAP Real Estate Management rapid-deployment solution

Copyright © 2010 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 prio r notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, PostScript, and Reader are either trademarks or registered registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWinare MultiWinare trademarks or registered trademarks of Citrix Systems, Inc. ®

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C , World Wide Web Consortium, Massachusetts Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, Clear Enterprise, SAP BusinessObjects BusinessObjects Explorer, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP France in the United States and in other countries. All other product and service service names mentioned are the trademarks of their respective respective companies. companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

© SAP AG

Page 2 of 34

SAP Best Practices


Copyright © 2010 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 prio r notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, PostScript, and Reader are either trademarks or registered registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWinare MultiWinare trademarks or registered trademarks of Citrix Systems, Inc. ®

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C , World Wide Web Consortium, Massachusetts Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, Clear Enterprise, SAP BusinessObjects BusinessObjects Explorer, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP France in the United States and in other countries. All other product and service service names mentioned are the trademarks of their respective respective companies. companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

© SAP AG

Page 2 of 34

SAP Best Practices


Icon

Meaning Caution Example Note Recommendation Syntax

Icons 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.

Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

© SAP AG

Page 3 of 34

SAP Best Practices


Content 1

About this Quick Guide .......................................................................................... 6

2

Solution Overview .................................................................................................. 6

3

Implementation Methodology ................................................................................ 6

4

SAP System Requirements (Administrator) .......................................................... 7 4.1

SAP Software Component Installation Check ....................................................... 7

4.2

Required SAP Software Components ................................................................... 7 4.2.1

SAP ERP Software Components ............................................................................ 8

4.2.2

SAP Best Practices Add-on and SAP Best Practices Solution Builder Add-on ...... 9

4.2.3

SAP Solution Manager ..........................................................................................10

4.3

Receiving the Software at the Correct SP Level ................................................. 11

4.4

Required SAP Notes and Messages ................................................................... 11

4.5

Troubleshooting ................................................................................................... 12

5

System Preparation for SAP RDS Implementation (Administrator/ Consultant) . 13 5.1

SAP Enterprise Extensions Sets and Enterprise Busin ess Functions ................ 13

5.2

Installation of the SAP Best Practices Add-On.................................................... 14

5.3

Installation of the SAP Best Practices Solution Builder ....................................... 15

5.4

General Client Settings ........................................................................................ 16 5.4.1

Creating User for Activation of SAP RDS Content ...............................................16

5.4.2

Deselecting Activation Links in BC Sets ...............................................................17

5.4.3

Maximum W ork Process Run Time ...................................................................... 17

5.4.4

SAP Scripting ........................................................................................................18

5.4.5

Set Default Timeout for HTTP and HTTPS Services ............................................19

5.5

Prepare S ystem User for Content Activation ....................................................... 20 5.5.1

SAP Software Change Registration (SSCR): Developer Key ..............................20

5.5.2

Activation Language .............................................................................................20

5.5.3

User Settings for Activation...................................................................................20

5.5.4

Deactivate Info Dialog Box on Dynpro Size Check .............................................. 20

5.5.5

Unicode Settings ...................................................................................................21

5.5.6

Allow GUI Scripting ...............................................................................................21

5.5.7

Set Decimal Notation and Date Format ................................................................21

6

Implementation of RDS Business Content (Consultant ) ..................................... 22 6.1

SAP Real Estate Management RDS Implementation ......................................... 22 6.1.1

Installation with the Existing SAP ERP Landscape .............................................. 22

6.1.2

Installation in a Sandbox or Test Environment – Baseline Germany as a basis ..22

6.1.2.1

General ................................................................................................................ 22

6.2

Installation of Language/Country-Specific Content ............................................. 24

6.3

RDS Content Installation Variants ....................................................................... 24 6.3.1

Manual Implementation .........................................................................................24

6.3.2

Solution Manager Template based Implementation .............................................24

6.3.2.1

Checking the System Landscape in S AP Solution Manager .............................. 24

6.3.2.2

Creating the SAP Solution Manager Project and Template Selection ................ 25

6.3.2.3 Adjust the Process Scope in SAP Solution Manager .......................................... 26 6.3.3

Automated Implementation using SAP Best Practices Solution Builder ..............27

6.3.3.1

Getting the Business Content for Activation ........................................................ 27

6.3.3.1.1

Getting the Solution Scope File....................................................................... 27

6.3.3.1.2

Getting the Installation Data Files ................................................................... 28

© SAP AG

Page 4 of 34

SAP Best Practices


6.3.3.2

Create Installation Folder for Content Activation ................................................. 28

6.3.3.3

Import Solution Scope File to the SAP system ................................................... 28

6.3.3.4

Maintain User Settings: Path to Installation Data ................................................ 29

6.3.3.5

Maintain User Settings: Path to Documentation ................................................. 30

6.3.3.6

Maintain authorization for activation .................................................................... 30

6.3.3.7

Upload Installation Data ...................................................................................... 31

6.3.3.8 Activating a Solution ............................................................................................ 31 6.3.3.9 7

© SAP AG

Processing General Errors during Installation ..................................................... 33 Remarks .............................................................................................................. 34

Page 5 of 34

SAP Best Practices


Quick Guide Implementing the SAP Real Estate Management Rapid-Deployment Solution (RDS) (EN) 1 About this Quick Guide This Quick Guide helps consultants and customer project members implement the SAP Real Estate Management rapid-deployment solution. The guide focuses on the technical implementation aspects and usage of the SAP Solution Manager and the SAP Best Practices Solution Builder add-on. The document mentions all required steps for a successful implementation of the SAP Real Estate Management rapid-deployment solution and directs you to more detailed documentation if necessary. The System Landscape Prerequisites section lists all system pre-requisites that have to be fulfilled by customers before the implementation of the rapid-deployment edition can start. Installation of the required systems is not part of the SAP Real Estate Management rapiddeployment solution’s delivery scope. The Preparation Activities section explains the tasks that need to be carried out specifically for the implementation of the SAP Real Estate Management rapid-deployment solution. In the Implementation section you will be guided step-by-step through the actual technical implementation process. What you actually implement and configure is subject to a previous scoping effort. The SAP Real Estate Management rapid-deployment solution addresses core functional needs implementing Lease and Space Management, Maintenance and Repair and Investment and Construction management. From a technical implementation perspective the content of this guide is valid for the SAP Real Estate Management rapid-deployment solution. There are generally two deployment options of the SAP Real Estate Management rapid-deployment solution: one for an implementation in a sandbox / test environment for rapid prototyping and one for implementation in an existing ERP environment. This guide is applicable for both cases. For implementation in an existing ERP environment, please take into consideration, that the solution itself has to be adapted to the existing environment.

2

Solution Overview

The SAP Real Estate Management rapid-deployment solution: 

Is based and tested on EHP5 for SAP ECC 6.0



Provides an accelerated deployment of the required configuration settings for Real Estate Management, in more detail Lease and Space Management, Maintenance and Repair Management and Investment and Construction Management.



Is targeted towards customers that: o



3

Already run operational SAP ERP

Is delivering one solution file for SAP ERP

Implementation Methodology

Overall project guidance is provided by a specific implementation roadmap, the Implementation Methodology for SAP Real Estate Management rapid-deployment solution, which is a phased, delivery-oriented methodology that streamlines implementation projects for solution packages, guiding project teams through the following phases: 

Discovery



Project Preparation



Realization

© SAP AG

Page 6 of 34

SAP Best Practices




Go-Live & Closing

The methodology supports project teams with templates, tools, questionnaires and checklists, including guidebooks and accelerators to ensure the quick and pragmatic implementation of rapid-deployment solutions. To get access to the methodology, approach your SAP Consulting contact.

SAP Real Estate Management RDS Content Implementation Options The SAP Real Estate Management rapid-deployment solution can be implemented as a sandbox implementation based on the SAP Best Practice Baseline Package for Germany V1.605 as well as on a customer specific environment. The first options require the Solution Scope File for automated business content activation. In case of a sandbox implementation based on German Baseline no additional effort is needed. The Solution Scope File downloading procedure is described in the paragraph Getting the Solution Scope File In case of a customer specific implementation the manual implementation following configuration guide and a detailled analysis of personalization and necessary adaption of the describe configuration is required.

SAP Real Estate Management RDS Content Implementation Variants For the implementation of the SAP Real Estate Management rapid-deployment solution, the following implementation variants are offered (see paragraph RDS Content Installation Variants): 

Manual Implementation following configuration guides



SAP Solution Manager Template based Implementation



Automated Implementation using SAP Best Practices solution builder (prerequisite: SAP Best practice Baseline Package for Germany V1.605)

4

SAP System Requirements ( A d m i n i s t r a t o r )

This chapter summarizes the prerequisites that are assumed to be delivered by the customer, that is, in a phase preceding the actual implementation project. Note that the setup of the system landscape is not part of the rapid-deployment solution delivery scope. The customer needs to provide the system landscape, that is, install the required software components, to enable the project team to implement and configure the scope of the SAP Real Estate Management rapid-deployment solution. During this phase, SAP provides advice on aspects of the system landscape and the components required. In addition to the following information, the SAP rapid- deployment solution’s specific implementation methodology provides an installation related checklist covering additional requirements.

4.1 SAP Software Component Installation Check Before the SAP Real Estate Management rapid-deployment solution content implementation activities can be executed, the SAP project team performs a check of the software installation based on the requirements provided in the following steps of this guide. Based on the results, the project team advises the customer on any missing steps to be performed.

4.2 Required SAP Software Components The deliverables of SAP Real Estate Management rapid-deployment solution were developed and tested in a system landscape with specific SPS levels. If the SPS level in your system is

© SAP AG

Page 7 of 34

SAP Best Practices


different, there may be errors during the activation. You may be able to perform the activation activities manually using the configuration guides, but errors may still occur.

Make sure that your system meets the minimum SPS level requirements. In case your system has an exceptional SPS level compared to the SAP Real Estate Management rapid-deployment solution requirements, issues might occur. If you need a higher SPS level in your system, for example because of additional functionality, FIRST import and activate the rapid-deployment solution SPS levels as mentioned below, THEN upgrade your system to the current SPS level. The support package levels relevant for the SAP Real Estate Management rapid-deployment solution V2.605 are listed together with the required components in the next sections.

4.2.1

SAP ERP Software Components

SAP Real Estate Management is built for customers who already run their business in SAP ERP, SAP ERP EhP5. If customers would also like to run the SAP Real Estate Management rapid-deployment solution in a sandbox or test environment, they must then also install SAP Best Practices Baseline package for Germany V1.605. You can find detailed information on SPS definition for SRs of SAP ERP in SAP Note 774615 – Support Package levels of ERP/ECC installations/upgrades . SAP enhancement package 5 for SAP ERP 6.0 With the goal of a standardized installation process among Baseline, industry and SAP BP SAP SCM rapid-deployment solution packages, a complete update of all ABAP software components of enhancement package 5 for SAP ERP 6.0 is required. For more information on the installation of enhancement Package 5 for SAP ERP 6.0, see SAP Note 1298878 - Installation of Enhancement Package 5 on SAP ERP 6.0 . To download the SAP Enhancement Package 5, go to the Software Distribution Center (SWDC) on the SAP Service Marketplace: https://service.sap.com/swdc, then choose Support Packages and Patches  Browse our Download Catalog  SAP Application Components  SAP ERP  SAP ERP ENHANCE PACKAGE  EHP5 FOR SAP ERP 6.0 https://service.sap.com/swdc, then choose Download  Support Packages and Patches  Support Packages and Patches - Entry by Application Group  SAP Application Components SAP ERP  SAP ERP ENHANCE PACKAGE  EHP5 FOR SAP ERP 6.0



The following software components are required in their respective SPS levels for the SAP ERP rapid-deployment solution for employee and manager self service: Software Component

Release

SAP ERP

6.0

SAP ERP Enhancement Package

EhP5 for SAP ERP 6.0

SPS/SP Level

Description SAP 6.0

SP8

SAP Enhancement Package 5 for SAP ERP 6.0

The required software components and SPS levels are usually downloaded using the Maintenance Optimizer of SAP Solution Manager . If you need to download the software manually from the Software Distribution Center on Service Marketplace, follow the path below: Installation:

© SAP AG

Page 8 of 34

SAP Best Practices


https://service.sap.com/swdc  Installations and Upgrades SAP Application Components  SAP ERP.

Browse our Download Catalog





As outlined in SAP Note 1064635, SPS levels for SAP ERP are synchronized throughout all enhancement package versions. Software components and addons not used within an enhancement pack should have the SP level assigned to the concurrent SPS of SAP ECC 6.00. For an overview of all software components and their Support Package levels combined in the various SAP ERP Support Package Stacks, see SAP Note 1386389. You can also find information about software components and a typical landscape in the Software Requirements document. See the step-by-step guide: Start → Confirm Installation.

4.2.2

SAP Best Practices Add-on and SAP Best Practices Solution Builder Add-on

The following SAP Best Practices Add-ons must be imported into the system: Software Component BP-ERP

(1)

BP-SOLBLD

BP-CANW

(1)

Release

Version

Description

605

Vx*

SAP Best Practices Allin-One based on EhP5.

70

702

Vx*

*Use the latest version 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 AddOns (ADDONINS.PDF) on the configuration DVD.

Vx*

This Add-on contains the SAP Best Practices technical framework (for example, BC-Sets, eCATTS, print programs). Best Practices Solution Builder. This Add-on contains the SAP Best Practices Solution Builder program. Technical add-on; facilitates handling of eCATT and BC set objects.

(1)

Additional and detailed information is listed in the document Importing SAP Best Practices Add-Ons (ADDONINS.PDF) on the configuration CD.

To download the SAP Best Practices ERP Add-ons, go to the SAP Software Download Center (SWDC) on the SAP Service Marketplace: https://service.sap.com/swdc , then choose Installations and Upgrades  Browse our Download Catalog  SAP Best Practices  SAP BP BASELINE PACKAGES  BASELINE PACKAGE – V1.-V2.605  Installation. From the Downloads area, select the Download Object ‘Config: SAP Business All-in One’. To activate the SAP Best Practices Solution Builder: 2.

Run the following activity: Transaction Code

© SAP AG

SICF

Page 9 of 34

SAP Best Practices


Menu

SAP Easy Access Menu  Tools  Administration  Administration  Network  HTTP Service Hierarchy Maintenance

3.

On the Maintain Services screen, select Execute for the defaulted Hierarchy Type SERVICE, Language ENGLISH.

4.

On the Maintain service screen, expand the Virtuelle Hosts / Services node as follows and activate the services listed below: Virtual Hosts/ Services

Status

Remarks

Default_host > sap > public > myssocntl

Active

Set the MYSAPSSO2 Cookie According to mysapsso2 Header Field

Default_host > sap > bc > bsp > smb > sc_scoping_tool

Active

BP Scoping Tool

5.

On locating the services (or relevant nodes), from the navigation menu select Service/Host > Activate.

6.

The system displays an informational dialog box. Choose Continue.

7.

Choose Back to navigate back to the SAP Easy Access screen.

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 Solution Builder. This technical framework is continuously updated providing enhanced, fixed, or additional technical objects required for the technical implementation process. SAP Best Practices therefore offers updated versions of the add-ons on a regular basis. Each updated add-on replaces the previous version in your system. For more information about the currently available versions of the add-on BP-ERP and the addon BP-SOLBLD, see SAP Note 1301301 (The relevant content and execution of SAP Note 1301301 is included in the section SAP Notes and Messages of this document.) Since the solution scope file and the most current installation data files always correspond to the current technical add-ons, you always need to make sure the most current versions are in your system before the technical implementation of your SAP Best Practices version starts. The update of the technical framework has no impact on scope or business content of your SAP Best Practices version as it is described in the respective documentation.

4.2.3

SAP Solution Manager

For the implementation of the SAP ERP rapid-deployment edition, a SAP Solution Manager system is recommended. SAP Solution Manager in general is needed for installing and managing maintenance certificates, Enhancement Packages and upgrades. In the context of SAP Rapid-Deployment solutions, implementation content is delivered via SAP Solution Manager templates. It is assumed that a productive SAP Solution Manager system (7.0 or higher) is available in the customer’s system landscape. If the customer is already using other SAP products (for example SAP ERP), the customer should already have SAP Solution Manager in the system landscape.

© SAP AG

Page 10 of 34

SAP Best Practices


For more information about SAP Solution Manager, see the SAP Library documentation for SAP Solution Manager at http://help.sap.com  SAP Solution Manager , or at http://service.sap.com/solutionmanager . Component

Mandatory

Remark

Recommended

If you do not wish to use SAP Solution Manager to leverage the SAP Real Estate Management rapid-deployment solution’s implementation content, see RDS Content Installation Variants

SAP Solution Manager SAP Solution Manager 7.0 (or higher) ABAP

Solution Manager suggested SP: 

Solution Manager 701: at least SP 18 is needed (for SP lower than SP24 note 1579267 has to be implemented)



Solution Manager 710: at least SP01

It is assumed that the customer already has the SAP ERP system installed and configured.

4.3 Receiving the Software at the Correct SP Level For the delivery of the software, an installation number and a corresponding license agreement are required. An S-USER is required to order software in the Software Catalog or download from SAP's Software Distribution Center within SAP's Service Marketplace (SAP's SWDC in SMP). You can only order unrestricted SAP software. Contact the SAP contract department to ask for a physical shipment or create a customer message on component XXSER-GEN-CONTR. For downloading SPSs, use the Maintenance Optimizer within your SAP Solution Manager. You can also select relevant SPs manually one-by-one via SAP's SWDC in the SMP:

Supp ort Packages (for ERP): https://service.sap.com/swdc  Software Download Center  Support Packages and Patches  Entry by Application Group  SAP Application Components  SAP ERP  SAP ERP ENHANCE PACKAGE  EHP5 FOR SAP ERP 6.0

Only the current Service Release (SR) is delivered to SAP customers or partners via SAP's SWDC in SMP and standard delivery (for example, Software Catalogue). If the required SPS for correct SAP BP packages activation is based on SPS level LOWER than the current SR, the request for the necessary SPS is handled via a customer message. For details, see the SAP Note 925690 Standard Ordering Procedures for SAP Software (https://service.sap.com/sap/support/notes/925690).

4.4 Required SAP Notes and Messages Issues might become apparent after the shipment of the SAP Real Estate Management rapiddeployment solution (and hence also of this document).

Before you start the building block installation process, check the latest version of the SAP Note below to obtain updates and corrections for problems that do not become apparent until after shipment. SAP

© SAP AG

Description

Remark

Page 11 of 34

SAP Best Practices


Note #

1672804

SAP Real Estate Management rapiddeployment solution (https://service.sap.com/sap/support/notes/167 2804)

Always check the SAP Note for SAP ERP rapiddeployment solution for the employee and manager self service for updates on the implementation.

All notes have to be applied to the system using the SAP Note Assistant (transaction SNOTE). All notes mentioned below need to have the implementation status Completely implemented . Note that some SAP Notes require manual action before you set them to the Completely implemented status. To avoid activation errors as a result of generating loads, you have to perform a mass generation using transaction SGEN as described in the SAP Note 481548 . Implement the following SAP Notes before proceeding with the next steps in this guide: SAP Note #

Description

1060253

Problem in activating BC Sets -> check if relevant

1577247

Message about failed authority check not passed on 1301301 refers to other SAP Notes. Always check the referenced Notes and follow the instructions.

1301301

Release Strategy for SAP Best Practices Package ABAP Add-ons

1588269

Solution Builder

1645206

Corrections for integratn of down paymnt chain in purchasing

The corrections for the add-on are attached to this add-on specific Note. Always apply the correction transport for the corresponding add-on. Additional information for the Solution Builder installation.

4.5 Troubleshooting If errors occur during the installation process, proceed as follows: 1.

Check for troubleshooting notes in the step description of the configuration guide.

2.

Check for SAP Notes on the relevant topic in the SAP Notes section in the building block configuration guide.

3.

Log on to the Service Marketplace and search for problem-related SAP Notes. If the problem persists, proceed as follows: - Only if the problem relates to the SAP Real Estate Management rapid-deployment solution preconfiguration, open a customer message with the component SV-RDS-ERP. - If the problem is a general one, indicate the relevant application component.

© SAP AG

Page 12 of 34

SAP Best Practices

5


System Preparation for SAP RDS Implementation (A d m i n i s t r a t o r / C o n s u l t a n t )

Before the consultant can start with the automated SAP Real Estate Management rapiddeployment solution content implementation, the following steps need to be performed. In case you are implementing SAP Real Estate Management rapid deployment solution in an environment, where the SAP Best Practices Package for Germany is activated, please follow the instructions as described in the Quick Guide for that package and take care, that also the Real Estate Extension is activated additionally.

5.1

SAP Enterprise Extensions Sets and Enterprise Business Functions

Use After installing SAP ERP, the following SAP ECC extension sets need to be activated before you start activation of the SAP Real Estate Lifecycle Management.

The activation of Enterprise Extensions, Business Functions and Business Function Sets will change your system and cannot be rolled back. For more details regarding the impact, check the documentation of the related extension or business function.

Ensure that you have activated all Enterprise Extensions Sets and Enterprise Business Functions as outlined below before you create the client in which the SAP Real Estate Lifecycle Management Package shall be activated (see chapter Creation of Client for SAP Best Practices Activation below).

Do NOT activate additional Enterprise Extensions or Business Functions because this will result in serious errors during activation of SAP Best Practices. Activate ONLY the Enterprise Extensions and Business Functions as listed below.

Procedure 1.

8.

Run the following activity: IMG Menu

Activate SAP ECC Extensions

Transaction Code

SFW5

On the Switch Framework: change Business Function Status screen, select each of the following entries (by marking the column Planned Status) and then choose the Activate Changes button.: Enterprise Extensions

Planned Status

Remarks

EA-FIN

On

Needed for scenario Cash Management

EA-FS

On

Needed for scenario Cash Management

EA-PLM

On

Only needed if you want to install one or more of the scenarios that belong to the area Service and full scope, respectively.

EA-TRV

On

Only needed if you want to install one or more of the scenarios that belong to the area Service and full scope, respectively.

© SAP AG

Page 13 of 34

SAP Best Practices

1.

2.


Business Functions

Planned Status

Remarks

LOG_FI_DPC_MM_1

On

Down Payment Chains

OPS_PS_CI_1

On

Project System Enhancements in functionality & Usability

LOG_FI_DPC_MM_1

On

Subcontractor Mgmt (DwnPayChain)

LOG_MM_CI_1

On

Materials Management

LOG_MM_CI_2

On

Material Management Purchasing

LOG_MM_CI_3

On

Enhancements in Procurement

LOG_MM_MAA_1

On

MM Multiple Account Assignment

LOG_MMFI_P2P

On

MM, Integration MM and FI

OPS_PS_CI_1

On

Project System Enhancements

RE_CRE_MISC

On

Corporate Real Estate

RE_GEN_CI_1

On

Real Estate

RE_GEN_CI_2

On

Real Estate 2

RE_GEN_CI_3

On

Real Estate 3

Access the activity using the following navigation path: Transaction code

SPRO

SAP ERP IMG menu

Flexible Real Estate Management (RE-FX) Estate Extension

 Basic

Settings

 Activate

On the Change View “Activate Real Estate Extension”: Details screen check / create the following settings. Field Name

Entry Value

Activate Real Estate Extension

X

3.

Save your entry and select a customizing request if required.

4.

Choose Back.

Result The Real Estate Extension is active.

5.2 Installation of the SAP Best Practices Add-On The following SAP Best Practices content add-on have to be installed to use the automated installation of the SAP Real Estate Management rapid-deployment solution: Software Component

Release

Version

BP-ERP

604Vx

Always use the latest available version as outlined in SAP Note 1301301 (Release Strategy for SAP Best Practices Package ABAP Add-ons) (https://service.sap.com/sap/support/notes/1301301 )

© SAP AG

Page 14 of 34

Real

SAP Best Practices


Use If possible, Business Configuration Sets (BC Sets) for maintaining customizing settings and Extended Computer Aided Test Tool procedures (eCATT) for master data creation are used for SAP Best Practices. This use automates the configuration of the SAP Best Practices scenarios. BC Sets and eCATTs were delivered as so-called add-on transport files with the SAP Best Practices ADD-ON BP-ERP 605Vx. Import these files into your ERP system if you want to make use of the automated configuration.

Procedure 1.

Download the Add-On BP-ERP 605V6 from the Software Distribution center: http://service.sap.com/swdc → Installations and Upgrades → Entry by Application Group → SAP Rapid Deployment Solutions → SAP Real Estate Management rapid-deployment solution

2.

Import the SAR file into your SAP ERP system using transaction SAINT.

Result BC Sets and eCATTs are now available in your ERP system and can be used in combination with the SAP Best Practices Solution Builder for automated configuration of BP ERP scenarios.

5.3 Installation of the SAP Best Practices Solution Builder The following SAP Best Practices add-ons have to be installed to use the automated installation of the SAP Real Estate Management rapid-deployment solution: Software Component

Release

Version

BP-SOLBLD

70Vx

Always use the latest available version as outlined in SAP Note 1301301 (Release Strategy for SAP Best Practices Package ABAP Add-ons) (https://service.sap.com/sap/support/notes/1301301 )

Use Use the SAP Best Practices Solution Builder to easily install the complete SAP Best Practices package or selected scenarios at minimum time. The SAP Best Practices Solution Builder is a tool that guides you step-by-step through the installation process directly in the system.

Procedure 1.

Download the Add-On BP-SOLBLD 70Vx from the Software Distribution center: http://service.sap.com/swdc → Installations and Upgrades → Entry by Application Group → SAP Rapid Deployment Solutions → SAP Real Estate Management rapid-deployment solution

2.

Import the SAR file into your SAP system using transaction SAINT.

Result The Solution Builder has been installed in your SAP ERP system. The use of the Solution Builder is described in the Installation of Business Content step.

© SAP AG

Page 15 of 34

SAP Best Practices


5.4 General Client Settings 5.4.1

Creating User for Activation of SAP RDS Content

Use If you want to create a certain user to run the activation of the related SAP rapid-deployment solution scope, consider the following: SAP Real Estae Management rapid-deployment solution does not supply separate roles for customizing or setup tasks. If necessary, you can define a separate role corresponding to your individual IMG project according to the functions provided in Role Maintenance (transaction PFCG), containing all the authorizations you need to access the corresponding IMG activities required for the SAP rapid-deployment solution scope. Alternatively, you can use the authorization profile SAP_ALL. If this authorization does not apply to your authorization concept, you should restrict the rights of the user according to your internal authorization guidelines. Without the profile SAP_ALL, issues during the activation may occur and need to be solved. You can use the transaction SU53 to get information on the missing authorizations and extend the authorization data as necessary. Directly after the activation of the SAP RDS Real Estate Management content, remove the authorizations you have given to the system user that has performed the activation steps. This is for security reasons to avoid that the system user misuses the authorizations granted before.

The following procedure describes how to set up a system user, which is necessary to activate the SAP Real Estate management rapid-deployment solution specific content.

Procedure 1.

To carry out the activity, choose one of the following navigation options: SAP Menu

Tools

Transaction Code

SU01

Administration



User Maintenance



Users



2.

and choose On the User Maintenance: Initial Screen, in the User field, enter Create.

3.

Choose the Address tab page.

4.

Make the following entries: Field name

User action and values

Last name

First name

5.

Choose the Logon Data tab page.

6.

Make the following entries: Field name


Initial Password

Repeat Password

© SAP AG

Note

Note

Page 16 of 34

SAP Best Practices


User type

Dialog

7.

Choose the Defaults tab page.

8.

Make the following entries:

9.

Field name


Logon language

EN

Decimal notation

1.234.567,89

Date format

DD.MM.YYYY

Note

Choose the Roles tab page.

10. Enter the user role you created that contains the necessary authorization profile. Alternatively, you can assign the profile SAP_ALL on the Profiles tab page. Make sure that this corresponds to your internal security guidelines. 11. Save your entries.

Result A user to activate the SAP Real Estate Management rapid-dep loyment solution content has been created.

5.4.2

Deselecting Activation Links in BC Sets

We recommend that you turn off the creation of activation links. By doing this, you can significantly increase activation speed and avoid errors.

Procedure 1.

Run the following activity: SAP Menu

Tools  Customizing Activation of BC Sets

Transaction Code

Business Configuration Sets



SCPR20

2.

On the Business Configuration Sets: Activation screen, choose Utilities → System Settings.

3.

Choose Change (Shift + F1).

4.

In the Activation section, select the Do Not Create radio button.

5.

An information message appears. Choose Enter .

6.

Save your settings.

5.4.3



Maximum Work Process Run Time

Use Dynamic switchable profile parameters (indicated by a flag in the checkbox of the parameter) have to be checked before activation. Therefore, the following profile parameters must be checked and adapted.

Procedure 1.


2.

RZ11

On the Maintain Profile Parameters screen, make the following entries: Field name

© SAP AG

Description


Note

Page 17 of 34

SAP Best Practices


Field name

Description


Param. Name

Profile parameter name

rdisp/max_wprun_time

3.

Choose Display .

4.

On the Display Profile Parameters Attributes screen, choose Change values.

5.

On the Change Parameter Value screen, make the following entries.

6.

Note

Parameter Name

Description

New value

Note

rdisp/max_wprun_time

Max work process run time

3600

Check and adapt value if value is <3600

Choose Save.

When you save the change, the window closes and the value of the parameter is changed. This change only becomes effective when you log off and then log on to the system again.

If the parameter is set in RZ11, you lose the change when you restart the server.

This parameter value is only needed for the activation of the SAP Real Estate Management rapid-deployed solution since there are some processes that need to be performed in dialog and last for more than ten minutes. Switch back to the default value after the activation of the SAP Real Estate Management rapid-deployed solution.

5.4.4

SAP Scripting

Use eCATTs are used to automate the activation of SAP Real Estate Management rapiddeployment solution configuration settings. Before the activation, you must allow eCATT processing in the system by setting the profile parameter sapgui/user_scripting . The value for Enable or disable user scripting on the front-end must be set true.

Procedure 1.


2.

RZ11

On the Maintain Profile Parameters screen, make the following entries Field name

Description


Param. Name

Profile parameter name

sapgui/user_scripting

3.

Choose Display .

4.

On the Display Profile Parameters Attributes screen, choose Change values.

5.

On the Change Parameter Value screen, make the following entries. Field name

© SAP AG

Description


Note

Note

Page 18 of 34

SAP Best Practices

6.


Field name

Description


Note

New Value

New Value for user scripting

TRUE

Enable SAP Scripting

Choose Save.

When you save the change, the window closes and the current value of the parameter changes to TRUE. This change only becomes effective when you log on to the system again.

If the parameter is set in RZ11, you lose the change when you restart the server.

5.4.5

Set Default Timeout for HTTP and HTTPS Services

Use We recommend that you set the following settings for both services TIMEOUT and PROCTIMEOUT to 300 or 600 (seconds). The default is 60. The values are also set using system parameters (see below section Procedure): icm/server_port_<*> - Standard value for *: 0: http, 1 or 2: https For example: icm/server_port_0 = PROT=HTTP, PORT=8000, PROCTIMEOUT=300, TIMEOUT=600 icm/server_port_1 = PROT=HTTPS, PORT=44300, PROCTIMEOUT=300, TIMEOUT=600

Procedure 1. Run the following activity: Transaction Code

RZ10

2. On the Edit Profiles screen, enter your instance profile. 3. In the Edit Profile box, select the Extended maintenance radio button and choose Change. 4. On the Maintain Profile screen, make the following entries Parameter Name

Description

New value

Note

icm/server_port_<*>

Standard value for *:

300 or 600

Set to 300 or 600 (seconds) for TIMEOUT and PROCTIMEOUT, the default is 60

0: http, 1 or 2: https

5. Choose Back 6. Choose Save.

This adaptation of these profile parameters is only necessary if you are using SAP NetWeaver Business Client.

© SAP AG

Page 19 of 34

SAP Best Practices


5.5 Prepare System User for Content Activation 5.5.1

SAP Software Change Registration (SSCR): Developer Key

The user ID used for the activation has to be registered as developer on SAP Service Marketplace (SAP Software Change Registration (SSCR)). For more information, see SAP Note 86161. The SSCR developer key is needed because the user ID used for the SAP Real Estate Management rapid-deployment solution activation creates and changes objects from the customer name range during the SAP Rapid-Deployment Solution activation process. If the SAP Rapid-Deployment solution activation user is not registered as a developer, the automated SAP Rapid-Deployment solution activation incurs errors.

Procedure 1.

Access the SAP Service Marketplace at http://service.sap.com/sscr .

2.

On the SAP Software Change Registration (SSCR) start page, you get the detailed user documentation containing the procedure to get the SSCR developer key.

An SSCR developer key is a 20 character combination of digits that is queried when an SAP ERP user tries to create or change an object from the customer name range FOR THE FIRST TIME. The prompting message for the developer key appears once for each SAP ERP user; if the registration is successful, this SAP ERP user is no longer prompted to enter a developer key. The SSCR developer key is generated from the installation number of the affected installation and the SAP ERP user name.

5.5.2

Activation Language

Make sure that your logon language is always English (and NOT your local language) for all activation activities.

5.5.3

User Settings for Activation For the activation, we recommend that only one user ID be used to activate the SAP Rapid-Deployment Solution. It can be a tedious procedure to change the ownership of the activation of the solution.

Make sure that you only have one single SAP GUI session running when you activate SAP Best Practices. If you run several SAP GUI sessions, some automated installation activities might run into errors.

5.5.4

Deactivate Info Dialog Box on Dynpro Size Check

The sizing conflicts dialog box may appear and has to be deactivated.

© SAP AG

Page 20 of 34

SAP Best Practices


Procedure 1. 2.

Log on with the user in the system. Choose the first button from the right side of the Standard Tool Bar Customizing of Local Layout or type ALT + F12 .

3.

Choose Options.

4.

Choose the SAP Internal tab page.

5.

Deselect the Enable dialog box for screen size check checkbox.

6.

Choose OK .

5.5.5

Unicode Settings

Use Before each user logs on to the system for the first time, the user’s local GUI must be set to use the Unicode code page.

Procedure 1.

From the SAP Logon pad, select your system ID.

2.

Choose Change Item.

3.

In the System Entry Properties dialog box, choose the Code Page tab page.

4.

In the Encoding drop-down list, select Unicode (UTF-8).

5.

Choose OK .

5.5.6

Allow GUI Scripting

Use Perform this activity that eCATTs GUI scripts can by executed with your GUI.

Procedure 1.

Choose the first button from the right side of the Standard Tool Bar Customizing of Local Layout or type ALT + F12 .

2.

Choose Options.

3.

Choose the Accessibility & Scripting tab page and Scripting sub-tab page.

4.

Select the Enable scripting checkbox.

5.

Deselect the Notify When a Script Attaches to SAP GUI and Notify When a Script opens a Connection checkboxes.

6.

Choose OK .

5.5.7

Set Decimal Notation and Date Format

Use Perform this activity to set up the activation user ID.

Procedure 1.

Run the following activity: SAP Menu

System  User Profile

Transaction Code

SU3

Own Data



2.

Choose the Defaults tab page.

3.

Make sure you set the Decimal Notation according to your country’s default, for example 1.234.567,89.

© SAP AG

Page 21 of 34

SAP Best Practices


4.

Make sure you set Date Format according to your country’s default, for example DD/MM/YYYY.

5.

Make sure that you assign your printer in the OutputDevice field (see also in Printer Environment ).

6.

Save your settings.

7.

Log off from the system.

8.

Log on to the system.

Logging off and on is necessary since the change in the user settings only becomes effective when you log on to the system again. 

When the complete activation procedure is finished, you may change these values as desired.

Result The decimal notation and date format have been set up according to your country format. The standard printer has been defined.

6 Implementation of RDS Business Content (C o n s u l t a n t ) When the customer has finished with the setup of the system landscape, the project team can start with the implementation of the rapid-deployment edition. The following steps describe additional preparation activities that need to be carried out by the project team. The SAP Real Estate Management rapid-deployment solution does not provide predefined roles. Each implementation project need to define and setup roles in accordance to the specific policies adopted by the customer.

6.1 SAP Real Estate Management RDS Implementation Before running the implementation as described in the Implementation of RDS Busness Content step, choose between the different installation options offered by the SAP Real Estate Management rapid-deployment solution. The SAP Real Estate Management rapid-deployment solution is an ERP solution that is usually used in a customer-specific SAP ERP system. To allow customers a fast implementation in a sandbox or test environment, the rapid-deployment solution package comes with a model ERP implementation based on SAP Best Practices.

6.1.1

Installation with the Existing SAP ERP Landscape

A real live customer environment already contains ERP customizing and master data. To use the rapid-deployment solution in a customer situation, the rapid-deployment solution solution has to be adjusted to the existing company structure and master data setup. Is suggested ot perform the implementation manually, on the basis of the configuration described in the configuration guide, with the concurrent adaptations needed due to the specific configuration of the development system; the business processes described in business process documentation will then be tested taking in consideration the perfomed adaptations.

6.1.2

Installation in a Sandbox or Test Environment – Baseline Germany as a basis 6.1.2.1 General

In a sandbox or test environment, customers can choose to implement the model campany that was used as a basis for the development of the SAP Real Estate Management rapiddeployment solution. The SAP Real Estate Management rapid-deployment solution provides master data. We use the SAP Best Practices Baseline package for Germay V1.605 as a basis. You can find more information about these packages here:

© SAP AG

Page 22 of 34

SAP Best Practices




SAP Best Practices Baseline US V1.605 for packages - Based on SAP ECC 6.00, localized for DE: http://help.sap.com/bp_bl605/BL_DE/html/index.htm



Activation of the SAP Best Practices Baseline Package for Germany o Refer to the Quick Guide of the SAP Best Practices Baseline Package for DE V1.605

Specifically for the usage of SAP Best Practices Baseline package for Germay V1.605 as a basis for the setup of a Sandbox or Test Enviroment the following notices need to be taken in consideration: 

System Requirements and System preparation: in addition to the system requirements and system preparation activities for SAP Real Estate Management RapidDeployment Solution (chapter 4 and 5 of this document) system requirements and system preparation activities for SAP Best Practices Baseline package for Germay V1.605 need to be fullfilled



During activation the selection of the scoping template “All scenarios” is suggested (Create/Change Customer Solution based on Standard Solution, or Ctrl+F9). This activation option will activate all the Baseline scenarios except: “123 Cross-Company Sales Order Processing” and “141 Internal Procurement: Cross-Company Stock Transfer ”



Activation language: at the start of the SAP Best Practices Baseline package for Germay V1.605 is suggested to select the target language “EN English” (this in coherence with the SAP Real Estate Management rapid-deployment solution english language)

Ensure during the baseline activation the activity of Rolling MM Period to Current Period as described in the baseline building block 154. Perform this activity only if the MM period in the system is not set to the current period. Usually, this activity has to be done once a month. The MM period can only be chosen as next period from the period set in the system.

Procedure 1. Access the activity using one of the following navigation options: SAP ECC menu

Logistics  Materials Management Other  Close Period

Transaction code

MMPV

Material Master





2. On the Close Period for Material Master Records screen, make the following entries: Field name

Description


From company code

Enter the company code.

1000 (for example)

Period

Enter the current period.

Fiscal year

Enter the current fiscal year.

Comment

3. Choose Execute.

© SAP AG

Page 23 of 34

SAP Best Practices


6.2 Installation of Language/Country-Specific Content The SAP Real Estate Management rapid-deployment solution provides content available in English and German without any country-specific settings. SAP Real Estate Management has been developed and tested with and ERP installation for Baseline Germany. Any other ERP localizations have to be tested very carefully and are not part of this rapid-deployment solution package. The current available version of SAP Real Estate Management rapid-deployment solution comprises the English and German languages; there are no separate SAP Real Estate Management rapid-deployment solution versions for different countries or other languages.

6.3 RDS Content Installation Variants 6.3.1

Manual Implementation

If you have decided to implement the SAP Real Estate Management rapid-deployment solution, implement the configuration guides relevant for your scenarios in the right sequence below. You can find the installation sequence for each scenario in the prerequisite matrix for this rapid-deployment solution package. You can find the configuration guides in the SAP Real Estate Management rapid-deployment content library.

6.3.2

Solution Manager Template based Implementation

The SAP Real Estate Management rapid-deployment solution includes a SAP Solution Manager Template that can be used to speed up the implementation.

6.3.2.1

Checking the System Landscape in SAP Solution Manager

Use The SAP Real Estate management rapid-deployment edition is designed for a specific system landscape that is represented by the logical components in the Solution Manager Template. The SAP Solution Manager template contains the logical components that define the system landscape required for the rapid deployment of SAP Real Estate Management. You can use the logical components to map the physical systems in your system landscape. This allows you to configure the systems directly using SAP Solution Manager. You can also check and maintain the system landscape during the template selection. However, we recommend to maintain the system landscape up-front to the template selection to complete this administrative IT task before starting the business-driven content implementation. To maintain the system landscape in the SAP Solution Manager tool, in the SAP Solution Manager Easy Access menu, choose System Landscape (SMSY).

Procedure In the SAP Solution Manager, access System Landscape – SAP Solution Manager (transaction SMSY): 1.

Choose System Groups and Logical Components → Logical Components.

2.

In the context menu of Logical Components, choose Create New Logical Components.

3.

In the dialog box, create the following settings: Field Name

Entry Value

Logical Component

Product

SAP ERP ENHANCE PACKAGE

Product Version

EHP5 for SAP ERP 6.0

© SAP AG

Page 24 of 34

SAP Best Practices


Name 4.

Choose Continue. In the left screen area, the Current System Assignments tab page appears.

5.

In case you are implementing Real Estate in an existing ERP environment, use the already existing entries. In case you implement Real Estate in a sandbox environment and you want to build a model company as described in this Quick Guide, maintain the ERP system corresponding to the sandbox environment in the column “Evaluation System”.

Technically, there are no restrictions regarding the rapid deployment of SAP Real Estate Management and deviating SAP ERP release levels since the installation of the SAP ERP components is performed manually without eCATTs or BC sets. However, the documentation delivered with this rapid-deployment solution is only based on the recommended SAP ERP release levels.

For more information about the Solution Manager System Landscape, see the SAP Solution Manager documentation in the SAP Help Portal at http://help.sap.com → SAP Solution Manager → SAP Solution Manager 7.0 EhP1 SP26 → Basic Settings → Solution Manager System Landscape.

6.3.2.2

Creating the SAP Solution Manager Project and Template Selection

Use You select the SAP Solution Manager template in SAP Solution Manager so that you can use the content in your implementation project. The template contains the content for the default implementation of the SAP Real Estate Management rapid-deployment edition.

Procedure Create a project to organize you work in SAP Solution Manager. To create a project, perform the following steps: 1.

In the SAP Solution Manager system, access transaction SOLAR_PROJECT_ADMIN.

2.

On the Project Administration screen, select an existing implementation project. To create a new project, proceed as follows: 1.

Choose Create Project.

2.

In the dialog box, make the following entries: 3.

Project

6. 9.

4.

Type

5.

Solution

7.

Implementation Project

8.

Choose Continue.

10. Enter a title. 11. On the General Data tab page, select the project language. 12. Save and confirm the message. 3.

On the Scope tab page, choose the Template Selection tab page.

4.

Select the template and expand the node to display the business scenarios it contains:

© SAP AG

Page 25 of 34

SAP Best Practices




If the system uses SAP Solution Manager 7.0 (ST 400) or SAP Solution Manager 7.1 (ST 710) < SP05: a. Select the Template Selection sub-tab by clicking the hyperlink for further information. b. Search for the template RDS_RE_LM_XX_V01.



If the system uses SAP Solution Manager 7.1 (ST 710) (at least SP05): a. Select the Solution Package sub-tab by clicking the hyperlink for further information. b. Search for the solution package SAP Real Estate Management rapid-deployment solution_XX_V01.

5.

Select the business scenarios you want to copy into your implementation project.

6.

Save your project.

If you save your project for the first time, you need to specify the enhancement context in which the project documents are to be saved in the Knowledge Warehouse. 7.

Map the logical components assigned to the process steps of the selected business scenario to your current system landscape. The system identifies missing logical components for product versions or instances required for the business processes. If necessary, correct any incorrect assignments using the value help. Select the correct logical components you have created in Checking the System Landscape in SAP Solution Manager . For more information about the system landscape in SAP Solution Manager, see the SAP Solution Manager documentation on SAP Help Portal at http://help.sap.com → SAP Solution Manager → SAP Solution Manager 7.0 EhP1 SP26 → Implementing and Upgrading SAP Solutions → Project Administration → Create/Change Project → Specify Scope.

8.

Choose Continue. The list of logical components is updated on the System Landscape tab page.

9.

Save your project.

If you use an earlier ERP release than SAP ERP 6.0 EHP 5, a different approach applies. The value help only displays logical components that match the product or product version specified in the SAP Solution Manager template delivered by SAP. Other logical components are not selectable. To proceed, assign the newly created logical components (see Checking the System Landscape in SAP Solution Manager ) as a placeholder and replace the product or product version later.

6.3.2.3

Adjust the Process Scope in SAP Solution Manager

You refine the solution scope to reflect your business needs and adjust the configuration settings in the systems accordingly:



In the SAP Solution Manager, adjust the scope of the business processes you would like to implement. On the SAP Easy Access screen, choose Business Blueprint (transaction SOLAR01).

© SAP AG

Page 26 of 34

SAP Best Practices




Switch to the correct project context, Choose Other Project (SHIFT+F5). Select the appropriate project in the dialog box. For more information about the scope of the rapiddeployment edition of SAP Real Estate management, refer to the template description. In the template, all business processes (scenarios) are self-contained, that is, have all related content assigned. Therefore, you do not need to select master data or organizational unit nodes or interface scenarios in the blueprint structure. We recommend deselecting these nodes to have a better overview during the configuration step later (transaction SOLAR02). Transaction SOLAR01: you can also access the template description to check which processes are mandatory or optional for the rapid-deployment edition. For more information about business blueprints in SAP Solution Manager, see the SAP Solution Manager documentation on SAP Help Portal at http://help.sap.com → SAP Solution Manager → SAP Solution Manager 7.0 EhP1 SP26 → Implementing and Upgrading SAP Solutions → Business Blueprint.



Once the blue-print is adjusted appropriately, we configure the systems using the transaction SOLAR02 The template’s content has only been validated with SAP ECC 6.0 EHP5. If you are using an SAP ERP release lower than SAP ECC 6.0 EHP5 and want to leverage the template’s ERP content, you can follow the steps below as a workaround solution:

Choose the project that you created in 6.3.2.2.  In Transaction SOLAR02, choose Business Scenarios → SAP Real Estate Management rapid-deployment edition → Business Processes. For the business process, select the entry in the configuration structure.  Check that the transaction is in display mode. Otherwise, change to display mode.   Choose Edit → Replace Log. Comp. in the menu.  On the screen that appears, enter the logical component for SAP ECC 6.0 EHP 4 in the Logical Component to Be Replaced field. Enter your actual R/3 or ERP logical component in the Replace with Logical Component field.  Choose Save.  Confirm the warning. 

6.3.3

Automated Implementation using SAP Best Practices Solution Builder

Refer to the Building Block Configuration Guides to review the rapid-deployment solution content for this package that will be automatically implemented as a result of content activation. The SAP Real Estate Management rapid-deployment solution contains one solution files – called RDS_RELM_ERP605V2.xml.

6.3.3.1

Getting the Business Content for Activation

Perform the following steps Getting the Solution Scope File and Getting the Installation Data Files on the same day. If you download the files at different times, you may encounter errors due to mismatches.

6.3.3.1.1 Getting the Solution Scope File Use The technical structure for each solution package (processes or scope items, building blocks and technical objects) is managed by a solution scope file.

© SAP AG

Page 27 of 34

SAP Best Practices


Procedure 1.

To download the solution scope file, first go to SAP Service Marketplace at http://service.sap.com/bp-implcontent.

2.

Choose the Solution files link and then the link for SAP ERP 6.0

3.

Download the following solution scope .zip file:

 EHP5

for SAP ERP 6.0.

SOL_ RDS_RELM_ERP605V2_ BP_ERP605V6.zip

6.3.3.1.2 Getting the Installation Data Files Use The installation settings (configuration settings and master data) of the solution packages are managed by the installation data files.

Procedure 1.

To download the installation data files, first go to SAP Service Marketplace at http://service.sap.com/bp-implcontent.

2.

Choose the Installation data file sets link and then the link for SAP ERP 6.0 ERP 6.0.

3.

Download the following installation data .zip file:

 EHP5

for SAP

INST_FILES_ RE_XX_BP_ERP605V6.zip

6.3.3.2

Create Installation Folder for Content Activation

Use The scoping, personalization, and installation phase of Solution Builder require solution scope and installation data files to be stored in a specific folder on your hard drive or presentation server.

Procedure 1.

Create an installation data folder on a server that can be accessed from within the SAP system where you want to install the SAP rapid-deployment solution content. Ensure that the person who will perform the installation has the necessary user rights to access this folder.

2.

Copy the installation data file INST_FILES_ RE_XX_BP_ERP605V6.zip (see paragraph 6.3.3.1.2) to the Installation Folder for Content Activation.

3.

Unpack the solution scope file in .zip format SOL_ RDS_RELM_ERP605V2_ BP_ERP605V6.zip and copy the contained file RDS_RELM_ERP605V2.xml to the Installation Folder for Content Activation.

6.3.3.3

Import Solution Scope File to the SAP system

The relevant solution scope file (*.xml file) required for the SAP Real Estate Management rapid-deployment solution, has been copied to the installation data directory (as described in section Create Installation Folder for Content Activation above ).

Procedure To install the SAP Real Estate Management rapid-deployment solution, upload the relevant solution scope file to the target SAP development system as follows:

© SAP AG

Page 28 of 34

SAP Best Practices


1.

Log on to the target SAP development system and start SAP Best Practices Solution Builder with transaction /n/smb/bbi Solution Builder – Solution Editor.

2.

The Solution Editor screen appears and lists all the solutions available in the system.

The solution list is empty the first time you start the Solution Editor (if no other users have imported or created solutions in the system).

We recommend that you add the transaction for Solution Builder (/SMB/BBI) to your favorites in the SAP user menu. 3.

On the Solution Builder – Solution Editor screen, choose Solution from the navigation menu.

Import

4.

In the Select the Solution Scope File (XML) dialog box, indicate the path to the installation directory, select the relevant solution scope file RDS_RELM_ERP605V2.xml and choose Open.

5.

An information box is displayed if the solution was uploaded successfully (depending on the size of the solution, the upload can take from a few seconds to one minute). Choose OK to confirm

6.

Set the uploaded solution as the favorite solution: choose Solution



Solution (XML)



Set Favorite



Result The uploaded solution is visible in the solution list and is marked as your favorite solution. If the path to the installation data directory is too long, the system displays an error message. If you receive this error message, either rename directories in the path to shorten the file path, or copy the installation files to a directory being closer to the root folder of the hard drive.

6.3.3.4

Maintain User Settings: Path to Installation Data

Use The solution definition (as uploaded as XML file) and the installation data define the solution content that is implemented. To simplify the procedure and to avoid confusion with different sets of installation data, we strongly recommend to assign the installation data directory’s path to the solution. You do this in the user settings (because the path information is very often user-dependent). This is an important step for consultants that have imported multiple solutions in the solution builder.

Procedure 1.

On the Solution Builder – Solution Editor screen, choose Goto  User Settings from the menu.

2.

On the Solution Specific tab page, select the directory where you stored your installation data files.

© SAP AG

Page 29 of 34

SAP Best Practices


The solution ID of the Favorite solution is fixed. To maintain it for another solution, select another solution as a Favorite before maintaining the solution-specific part of the user settings. 3.

Choose OK to confirm the settings.

Result The path to the installation data directory being assigned to the solution is always set as default entry for the particular solution.

6.3.3.5

Maintain User Settings: Path to Documentation

Use This activity sets the document path for information that may be useful during the activation so that users can find details from the SAP Help Portal about the scenario being activated.

Procedure 1.

Run the following activity:

/n/SMB/BBI

Transaction Code 2.

From the menu, choose Goto

User Settings.

3.

Choose the External Documents tab page.

4.

Choose Display ↔ Change.

5.

Choose Insert Row .

6.

Enter the following value:



Parameter

Value

% DOCUMENTATION %

path to directory

7.

Choose Save.

8.

Choose Back .

6.3.3.6

http://help.sap.com/saap/sap_bp/bblibrary/HTML/

Maintain authorization for activation

During the activation, follow the recommendations for your activation of Activation User as described in 5.4.1 Directly after the activation of the SAP Real Estate Management rapiddeployment solution content, remove the authorizations you have given to the system user that has performed the activation steps. This is for security reasons to avoid that the system user misuses the authorizations granted before.

© SAP AG

Page 30 of 34

SAP Best Practices

6.3.3.7


Upload Installation Data

Prerequisites The installation files have been downloaded to the local directories you created in the step Create Installation Folder for the SAP Real Estate managment rapid-deployment solution Installation Files and Scope File. The Solution Scope file has been uploaded into the ERP systems.

Use In addition, the upload allows you to review the installation data for the tasks in the Building Block Builder for better transparency, troubleshooting, or to maintain installation data. Activating a solution is independent from uploading the installation data. The activation step uses the files in the installation data folder on the presentation server to ensure that you have uploaded the correct installation data files and been pointed to the correct folder location.

Procedure To upload the installation files, proceed as follows in Solution Builder: 1.

Go to view Solution Builder – Solution Editor

2.

From the navigation menu, choose Go to Installation Data window.

3.

Select the Upload with single ZIP file checkbox.

4.

Use the browser search in the Path field to locate and retrieve the zip file created in a previous step. Select Open to select it and return to the Upload Installation Data window.

5.

Choose the Continue pushbutton.

Installation Data



Upload to open the Upload



Perform the steps for retrieving the solution file and importing the scope and installation data files in the same day. If you download them at different times, you may encounter errors due to mismatches.

Result A system message confirms that the installation data has been uploaded successfully to Solution Builder.

6.3.3.8

Activating a Solution

Solutions are implemented in the Implementation Assistant . To activate a solution, the following information must be provided when prompted in the Activate Solution window (see Procedure below): Field name


Comments

Target Language

EN

Target language (the language of text fields for system parameters that are not language-dependent in a technical sense; once the installation has been started, the target language cannot be changed). For this rapiddeployment solution, the target language should always be EN.

Installation Data

Location of the folder with

This folder was created in the step Create Installation Folder for Content Activation

© SAP AG

Page 31 of 34

SAP Best Practices

Field name


User action and values installation data, for example, Z:\rds\files

Comments

You cannot use UNC paths (for example, \\dwdf030\SME\...). Always use a mapped network drive (for example, Z:\SME). Root directories on your local drive (for example, C:\) also cannot be used.

Workbench

Workbench request number

Leave blank – this will be created automatically during the solution activation process.

Customizing

Customizing request number

Leave blank – this will be created automatically during the solution activation process.

Create request

Select

This indicator ensures that associated workbench and Customizing requests are generated during the solution activation process.

Skip this screen

Deselect

If this option is selected, the system does not display the Activate solution dialog box upon resumption of activation following an error or manual activity. If this option is deselected, the Activate solution dialog box will display every time activation resumes.

With demo data

Select

If this option is selected, the system executes activation steps that create sample data. If it is deselected, these steps are not executed.

Procedure 1.

From the Solution Builder – Solution Editor screen, choose the Implementation pushbutton. Your imported solution scenarios and building blocks are displayed.

2.

On the Implementation Assistant – Solution View screen, choose the Activate pushbutton.

3.

Specify the activation options in the Activate Solution window, as described above.

4.

Confirm the Activation dialog box.

Result Activation is started. Depending on the number of manual activities and possible errors during implementation, the activation process may stop occasionally and wait for manual input or troubleshooting.

Unnecessary interruptions during the content activation process can be minimized or avoided by ensuring that the user settings in Section 6.4 above have been defined correctly in advance.

© SAP AG

Page 32 of 34

SAP Best Practices


If several people are involved in the implementation, make sure to take activation ownership (choose the Change Activation Ownerbutton). Otherwise, the solution is locked.

Manual interaction During Installation of Building Blocks Use The installation procedures of the following scenarios or building blocks contain manual installation steps or require manual confirmation.

Procedure If the Solution Builder stops because of a manual activity, proceed as follows: 1.

Read the information screen in the dialog text box

2.

On the navigation option screen, memorize the header of this screen. This header information is identical with the configuration activity that has to be executed manually.

3.

Open the configuration guide for this building block that is provided on the documentation html structure in the Technical Information  Content Library section. Navigate to the building block and open the configuration guide.

4.

Choose the proposed navigation option, for example Navigate to IMG.

5.

Execute the configuration activity manually by following the instruction of the related section in the configuration guide.

6.

Choose Back (from the IMG activity or the transaction).

7.

Choose Proceed.

8.

On the Implementation Assistant – Scenario Edit View, choose Confirm Manual Step.

9.

Enter a reason (optional) and choose Enter .

10. Proceed with the activation.

6.3.3.9

Processing General Errors during Installation

Use When an activation of an automated task runs into errors, the activation stops at the point of the error. No further implementation can be done until the error is resolved.

Procedure 1.

On the Implementation Assistant – Solution View screen, select a task that has a red light in the Current status column.

2.

Expand the task and choose the log that is assigned to this task. Detailed information about the error is displayed in the Error List pane.

3.

In the Error List pane, choose Display Detailed Log . The detailed log information about an eCATT or BC Set activation is displayed.

4.

In this log information, check entries with a red light to identify the reason for the error. If the error can be solved based on the log information, you can run the eCATT or BC Set again. If the activation fails because of locked objects, make sure that no objects are locked by any users. Then try to activate the activity again. See the document SAP Best Practices Tools for details about the manual

© SAP AG

Page 33 of 34

RE Quick Guide

Recommend Documents