ServInd Quick Guide V2605 en De

SAP ECC 6.0 EhP5

June 2011

English

Quick Guide to Installing the SAP Best Practices for Services Industries V2.605 (DE)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

SAP Best Practices Quick Guide to Implementing the SAP Best Practices for Services Industries (DE) V2.605

Copyright

© Copyright 2008 SAP AG. All rights reserved.

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

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

© SAP AG of 72


Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

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 of 72


Contents1 Purpose................................................................................................................. 7

2 Technical Prerequisites for Installation..................................................................7

2.1.1 System Status of Client Roles...............................................................................7

2.1.2 General Recommendations...................................................................................7

2.2 SAP ERP..............................................................................................................8

2.2.1 Install SAP ERP.....................................................................................................8

2.2.2 SAP Best Practices Add-On and Transport...........................................................8

2.2.3 Release and Support Package Level.....................................................................9

2.2.4 Required SAP Components...................................................................................9

2.2.5 SAP Enterprise Extensions and Enterprise Business Functions.........................12

2.2.6 SAP Notes and Messages...................................................................................13

2.2.7 General Settings in the ERP System...................................................................15

2.2.8 Getting the Solution Scope File...........................................................................19

2.2.9 Getting the Installation Data Files for ERP..........................................................20

2.2.10 Creating a Folder for the SAP Best Practices Activation.....................................20

2.3 SAP CRM............................................................................................................20

2.3.1 CRM System Landscape Considerations............................................................21

2.3.2 Release and Support Package Level...................................................................22

2.3.3 SAP Best Practices Add-ons...............................................................................24

2.3.4 SAP Notes and Messages for CRM.....................................................................24

2.3.5 Activation of the Component VM Container.........................................................25

2.3.6 Troubleshooting...................................................................................................25

2.3.7 Related Documentation for CRM issues..............................................................26

2.3.8 General Settings in the CRM System..................................................................26

2.3.9 Setup of SAP Best Practices Solution Builder for CRM.......................................28

2.3.10 Installation Options for Services Industries with CRM.........................................30

2.3.11 Create Installation Folder for the SAP Best Practices CRM Installation Files and Scope File............................................................................................................31

3 Pre-Activation Activities.......................................................................................32

3.1 User Settings for Activation.................................................................................32

3.1.1 User Maintenance................................................................................................32

3.1.2 SAP Software Change Registration (SSCR): Developer Key..............................33

3.1.3 Unicode Settings.................................................................................................34

3.1.4 Allow GUI Scripting..............................................................................................34

3.1.5 Set Decimal Notation and Date Format...............................................................35

3.1.6 Deselection of Activation Links in BC Sets..........................................................35

3.2 Maintain Profile Parameters................................................................................36

3.2.1 Maximum Work Process Run Time.....................................................................36

© SAP AG of 72


3.2.2 SAP Scripting......................................................................................................37

3.2.3 Authentication using SAP Logon Tickets.............................................................37

3.2.4 Set Default Timeout for http and https Services..................................................38

3.3 Printer Settings....................................................................................................39

3.3.1 Default Printer......................................................................................................39

3.3.2 Optional Activity: Set up Printer Environment......................................................40

3.3.3 Printing Bar Codes...............................................................................................40

3.4 Installation and Usage of the SAP Best Practices Solution Builder.....................41

3.4.1 Technical Installation...........................................................................................41

3.4.2 Running the Solution Builder...............................................................................41

3.4.3 Interfaces.............................................................................................................41

3.4.4 SAP Best Practices Solution Builder User Guide................................................42

4 Activation............................................................................................................42

4.1 Activation Approaches........................................................................................42

4.1.1 Automated Activation...........................................................................................42

4.1.2 Manual Activation................................................................................................42

4.1.3 Automated Activation w/o Demo Data.................................................................42

4.2 Activation Sequence...........................................................................................43

4.2.1 Activation Sequence of Building Blocks...............................................................43

4.2.2 Scoping and Activation of Scenarios...................................................................44

5 Troubleshooting..................................................................................................51

5.1 Error Handling: Installation Errors.......................................................................51

5.1.1 Error Occurs During Automated Task..................................................................51

5.1.2 Error Message for eCATT /xxxxxx/PA40_O001_xxx Field PSPAR-PERSK. is not an input field........................................................................................................52

5.1.3 Warnings in the BC-Set Logs..............................................................................53

5.1.4 eCATT Error Variable xyz does not exist….........................................................53

5.1.5 Window Appears During Activation Start Options – Test Configuration /SMB99/BMSM_O237_J01..................................................................................53

5.1.6 Window appears during installation A script is trying to attach to the GUI...........53

5.1.7 Window appears during installation asking to confirm that text was changed.....53

5.1.8 Issue with SAP GUI.............................................................................................54

5.1.9 Description of Manual Steps in Installation Process............................................54

5.1.10 Processing of Scenario Specific Errors................................................................54

6 Evaluate Business Content / Scenarios – Business Consultant..........................57

6.1 Review of Business Scenarios............................................................................57

6.2 Usage of Personalized Values in Business Process Documentation (BPD).......58

6.3 User maintenance and Settings..........................................................................58

6.3.1 Assigning a Role to an User................................................................................58

6.3.2 Mandatory User Parameter.................................................................................60

© SAP AG of 72


6.3.3 Optional User Parameter.....................................................................................60

6.4 Creation of Queries in Personal Object Worklists (POWLs)................................62

6.5 Errors during Usage of Activated Package.........................................................64

6.5.1 Using Requirement Class YB5 - Scenario 195: Sales Contract with Fixed Price and T&M Billing...................................................................................................64

6.5.2 Scenario General Cost Center Planning (175): Step 4.10 Execute Plan Assessment, Transaction KSUB; error message Customizing error: Business transaction groups are not current. Message no. GA627....................................65

6.5.3 Posting only possible in periods 200[x]/0[y] and 0000/00 in company code [1000]............................................................................................................................ 65

6.5.4 Maintain Allocation Structures — Settlement Cost Elements (CE), Error no entries exist when using F4 Help.........................................................................66

6.5.5 Various Scenarios in the Area Controlling: Error System error or customizing error: Read error in set for table CCSS, message GA622...................................66

6.6 Errors with SAP NetWeaver Business Client (SAP NWBC)................................67

6.6.1 Queries Show No Data / No Columns.................................................................67

6.6.2 Printing functionality.............................................................................................67

6.7 Security Aspects – System Administrators..........................................................67

6.7.1 User Administration and Authentication...............................................................68

6.7.2 Roles Management..............................................................................................68

6.7.3 RFC Destinations.................................................................................................68

© SAP AG of 72


Quick Guide to Installing the SAP Best Practices for Services Industries (DE)

1 PurposeThis quick guide provides the information you need to install the complete SAP Best Practices for Services Industries V2.605 for DE (hereinafter known simply as Services Industries) using the SAP Best Practices Solution Builder. It also explains how to proceed if you want to install individual scenarios instead.

This document is intended for consultants and system administrators who already have a sound knowledge of SAP Best Practices, including the tools and documentation. If you are not familiar with these, refer first to the document Essential Information.

Information on SCOPE OF PACKAGEThe scope of SAP Best Practices for Services Industries (Germany) V2.605 consists of scenarios in SAP ERP and SAP CRM. Some scenarios describe integrated processes starting in SAP CRM and continue/end in SAP ERP.

The selected CRM scope is based on the package SAP Best Practices for CRM V1.701, from which we have selected the Professional Services relevant scenarios, have enhanced and integrated them into the Services Industries Best Practices scenarios in ERP.

Nevertheless, you are free to install only the ERP scope or the CRM scope, or start with one part and continue at another time with the installation of the other application.

Information on documentation of the Services Industries DE V2.605: All documentation (e.g. QuickGuide) consists of the complete scope (SAP ERP & SAP CRM), so no reference to the CRM BP package necessary.

2 Technical Prerequisites for InstallationPlease always check the SAP Best Practices for Services Industries DE V2.605 note (1595694) for updates regarding the installation of SAP Best Practices.

2.1.1 System Status of Client RolesThe system cannot have any clients with a role of 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 code SCC4.

2.1.2 General Recommendations Information on the support package levels & technical prerequisites relevant for SAP Best Practices for Services Industries Package (DE) V2.605 in SAP ERP and/or SAP CRM are listed in the following chapters "SAP ERP" and "SAP CRM". Please follow all steps in these chapters depending on the scope, respective the system landscape you have to install. See also chapter 1 "Information on scope of Package".

© SAP AG of 72


2.2 SAP ERP2.2.1 Install SAP ERP

Prior to installing an SAP Best Practices package, the target SAP application (for the SAP Best Practices for Services Industries Package this would be SAP ERP) must be installed up to the specific SAP Support Package with the correct SAP Notes applied as specified in detail in section SAP Notes and Messages in this guide.

2.2.2 SAP Best Practices Add-On and TransportThe following SAP Best Practices Add-ons must be imported into the system:

BP-ERP 605V[xy]

BP-SOLBLD 70V[yz]

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 details, see the document Importing SAP Best Practices Add-Ons (ADDONINS.PDF) on the configuration CD.

Check the SAP Best Practices Services Industries Package DE V2.605 Note (1595694). If a correction transport is mentioned in the SAP Note, you must import this correction transport into the system.

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 is therefore offering updated versions of the Add-ons on a regular basis. Each updated Add-on replaces the previous version in your system. More information about the currently available versions of the Add-on BP-ERP05 and the Add-on BP-INSTASS can be found in the SAP Note 1301301.

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 having the most current versions 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.

Please also check the SAP Best Practices Services Industries Package DE V2.605 note (1595694). If a correction transport is mentioned in the note you also have to import this correction transport into the system.

© SAP AG of 72


2.2.3 Release and Support Package Level The deliverables of SAP Best Practices were developed and tested in a system landscape with specific support package levels. If the support package levels in your system are different, there might be errors during the installation. You may be able to perform the installation activities manually using the configuration guides, but errors may also occur.

For cases when the support package levels do not match the SAP Best Practices requirements, especially when HIGHER support package levels are implemented, only LIMITED SUPPORT can be provided.

If you need a higher support package level in your system, for example because of additional functionality, FIRST import and activate SAP Best Practices on the system support package levels as mentioned below, THEN upgrade your system to the latest support package level.

The support package levels relevant for SAP Best Practices for Services Industries Package (DE) V1.605 are as follows. The following components listed in chapter Required SAP Components must be installed.

2.2.4 Required SAP Components 2.2.4.1 Component Information1) SAP ERP Core Component Server 6.0You can find detailed instructions on how to order or download the right SP Level of SAP ERP, in SAP Note 774615 – Support Package levels of ERP/ECC installations/upgrades.

2) SAP Enhancement Package 5 Support Package Stack 4 for SAP ERP 6.0 Application Server ABAP (SAP ERP 6.05 SPS04 AS ABAP)SAP ERP 6.0 based SAP BP packages mainly focus 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 BP packages, a complete update of all ABAP software components of enhancement package 5 for SAP ERP 6.0 is required.

Detailed information regarding the installation of enhancement Package 5 for SAP ERP 6.0 can be found in 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

As per SAP Note 1064635 SPS levels for SAP ERP are synchronized over all enhancement package versions. Software components / add-ons not touched within an enhancement pack should have the SP level assigned to the concurrent SPS of SAP ECC 6.00.

Attached to note 1386389 - SAP BAiO/BP: Stack Information/Explanation for Used Products, an overview of all software components and their support package levels combined in the various support package stacks is given (PDF).

© SAP AG of 72

https://service.sap.com/swdc

https://service.sap.com/sap/support/notes/774615


3) SAP frontend components, for example SAP GUI for Windows and SAP NetWeaver Business ClientEnsure that you have installed the latest and appropriate SAP frontend components.

The following download path below leads you to an overview on how to install SAP frontend components and how to apply patches. On the navigation level SAP Frontend Components, 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:

https://service.sap.com/swdc, then choose Support Packages and Patches Browse our Download Catalog SAP Frontend Components

Regarding SAP GUI: Ensure that you have installed the latest version of SAP GUI and of the SAP Scripting Engine. Old versions might result in serious activation errors.

SAP NetWeaver Business Client:

https://service.sap.com/swdc, then choose Support Packages and Patches Browse our Download Catalog SAP Frontend Components Netweaver Business Client NWBC NW Business Client 3.0.

SAP NetWeaver Business Client 3.0: You need to import the corrections referred to in SAP Note 1353538 - SAP NetWeaver Business Client 3.0 - Patch Collection.

4) SAP ERP 6.0: SAP Best Practices All-in-One Add-on and SAP Best Practices solution builder Add-on

Software Component

Release Version Description

BP-ERP (1) 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 ERP 6.0 (ECC 600, EhP5)

BP-SOLBLD (1) 70 V[yz] Use the latest version as outlined in SAP Note 1301301 Release Strategy for SAP Best Practices Package ABAP Add-ons

Best Practices Solution Builder on EHP5

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

Path to download the Software Component BP-ERP05 and BP-INSTASS from the Software Distribution Center (SWDC) on Service Marketplace (SMP): https://service.sap.com/swdc then choose Installations and Upgrades Browse our Download Catalog SAP Best Practices SAP BP FOR SERVICES INDUSTRIES SERVICES INDUSTRIES V2.605 Installation.

© SAP AG of 72





7) Adobe Document Services (ADS)

The Adobe Document Services (ADS) is only needed if you want to install the business scenario Offline Time Recording (266).

Please note: For Adobe Document Services (ADS) a special license is required to use the 'interactive' feature of Adobe Forms. Please get in contact with your SAP Sales Representative for licensing and pricing information.

Adobe Interactive Forms as well as standard print forms are rendered in a software component Adobe Document Services (ADS), which runs in the Web AS JAVA (J2EE-Server) of Netweaver. The configuration of ADS is described in SAP Note 894009. Additional information, including the most recent version of the ADS configuration guide, is provided on the SAP Community Network under

https://www.sdn.sap.com/irj/sdn/adobe

As described in SAP Notes 750784 and 736902, a special license is required to use the 'interactive' feature of Adobe Forms. In particular, a special creditial file must be installed in the ADS. This creditial will give the forms special 'ReaderRights' each time they are rendered in ADS and allow them to be filled in using Adobe Reader. In the ADS configuration guide step 7.3 Installing a PKCS #12 Credential must be performed.

In order to configure the interactive form templates delivered in this guide, the person performing these steps must have the LiveCycle Designer application installed locally on the client PC. The Designer application is available for download from the SAP Service Marketplace.

In order to use the forms the latest version of Adobe Reader (currently 9.1.0) must be installed on all client PCs that use them.

8) Web Services: Netweaver ESA ECC-SE 605 (eSOA Enterprise service oriented architecture) AddOn

The Web Services (ECC-SE 605) is only needed if you want to install the business scenario Offline Time Recording (266).

The interactive forms, used within scenario Offline Time recording (266), utilize web services from the ES Bundle HCM Time Management in order to obtain a current worklist of network operations (for business case 1: OTR Project), and to submit working times to the ECC cross-application timesheet (both business cases, OTR Project and OTR Sales).

The web services are installed with the Netweaver software component ESA ECC-SE 605. To check that this component is installed in your system, use transaction SAINT and ensure that the Add-On 'ECC-SE' with the release '604' is in the list. If it is not listed and you want to set up Scenario Offline Time Recording, please install it.

2.2.4.2 Receiving the Software at the Correct SP LevelFor 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. You can only order

© SAP AG of 72


unrestricted SAP software. Please contact the SAP contract department (or create customer message on component XX-SER-GEN-CONTR) for physical shipments.

Receiving the software at the correct SP level: In SAP Service Marketplace and via standard delivery (for example Software Catalogue) only the current Service Release is delivered to SAP customers / partners. If you encounter the situation that SAP Best Practices is based on SP levels LOWER than the current SR, the request for the necessary SP 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).

2.2.5 SAP Enterprise Extensions and Enterprise Business Functions

UseAfter installing SAP ERP, the following SAP ECC extension sets need to be activated before you start activation of the SAP Best Practices for Services Industries Package:

EA-FS Financial Services

EA-PLM PLM Extension (this extension is only needed if you want to activate one or more of the scenarios that belong to the Service Providers area).

EA-TRV Travel Management Extension (this extension is only needed if you want to activate one or more of the scenarios that belong to the Service Providers area).

The following business functions need to be activated:

/KYK/GEN_AIO_SIMPLIFICATION (SAP All-In-One Roles)

Procedure1. Run the following activity:

IMG Menu Activate SAP ECC Extensions

Transaction Code SFW5

2. On the Switch Framework: change Business Function Status screen, select each of the following entries and then choose the Activate Changes button.:

Enterprise Extensions Planned Status

EA-FS On

EA-PLM On

EA-TRV On

Business Functions Planned Status

Remarks

LOG_MM_CI_1 On Materials Management

Required for all Materials Management/Procure-ment (BB 104) Scenarios

LOG_MM_CI_3 On Materials Management - Enhancements in Procurement

Required for all Materials Management/Procure-

© SAP AG of 72



ment (BB 104) Scenarios

LOG_SD_CI_02 On Required for Sales Scenario Batch Recall (BB 122)

Required for Service Scenario (BB 196)

Only if you use SAP NWBC 3.0, activate the following business function in addition to the business functions as listed above.

Business Functions Planned Status

Remarks

/KYK/GEN_AIO_SIMPLIFICATION

On SAP All-In-One Roles

Required for all scenarios (BB 100)

ESOA_OPS01 On Enhancement Package 2 - Service Enabling / ERP Operations

Required for Service Scenarios (BB 192)

LOG_EAM_CI_1 On Enhancement Package 2 - Enterprise Asset Management:


LOG_EAM_CI_2 On Enhancement Package 3 - Enterprise Asset Management


LOG_EAM_CI_3 On Enterprise Asset Management: Continuous Improvements


LOG_ESOA_OPS_2 On Enhancement Package 3 - Service Enabling / ERP Operations


LOG_MM_CI_2 On Material Management - Enhancements in Purchasing for Buyer Role:

Required for all Materials Management (BB 104) Scenarios

LOG_MM_P2PSE_1 On Procurement - SRM Integration


LOG_SD_CI_01 On Sales & Distribution

Required for all Sales & Distribution Scenarios (BB 105)

LOG_SD_CI_02 On Required for Service Scenario (BB 196)

LOG_SD_SIMP_02 On Sales & Distribution Simplification 2 (Order-to-Cash)


OPS_SME_SIMP_01 On Small & Midsize Enterprises Simplification 1 (POWLs for re-usable pool role)

Required for all scenarios (BB100)

© SAP AG of 72


PRS_GEN_UI On Prof. Services, UI Enhancements Required for all Service Scenarios

PRS_HCM_CPILS_1 On HCM, CATS WD Lean Staffing (Reversible)

PRS_ERP_CPILS_1 On Commercial Project Inception & Lean Staffing (Reversible)

SD_01 On Logistics S&D Simplification


3. The system displays an informational dialog box. Choose Continue.

4. Choose Back.

5.

2.2.6 Creation of Client for SAP Best Practices ActivationYou have to create a client in which you will activate the SAP Best Practices Package. Usually this client is a copy of the SAP standard client 000.

Ensure that you have activated all Enterprise Extensions Sets and Enterprise Business Functions as outlined in the chapter SAP Enterprise Extensions Sets and Enterprise Business Functions (see above) before you start the client copy.

If you want to perform several activations of SAP Best Practices in different clients, you can create as many clients as you need. In this case pay attention to the following remarks:

Note that the default operating concern as delivered by SAP Best Practices can be created only once in a system, i.e. during the second activation in another client of the same system you will get a dialog box that outlines that the operating concern already exists. In this case, you can use the SAP Best Practices personalization feature (see below chapter Scoping and Activation of Scenarios, Step 5: Personalize the Solution) and choose another value for the operating concern.

Note that you have to release the transport request including the SAP Script objects after you have completed the activation in one client and before you start the next activation in another client. Otherwise you will run into an error in Building Block 153.

Note that you have to release the transport request including the DataSource Application Component Hierarchy object (APCO_MERGED) after you have completed the activation in one client and before you start the next activation in another client. Otherwise you will run into an error in Building Block 106.

2.2.7 System Status of Client RolesThe system cannot have any clients with a role of 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 code SCC4.

© SAP AG of 72


The client role must not be empty to avoid activation errors; SAP recommends to choose the client role Test (development test client) or Customzing (customizing and development client). More information on the client role concept can be found in the SAP NetWeaver help library in the section Change and Transport System - Overview (BC-CTS) Basics of the Change and Transport System Clients and Their Roles.

2.2.8 SAP Notes and MessagesIt may be that issues become apparent after shipment of this Best Practice Package (and hence of this document). An SAP Note exists to cover such eventualities.

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.

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 have to perform a mass generation using transaction SGEN as described in the SAP Note 481548.

SAP Note # Description Component

1595694 SAP Best Practices for Services Industries Package DE V2.605

SV-SMB-AIO-BP-PSV

The following SAP Notes must be implemented (if not stated otherwise in the note mentioned above):

SAP Note #

Description Component Area Cross client

Remark

1301301 Release Strategy for SAP Best Practices Package ABAP Add-ons

SV-SMB-AIO-BP

Activation x In this SAP note the relevant solution builder overview note for your solution builder version is referenced. Always check this referenced note and apply the mentioned notes.

2.2.8.1 SAP Notes and Messages for ERPThe following SAP Notes must be implemented (if not stated otherwise in the note mentioned above):

SAP Note # Description Area Component

1169255 Status MVA0 of the user interface SAPLCSDI missing

Activation LO-MD-BOM

1140645 SPRO: Error message when changing statistical key figures

Usage PS-PRG-EVA

1273429 KSAZ: Maintaining new overhead rates w/ several

Usage CO-OM-CCA

1161685 Real-time integration/KALC: Error Usage FI-GL-GL-RP

© SAP AG of 72


SAP Note # Description Area Component

message K5 110

1279236 Change in the Standard VAT RATE UK Usage XX-CSC-GB

1504266 Message CY374 issued when exiting a PM/CS order

Usage CS-SE

1513780 Config. sales UI, Business Partner: Sales employee

Usage EP-PCT-SD-S

1382685 SE 729 Customizing incorrectly maintained

Usage MM-SRV-SR

1541888 Frequent/repeated accesses to the table REPOSRC

Usage BC-ABA-LA

Only if you use SAP NWBC 3.0, implement the following SAP Notes in addition to the SAP Notes as listed above.

SAP Note #


Remark

1069540 Printer Configuration for PDF Display in NWBC

BC-MUS-WDK Usage partly This SAP Note is only needed if you want to use PDF display of print output.

1388279 Initialization of Sales Order Type per BADI in NWBC

SV-SMB-AIO-BP

Usage x

1433603 NWBC causes locks in WebDynpro applications

BC-WD-CLT-BUS

Usage x

1353538 SAP NetWeaver Business Client 3.0 - Patch Collection

BC-WD-CLT-BUS

Usage x

1400383 SAP BP: SAP NWBC 3.0 as of EhP4 for SAP ERP 6.0

BC-WD-CLT-BUS

Usage 1) Some of the activities listed in this SAP Note are also addressed in the following chapters. If you encounter some steps that already have been covered by applying this SAP Note, you can skip them accordingly.2) Skip the section in the SAP Note Activate Services in TX SICF. All services are listed in the Quick Guide below.

1586295 IFbA: unnecessary call of ADS

BC-WD-ABA Usage x Fix for Display as PDF functionality for selected forms in POWL

570861 Checking the size between subscreens and elements

BC-FES-GUI Usage x

1230387 ICF: Program termination when displaying the context

BC-MID-ICF Usage x

1302877 Maintenance EP-PCT-MAN- Usage x

© SAP AG of 72


SAP Note #


Remark

Roles: Problem with the BC sets

MT

1308147 SAP GUI Crash with Adobe 9 and ECL Viewer 6.0

CA-DMS-EAI Usage x

1368177 NWBC v3.0 for BAiO

BC-WD-CLT-BUS

Usage x

1391068 Configurable sales UI, creating sales document type

EP-PCT-SD-S Usage x

1395169 Portal role ISR, orders due for delivery

LE-SHP-DL Usage x

1396373 PReq without material number in portal or NWBC

EP-PCT-PUR-BP

Usage x

2.2.9 General Settings in the ERP SystemAfter installing SAP ERP and the other needed SAP components, applying the required SAP SP and SAP Notes, and importing the SAP Best Practices Add-on, you can prepare your system for activation.

2.2.9.1 Set Up of http and https Services

Usehttp and https services have to be set up.


Transaction Code SMICM

2. On the ICM Monitor screen, choose the menu path Goto Services (shift+F1)).

3. Activate http and https services.

2.2.9.2 Activation of Services for SAP Best Practices Solution Builder and SAP NWBC

Activate the services needed for the SAP Best Practices solution builder and SAP NWBC using the transaction SICF.

1. Call transaction SICF

2. On the Maintain Services screen choose Execute (F8).

3. On the Maintain service screen expand the Virtuelle Hosts / Services node as follows and activate all the services listed below:

default_host sap public myssocntl

© SAP AG of 72


default_host sap bc bsp smb sc_scoping_tool

Remark: These services are needed for the SAP Best Practices solution builder

Only if you use SAP NWBC 3.0, activate the following services in addition to the services as listed above.

default_host sap bc bsp sap bsp_veri

default_host sap bc bsp kyk dal_home

default_host sap bc bsp sap htmlb_samples

default_host sap bc bsp sap it00

default_host sap bc bsp sap public bc

default_host sap bc bsp sap sbspext_htmlb

default_host sap bc bsp sap sbspext_xhtmlb

default_host sap bc bsp sap system

default_host sap bc dal demoA

default_host sap bc dal demoB

default_host sap bc echo*

default_host sap bc error*

default_host sap bc igs_data

default_host sap bc NWBC*

default_host sap bc print*

default_host sap bc smart_forms

default_host sap bc wdvd

default_host sap bc wd_trace_tool

default_host sap bc webdynpro kyk*

default_host sap bc webdynpro sap o2c_*

default_host sap bc webdynpro sap cust_cockpit_comp

default_host sap bc webdynpro sap create_complaints_comp

default_host sap bc webdynpro sap lcm_application

default_host sap bc webdynpro sap lo_oif_main_app call

default_host sap bc webdynpro sap lo_oif_cdocs_appl

default_host sap bc webdynpro sap LO_OIF_OC

default_host sap bc webdynpro sap lo_oif_reuse_cond_appl

default_host sap bc webdynpro sap lo_oif_vcfg_appl

default_host sap bc webdynpro sap lord*

default_host sap bc webdynpro sap POWL*

default_host sap bc webdynpro sap WDK*

default_host sap bc webdynpro sap wdhc_application

default_host sap bc webdynpro sap WDR_TEST_EVENTS

default_host sap bc webdynpro sap wdr_test_ui_elements

default_host sap bc webdynpro sap WDR_TEST_TABLE

default_host sap bc webdynpro sap WDR_TEST_POPUPS_RT

© SAP AG of 72


default_host sap bc webdynpro sap configure_*

default_host sap bc webdynpro sap wd_*

default_host sap bc webdynpro sap mt_order_app

default_host sap bc webdynpro sap mmsrv_sp_details_app

default_host sap bc webdynpro sap mmpur_vndctcdta_app

default_host sap bc webdynpro sap qimt_notification_app

default_host sap bc webdynpro sap cfs_application

default_host sap bc webdynpro sap mmpur_ui_pr_app call

default_host sap bc webdynpro sap PRS_GAF_APP

default_host sap public bc icons

default_host sap public bc icons_rtl

default_host sap public bc pictograms

default_host sap public bc ur

default_host sap public bcwebdynpro*

default_host sap public bc webicons

default_host sap public bsp sap htmlb

default_host sap public icf_info*

default_host sap public icman

*activate all services.

Choose Back.

2.2.9.3 Generation of RV13xxxx Reports1. Call transaction SE38.

2. In the Program field, enter RV12A001, then choose Execute (F8).

3. In the Condition tables: Subsequent Generation – Online screen, select the Reports and Screens checkbox and Online checkbox. Leave all other fields empty.

4. Choose Execute (F8).

The system starts generating the RV13xxxx reports. This process may take up to two hours.

If the system shows error messages (for example message no.VK769, VK769, VK770), you can ignore these errors.

2.2.9.4 Generation of Financial Accounting Programs 1. Call transaction SE38.

2. In the Program field, enter RGZZGLUX. Then choose Execute (F8).

3. Choose Back and leave the transaction.

© SAP AG of 72


2.2.9.5 Creation of Consistent Business Transaction Groups For the execution of assessments, distributions, periodic repostings or indirect activity allocations in several applications (for example, the CO-OM application), groups have to be defined in the current client which summarize all actual or planned transactions. As default, these groups are either not available or do not have the latest status. As consequence, some system transactions (for example KSVB, KSUB, KSV5, KSU5, etc.) will result in the following error: Customizing error: Business transaction groups are not current. Message no. GA627.

Proceed as follows to correct the inconsistency:

1. Call transaction SE38.

2. In the Program field, enter the report name RK811XST to run the correction in your current client (the client where the SAP Best Practices activation is planned to be done).

3. Choose Execute (F8).

2.2.9.6 Generation of Characteristic VRTNRThe characteristic VRTNR is not correctly provided in the system. It is not possible to maintain this characteristic.

This error is not caused by SAP Best Practices configuration. The following procedure provides a method to correct an inconsistency which might be caused by system set up. Note: Usually the step /SMB99/KEA0_O200_168 in building block 168 runs red if this correction is not done.

Proceed as follows to correct the inconsistency:

1. Access the activity using the following navigation options:

IMG Menu Controlling Profitability Analysis Structures Define Operating Concern Maintain Characteristics

Transaction Code KEA5

2. Check first availability of characteristic VRTNR. On the Edit Characteristic: Start screen select All Characteristics and choose Display.

3. On the Display Characteristics:Overview screen search for char. (characteristic) VRTNR and choose Back

If VRTNR is listed in the table, the error does not exist. In this case no further actions are required. Leave the transaction.

4. Proceed with following steps if characteristic VRTNR is not found.

5. On the Edit Characteristic: Start screen enter the value WWXXX in field Char. and select Create/Change.

© SAP AG of 72


Enter exactly the value WWXXX.

The characteristic WWXXX is used to enter the transaction without any change. Maintenance is done for the missing characteristic VRTNR.

6. In the Caution: You are processing Cross client data structures dialog box, choose Continue.

7. On the Change Characteristic: Overview screen, choose Create.

8. In the Creat Char: Assignment dialog box:

a. Select the Transfer from SAP Table option.

b. In the Table field, enter PAPARTNER.

c. Choose Create.

9. In the Reference table dialog box, select the VRTNR field and choose Confirm.

10. In the Warning dialog box, choose Enter.

11. In the Save Inspite of Warnings dialog box, choose OK.

12. On the Create Char. VRTNR screen enter 2 in field “Display opt.” (see section “further properties”).

13. Save your entries.

2.2.10 Getting the Solution Scope File

UseThe technical structure for each solution (scenarios, building blocks and technical objects) of the SAP Best Practices is managed by a solution scope file.

Procedure1. The solution scope file can be found as attachment to the SAP Best Practices Services

Industries support Note (for details on the SAP Note number see above section SAP Notes and Messages).

2. Download the solution scope ZIP-file which corresponds to:

5XXXXXXX_SCOPE_SP_DE_V2605_<Add-On Version>.ZIP

The naming convention corresponds to:

the material number of the configuration DVD 5XXXXXXX

or the number of the download object / file in the software distribution center (same number as material number of configuration DVD)

5XXXXXXX.ZIP

The number of the download object can be found on the SAP Software Distribution Center in the download area for the download object Config: Best Practices All-in-One.

© SAP AG of 72


or the SAP Best Practices Add-On Version for example BP-ERP 605V1

You can determine the Add-On Version as follows:SAP Easy Access menu: System ® Status ® Component information (Prerequisite: The Add-On version/release has been installed in the system).

2.2.11 Getting the Installation Data Files for ERP

UseThe installation settings (configuration settings and master data) of the SAP Best Practices are managed by the installation data files.

Procedure1. The installation data files can be found in the SAP Best Practices area on the SAP Service

Marketplace at http://service.sap.com/bestpractices. On the left side menu select the section Data Files for Installation and then choose the release SAP ERP 6.0 EhP5 and select the country Germany.

2. Download installation data ZIP-file package

<Mat-Nr Config DVD>_BP_FILES_<country>_<Add-On Version>.ZIPThe naming convention corresponds to:

the material number of the configuration DVD 5XXXXXXX

or the number of the download object / file in the software distribution center (same number as material number of configuration DVD)

5XXXXXXX.ZIP

The number of the download object can be found on the SAP Software Distribution Center in the download area for the download object Config: Best Practices All-in-One.

or the SAP Best Practices Add-On Version for example BP-ERP 604V1

You can determine the Add-On Version as follows:SAP Easy Access menu: System ® Status ® Component information (Prerequisite: The Add-On version/release has been installed in the system).

2.2.12 Creating a Folder for the SAP Best Practices Activation1. Create a folder on a hard drive (on your local hard drive) that can be accessed from within

the SAP system where you want to activate the SAP Best Practices Services Industries Package. Ensure that the persons who will activate SAP Best Practices have the necessary user rights to access this folder.

2. Extract the files from the files you downloaded in the previous task into the folder you created in step 1. You should have a solution scope file (*.xml) and many variant files (*.txt) and one bitmap file (smb40_leaf.bmp).

© SAP AG of 72

http://service.sap.com/bestpractices


2.3 SAP CRM

The complete chapter 2.3 SAP CRM is only necessary if you are interested in CRM and if the CRM Scenarios included into the Services Industries Solution should be installed!

The CRM Scenarios are listed below:

BB Nr. Description

431 Opportunity Management for Services Industries

C39 Lean Campaign Management

C30 Lead Management

C80 Interaction Center Service

C81 Interaction Center Marketing

C66 Account and Contact Management

C62 Activity Management

C67 Pipeline Performance Management

C82 Interaction Center Sales (with ERP Sales Order)

C38 Complaints and Returns Management

CR2 Interactive Reporting for Marketing, Sales and Service Scenarios

The configuration of the CRM scenarios in the Best Practice for Services Industries package requires a consistently and completely installed SAP CRM system landscape.

2.3.1 CRM System Landscape Considerations

The configuration of the Best Practice Services Industries with CRM scenarios requires a consistently and completely installed SAP CRM system landscape. An overview with all listed CRM Scenarios is listed in the chapter SAP CRM System.

Depending on the selected Services Industries CRM Scenario scope, different system landscape components have to be installed.

The Master Guide SAP enhancement package 1 for SAP CRM 7.0 provides important information about installation planning for SAP CRM 7.01 scenarios. It gives an overview of the installation documents that are available for the installation of a CRM component.

This document is available on the SAP Service Marketplace (www.service.sap.com/crm-inst).

© SAP AG of 72

http://www.service.sap.com/crm-inst


The Services Industries CRM scenarios are often only use a subset of the overall SAP CRM functionality. Therefore the required system components for the BP CRM scenarios may differ from the recommendation in the Master Guide SAP enhancement package 1 for SAP CRM 7.0.

Please use the following table as guidance if you would like to install the minimum CRM system landscape required for running the BP CRM scenarios, listed as follows.

2.3.2 Release and Support Package Level 2.3.2.1 General RecommendationsThe deliverables of SAP Best Practices were developed and tested in a system landscape with specific support package levels. If the support package levels in your system are different, there might be errors during the installation. You may be able to perform the installation activities manually using the configuration guides, but errors may also occur.

For cases when the support package levels do not match the SAP Best Practices requirements, especially when HIGHER support package levels are implemented, only LIMITED SUPPORT can be provided.

If you need a higher support package level in your system, for example because of additional functionality, FIRST import and activate SAP Best Practices on the system support package levels as mentioned below, THEN upgrade your system to the latest support package level.

© SAP AG of 72


The support package levels relevant for SAP Best Practices for Services Industries Package (DE) V2.605 are as follows. The following components listed in chapter Required SAP Components must be installed.

2.3.2.2 SAP CRM SystemIf you want to install the Services Industries CRM-Scenarios of SAP Best Practices for Services Industries V2.605, they require SAP CRM 7.0 Enhancement Package 1 with Support Package Stack 04. The relevant scenarios are as follows:

Relevant building blocks for CRM:

BB Nr. Description

431 Opportunity Management for Services Industries

C39 Lean Campaign Management

C30 Lead Management

C80 Interaction Center Service

C81 Interaction Center Marketing

C66 Account and Contact Management

C62 Activity Management

C67 Pipeline Performance Management

C82 Interaction Center Sales (with ERP Sales Order)

C38 Complaints and Returns Management

CR2 Interactive Reporting for Marketing, Sales and Service Scenarios

Path to download from the Software Distribution Center (SWDC) on the SAP Service Marketplace (SMP):https://service.sap.com/swdc SAP Software Download Center Support Packages and Patches Support Packages and Patches A - Z Index C SAP CRM SAP CRM ENHANCE PACKAGE EHP1 FOR SAP CRM 7.0 Entry by Component CRM Application Server ABAP SAP CRM ABAP 7.01 Support Packages BBP CRM 7.01: SP 0004 (04/2011).

Detailed information regarding the installation of this support package stack can be found in SAP Note SAP Enhancement Package 1 for SAP CRM 7.0 SP-Stack 04

2.3.2.3 SAP BW SystemSAP BW can optionally be used in combination with BP CRM.

Services Industries V2.605 CRM Scenarios has only been validated with SAP BW 7.02 including SAP BI Content Add-on 7.05.

In general, SAP CRM 7.01 can be combined with SAP BW releases lower than 7.0.Please see the document Master Guide SAP enhancement package 1 for SAP CRM 7.0 for details about required SAP BW releases depending on the selected scenario.

© SAP AG of 72



However, the Services Industries V2.605 CRM Scenarios documentation is only provided for the recommended SAP BW release level, therefore this documentation is not valid for topics that are not identical in the different SAP BW releases.

2.3.3 SAP Best Practices Add-onsThe following SAP Best Practices add-ons have to be installed in order to use the automated installation of BP CRM:

Software Component

Release Version

BP-CRM (1) 701 Always use the latest available version as outlined in SAP Note 1301301 (Release Strategy for SAP Best Practices Package ABAP Add-ons)BP-SOLBLD (1) 70

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

The installation procedure of the SAP Best Practices add-ons is described in the following sections of this guide:

Installation of the SAP Best Practices Add-On

Installation of the SAP Best Practices Solution Builder

2.3.4 SAP Notes and Messages for CRMIt may be that issues become apparent after shipment of BP CRM (and hence of this document). An SAP Note exists to cover such eventualities.

1) 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.

2) All notes have to be applied to the system via the SAP Note Assistant. 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 status completely implemented.

SAP Note # Description

1569021 SAP Best Practices for CRM V1.701

1595694 SAP Best Practices for Services Industries Package DE V2.605

Implement the following SAP Notes before proceeding with the next steps in this guide:

SAP Note # Description

854170 * Activation of the Component VM Container

1084188 SCPR20: SCPR116 Error during BC Set Activation.

1060253 Problem in activating BC Sets

* Activate the component VM Container in case this has not been done during the system installation.

© SAP AG of 72





Attached to central SAP Note 1569021 you can find file xxxxxxxx_BP_CRM_SAP_Notes_701V1.zip. It's an overview list (XLS) of all SAP Notes, which are of relevance for implementing the SAP Best Practices for CRM solution.

Those SAP Notes in the overview list, which are classified as Application Software Correction (that are SAP CRM application software corrections) can already be implemented in advance, before starting with the SAP Best Practices for CRM implementation.

Note that there are more SAP Notes valid for either the SAP Best Practicesinstallation or the scenario usage; such Notes are explicitly mentioned in theConfiguration Guides of the relevant building blocks.

2.3.5 Activation of the Component VM ContainerActivate the component VM Container if this has not been done during system installation. For details, refer to SAP Note 854170.

At least the following system parameters need to be set:

vmcj/enable = on

vmcj/guard_page_num = 5

vmcj/max_vm_heap_MB = 64M

vmcj/option/maxJavaHeap = 100M

vmcj/option/ps = 256M

After the definition of these parameters the system needs to be restarted.

Some scenarios are making use of the Virtual Machine Container (VMC). To ensure that VMC is running correctly we recommend to install the current SAP AP IPC JAVA 7.00 patch according to the following SAP Notes:

SAP Note 1426699 (procedure): (-> SP Patchlevel)

SAP Note 880749 (technical backround).

In product SAP CRM 7.0 SPS05 software component SAP AP 7.00 SP18 is included – please download therefore the SCA provided with the download link in note 1426699 for Software Component Version SAP AP IPC JAVA 7.00 SP018 to your PC. After that you can upload the SCA using transaction SE38, program RSVMCRT_UPLOAD_SCA_FROM_PC. Further details are given in the two mentioned notes.

In order to ensure, that current objects were selected after the installation of a new patch, you should reset the VMC using transaction SM52:Goto > System Wide Display > Virtual Machine Container > Reset Globally

2.3.6 TroubleshootingIf errors occur during the installation process, proceed as follows:

1. Check for troubleshooting notes in the SAP notes overview list being attached to SAP note 1569021, or in the step description of the Configuration Guide.

© SAP AG of 72








2. Check for SAP Notes on the relevant topic in the SAP notes overview list being attached to

SAP note 1569021, or in the section SAP Notes 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:

1. Only if the problem relates to the package's SAP Best Practices pre-configuration, open a customer message

for package SAP Best Practices for CRM with component SV-SMB-AIO-BP-CRM.

2. If the problem is a general one, indicate the relevant application component.

2.3.7 Related Documentation for CRM issuesThe Master Guide SAP enhancement package 1 for SAP CRM 7.0 provides crucial information on the installation of SAP CRM 7.01. Read this guide thoroughly.

The Security Guide SAP enhancement package 1 for SAP CRM 7.0 provides an overview of the security-relevant information that applies to SAP CRM.

The Application Operation Guide EhP1 for SAP CRM 7.0 provides a starting point for managing your SAP solutions and keeping them up and running optimally.

To access the latest version of these guides, log on to the SAP Service Marketplace (www.service.sap.com/crm-inst) to access the installation guidelines. Go to section SAP enhancement package 1 for SAP CRM 7.0.

2.3.8 General Settings in the CRM System2.3.8.1 Changing the CRM SAP Menu

UseSet the default SAP menu to the CRM standard menu CRM_MENU (Extended Relationship Management).

Run this default setting only once.Skip this activity if the SAP menu in the CRM system already contains the standard CRM entries.


SAP CRM transaction code SSM2

2. On the Set initial screen for the R/3 System screen, choose Set initial menu systemwide. It lists all the possible entries.

3. In the column Area menu, choose CRM_MENU (Extended Relationship Management)

4. Choose Copy or double-click the entry.

5. In the dialog box Prompt for Workbench request, choose Create request (F8) (or use an existing Workbench request).

6. Enter a short description and choose Save or Enter.

© SAP AG of 72

http://www.service.sap.com/crm-inst



7. Choose Continue.

2.3.8.2 Client Settings2.3.8.3 Maintain Client Settings for SAP CRM

UseThis activity adjusts the client settings to enable the SAP Best Practices installation.

Procedure1. Access the activity using one of the following navigation options:

Transaction code SCC4

SAP CRM GUI menu Architecture and Technology System Administration Administration Client Administration Client Maintenance

2. Choose Display Change.

3. Confirm the message Caution: The table is cross-client.

4. Select your CRM client.

5. Choose Details. The Change View “Clients”: Details screen appears.

6. Enter the following data:

Field / Area Entry

Logical system <Entry will be created in the building block CRM Connectivity>

Client role Customizing

Changes and Transports for Client-Specific Objects

Automatic recording of changes

Cross-Client Object Changes Changes Allowed to Repository and Cross-Client Customizing

Protection: Client Copier and Comparison Tool

Protection level 0: no restriction

CATT and eCATT Restrictions eCATT and CATT Allowed

7. Save and confirm the warning message Be careful when changing the logical system.

2.3.8.4 Maintain Client Settings for SAP ERP (CRM Back-end)

UsePlease check the following settings in the SAP ERP system.


Transaction code SCC4

SAP ERP IMG menu Tool Administration Administration Client Administration Client Maintenance

© SAP AG of 72


2. On the screen <Display View: “Clients”: Overview> switch to the change mode.

3. Select your current client and choose Details.


Field / Area Entry

Logical system <Entry will be created in the building block CRM Connectivity>

Client role Customizing

Changes and Transports for Client-Specific Objects

Automatic recording of changes

Cross-Client Object Changes Changes to Repository and cross-client Customizing allowed.

Protection: Client Copier and Comparison Tool

Protection level 0: no restriction

CATT and eCATT Restrictions eCATT and CATT Allowed

5. Save and confirm the warning message Be careful when changing the logical system.

2.3.9 Setup of SAP Best Practices Solution Builder for CRM

UseBefore using the SAP Best Practices Solution Builder, you maintain the crucial connectivity settings. Otherwise, transactions and IMG activities located in other systems like SAP ERP cannot be accessed directly from the Solution Builder in the CRM system.

2.3.9.1 Maintaining RFC Connection

UseRFC connections between the CRM application client and the following systems have to be created:

SAP ERP application client

SAP BI client

SAP Interactive Reporting client


Transaction code SM59

SAP CRM IMG menu Customer Relationship Management CRM Middleware and Related Components Communication Setup Define RFC Destinations

2. Choose Create (F8).


© SAP AG of 72


Field Entry

RFC Destination <ERP system name>CLNT<client>_IA, e. g. CS7CLNT200_IA

Connection Type 3 (ABAP connection)

Description ERP RFC connection for Solution Builder

4. Choose Enter.

Technical settings

Load Balancing No

Target host <Target host ERP system>, e. g. pwdf0421

System number <System number of ERP system>

Logon/Security

Trusted system No

SNC Option Inactive

Language EN

Client <ERP client>

User<A dialog user is required in the ERP system for this RFC connection. Sufficient authorizations to run the configuration activities have to be assigned to this user.>

Password <Enter a password for the user>

Current user

Unencrypted password

MDMP & Unicode

Communication Type with target system

Set Unicode flag if Unicode Test has been executed successful

5. Save your RFC destination.

6. You can now test your newly created RFC connection using Test connection.

7. Repeat these steps in order to create RFC connection to the BI client and/or the Interactive Reporting client.

In case you would like to avoid maintaining a general user for the RFC connections, you can also set up a trusted connection from SAP CRM to the other SAP systems/clients.

2.3.9.2 Maintaining System Landscape

UseWhen activating scenarios in the Solution Builder, access to different systems is required. Therefore, RFC connections have to be maintained and assigned to the project.

Information on the connections to other relevant systems is maintained in a system data container of the eCATT. This system data container must be assigned to the project.

© SAP AG of 72


The assignment of this system data container to the Solution Builder project is described in section Implementing a Solution.


Transaction code SECATT

SAP CRM menu Architecture and Technology ABAP Workbench Test Test Workbench Test Tools Extended CATT

2. Enter /SMB20/ALL_H001 in field System Data and choose Copy Objects.

3. In the Copy dialog box enter Z_SMB20_ALL_H001 in field to System Data Container and choose Copy.

4. In the Create Object Directory Entry dialog box choose Local Object.

5. On the Extended Computer Aided Test Tool screen enter Z_SMB20_ALL_H001 in field System Data and choose Change Object.

6. Make the following entries:

Target System RFC Destination

ECC Enter the RFC connection to SAP ERP application client

BI Enter the RFC connection to SAP BI application client

REP Enter the RFC connection to SAP CRM Interactive Reporting client

CRM No real RFC connection but only the value NONE has to bemaintained

7. Choose Save.

2.3.10 Installation Options for Services Industries with CRM

UseBefore running the installation as described in section Installation of Business Content, choose between the different installation options offered by Services Industries CRM Scenarios.

2.3.10.1 SAP ERP Back-End with SAP Best Practices Configuration or Customer-specific Configuration

UseServices Industries CRM Scenarios can be used in combination with an arbitrary customer-specific SAP ERP system or an SAP ERP system configured with the help of a SAP ERP-based SAP Best Practices for Services Industries package version.

© SAP AG of 72


2.3.10.1.1 Arbitrary SAP ERP Back-End SystemIn case of integration with an SAP ERP system, Services Industries CRM Scenarios provides no sample master data on customers, products, conditions and the like, nor standard sales or distribution customizing such as pricing procedures.

Usually, this data is initially replicated from the SAP ERP system into the SAP CRM system. Therefore, it depends on the content of the connected customer-specific SAP ERP system.

For this reason most of the configuration activities related to this data are generic, that is without concrete master data samples.

Master data samples are only provided for purely CRM-specific master data, such as product catalog or service products.

2.3.10.1.2 SAP ERP Back-End System with other SAP Best Practices Packages

If an SAP Best Practices for Services Industries package or Industry package has been applied in the SAP ERP system, the master data and the sales and distribution customizing data is known, so the CRM configuration can be done by using the data of the For Services Industries package data.

In this case so-called Delta Guides will provide all relevant information for an easy integration of the Industry package ERP scenarios with the CRM scenarios, such as mapping of organizational structure, replication of customizing, master data and basic functions.

Every configuration activity in a Configuration Guide or Installation Guide of BP for Services Industries CRM Scenarios for which Industry package-specific data is provided has a reference to the corresponding Delta Guide. This is indicated by the remark Please Check Delta Guide at the beginning of the configuration activity. In this case a Industry package-specific Delta Guide for the Configuration Guide exists, open the corresponding Delta Guide and use the concrete data instead of the generic configuration description of the configuration activity.

2.3.10.2 Installation with SAP ERP Integration or SAP CRM Standalone Integration

The typical use case of Services Industries CRM Scenarios is to set up the configuration for CRM scenarios in an SAP CRM system that is connected to an SAP ERP system.

This is valid for all scenarios requiring integration with logistics and/or accounting.

But Services Industries CRM Scenarios also provides the relevant configuration for a standalone use of SAP CRM, that is without integration of a SAP ERP system.

A Services Industries CRM Scenarios standalone installation makes sense for the following use cases:

An implementation of SAP ERP is not in scope.

The implementation scope of Services Industries CRM Scenarios only comprises scenarios which do not require integration with logistics and/or accounting.

For prototyping or demo purposes the SAP ERP integration is postponed to a later project phase in order to run a very quick installation of the Services Industries CRM Scenarios.Therefore, functional restrictions of the scenarios caused by missing SAP ERP integration are accepted.In the development phase, use the SAP CRM integration option to newly configure the scenarios.

The Services Industries CRM Scenarios documentation DVD contains the following sources of information to identify the possible scenario scope of these installation options:

© SAP AG of 72


Business Information Preconfigured Scenarios Scenario Map

The Solution Builder provides separate Solution Scope files for these installation options. See section Step 1: Import Solution for details.

2.3.11 Create Installation Folder for the SAP Best Practices CRM Installation Files and Scope File

UseThe scoping, the personalization and the installation phase of the Solution Builder require solution scope and installation data files in a specific folder.

Procedure1. Create an installation data folder on a server that can be accessed from within the CRM

system where you want to install the CRM Scenarios from the Services Industries package. Ensure that the persons who will install SAP Best Practices have the necessary user rights to access this folder.

2. The solution scope file can be found as attachment 51040873_SCOPE_SP_V2605_CRM_605V3.zip to the BP for Services Industries support note (for details on the current note number, see the above section SAP Notes and Messages):SAP Best Practices for Services Industries Package DE V2.605

3. Unpack the file 51040873_SCOPE_SP_V2605_CRM_605V3.zip and copy the solution scope file (*.xml file) that is needed for the SAP Best Practices installation into the installation data folder created in step 1.

4. The installation data files can be found as following attachments to the support SAP note of BP CRM: 51039840_BPCRM_InstFiles_<language>_700V3.zip.

Here you find a number of ZIP files named with a two letter language abbreviation (for example, ‘DE’). Unpack the language-specific ZIP file, which is relevant for your project, into the installation data folder created in step 1. Now you have the installation data files (*.txt files) also containing language-specific sample master data unpacked in this folder.

3 Pre-Activation ActivitiesUseAfter installing SAP ERP and/or SAP CRM and the other needed SAP components, applying the required SAP SP and SAP Notes, and importing the SAP Best Practices Add-on, you can prepare your system(s) for activation.

The following chapters have to be performed for all systems you want to set up!

© SAP AG of 72


3.1 User Settings for Activation

For activation, we recommend that only one User ID be used to activate the SAP Best Practices. It can be a tedious procedure to change ownership of the activation of the solution.

3.1.1 User Maintenance

UseIn this activity, you create test users.

Newly-created users are assigned the profiles SAP_ALL and SAP_NEW, giving them full authorization rights. If this authorization does not apply to your project, you should restrict the rights of the users according to your internal authorization guidelines. For more information, see SAP Note 0338537.

Procedure 1. To carry out the activity, choose one of the following navigation options:

SAP Menu Tools ® Administration ® User Maintenance ® Users

Transaction Code SU01

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

3. Choose the Address tab.


Field name User action and values Note

Last name Test user

First name Test user

5. Choose the Logon Data tab.



Password Initial

User type Dialog

7. Choose the Defaults tab.



Logon language EN

Decimal notation 1.234.567,89

Date format DD.MM.YYYY

© SAP AG of 72


9. Choose the Profiles tab.

10. Maintain the profiles SAP_ALL and SAP_NEW.


ResultA test user has been created.

3.1.2 SAP Software Change Registration (SSCR): Developer Key

UseThe user ID used for activation has to be registered as developer on SAP Service Marketplace (SAP Software Change Registration (SSCR)). For details see SAP Note 86161. The SSCR developer key is needed, because the user ID used for SAP Best Practices activation creates and changes objects from the customer name range during the SAP Best Practices activation process. If the SAP Best Practices activation user is not registered as developer, the automated SAP Best Practices activation will run into errors.

Procedure1. 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 on how to proceed to get the SSCR developer key.

An SSCR developer key is a 20 character combination of digits which 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 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.

3.1.3 Unicode Settings

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

Procedure1. From the SAP Logon 720 pad, select your system ID, then choose the Change Item button.

2. On the System Entry Properties dialog box, choose the Code Page tab.

3. On the Encoding dropdown, select Unicode (UTF-8).

4. Choose OK.

© SAP AG of 72

http://service.sap.com/sscr


3.1.4 Allow GUI Scripting

UsePerform this activity so that eCATTs GUI Scripts can by executed with your GUI.

Only those installation users have to perform this activity that do not install the first scenario (for example, someone else already installed a specific scenario and you want to install an additional scenario).

Procedure1. Choose the first button from the right side of the Standard Tool Bar Customizing of Local

Layout or type ALT + F12.

2. Select the menu item Options.

3. Choose the tab Scripting.

4. Select the checkbox enable scripting.

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

6. Choose the OK button at the bottom.

3.1.5 Set Decimal Notation and Date Format

UsePerform this activity to set up the activation user ID.


SAP Menu System à User Profile Own Data



3. Make sure you set Decimal Notation according to your country’s default, like 1.234.567,89.

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

5. Make sure to assign your printer in the field output device (see also chapter Printer Environment above).

6. Save your settings.

7. Log off from the system.

8. Log on to the system.

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

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

© SAP AG of 72


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

3.1.6 Deselection of Activation Links in BC SetsWe recommend that you turn off the creation of activation links. By doing this, you can increase activation speed significantly and avoid errors.


SAP ECC menu Tools Customizing Business Configuration Sets Activation of BC Sets

Transaction Code 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 radio button for Do Not Create parameter.

5. Choose Enter on the information message.


3.2 Maintain Profile Parameters3.2.1 Maximum Work Process Run Time

UseDynamic switchable profile parameters (indicated by a flag in the check box of the parameter) have to be checked before activation. Therefore the following profile parameters must be checked and adapted.


SAP Menu Preparation Maintain Profile Parameters – SAP Scripting

Transaction Code RZ11

2. On the Maintain Profile Parameters screen, make the following entries

Field name Description User action and values Note

Param. Name Profile parameter name rdisp/max_wprun_time

3. Choose Display.

4. On the Display Profile Parameters Attributes screen, select Change values.

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

Parameter Name Description New value

Note

rdisp/max_wprun_time Max work process run time 3600 Check and adapt value if value is <3600

© SAP AG of 72


6. Choose Save.

When you save the change, the window closes and the current value of the parameter changes. 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 activation of SAP Best Practices as there are some processes which need to be performed in dialog and last for more than ten minutes.Switch back to the default value after activation of SAP Best Practices!

3.2.2 SAP Scripting

UseeCATTs are used to automate the activation of SAP Best Practices configuration settings. Prior to activation, you must allow eCATT processing in the system: the profile parameter sapgui/user_scripting must be set. The value for Enable or disable user scripting on the front-end must be set true.

During the activation, this task is executed automatically in Building Block 100, SAP Best Practices activation. After the activation of Building Block 100, if the server is restarted during the activation process, the activation user must perform this activity to allow eCATT scripting.


SAP Menu Preparation Maintain Profile Parameters – SAP Scripting



Field name Description User action and values

Note

Param. Name Profile parameter name sapgui/user_scripting

9. Choose Display.




New Value New Value for user scripting

TRUE Enable SAP Scripting

12. Choose Save.

© SAP AG of 72


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 onto the system again.

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

3.2.3 Authentication using SAP Logon Tickets

UseAs requirement for the usage of the SAP Best Practices solution builder, the following profile parameters have to be set as listed below. The set of these profile parameters is also necessary for the communication between SAP NetWeaver Business Client and SAP EEC system to work correctly. The following points must be met:





Param. Name Profile parameter name login/accept_sso2_ticket

3. Choose Display.




Note

login/accept_sso2_ticket Accept SSO ticket logon for this (component) system

1 Check and adapt value if necessary

6. Choose Save.

7. Choose Back (F3).



Param. Name Profile parameter name login/create_sso2_ticket

9. Choose Display.




Note

login/create_sso2_ticket Create SSO tickets on this system

2 Check and adapt value if necessary

© SAP AG of 72


12. Choose Save.

This adaptation of the profile parameters login/accept_sso2_ticket and login/create_sso2_ticket is necessary if you use the SAP Best Practices solution builder and/or the SAP Netweaver Business Client.

3.2.4 Set Default Timeout for http and https Services

UseIt is recommended that you set the following 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_2 = PROT=HTTPS, PORT=44300, PROCTIMEOUT=300,

TIMEOUT=600



2. On the Edit Profiles screen, enter your instance profile. In the Edit Profile box, select the radio button for Extended maintenance and choose Change.

3. On the Maintain Profile screen, make the following entries


Note

icm/server_port_<*> Standard value for *:

0: http, 1 or 2: https

300or

600

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

4. Choose Back

5. Choose Save.

This adaptation of these profile parameters is only necessary if you use SAP Netweaver Business Client.

© SAP AG of 72


3.3 Printer Settings3.3.1 Default Printer For activation of SAP Best Practices, the standard default printer LP01 is used that is generated during the SAP standard system set up.Once you have activated the SAP Best Practices For Services Industries Package, the printer LP01 cannot be used for printing (for more information on this, see SAP Note 573309). Instead, you must select an existing printer at your site.

Your printer must be linked to a device type for which the HELVE font family is defined (for example to the device type SAPWIN) to ensure that the forms printout is correct.

For personalized SAP Best Practices activations (also see chapter Scoping and Activation of Scenarios, step 5: Personalize the Solution, below), replace the printer LP01 as follows:

1. In the solution builder (solution editor) choose Generic PA (Ctrl + F8).

2. Choose the PA ID OUTPUT_DEVICE (DEFINE PRINTER) from the PA list (on the left side).

3. Enter the new printer name for the parameter I_LDEST (on the right side).

4. The default printer LP01 can only be replaced by a printer already existing in your system (for more information on the printer environment, see next paragraph). If no printer exists, the value LP01 has to be kept to avoid errors during the following SAP Best Practices activation.

3.3.2 Optional Activity: Set up Printer EnvironmentThe following activities are only needed you want to use print functionality in SAP ERP. If you skip these activities, it is still possible to activate SAP Best Practices, but it will not be possible to print in SAP ERP unless you have set up the printer environment.

For details about setting up the printer environment please read the documentation in the SAP Printing Guide (BC-CCM-PRN). The documentation can be found on the SAP Help Portal at

http://help.sap.com/saphelp_nw70/helpdata/en/d9/4a8eb751ea11d189570000e829fbbd/frameset.htm

Once you have set up your printer environment, you can forward the printing requests to your locally installed printers (Win):

1. Choose the transaction SPAD.

2. Select the menu Configuration, Output Devices

3. Choose Edit (select F8)

4. Select Create (Shift + F1)

5. Create the Output Device: LOCL with the short name LOCL

6. In the tab Device Attribute, enter the Device Type: SWIN: Windows printing via SAPlpd

7. In the tab: Access Method, enter the Host Spool Access Method G: Front End Printing with Control Techand the Host printer __DEFAULT

© SAP AG of 72




Inform the users to assign printer LOCL to their default values using the following procedure:

1. Choose transaction SU3.


3. In the Spool Control section enter the Output Device LOCL

4. Select the Output Immediately and Delete After Output checkboxes.


If you want to use the PDF Display in NWBC and you have followed the instructions mentioned in SAP Note 1069540 you may have already assigned a default printer in the user settings.

3.3.3 Printing Bar CodesIf you want to print bar codes, you must follow important information on the requirements to be fulfilled to print bar codes and about printers supported.

See SAP Note 5196 on important details regarding printing bar codes with SAPscript and SAP note 645158 regarding important details regarding printing bar codes with SAP Smart Forms.

3.4 Installation and Usage of the SAP Best Practices Solution Builder

3.4.1 Technical InstallationSAP delivers the SAP Best Practices solution builder program as a separate add-on (BP-INSTASS) on the SAP Best Practices solution configuration CD. Your system administrator will handle installation of the SAP Best Practices solution builder. This component is listed in section Required SAP Components.

3.4.2 Running the Solution Builder

UseThis activity runs the SAP Best Practices solution builder.

ProcedureAccess the activity using the following option:

Transaction Code /n/SMB/BBI

© SAP AG of 72


3.4.3 InterfacesThe SAP Best Practices solution builder consists of three main interfaces:

Solution Builder - Solution Editor

Implementation Assistant

Building Block Builder

DetailsThe Solution Builder – Solution Editor interface covers the following basic functionality:

Manages different solutions (solution editor)

Graphical scoping engine

Enterprise structure composer

Application area editor and assignment

The Implementation Assistant interface focuses on:

Manages and monitors implementation of a solution (scenario based), access to logs

Building block assignment, maintenance of information on scenario level/scenario edit view (e.g. pricing parameters)

The Building Block Builder interface is used for:

Creation of building blocks

Inserting different task types of implementation activities

Maintenance of installation data

The Solution Builder - Solution Editor screen is the first screen you see when you run the transaction; this is the relevant screen for the start of the installation of the SAP Best Practices Services Industries Package. After scoping activities, the actual installation will be done in the Implementation Assistant interface.

3.4.4 SAP Best Practices Solution Builder User GuideThis document describes all the functionalities of the SAP Best Practices solution builder in detail

This user guide is not required for the activation process. All activation steps are described in detail in the following chapter.

The user guide can be found as attachment to the SAP Best Practices solution builder support Note Additional information for BP- SOLBLD 70V* (see SAP Note 1301301; in this SAP note the release strategy for SAP Best Practices ABAP Add-ons is listed including information on the latest solution builder version. Once you have identified your solution builder version, you can check the relevant SAP Note Additional information for BP- SOLBLD 70V* which refers to the version of the solution builder you have in usage).

© SAP AG of 72


4 Activation

4.1 Activation Approaches4.1.1 Automated ActivationFor an accelerated activation approach, most projects use automated activation when deploying SAP Best Practices. This main purpose of this document is to define the requirements and steps required for an automated activation.

4.1.2 Manual ActivationIf you want to activate the Services Industries Package manually using the configuration guides, refer to the Building Block prerequisite matrix (on the documentation DVD, under \BBLibrary\Documentation\ Prerequisites_Matrix_BL_EN_FI.xls). The list contains the information on the activation sequence of the Services Industries Package building blocks.

4.1.3 Automated Activation w/o Demo DataIf you want to activate the Services Industries package without demo data, you can choose to do so during activation. You can deselect a checkbox during activation to turn off activation of demo data. For more information see Step 7: Starting Activation in the Activation section.

After activation is completed, you will not be able to test the business scenarios. The scenario testing requires the presence of the demo data and related configuration settings.

To test the business processes with customer demo data, you can create your own demo data. Proceed as follows:

Select the business scenario you want to test

Check the row in the Prerequisites Matrix spreadsheet for this scenario to determine the required prerequisite building blocks.

Check the master document spreadsheets for this scenario and all prerequisite building blocks to identify the demo data activities. In the master document spreadsheet, this information is on the Building Block Implementation tab, in the Demo Data (& Dependent Configuration) column.

Refer to the corresponding Configuration Guide and create the required configuration and master data activities manually.

For cases when the installation is done without Demo only LIMITED SUPPORT can be provided. Apart form that you need to create the Master data manually absolutely identical with the Master Data description, which is delivered with the DVD (/BBLibrary/Documentation/…).

© SAP AG of 72


4.2 Activation SequenceBefore you activate the Services Industries Package, you must decide if you want to activate the complete package (full scope) or a subset of the complete package. Details for individual scenarios are available on the documentation DVD.

Make sure that you have finished all activities in section Technical Prerequisites for Installation successfully.

Make sure that your logon language is always English (and NOT your local language) for all activation activities. However, some installation activities require to be logged on in your local language. In these cases, and only in these cases, switch your logon language temporarily. In the SAP Best Practices solution builder, you will be prompted to do so.

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.

4.2.1 Activation Sequence of Building BlocksWhen activating the complete Services Industries Package (all scenarios) or just selected scenarios, the necessary technical building blocks must be activated in the correct sequence. When you use the SAP Best Practices solution builder, the activation is automatically carried out in the correct sequence.

Activate Document SplittingIf you are modifying one of the SAP-shipped scopes, and plan to use the scenarios Activate Document Splitting (165), Segment Reporting (166) and Cost Of Sales Accounting (161), these three scenarios MUST be the last three to be activated. Specifically, activate all other required scenarios, then activate scenario 165 first, then activate 161, then activate 166.

SAP Best Practices supports implementations with or without document splitting. This approach makes it necessary to respect a certain activation sequence that can only be checked manually, as mentioned in the paragraph above.

You must decide if you will use the scenarios Activate Document Splitting (165), Segment Reporting (166) and Cost Of Sales Accounting (161) BEFORE the first posting in the system. If the solution has been set up without document splitting and postings have been made, you cannot activate the document splitting subsequently. This can take place only as part of a very complex migration project (see also SAP Note 891144) and is not supported by SAP Best Practices.

4.2.2 Scoping and Activation of ScenariosYou can choose to activate the entire Services Industries Package scope or certain scenarios. If you wish to activate the full scope, follow the common steps below and read the sections highlighted with a gray solid-lined box. If you wish to activate certain scenarios, follow the common steps below and read the sections highlighted with a yellow dash-lined box.

© SAP AG of 72


For a full list of all scenarios included in the Services Industries Package, see section Scenarios Included in the Services Industries Package below.

Step 1: Import the Solution File1. To run the SAP Best Practices solution builder, from the Command field, enter /n/smb/bbi

and press Enter.

2. On the Solution builder – solution editor screen, from the menu, choose Solution Import.

3. On the Select one format to import dialog box, choose the Import XML file button.

4. On the Select the XML file dialog box, browse to the location of your XML file (in the folder you created during step Creating a Folder for the SAP Best Practices Activation, see above), select it, and choose Open.

5. Set the uploaded solution as the favorite solution: choose Solution Set Favorite.

Step 2: Set Document Path for Solution Builder

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

Procedure6. From the SAP Best Practices solution builder menu, choose Goto User Settings.

7. Choose the External Documents tab.

8. Choose the Display <> Change button.

9. Choose the Insert Row button.


Parameter Value

DOCUMENTATION http://help.sap.com/

11. Choose Save.

12. Choose Back.

Step 3: Upload the Installation Data

In order to assure the installation data upload is working correctly, make sure before installation data upload the following user settings are set as described (access via Solution Builder Solution Editor Goto User Settings, tab strip General):

o Deselect the setting Check consistency with eCATT definitions during Installation data upload

o Select the setting Maintain references in eCATT Definitions during Installation Data upload

13. From the SAP Best Practices solution builder main menu, choose Upload Installation Data (Ctrl + F5).

© SAP AG of 72


14. On the Upload and Download external file data dialog box, browse to the location of your

installation data files (in the folder you created during step Creating a Folder for the SAP Best Practices Activation, see above), select it, and choose Continue (Enter).

Step 4: Scope the Solution

If you are activating the complete Services Industries Package scope, you can skip to step 4 Personalize the Solution below. You can also follow the steps in this section, if desired, but they are not required for activation of a complete scope.

15. Choose the Scoping button (Ctrl+F9).

16. On the Scoping – Start screen, you can define the scope of scenarios you want to install. From the Select Template dropdown, select the desired scope. There are three scopes available:

a. Services Industries V2.605 Full Scope

b. Services Industries V2.605 ERP Scope

c. Services Industries V2.605 CRM Scope

Choose one of the available scopes and select Scope.

Full Scope: Select 04 All Scenarios from the dropdown.

Partial Scope: Select any scope except 04 All Scenarios. Each of these scopes are fully-integrated end-to-end solution proposals that each focus on a different area: Manufacturing, Trade, and Service. These subsets include all building blocks necessary to deliver the appropriate functionality.

17. The system displays the Scoping for Solution screen. The screen displays all of the available scenarios that are part of the Services Industries Package.

Full Scope: If you are activating the full scope, do not make any changes on this screen, and continue with step 8.

If you want to activate the scenarios 123, 141, or 140 as per the warning in the Activation Sequence of Building Blocks section above, read the Partial scope description immediately following this paragraph.

Partial Scope: You can disable or enable scenarios by clicking on the colored box for the scenario. An informational box displays. To remove a scenario from the scope, choose the Deselect button. The informational box disappears and the colored box turns gray. To activate a disabled scenario, click the gray box for the scenario, and choose the Select button on the informational box.

18. Choose the Save Data button.

19. On the informational box, enter a Solution ID and a Description, then choose OK. On the next dialog box, choose OK.

20. Choose Back twice.

21. Select your solution from the list, then choose the Favorite button.

22. Maintain flag multiple activations for building block 142.

© SAP AG of 72


Full Scope: In the Building Block 142 (Production Planning and Control) the flag Allow multiple activations of BB in client is set. This is obsolete if you want to install the full scope of the Services Industries Package. To reduce activation time you can delete this flag. To do so, start the solution builder and choose Goto -> Building Block Builder. In the Building Block Builder – Solution View screen select the Building Block 142 and choose Change (Shift + F9). Delete the flag Allow multiple activations of BB in client and choose Enter. Choose Save.

Partial Scope: Do not change the multiple activation settings of building block 142.

Step 5: Personalize the Solution

If you want to use the default shipped values, skip to the Download the Installation Data section below.

23. Ensure that the graphic files have been imported into the system. These graphics are attached to SAP Note Additional information for BP- SOLBLD 70V* (see SAP Note 1301301; in this SAP note the release strategy for SAP Best Practices ABAP Add-ons is listed including information on the latest solution builder version. Once you have identified your solution builder version, you can check the relevant SAP Note Additional information for BP- SOLBLD 70V* which refers to the version of the solution builder you have in usage)..

24. Choose Enterprise Structure Personalization (Ctrl + F7).

25. On the Personalization Enterprise Structure screen, select your target language, then choose Personalization.

26. Navigate to the relevant objects in the Navigation Area.

27. To personalize an entry, double-click the object in the graphical area.

28. Make any personalized entries on the detail screens.

29. If you want to personalize the printer, proceed as outlined in chapter Printer Settings, Default Printer above.

Use the SAP Best Practices documentation adaptation to update the business process documentation with your personalized values. For information on the necessary technical settings and the adaptation procedure, go to the SAP Best Practices Services Industries Package documentation DVD and choose the section Implementation -> Activation on the left side menu. In the information box Personalization of Documentation select Technical Settings for information on the technical prerequisites and Documentation Adaptation to start the actual adaptation process.

Note that you have to perform the next step Step 5: Download the Installation Data as prerequisite before you can adapt your documentation.

Step 6: Download the Installation Data

30. Choose Download Installation Data (Ctlr + F6). Download the installation files to a local folder. Existing files will be overwritten.

© SAP AG of 72


You have to download the installation data to the folder that already contains the complete set of installation data as delivered by your solution provider (confirm overwrite in case of a warning message). Otherwise required files that are not covered by the up- and download process (such as graphic files) will be missing.

Step 7: Starting Activation31. Ensure that your solution is set as a favorite solution.

32. From the menu, choose Goto Implementation (Ctrl + F6).

33. Select the top node of the solution, then choose the Activate button.

34. On the Activate solution dialog box, make the following entries:

Field name User action and values

Comments

Target Language

DE

Installation Data

<location of folder with installation data>

e.g. Z:\sme\files

This folder was created in step Creating a Folder for the SAP Best Practices Activation(*.txt files)

You cannot use UNC paths (e.g. \\dwdf030\SME\...).

Always use a mapped network drive (e.g. Z:\SME )

Also it is not possible to use any root directory of your local drive (e.g. Z:\ or C:\)

Workbench <workbench request number>

Enter an existing workbench request number, or choose the Workbench Request button to create one.

Customizing <customizing request number>

Enter an existing customizing request number, or choose the Customizing Request button to create one.

Skip this screen

Deselect If selected, the system will not display the Activate solution dialog box upon resumption of activation following an error or manual activity. If deselected, the Activate solution dialog box will display every time after resumption of activation.

With demo data

Select If selected, system executes activation steps that create demo data. If deselected, these steps are not executed.

More information for installing without Demo Data in the chapter Automated Activation w/o Demo Data.

35. Choose Continue.

There are some manual steps that you will need to handle during activation. The solution builder will display a procedure dialog box with instructions for you to follow

© SAP AG of 72


to process the step. The table below lists these manual steps as they are part of the default full scope activation:

Building Block Number

Building Block Title

Step Name Manual requirement

BB 100 SAP BP Installation Create logical System

only manual confirmation required

BB 161 Cost of Sales Accounting

Creating a Library with a Template

BB 165 Activate Document Splitting

Assign scenarios and customer fields to ledgers (Message)

only manual confirmation required

BB 168 Profitability Analysis Change Forms f. PA Reports; Add additional lines

BB 168 Profitability Analysis LOG ON IN COUNTRY LANGUAGE

manual activity only required if target language is not English

BB 168 Profitability Analysis LOG ON IN ENGLISH LANGUAGE

manual activity only required if target language is not English

BB 260 Extended Accounting for Services Industries

Change Form for Profitability Reports

BB 263 SD/MM Generic Settings for Services Industries

User Exit: Travel Per Diem and Print-/Smartform Enhancement

BB 266 Offline Time Recording

Check that the technical requirements have been met

BB 266 Offline Time Recording

Enhancement: Adobe Interactive Form and ABAP Program according to Config Guide

BB 270 Project with external Resources

Models for Easy Cost Planning

BB 279 Time Recording External Resources

User-Exit: DIP - Itemization of Activities by External Resources Enhancement

BB 438 Project Staffing Customer

© SAP AG of 72


Enhancements

If you use PERSONALIZED values (for example company code 9999 instead of the default value company code 1000 or shipping point 8888 instead of default value shipping point 1000 and so on), do NOT use the DEFAULT values in the manual step configuration descriptions and configuration guides, respectively, but use your personalized values wherever applicable.

Step 8: Concluding ActivitiesAfter you finished the activation of the scenarios, you must run all steps in the Prerequisite Process Steps document (BPD 154) as prerequisite before you can test your scenarios.

The Prerequisite Process Steps document (BPD 154) can be found on the SAP Best Practices documentation DVD: On the left side menu choose Business Information Preconfigured Scenarios. In the information box Entry Level Scope choose Full scope. Then, in the information box Scenarios – by Business Areas select Integration Processes Other Prerequisite Process Steps.

Step 9: Documentation Adaptation (optional)You can personalize the Business Process Documentation with the SAP Best Practices documentation adaptation tool.

This is an optional step and is only possible if you have personalized the solution (see step 5).

Use the SAP Best Practices documentation adaptation tool to update the Business Process Documentation (BPD) with your personalized values.

For information on the necessary technical settings and the adaptation procedure, follow the steps listed below:

1. Go to the SAP Best Practices For Services Industries package documentation DVD

2. From the navigation bar, choose Implementation ® Activation .

3. In the Personalization of Documentation information box, choose Technical Settings for information on the technical prerequisites.

4. In the Personalization of Documentation information box, choose Documentation Adaptation. This starts the adaptation process.

5. Confirm the File Download dialog with Open.

6. If a security warning dialog box appears, confirm the warning by choosing Enable Macros.

7. To use personalized values, choose Use Personalized Data.

If you have already personalized your BPD and you want to restore the default values, choose Use Default Data radio button.

8. In the Folder with Personalized Installation Data Files entry field, enter the path to the folder containing your variant files.

© SAP AG of 72


9. Choose Adapt Documentation, The tool changes a setting and BPD displays personalized values.

10. Choose Exit.

© SAP AG of 72


5 Troubleshooting

5.1 Error Handling: Installation Errors The following information helps you to solve problems that might occur during the installation process.

Before you start with detailed error analyzing and working through the error processing as described below proceed as follows:

Activate your solution or the respective scenario in the solution builder implementation assistant again. It might be the case that error will not reappear. In this case no correctional activities are needed and the installation is proceeding.

5.1.1 Error Occurs During Automated Task

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

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

a. In case the error can be solved based on the log information, you can run the eCATT or BC set again.

In case the activation fails because of locked objects, please 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 activation of eCATTs and BC sets. The document can be found on the documentation DVD in the area Technical Information -> Concept.

5. In case the log information is not sufficient to solve the problem you can proceed as follows:

a. Execute the task manually: use the description of the related section in the configuration guide for executing the task,

or

b. Open a customer message for this problem specifying the component SV-SMB-AIO-BP-PSV.

© SAP AG of 72


Do NOT delete Solution Builder scenarios ONCE they have been activated. If you delete scenarios, the activation history and the respective logs are lost and it is not possible to find possible error reasons with tenable efforts.

In such cases NO SAP SUPPORT CAN BE PROVIDED.

6. When you have solved the problem (either executed the task manually or a solution has been

provided via customer message), choose the Change button that is displayed in the Old Status column to the right of the task.

Do NOT proceed with installation if the problem has not been solved. If you continue without solving the problem, severe errors might result in the subsequent installation steps that cause incalculable efforts to fix.

In such cases NO SAP SUPPORT CAN BE PROVIDED.

7. Choose the Change button that is displayed in the Old Status column to the right of the task.

8. On the Confirmation dialog box, choose OK to manually change the status to successful.

9. On the Information dialog box, enter a reason for changing the status.

10. Choose Continue.

The information is saved in a log. To view details for a changed task, choose the red light in the Original Status column for that task. A dialog box displays the user who performed the change, the date of the change, and the reason for the change. Choose Continue to close the dialog box.

11. Choose Activate to continue with the installation.

5.1.2 Error Message for eCATT /xxxxxx/PA40_O001_xxx Field PSPAR-PERSK. is not an input field

The eCATT /xxxxxx/PA40_O001_xxx is used in several building blocks (e.g. BB 122). If it is run more than one time trying to create the same employee numbers, you get the error message Field PSPAR-PERSK. is not an input field, because employee numbers have already been created during the first run.To solve this issue, delete existing and not completely installed personnel numbers manually using the following steps:1. Access the activity using one of the following navigation options:

SAP ECC Menu Human Resources ® Personnel Management ® Administration ® HR Master Data ® Maintain

Transaction Code PA302. Press Search Term in the Find by section and confirm the dialog box

Find Person with Find.3. Select a personnel number, for example 999301. Personnel data is shown in the right-hand

half of the screen.4. Select Utilities ® Delete Personnel Data from the menu bar.5. On the Delete Personnel Data screen press Select All, and then press Delete.

© SAP AG of 72


6. Confirm the dialog box Delete Personnel Data.7. Enter or confirm Customizing Request.8. Repeat steps 3 to 7 for all personnel numbers that are supposed to be created by the specific

eCATT /xxxxxx/PA40_O001_xxx (see the respective configuration guide of the affected building block for details on the personnel numbers).

9. Start eCATT /xxxxxx/PA40_O001_xxx again.

5.1.3 Warnings in the BC-Set LogsIf an eCATT runs on status red (error), check the eCATT log with regard to the BC Sets that have been activated by this eCATT. If the eCATT log ran on error because the BC Sets have been activated with warnings (use the BC Set log to check this), the eCATT error can be ignored. Set the installation status manually on green, if the BC Set has been activated successfully.

5.1.4 eCATT Error Variable xyz does not exist….If an eCATT runs on status red (error), check the eCATT log with regard to the BC-sets that have been activated by this eCATT. If the error message is variable xyz does not exist…. the error can be ignored if the BC Sets have been activated successfully (use the BC Set log to confirm this). Set the installation status manually on green, if the BC Set has been activated successfully.

5.1.5 Window Appears During Activation Start Options – Test Configuration /SMB99/BMSM_O237_J01

This is not an error but a standard manual step that has to be done during the activation process (see section Scoping and Activation of Scenarios, Step 7: Starting Activation, above). To continue with the installation, proceed as follows:

On the screen Start Options – Test Configuration /SMB99/BMSM_O237_J01 choose tab page UI Control.

Choose Start mode for Command TDC: A-Process in Foreground and choose Execute.

Confirm the single steps. Only in case the eCATT-procedure stops choose Back (F3) .

On eCATT log screen choose Back (F3) twice and confirm the dialog box Interactive step - set status, with OK.

5.1.6 Window appears during installation A script is trying to attach to the GUI

If such a window appears during the installation process with the Solution Builder, choose OK.

© SAP AG of 72


5.1.7 Window appears during installation asking to confirm that text was changed

If such a window appears during the installation process with the Solution Builder, confirm the information dialog box with Yes.

5.1.8 Issue with SAP GUIIf you get the error message Installed scripting engine is older than engine of eCATT script. Do you want to continue anyway? (see screenshot below) you need to update your SAP GUI to solve this issue.

5.1.9 Description of Manual Steps in Installation ProcessIn the SAP Best Practices solution builder, SAP documented all the manual installation steps that are necessary during the installation process of a specific building block. These descriptions are directly attached to the installation activity in the SAP Best Practices solution builder scenarios in the system. However, if a description should be missing in the solution builder, you can refer to the description in the configuration guide of the respective building block.

If you use PERSONALIZED values (for example company code 9999 instead of the default value company code 1000 or shipping point 8888 instead of default value shipping point 1000 and so on), do NOT use the DEFAULT values in the manual step configuration descriptions and configuration guides, respectively, but use your personalized values wherever applicable.

© SAP AG of 72


5.1.10 Processing of Scenario Specific Errors

5.1.10.1 BB 104 (Materials Management): Error in eCATT /SMB99/CHARACTERISTIC_O209_J01; Some Variants Run Red

If the eCATT /SMB99/CHARACTERISTIC_O209_J01 Create Release Procedure Characteristics shows an error (some of the eCATT variants run on red status), restart the solution builder scenario again. During the second activation the variants which have been run on red status during the first run are now green; however the variant which run on green or now red. This is not an error, it only shows that the characteristics are already there. After the second activation you can manually set the activity to status okay and proceed with the activation.

5.1.10.2 BB 104: (Materials Management): Error in eCATT /SMB99/CL20N_PO_O001_J01; Some Variants Run Red

If the eCATT /SMB99/CL20N_PO_O001_J01 Define Release Procedure for Purchase Orders - Set Criterias shows an error (some of the eCATT variants run on red status), restart the Solution Builder scenario again. The error should then not occur anymore.

5.1.10.3 BB 153: (Printing: Forms): Error in eCATT /SMB99/SE38_O001_J05 (Copy SAPScripts Forms from Client 000 and Activate); S00344 No batch input data for screen SAPLSTRD 0302

If the eCATT /SMB99/SE38_O001_J05 Copy SAPScripts Forms from Client 000 and Activate shows the error S00344 No batch input data for screen SAPLSTRD 0302, check the system change options for the software component HOME (Customer Developments). Make sure that the change option for this component is set to F Modifiable.

1. Access the activity using the following navigation option:

Transaction Code SE03

2. On the Transport Organizer Tools screen, choose Set System Change Option (folder Administration).

3. On the System Change Option screen, check the setting for the software component HOME (Customer Developments) (first section of the screen).

4. For the software component HOME (Customer Developments) choose the option „F (Modifiable)“.

5. Choose Save.

After you made that change start the activation again.

5.1.10.4 BB 153: (Printing: Forms): Error in eCATT /SMB99/SE38_O002_J01 (Copy Print Programs into customer namespace); S00344 No batch input data for screen SAPLSKEY 1000

If the eCATT /SMB99/SE38_O002_J01 Copy Print Programs into customer namespace shows the error S00344 No batch input data for screen SAPLSKEY 1000, check if the user ID used for activation has a valid SAP Software Change Registration (SSCR) developer key. For details on

© SAP AG of 72


the SCCR developer key, see above the chapter User Settings for Activation, section SAP Software Change Registration (SSCR): Developer key.

5.1.10.5 BB 168 (Profitability Analysis): Error eCATT /SMB15/KEA5_O024_J17; Some Variants Run Red

If the eCATT /SMB15/KEA5_O024_J17 Maintain Characteristics - Transfer from SAP table shows an error (some of the eCATT variants run on red status), restart the Solution Builder scenario again. The error should then not occur anymore.

5.1.10.6 BB 168 (Profitability Analysis): Error generating table KOMPAKE, Message no. KE434; eCATT /SMB15/KEA0_O042_J17

If the eCATT /SMB15/KEA0_O042_J17 Activate Operating Concern shows the error Error generating table KOMPAKE, Message no. KE434. Diagnosis: An error occurred while Table KOMPAKE was being generated. restart the Solution Builder scenario again. The error should then not occur anymore.

5.1.10.7 BB 168: (Profitability analysis): Error executing transaction KEA0 or KES1

Only in the case if you get an error executing installation step KEA0 or KES1 (168, e.g. installation step Maintain Characteristic Values):Execute the report RKEAGENV as described in note 64490. Maybe you get an error during the execution, but the inconsistencies are resolved. Now, reactivate the operating concern (transaction KEA0, Tab Environment, cross-client and client-specific part). Just in case the error still exists, check note 942785.

5.1.10.8 BB 161 (Cost of Sales Accounting): Error BC-Set /SMBA0/V_FAGL_LEDGER__B1DV_J0A – Program modified during

If the activation of BC-Set /SMBA0/V_FAGL_LEDGER__B1DV_J0A ends with the message Program CL_FAGL_SPLIT_SERVICES========CP was modified during the run and the solution builder activation crashes you have to restart the activation of the solution again. This error is caused by a bottleneck of local program buffer. To avoid this error also adapt the parameter for the local program buffer.

5.1.10.9 BB 161 (Cost of Sales Accounting): Error eCATT /SMB15/KS02_O010_N74 – Error in eCATT command TCD KS02

If the last variant (VAR015) of the eCATT /SMB15/KS02_O010_N74 runs red with the error message „Error in eCATT command TCD KS02; Field CSKZ-FUNC_AREA. is not an input field; S00347 Field CSKSZ-FUNC_AREA. is not an input field“ you have to make a correction in customizing.

1. Access the activity using one of the following navigation options:

IMG Menu Financial Accounting Global Settings (New) ® Global Parameters for Company Code -® Enter Global Parameters

© SAP AG of 72


Transaction Code SPRO

2. On the Change View “Company Code Global Data”: Overview screen select the company code created with BB 216 (default value 1010) and choose Details (F2).

3. Make the following entry:

Field Name User Action and Values

Cost of sales accounting actv.

2 (Active)


Restart the activation of the eCATT. The error should then not occur anymore.To avoid this error also adapt the parameter for the local program buffer.

6 Evaluate Business Content / Scenarios – Business Consultant

The following chapters describe the activities that have to be done by the business consultant who is taking care that the business processes work as desired.

The section Review of Business Scenarios provides an overview where the business consultant can get information on the SAP Best Practices scenarios activated in the system.

The chapter on Usage of Personalized Values explains how to proceed if the SAP Best Practices activation was done using personalized data files and you want to use the process documentation reflecting the personalized values. This section can be ignored if the SAP Best Practices activation was performed using default values.

The section User Maintenance and Settings outlines the activities that the business consultant has to perform to enable system users to exploit the business process documentation. The necessary user settings are described.

The section Creation of Queries in Personal Object Worklists (POWLs) refers to information that is needed when you work with the SAP NWBC. In several business process documents it is necessary that you create queries. In such cases refer to the description as outlined below. This section can be ignored if SAP NWBC is not used.

The chapter Errors during Usage of Activated Package lists errors that users might face in the system when applying the business process documentation. The information provided helps to solve such errors.

The section Errors with SAP NetWeaver Business Client (SAP NWBC) describe possible errors specific to the usage of SAP NWBC. This section can be ignored if SAP NWBC is not used.

6.1 Review of Business Scenarios

Details for individual scenarios are available on the documentation DVD in the area Business Information Preconfigured Scenarios. In the upper right box Entry Level Scope, choose Full Scope to get an overview of all scenarios delivered with the Services Industries package. Select the scenarios map for an overview of all scenarios. Depending on the scenarios you are interested in, choose the corresponding scenario box on the map. When you click on the box, an information window will open. When you then select the information icon, you directly get to the scenario overview HTML page. On that page, you can access the business process

© SAP AG of 72


documentation, process overview document and the configuration guide of the respective scenario.

The business process documentation (BPD) provides a detailed process step description of the business scenario.

The scenario overview document comprises of a graphical overview of the scenario process flow.

The configuration guide describes crucial parts of the system configuration of the respective scenario. Together with the configuration guides of the underlying building blocks, you can track which system settings have been configured. Due to the technical concept, not all scenarios have configuration applied on a top level. For such scenarios, the necessary configuration is described in the configuration guides of the underlying building blocks. For more information on the building block concept, see the section Technical Information Tools and Concept on the documentation DVD. Then select Building Block Concept.

You can use the documents as described above to review the business scenarios you are interested in. Use the business process documentation (BPD) to pass through the scenario in the system.

6.2 Usage of Personalized Values in Business Process Documentation (BPD)

This section can be ignored if the SAP Best Practices activation was performed using default values.

SAP Best Practices allows an update of the Business Process Documentation (BPD) based on the personalized enterprise structure. Use the SAP Best Practices documentation adaptation to update the documentation with your personalized values. To get the list of default values and their personalized values, open the Mapping Document.

On details how to proceed, see the instruction above in the chapter Scoping and Activation of Scenarios, Step 9: Documentation Adaptation (optional). This is a task that usually the business consultant performs together with the consultant who carries out the SAP Best Practices activation.

6.3 User maintenance and Settings6.3.1 Assigning a Role to an UserIf you plan to use the SAP NetWeaver Business Client (NWBC) interface, the system users need to have roles assigned in the system as prerequisite for usage of NWBC. If you do not plan to use NWBC, you can skip the activities described in this chapter.

The SAP Best Practices roles are delivered with the SAP Best Practices Add-on and are available in the system once the Add-on has been applied. All user roles provide specific user menus for demo or reference purposes. These are only required if you

© SAP AG of 72

http://help.sap.com/bp_bl603/BBLibrary/General/BBConcept_EN.pdf


are using the SAP NetWeaver Business Client interface, and are intended for demo or evaluation use. If your company chooses to use these roles more extensively, they should be adjusted according to your company’s system and security policies prior to use in a production environment.

The SAP Best Practices roles (SAP_NBPR* roles) are designed to be used with the SAP NetWeaver Business Client - version 3.0 interface only. They shall NOT BE USED with the SAP GUI or SAP NetWeaver Business Client - version 1.0 since they are not designed for it.

UseThis section describes how you can assign roles for users.

Procedure1. Choose one of the following navigation options:


SAP Menu Tools ® Administration ® User Maintenance ® Users

2. In the User Maintenance screen, enter the user ID of the user for which a role assignment shall be done.

3. Choose Change.

4. In the Maintain User view, choose the Roles tab.

5. In the Role field, enter the role name. You can use a wildcard to search for a role.

You can assign several roles to a user at this stage, if necessary.

Information on which SAP Best Practices roles have to be assigned

You assign only the roles needed for a specific scenario. In this case, check the scenario business process documentation guide (BPD) of the respective scenario. The BPDs are provided on the SAP Best Practices documentation DVD. The necessary roles are listed in the chapter Roles in the Prerequisite section of each BPD.

6. Choose Enter, save, and go back to the SAP Easy Access view.

To access business objects or execute SAP transactions, a user requires corresponding authorizations, as business objects or transactions are protected by authorization objects. The authorizations represent instances of generic authorization objects and are defined depending on the activity and responsibilities of the employee. The authorizations are combined in an authorization profile that is associated with a role. The user administrators then assign the corresponding roles using the user master record, so that the user can use the appropriate transactions for his or her tasks.

© SAP AG of 72


SAP Best Practices does not deliver an authorization concept, i.e. the SAP Best Practices roles contain authorization objects that may not be maintained completely. However, SAP Best Practices facilitates the definition of authorization profiles by listing the SAP transactions that are necessary to perform all system activities required for the handling of the respective business scenario. Using the profile generator you can automatically create authorization profiles covering selected system transactions. You can check the function list to get an overview of the transactions used in the different SAP Best Practices scenarios.

All authorization profiles will have to be adapted according to the necessary requirements and the authorization concept that has to be realized, respectively. Further information on this topic can be found on the SAP Help Portal at http://help.sap.com in the area SAP Netweaver -> Security -> Identity Management.

ResultThe roles are now assigned to the user. These roles are referred to in the scenario business process documentation guides (BPDs) provided in SAP Best Practices.

6.3.2 Mandatory User Parameter


SAP menu System à User Profile Own Data


2. Choose the Parameters tab.

3. On the Maintain User Profile screen, make the following entries.

Parameter-ID

Parameter Value

Note

NDR X If you want to create / print messages for material documents (output types WAxx, WExx, WFxx) you have to maintain the following parameter in the user settings.

Print via output control in MM - Inventory management

Make sure to use capital letters only.


6.3.3 Optional User ParameterA field can be filled with proposed values from SAP memory using a parameter ID stored in the user parameters. Depending on the user requirements default values for a field for the parameter can be specified. If you specify a value for the parameter, this value is always defaulted when the user displays the field.

© SAP AG of 72

http://help.sap.com/


You can skip this step if you do not want to use any predefined user specific parameter-values.

You can use copy and paste functionality not to enter each parameter and parameter value individually.


SAP menu System à User Profile Own Data


2. Choose the Parameters tab.

3. On the Maintain User Profile screen, you can make the following entries

Parameter-ID Parameter Value

Note

AAF Parameters, order type, production orders

AAT SD Customer Order

AFT SD Inquiry

AGT SD Quotation

BUK 1000 Company code

CY- XCapacity eval.: Scenarios with production order 'X'=on

CAC 1000 Controlling area

CYX YBLTP01 Cap.plan.prof.(TCY06) long-term planning

CORUPROFConfirmation Profile, will be set in each Buisness Process Documentation

CSA PP01 BOM application

EKG 001 Purchasing group

EKO 1000 Purchasing organization

F4METHOD ActiveX ActiveX/NoActiveX

KAR 001 Class type

LAG 0001 Storage location

LE_SHP_DEL_MON_LISTT HC Delivery Monitor: List Type

PIN 1 PP: Profile/Default Values

QAE X Automatic close on entering

QAP Work center for inspection processing

QAS X Automatic close when saving

QCHARTTYPEGraphic Type when Calling Inspection Results

QDOCUON Documentation indicator on/off

© SAP AG of 72


Parameter-ID Parameter Value

Note

QEE_TEXT_CLOSE 99Results Recording: Text Color of Completed Item

QEE_TEXT_OPEN 99Results Recording: Text Color of Open Item

QER Recording view in results recording

QERF_SOFStart Results Recording Using Automatic Selection

QERSMAL X Limiting Options in the Recording View

QESEL_MAN Expand Worklist Manually

QEXTTREE

224Expansion of the Docking Tree in QM Results Recording

QF1 Defects recording: Report type modifiable

QFA Entry screen for active defect class

QFE Y0000010 Defects recording: Specs. for report type

QFMDefects Recording: Automatic Popup for Multiple Selection

QGRAFIKON Graphic On/From

QMO 1Processing mode for inspection characteristics

QPR Name of the inspector

SCL XUpper and lower case in source code: 'X' = lower, ' ' =upper

SD_SWU_ACTIVE X Activate Workflow Box in VA02 & VA03

SPA 10 DIVISION

SP01_WARN 000000500Threshold Value for Number of Lines in Display

VKO 1000 Sales organization

VST 1000 Shipping point

VTW 10 Distribution channel

WLC X X XX X Workflow: User-specific settings

WRK 1000 Plant

Make sure to use capital letters only.


© SAP AG of 72


6.4 Creation of Queries in Personal Object Worklists (POWLs)

This section can be ignored if the SAP NWBC is not used.

This section refers to information that is needed when you work with the SAP NWBC. In several business process documents it is necessary that you create queries. In such cases refer to the description as outlined below and provide system users with the relevant information, respectively.

UseYou want to create a completely new query.

Procedure

To show the procedure how to Define New Query we use the Sales area.

1. Access the activity choosing the following navigation option:

SAP NetWeaver Business Client Menu

Sales® Sales Order ® Worklist

2. Choose the link Define New Query. A process template takes you through the individual steps. You work through the specified steps and define the following data:

3. For selecting the Object Type make the following entries:


Comment

Select Object Type All Sales Orders By selecting an object type, you choose one of the pre-defined types of the POWL.

Select an Existing Query As Template You can use a template for the selected Object Type if one exists.

4. Choose pushbutton Next.

5. Maintain selection criteria for your query as required.

6. Via button Preview you can get a test view of the list.

7. Next to the Preview button you find the link Criteria Personalization where you can select additional fields for the quick search.

8. Choose Next.

© SAP AG of 72




Comment

Enter Query Description Test Example of Query Description

Activate Query Select checkbox to activate the query.

10. Then choose pushbutton Finish.

For setting your query as the default query, choose link Personalize from the Query Area and select tab strip Personalize View. In the Active Queries list you find the column Set Default Query where you can set your query as the default query. That means that this default query is always active when you log in.

ResultThe newly defined query has created a new work item (POWL) which appears in the Query Area as Tab Strip or Link Matrix.

For more information on working with POWL, refer to the guide How to Use POWER lists in the Enablement Kit .

6.5 Errors during Usage of Activated Package

6.5.1 Using Requirement Class YB5 - Scenario 195: Sales Contract with Fixed Price and T&M Billing

The requirement class YB5 is used in the scenario 195 Sales Contract Fixed Price and T&M-Based Billing.

During the creation of the sales document (sales order or sales contract) after having entered a material in the item line and confirmed with Enter the error message Requirements class YB5 is not defined could appear. Further processing is not possible. Go back and follow the below described steps in the configuration IMG for both scenarios:

Go to Sales and Distribution -> Basic Functions -> Availability Check and Transfer of Requirements -> Transfer of Requirements:

1. Select Define Requirements Types.

2. Go to the requirement type YB5 and delete the assigned requirement class YB5 in the field ReqCl.

3. Save your entries and go back.

4. Select Determination Of Requirement Types Using Transaction.

5. Go to the ItCa (Item Category) YBS3 and delete the assigned requirement type YB5 in the field RqTy (Requirement Type).


7. Select Define Requirements Classes.

© SAP AG of 72


8. Change class YB5 (e.g. description text) and save. Afterwards undo the change, save again and go back.

9. Select Determination Of Requirement Types Using Transaction.

10.Reassign the requirement type YB5 to the item category YBS3 in the field RqTy (Requirement Type).

11.Save your entries and go back.

12. Select Define Requirements Types.

13. Reassign the requirement class YB5 to the requirement type YB5 in the field ReqCl.


15.Go back and create the sales document with material items again. Now the requirement class should be found.

6.5.2 Scenario General Cost Center Planning (175): Step 4.10 Execute Plan Assessment, Transaction KSUB; error message Customizing error: Business transaction groups are not current. Message no. GA627

If you want to use the transaction KSU5 the following error appears:

Customizing error: Business transaction groups are not current. Message no. GA627

DiagnosisFor the execution of assessments, distributions, periodic repostings or indirect activity allocations in the CO-OM application, groups have to be defined in the current client which summarize all actual or planned transactions. In the current client, these groups are either not available or do not have the latest status.

System ResponseTo avoid subsequent errors, processing cannot be continued until these transaction groups are consistent again.

Error Solution ProcedureSuch errors are mostly caused by problems during a release upgrade or by incomplete client copies; they can be solved by starting report

RK811XST (only in the current client) or

RK811XUP (in all clients).

Start one of these two reports and then restart processing. If the error still occurs, inform your system administrator.

6.5.3 Posting only possible in periods 200[x]/0[y] and 0000/00 in company code [1000]

© SAP AG of 72


This error might occur in building block 198, for example. The reason for this error message is that the posting date entered is not within one of the permitted posting periods (current period/previous period).

Maybe you have not set the correct current period in the system. For the system, the first of the entered periods is the current period. At the beginning of a new period, your system administrator must change the current period in the material master record, using the function Shift periods (TA MMPV). This has not yet been done.

6.5.4 Maintain Allocation Structures — Settlement Cost Elements (CE), Error no entries exist when using F4 Help

UseAfter activation of BC-Sets for allocation structures the F4 Help for searching cost elements sometimes does not deliver the correct selection.

For selection of cost element with cost element category (for example, 21) you get the error “no entries exist” even if the cost elements are maintained in the client.


Transaction Code SPRO

IMG Menu Controlling Internal Orders Actual Postings Settlement Maintain Allocation Structures

2. On the Change View “Allocation Structures”: Overview screen, select the allocation structure (right hand side of the screen) YM.

3. Choose Assignments with a double-click (left hand side of the screen).

4. Select the assignment 010 (right hand side of the screen).

5. Choose Settlement Cost Elements with a double-click (left hand side of the screen).

6. On the Change View “Settlement Cost Elements”: Overview screen, select the line “Receiver Cat.” CTR and enter the cost element.

Enter the settlement cost element directly in the field. Do not use the F4 help.

Allocation Structure

Assign-ment

Receiver cat.

ByCost Element

SettlementCost Element

YM 010 CTR 921010


© SAP AG of 72


6.5.5 Various Scenarios in the Area Controlling: Error System error or customizing error: Read error in set for table CCSS, message GA622

You might encounter the following error: Error System error or customizing error: Read error in set for table CCSS, message GA622.

Error Solution ProcedureThis error is mostly caused by problems during a release upgrade or by incomplete client copies; they can be solved by starting report

RK811XST (only in the current client) or

RK811XUP (in all clients).

Start one of these two reports and then restart processing. If the error still occurs, inform your system administrator.

6.6 Errors with SAP NetWeaver Business Client (SAP NWBC)

6.6.1 Queries Show No Data / No Columns

Problem DescriptionA query shows no data.

Error Solution ProcedureIf a query shows no data, check the current selection and filter. Remember to refresh the list after changing the selection and filters.

If a query shows no columns, create a new query.

Refer to the SAP Business All-In-One Enablement Kit, Building Block K51, on how to use and change existing queries and create new queries.

Some CO related queries require that the parameter ID CAC is set to the used Controlling Area as default value. Use transaction SU01 / SU3 to maintain the value.

6.6.2 Printing functionality

Problem DescriptionIt is not possible to show or print documents (e.g. invoices) via the system icon Print Version, Billing Document in PDF Format or similar icons.

© SAP AG of 72


Error Solution ProcedureThe above mentioned functionality only supports PDF based forms and in some cases also SAPScript forms. It is not possible to show or print Smartforms.

6.7 Security Aspects – System AdministratorsThis section provides an overview of the security-relevant information that applies to the deliverables of this SAP Best Practices package.

6.7.1 User Administration and Authentication In this chapter you will find an overview of the required users for this package.

Purpose User-ID User Type

Created in

Initial Password

Authoriza-tion Profile

Comment

Activation User

User ID is defined by your System-Admin.

Dialog (Type A)

Creation described in Quick Guide

Password is defined by your System Admin.

Authorization is defined by your System Admin.

For more details, see above chapter Creating User for Activation of SAP Best Practices Content

Evaluation User

User ID is defined by your System-Admin.

Dialog (Type A)

Creation described in Quick Guide



For more details, see above chapter Assigning a Role to an User

User for Offline Time recording

KBACH Dialog (Type A)

Creation described in Configuration Guide of BB266 (Offline Time Recording)



For more details, see chapter Create user for Offline Time Recording in Configuration Guide of Offline Time Recording

You can check the user using transaction SU01.

6.7.2 Roles ManagementIn the above chapter Assigning a Role to an User (see heading section User Maintenance and Settings) you will find an overview of the template roles used for this package.

You can check the roles using transaction PFCG.

6.7.3 RFC DestinationsIn this chapter you will find an overview of the required RFC destinations created and used for this package.

© SAP AG of 72

http://help.sap.com/saphelp_nw04s/helpdata/en/99/acdc3ed98f7650e10000000a114084/content.htm


RFC Destination

Description Connection Type

Created in

Logon Data Comment

No RFC destinations required for this package

You can check the roles using transaction SM59.

© SAP AG of 72

ServInd Quick Guide V2605 en De

Documents

Transcript of ServInd Quick Guide V2605 en De