English
Quick Guide to Installing
the SAP Best Practices for
Services Industries
V1.607 (NL)
SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf GermanyCopyright
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Please see
http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.
Icons
Icon Meaning Caution Example Note Recommendation SyntaxTypographic 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.
Contents
1 Purpose... 7
2 System Setup & Preparation – System Administrator...7
2.1 SAP ERP... 8
2.1.1 Install SAP ERP... 8
2.1.2 Release and Support Package Level...8
2.1.3 Required SAP Components...9
2.2 SAP Best Practices Add-On...12
2.3 SAP Enterprise Extension Sets and Enterprise Business Functions...13
2.4 Creation of Client for SAP Best Practices Activation...16
2.5 System Status of Client Roles and Cross-Client Object Changes...16
2.5.1 Client Roles... 16
2.5.2 Cross-Client Object Changes...17
2.6 SAP Notes and Messages...17
2.7 Pre-Activation Activities...20
2.7.1 Set Up of http and https Services...21
2.7.2 Activation of Services for SAP Best Practices Solution Builder and SAP NWBC 21 2.7.3 Generation of RV13xxxx Reports...21
2.7.4 Generation of Financial Accounting Programs...22
2.7.5 Creation of Consistent Business Transaction Groups...22
2.7.6 Generation of Characteristic VRTNR...22
2.7.7 Deactivation of CRMAPO...23
2.7.8 Deselection of Activation Links in BC Sets...24
2.8 Printer Settings...24
2.8.1 Default Printer... 24
2.8.2 Optional: Set up Printer Environment...24
2.8.3 Printing Bar Codes...25
2.9 Maintain Profile Parameters...26
2.9.1 Maximum Work Process Run Time...26
2.9.2 SAP Scripting... 26
2.9.3 Authentication using SAP Logon Tickets...27
2.9.4 Set Default Timeout for http and https Services...28
2.10 Creating User for Activation of SAP Best Practices Content...29
3 Activation of Business Content / Scenarios – Activation consultant...31
3.2.2 Information on Combining Scenarios...31
3.3 Activation Language...31
3.4 User Settings for Activation...32
3.4.1 SAP Software Change Registration (SSCR): Developer Key...32
3.4.2 Unicode Settings...32
3.4.3 Allow GUI Scripting and Change Default Security Settings...33
3.4.4 Set Decimal Notation and Date Format...33
3.5 Getting the Business Content for Activation...34
3.5.1 Getting the Solution Scope File...34
3.5.2 Getting the Installation Data Files...34
3.5.3 Creating a Folder for the SAP Best Practices Activation...35
3.6 Activation Sequence of Scenarios...35
3.7 Scoping and Activation of Scenarios...35
3.8 Error Handling: Installation Errors during activation...43
3.8.1 Error Occurs During Activation of Automated Task...43
3.8.2 Error Message for eCATT /xxxxxx/PA40_O001_xxx: Field PSPAR-PERSK. is not an input field... 44
3.8.3 Warnings in BC-Set Logs...45
3.8.4 eCATT Error: Variable xyz does not exist…...45
3.8.5 Window Appears During Activation Start Options – Test Configuration /SMB99/BMSM_O237_J01...45
3.8.6 Window Appears During Activation A script is trying to attach to the GUI...45
3.8.7 Window Appears During Activation Asking to Confirm that Text Was Changed...46
3.8.8 Issue with SAP GUI...46
3.8.9 Description of Manual Steps in Installation Process...46
3.8.10 Processing of Scenario Specific Errors...47
4 Evaluate Business Content / Scenarios – Business Consultant...51
4.1 Review of Business Scenarios...51
4.2 Usage of Personalized Values in Business Process Documentation (BPD)...51
4.3 User Maintenance and Settings...52
4.3.1 Activate SAP GUI Option Show Keys With Dropdown Lists...52
4.3.2 Assigning a Role to an User...53
4.3.3 Mandatory User Parameter...54
4.3.4 Optional User Parameter...55
4.4 Creation and Change of Queries in Personal Object Worklists (POWLs)...57
4.4.1 Create Query... 57
4.4.2 Change Query... 59
4.5.1 Scenario Segment Reporting (166): Step Period End Processing; Error message Field use for mandatory field OCURR is not maintained correctly (T811I).
Message no. GA404...60
4.5.2 Posting only possible in periods 200[x]/0[y] and 0000/00 in company code [1000] ... 60
4.5.3 Maintain Allocation Structures — Settlement Cost Elements (CE), Error no entries exist when using F4 Help...60
4.5.4 Various Scenarios in the Area Controlling: Error System error or customizing error: Read error in set for table CCSS, message GA622...61
4.5.5 Scenario SAP ERP Reports for Accounting (221): Selection Screen in wrong language... 62
4.5.6 Scenario General Cost Center Planning (175) and Overhead Cost Accounting - Actual (184): Only use overhead rates with application 'KA'...62
4.5.7 Scenario General Ledger (156): Transaction FB50: Field ‘Assignment no.’ is too large... 63
4.5.8 Scenario Return to Vendor (136): Transaction ME2L: runtime error due to POHVAL issue...64
4.6 Errors with SAP NetWeaver Business Client (SAP NWBC)...64
4.6.1 Queries Show No Data / No Columns...64
4.6.2 Printing functionality...65
5 Security Aspects – System Administrators...65
5.1 User Administration and Authentication...65
5.2 Roles Management...65
Quick Guide to Implement the SAP Best Practices
for services Industries (Netherlands)
1 Purpose
This quick guide provides the information you need to activate the SAP Best Practices for Services Industries V1.607 for Netherlands using the SAP Best Practices solution builder step by step. It also explains how to proceed if you want to implement individual scenarios instead. Before proceeding with this document,
The scope relevant for you need to be defined
The technical prerequisites have to be finalized
The required resources (see involved roles) need to be available
This document does not provide a general overview and explanations of SAP Best Practices. For general information regarding content and positioning, refer to the SAP Best Practice
documentation package. This document is intended for
System administrators / basis consultants
Business consultants
who already have a sound knowledge of SAP Best Practices, including the tools and documentation.
The following sections are assigned to the roles required for it.
SAP Best Practices is not designed to be used to set up a productive system as direct result of the SAP Best Practices activation. Instead, SAP Best Practices only serves the purpose to quickly set up a system to be used as demonstration and evaluation environment in which you can try out the predefined business processes delivered by SAP Best Practices. For more information, you can refer to the SAP Best Practices homepage on the SAP Service Marketplace at
http://service.sap.com/bestpractices.
Information on SCOPE OF PACKAGE
The scope of SAP Best Practices for Services Industries (NL) V1.607 consists of scenarios in SAP ERP. Some scenarios describe integrated processes starting in SAP CRM and
continuing/ending in SAP ERP.
The selected SAP ERP Service package scope could be combined with processes starting in SAP CRM and you are free to install CRM BP package and integrate as necessary.
Nevertheless, the scope covered in this package is solely SAP ERP. .
2 System Setup & Preparation – System
Administrator
Always check the SAP Best Practices for Services Industries NL V1.607 note (1927561) for updates regarding the installation of SAP Best Practices.
2.1
SAP ERP
Install SAP ERP
Prior to installation and activation of a SAP Best Practices package (SAP BP package), the target SAP Application Server (AS) must be installed with the Support Package Stack (SPS) specified in this section and the SAP notes as specified in detail in section SAP Notes and Messages in this guide.
Release and Support Package Level
The deliverables of SAP Best Practices were developed and tested in a system landscape with specific support package levels.
The mentioned Support Package Stack (SPS) is the minimum level which must be applied to the system before you can use the SAP Best Practice package and this is as well the recommended level.
If you run the activation on a higher SPS you may run into activation errors. If you encounter this, perform the activation activities by switching the eCATT to run in foreground mode or implement the configuration manually by using the configuration guides. For more details refer to the document SAP Best Practices Tools that is provided in the documentation package in the section Intro Concepts accelerator
SAP Best Practices Tools..
If you need a higher SPS level in your system FIRST import and activate SAP Best Practices on the SPS levels as mentioned below, THEN upgrade your system to the current SPS level.
The SPS level relevant for the SAP Best Practices for Services Industries Package (NL) V1.607 is listed together with the required components in the next section.
Receiving the Software at the Correct SP Level
If the support level needed for Services Industries Package (NL) V1.607 is not available on the SAP service marketplace download area you need to follow the procedure described in this section.
For 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 Catalogue or download form SAP's Software Distribution Center within SAP's Service Marketplace (SAP's SWDC in SMP). You can only order unrestricted SAP software. Contact the SAP contract department to ask for a physical shipment or create a customer message on component XX-SER-SWFL-SHIP.
Receiving the software at the correct SP level: Via SAP's Software Distribution Center (SWDC) on the SAP Service Marketplace and standard delivery (for example SAP Software Catalogue) only the current Service Release (SR) is delivered to SAP customers / partners. If you encounter the situation that the required Support Package Stack (SPS) for correct SAP Best Practices packages activation is based on SPS level LOWER than the current SR, the request for the necessary SPS is handled via a customer message. For details, see the SAP Note 925690 - Standard Ordering
Procedures for SAP Software (https://service.sap.com/sap/support/notes/925690).
Required SAP Components
2.1.3.1
Installation of Additional Language
You need to import NL (Dutch) as additional language directly after installation before applying the enhancement packages and support packages using transaction SMLT.
Doing this you avoid performing the import of the language parts of the support packages. After you updated afterwards the system to the required enhancement and SPS level please perform in client 000 a language supplementation of NL with EN, depending to your needs. This should be performed before you copy client 000 to your activation client.
2.1.3.2
Component Information
1) SAP enhancement package 7 for SAP ERP 6.0 (ECC Server)
You can find detailed information for SPS definition for the SRs of SAP ERP, in SAP Note
774615 - Support Package levels of ERP/ECC installations/upgrades.
To download the SAP enhancement package 7 for SAP ERP 6.0, go to the Software Distribution Center (SWDC) on the SAP Service Marketplace: https://service.sap.com/swdc, then choose
Installations and Upgrades A – Z – Index SAP ERP SAP ERP ENHANCE PACKAGE EHP7 FOR SAP ERP 6.0
2) SAP enhancement package 7 for SAP ERP 6.0 Support Package Stack 02 for SAP ERP 6.0 Application Server ABAP (SAP ERP 6.07 SPS01 AS ABAP)
SAP ERP 6.0 based SAP Best Practices packages mainly focus on the set of software
components bundled in ECC Server. With the goal of a standardized installation process among baseline and industry SAP BP packages, a complete update of all ABAP software components of
EHP7 FOR SAP ERP 6.0 is required.
Further information regarding the installation of SAP enhancement package 7 for SAP ERP 6.0 can be found in SAP Note 1818596 - Enhancement package 7 for SAP ERP 6.0: Required SWC To download the EHP7 FOR SAP ERP 6.0 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 SAP enhancement package 7 for SAP ERP 6.0
As per SAP Note 1737650 - 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 EHP7 FOR SAP ERP 6.0
3) SAP frontend components, for example SAP GUI for Windows and SAP NetWeaver Business Client
Ensure 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:
SAP GUI:
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 4.0
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) 617 V[xy] Use the latest version as
outlined in SAP Note 1301301 Release Strategy
for SAP Best Practices Package ABAP Add-ons
SAP BP ADD-ON FOR ERP 617
BP-CANW (1) 740 V[yz] Use the latest version as
outlined in SAP Note 1301301 Release Strategy
for SAP Best Practices Package ABAP Add-ons
BP CROSS
APPLICATION ADD-ON 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
To download the SAP Best Practices Add-ons, go to the Software Distribution Center (SWDC) on the SAP Service Marketplace:
https://service.sap.com/swdc, and then choose Installations and Upgrades Browse our
Download Catalog SAP Best Practices SAP BP FOR SERVICES INDUSTRIES
SERVICES INDUSTRIES V1.607 Installation. 5) Adobe Document Services (ADS)
The Adobe Document Services (ADS) is only needed if you want to install the business scenario Offline Time Recording (266).
For Adobe Document Services (ADS) a special license is required to use the interactive feature of Adobe Forms. Contact your SAP Sales Representative for licensing and pricing information.
Adobe Interactive Forms as well as standard print forms are rendered in the Adobe Document Services (ADS) software component, 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 credential file must be installed in the ADS. This credential gives the forms special ReaderRights each time they are rendered in ADS and allows them to be filled in using Adobe Reader. In the ADS configuration guide step 7.3, perform Installing a PKCS #12 Credential.
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.
To use the forms, the latest version of Adobe Reader (currently 9.1.0) must be installed on all client PCs that use them.
6) 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 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 605 is in the list. If it is not listed, and you want to set up
2.2
SAP Best Practices Add-On
The following SAP Best Practices Add-ons must be imported into the system:
BP-ERP 617V[xy] and BP-CANW 740V[xy]
These Add-Ons contain the SAP Best Practices technical framework (e.g. BC-Sets, eCATTS, print pgrams)
BP-SOLBLD 70V[yz]
This Add-On contains the SAP Best Practices solution builder program
Always use the latest versions of the Add-ons as outlined in SAP Note 1301301
Release Strategy for SAP Best Practices Package ABAP Add-ons
Check the SAP Best Practices Services Industries Package NL V1.607 Note (1927561). If a correction transport is mentioned in the SAP Note, you must import this into the system.
For more details, see the document Importing SAP Best Practices Add-Ons (ADDONINS.PDF) on the configuration DVD.
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-ons ERP and BP-CANW and the Add-on BP-SOLBLD 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 to have 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. Correction transports may also be mentioned in the SAP Best Practices Services Industries Package NL V1.607 note (1927561). It may be necessary to import such a correction transport into the system.
2.2.1.1
Recommendation for SAP Best Practices Activation
The preconfigured content of SAP Best Practices can be used to initially set up a prototype or development system.
ERP system. These SAP Best Practices configuration settings can be transported into test systems and production systems as necessary.
2.3
SAP Enterprise Extension Sets and Enterprise
Business Functions
Use
After installing SAP ERP, the following SAP ECC extension sets must be activated before you start activation of the SAP Best Practices for Services Industries Package.
The activation of Enterprise Extensions, Business Functions and Business Function Sets will change your system and cannot be rolled back. For more details regarding the impact, check the documentation of the related extension or business function.
Ensure that you have activated all Enterprise Extension Sets and Enterprise Business Functions as outlined below before you create the client in which the SAP Best Practices Baseline Package shall be activated (see section Creation of Client for SAP
Best Practices Activation below).
Do NOT activate additional Enterprise Extensions or Business Functions because this will result in serious errors during activation of SAP Best Practices. Activate ONLY the Enterprise Extensions and Business Functions as listed below.
Procedure
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 (by marking the column Planned Status) and then choose the Activate
Changes button.:
3.
Enterprise
Extensions Planned Status Remarks
EA-FIN On Needed for scenarios Cash Management and Asset
Accounting (new depreciation calculation).
EA-FS On Needed for scenario Cash Management
EA-PLM On Only needed if you want to install one or more of the scenarios that belong to the area Service and full
scope, respectively.
EA-TRV On Only needed if you want to install one or more of the scenarios that belong to the area Service and full
scope, respectively.
Business Functions Planned
Status Remarks
LOG_MM_CI_1 On Materials Management
Required for all Materials Management/Procurement (BB 104) Scenarios
LOG_MM_CI_3 On Materials Management - Enhancements in Procurement
Required for all Materials Management/Procurement (BB 104) Scenarios
LOG_SD_CI_02 On Required for Sales Scenario Batch Recall (BB 122) Required for Service Scenario (BB 196)
LOG_SD_SIMP_02 On Sales & Distribution Simplification 2 (Order-to-Cash) Required for all Sales & Distribution Scenarios (BB 105)
Note: This BF is required as prerequisite for BF LOG_SD_CI_02
PRS_ERP_CPILS_1 On Required for all Service Scenarios (BB 192) PRS_GEN_UI On Prof. Services, UI Enhancements Required for all
Service Scenarios (BB274, BB263)
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:
Required for Service Scenarios (BB 192) LOG_EAM_CI_2 On Enhancement Package 3 - Enterprise Asset
Management
Required for Service Scenarios (BB 192) LOG_EAM_CI_3 On Enterprise Asset Management: Continuous
Improvements
Required for Service Scenarios (BB 192)
LOG_ESOA_OPS_2 On Enhancement Package 3 - Service Enabling / ERP Operations
Required for Service Scenarios (BB 192) 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
Required for Service Scenarios (BB 192) LOG_SD_CI_01 On Sales & Distribution
Required for all Sales & Distribution Scenarios (BB 105)
LOG_SD_SIMP_02 On Sales & Distribution Simplification 2 (Order-to-Cash) Required for all Sales & Distribution Scenarios (BB 105)
Note: This BF is required as prerequisite for BF LOG_SD_CI_02
OPS_SME_SIMP_01 On Small & Midsize Enterprises Simplification 1 (POWLs for re-usable pool role)
Required for all scenarios (BB100)
OPS_PS_CI_1 On Required for all Service Scenarios (BB 192) PRS_HCM_CPILS_1 On HCM, CATS WD Lean Staffing (Reversible) BB263
SD_01 On Logistics S&D Simplification
Required for all Sales & Distribution Scenarios (BB 105)
4. The system displays an informational dialog box. Choose Continue.
5. Choose Back.
2.4
Creation of Client for SAP Best Practices
Activation
You 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 Extension Sets and Enterprise Business Functions as outlined in the section SAP Enterprise Extension 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 section 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.5
System Status of Client Roles and Cross-Client
Object Changes
Client Role
sThe 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.
The client role must not be empty to avoid activation errors; SAP recommends to choose the client role Test (development test client) or Customizing (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.
Cross-Client Object Changes
Some of the system preparation activities and the activation of the SAP Best Practices package itself require that cross-client object changes are possible in the system. To check the relevant setting of your system, use transaction code SCC4. In the area cross-client object changes you need to select the option Changes to Repository and cross-client Customizing allowed.
2.6
SAP Notes and Messages
If issues become apparent after shipment of this this Best Practice Package (and hence of this document), an SAP Note exists to cover such eventualities.
Before you start the activation of the related SAP Best Practices scope, check the latest version of the SAP Note below to obtain updates and corrections for problems that do not become apparent until after shipment.
All SAP Notes have to be applied to the system via the SAP Note Assistant. All SAP Notes mentioned below need to have the implementation status Completely
implemented. Some SAP Notes require manual action before you set them to status
completely implemented.
To avoid activation errors as a result of generating loads, you have to perform a mass generation using transaction SGEN as described in the SAP Note 481548.
SAP Note # Description Component
1927561 SAP Best Practices for Services Industries Package NL V1.607 SV-SMB-AIO-BP-PSV
The following SAP Notes must be implemented (if not stated otherwise in the SAP 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 Cross client Important:
Always check the Related Notes in SAP Note 1301301 for relevant versions of your BP-ERP, BP-CANW and BP-SOLBD add-ons. The corrections may be attached to these related notes.
1859871 Assignment to command interfaces with generic type BC-TWB-TST-ECA Activation Cross
SAP
Note # Description Component Area Cross client Remark
1865822
NR: Error in NUMBER_RANGE _INTERVAL_LIST
BC-SRV-NUM Activation Cross client
70038
VPRS is not generated for batch items
SD-BF-PR Usage Cross client
This note is only required if you want to activate and use Batch Management (scenario 117). Only item 4 in the solution section of the note need to be implemented. Proceed as follows: Open the transaction SE38 and change the report RV60AFZZ in the following way: At the end, in the section FORM USEREXIT_PRICING_PREPARE_TKOMP 497850 Condition maintenance reports and Unicode
SD-MD-CM Usage Cross client Use transaction V/LE or call report RV14ALLE
1276914 Advanced Installation Options of SAP Best Practices SV-SMB-AIO-BP Usage No
This note has only be checked if you want to activate and use the Cross Company Code Scenarios (Scenario 123,141; Building Block 216) or you are going to activate SAP Best Practices on a system in which already other SAP Best Practices Country Packages have been installed in different clients. 1382685 SE 729 Customizing incorrectly maintained
MM-SRV-SR Usage Cross client
As for clarification of the information provided in this SAP Note, you can use the following information on how to proceed: Choose transaction ML81N. Then double click table configuration (the symbol on right top corner of the ALV grid). Choose the button Administrator. Then scroll to the end and identify the numbers of columns / positions. After that, copy entries of column Fld name into an XLS file. Then compare against se16n T162V, for layout 0,..,5. It should be equal.
Entries need to be deleted for all layouts - six layouts - six entries to be deleted if one is not included in ML81N.
1383507
Error BM305 when using lower case units of measure
CO-PA-SPP Usage Cross client
1541888
Frequent/repeated accesses to the table REPOSRC
BC-ABA-LA Usage Cross client
Needed to avoid unnecessary database accesses to the table REPOSRC in scenarios using ABAP contexts (e.g. Sales and Distribution, for example in the transaction VA01).
SAP
Note # Description Component Area Cross client Remark
1553281
Mexico Hard Currency change to USD
XX-CSC-XX Usage (Cross client)
Needed for closing scenarios. It solves the following issue in foreign currency valuation: Even if company codes are not used in the client they are all checked in the foreign currency valuation program. The missing entry in standard settings for Mexico will result in errors during check independent from the actual country of your company code. The SAP Note fixes this issue.
This setting is client dependent, but if you apply it to your source client prior to copy your client it will get de facto cross client.
1659573 Determination of WBS Settlement Rule Strategies per BADI SV-SMB-AIO-BP Usage Cross client
Needed for Service scenarios: an implementation class for the Business Add-In WBS_SETTLEMENT_RULE is created.
1702488
OFFI: Save As menu item can't be disabled in Office 2010 BC-FES-OFFI Usage NO, local GUI installat ion
Save As menu item cannot be disabled.
This happens with MS Office 2010 since SAP is having its own menu rather than Microsoft menu because of limitation in Microsoft side while rendering File menu when document rendered in in-place mode.
1857140
Abbruch des Programms TFC_COMPARE_ VZ
FI-GL-GL-D Usage Cross client FAGLF03 used on BPD 159
1774625 SNRO: Creating an external interval
Usage
SAP
Note # Description Component Area Cross client Remark
1935076 Short dump ERR_PRHI_BUF during plan distribution Usage PS-COS-PLN-PLN (Planned Costs) Cross
client Error occurs in BPD 433
Only if you use SAP NWBC 4.0, implement the following SAP Notes in addition to the SAP Notes as listed above.
SAP
Note #
Description Component Area Cross client
Remark
1388279
Initialization of Sales Order Type per BADI in NWBC
SV-SMB-AIO-BP Usage
Cross
client Needed for Lean sales order UI. (NWBC)
900000
Netweaver Business Client -
FAQ BC-FES-BUS Usage n/a FAQ about NWBC 1754946 NWBC for Desktop 4.0: Prerequisites and restrictions BC-FES-BUS-DSK Usage x 1707626 NWBC 4.0 Patches -CLIENT ONLY- SAP NetWeaver BC-FES-BUS-DSK Usage x 1830798 SAP BP: SAP NWBC 4.0 as of EhP6 for SAP ERP 6.0
BC-FES-BUS-RUN Usage x Relevant for EhP7
1845518 Impact of NWBC 4.0 on SAP_NBPR_* roles
SV-SMB-AIO-BP Usage Cross client Workaround for NWBC Index navigation path
1871982
Contact persons returned for sold-to party incorrectly
SD-SLS-API Usage Cross client Unwanted Ship-to party selection in Lean sales order UI. (NWBC)
2.7 Pre-Activation Activities
Use
After 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 for activation.
Set Up of http and https Services
Use
http and https services have to be set up.
Procedure
1. Run the following activity:
Transaction Code SMICM
2. On the ICM Monitor screen, choose the menu path Goto Services (shift+F1)). 3. Activate http and https services.
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 bc bsp smb sc_scoping_tool
default_host sap public myssocntl
These services are needed for the SAP Best Practices solution builder 4. Choose Back.
Generation of RV13xxxx Reports
0 Call transaction SE38.
1 In the Program field, enter RV12A001. Then choose Execute (F8).
2 In the Condition tables: Subsequent Generation – Online screen, select the Reports and
Screens checkbox and Online checkbox. Leave all other fields empty.
3 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; error 862 system cannot read the structure for table B047), you can ignore these errors.
5. Choose Back and leave the transaction.
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.
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).
Generation of Characteristic VRTNR
The 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
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.
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 Create 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 line VRTNR and choose Confirm. 10. In the subsequent Information dialog boxes, choose Enter.
11. On the Create Char. VRTNR screen enter 2 in field Display opt. (see section further
properties).
12. Choose Save.
13. In the Check results: Display messages dialog box, select Continue. 14. In the Save (Save in spite of warnings?) dialog box, choose Yes.
Deactivation of CRMAPO
1. Call transaction BF11.
2. On the information message, choose Enter.
3. On the Change View BTE Application Indicator: Overview screen, deselect the checkbox for the CRMAPO CRM-APO Adapter application.
4. Save your entries.
5. Enter a workbench request in the dialog box. 6. Choose Back.
Deactivation of the CRMAPO CRM-APO Adapter application prevents a system short dump when saving a sales order with configurable items (scenario 147).
Deselection of Activation Links in BC Sets
We recommend that you turn off the creation of activation links. By doing this, you can increase activation speed significantly and avoid errors.
Procedure
1. Run the following activity:
SAP 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.
6. Save your settings.
2.8 Printer Settings
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 replace the printer LP01 as described in section Scoping and Activation of Scenarios, step 5: Personalize the Solution, below.
Optional: Set up Printer Environment
The following activities are only needed if 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 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: <your printer name> with the short name <your
printer name>
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
Inform the users to assign printer <your printer name> to their default values using the following procedure:
1. Choose transaction SU3. 2. Choose the Defaults tab.
3. In the Spool Control section enter the Output Device <your printer name> 4. Select the Output Immediately and Delete After Output checkboxes.
5. Save your entries.
Printing Bar Codes
If 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.
2.9 Maintain Profile Parameters
Maximum Work Process Run Time
Use
Dynamic 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.
Procedure
1. Run the following activity:
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 6. Choose Save.
When you save the change, the window will be closed and the value of the parameter will be changed. This change only becomes effective when you log off and then log on to the system again.
If the parameter is set in RZ11, you lose the change when you restart the server.
This parameter value is only needed for 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!
SAP Scripting
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.
Procedure
0 Run the following activity:
Transaction Code RZ11
1 On the Maintain Profile Parameters screen, make the following entries
Field name Description User action and
values Note
Param. Name Profile parameter name sapgui/user_scripting 2 Choose Display.
3 On the Display Profile Parameters Attributes screen, select Change values. 4 On the Change Parameter Value screen, make the following entries.
Field name Description User action and values Note
New Value New Value for user
scripting TRUE Enable SAP Scripting
5 Choose Save.
When you save the change, the window closes and the current value of the
parameter changes to TRUE. This change only becomes effective when you log onto the system again.
If the parameter is set in RZ11, you lose the change when you restart the server.
Authentication using SAP Logon Tickets
Use
As 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:
Procedure
1. Run the following activity:
2. On the Maintain Profile Parameters screen, make the following entries
Field name Description User action and values Note
Param. Name Profile parameter name login/accept_sso2_ticket 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
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).
8. On the Maintain Profile Parameters screen, make the following entries
Field name Description User action and values Note
Param. Name Profile parameter name login/create_sso2_ticket 9. Choose Display.
10. On the Display Profile Parameters Attributes screen, select Change values. 11. On the Change Parameter Value screen, make the following entries.
Parameter Name Description New
value
Note
login/create_sso2_ticket Create SSO tickets on this system
2 Check and adapt value if necessary
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.
Set Default Timeout for http and https Services
Use
It 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
icm/server_port_0 = PROT=HTTP, PORT=8000, PROCTIMEOUT=300, TIMEOUT=600
icm/server_port_2 = PROT=HTTPS, PORT=44300, PROCTIMEOUT=300, TIMEOUT=600
Procedure
1. Run the following activity:
Transaction Code RZ10
2. On the Edit Profiles screen, enter your instance profile. 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
Parameter Name Description New
value Note
icm/server_port_<*> Standard value for *: 0: http, 1 or 2: https 300 or 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.
2.10 Creating User for Activation of SAP Best Practices
Content
Use
In this activity, you create an user to run the activation of the related SAP Best Practices scope. However, SAP Best Practices does not supply separate customizing or setup roles. Instead, you should use the functions provided in Role Maintenance (transaction PFCG). Here you can define a role corresponding to your individual IMG project with all the authorizations you need to access the corresponding IMG activities required for the SAP Best Practices scope. For more information about building a role for a Customizing project, see the documentation for the transaction PFCG.
Alternatively you can use the authorization profile SAP_ALL. If this authorization does not apply to your authorization concept, you should restrict the rights of the user according to your internal authorization guidelines. Without the profile
SAP_ALL, issues during the activation may occur and need to be solved. You can
use the transaction SU53 to get information on the missing authorizations and extend the authorization data as necessary.
Directly after activation of the SAP Best Practices content, remove the authorizations you have given to the system user that has performed the activation steps. This is for security reasons to avoid that the system user misuses the authorizations granted before.
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 <User-ID> and choose
Create.
3. Choose the Address tab. 4. Make the following entries:
Field name User action and values Note
Last name <Last name of the user> First name <First name of the user> 5. Choose the Logon Data tab.
6. Make the following entries:
Field name User action and values Note
Password <initial password>
User type Dialog
7. Choose the Defaults tab. 8. Make the following entries:
Field name User action and values Note
Logon language EN
Decimal notation 1.234.567,89
Date format DD.MM.YYYY
9. Choose the Profiles tab.
10. Assign the authorization profile as defined before. 11. Save your entries.
Result
3 Activation of Business Content / Scenarios –
Activation consultant
The following sections describe the activities that have to be done by the consultant who is going to activate SAP Best Practices in the system.
3.1 Initial Check of System Readiness
It is necessary that you check if your system administrator has applied the correct SPS level as outlined above in the section Release and Support Package Level.
In addition, ensure that the system administrator has also finished all activities as described in the section System Setup & Preparation – System Administrator.
Only if these prerequisites are met, continue with the following steps.
3.2 Decision on the Scope to be Activated
Before 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.
The decision on the scope to be activated has to be done together with the business consultant who is taking care that the business processes reflect the scope as desired by the project owner.
Detailed Information on the Scenarios
Details for individual scenarios are available in the documentation package under Business Info
Preconfigured Processes, Preconfigured Processes accelerator.
Information on Combining Scenarios
3.2.2.1
Information on Scenario Business Dependencies
Since the SAP Best Practices Services Industries package provides integrated business processes, the given process flows covered by the scenarios are in some cases connected, i.e. you will find business dependencies between scenarios. For example, the scenario Returns and
Complaints requires – from a business point of view – the scenario Sales Order Processing – Sale from Stock as prerequisite, because the returns process refers to a sales order and delivery
created in the sales order processing scenario.
Since various dependencies exist, you have to check if a scenario that you want to include in your solution requires one or more additional scenarios as a prerequisite from a business point of view.
3.3 Activation Language
Make sure that your logon language is always English (and NOT your local language) for all activation activities.
3.4 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.
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.
SAP Software Change Registration (SSCR): Developer
Key
Use
The 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.
Procedure
1. Access the SAP Service Marketplace at http://service.sap.com/sscr.
2. On the SAP Software Change Registration (SSCR) start page, you get the detailed user documentation 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.
Unicode Settings
Use
Before each user logs onto the system for the first time, the user’s local GUI must be set to use the Unicode code page.
Procedure
3. From the SAP Logon pad, select your system ID. Then choose the Change Item button. 4. On the System Entry Properties dialog box, choose the Codepage tab.
6. Choose OK.
Allow GUI Scripting and Change Default Security
Settings
Use
Perform this activity so that eCATTs GUI scripts can by executed with your GUI and default security settings are adapted.
Procedure
1. 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. From the Accessibility & Scripting folder choose Scripting.
4. Select the Enable scripting checkbox.
5. Deselect the checkboxes Notify when a script attaches to SAP GUI and Notify When a Script
opens a Connection.
6. Then, from the Security folder choose Security Settings.
7. Select the Default Action as Allow.
8. Choose the OK button at the bottom.
Change these SAP GUI settings back to default settings after the activation is completed to ensure enhanced security of your SAP system.
Set Decimal Notation and Date Format
Use
Perform this activity to set up the activation user ID.
Procedure
1. Run the following activity:
SAP Menu System à User Profile Own Data Transaction Code SU3
2. Choose the Defaults tab.
3. Make sure you set Decimal Notation to the following format: 1.234.567,89. 4. Make sure you set Date Format to the following format DD.MM.YYYY.
5. Make sure to assign your printer in the field output device (see also section Printer
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.
Result
The decimal notation and date format have been set up according to your country format. The standard printer has been defined.
3.5 Getting the Business Content for Activation
Perform the following steps Getting the Solution Scope File and Getting the
Installation Data Files on the same day. If you download the files at different times,
you may encounter errors due to mismatches.
Getting the Solution Scope File
Use
The technical structure for each solution package (processes or scope items, building blocks and technical objects) is managed by a solution scope file.
Procedure
1. To download the solution scope file, first go to SAP Service Marketplace at
http://service.sap.com/bp-implcontent.
2. Choose the Solution files link and then the link for EHP7 for SAP ERP 6.0 3. Download the following solution scope .zip file:
SOL_SERV_ERP607_NLV1_BP_ERP607V[y].
Getting the Installation Data Files
Use
The installation settings (configuration settings and master data) of the solution packages are managed by the installation data files.
Procedure
1. To download the installation data files, first go to SAP Service Marketplace at
http://service.sap.com/bp-implcontent.
2. Choose the Installation data file sets link and then the link for EHP7 for SAP ERP 6.0. 3. Download the following installation data .zip file: INST_FILES_NL_pre_BP_ERP617V[y].
Note: [y] is a placeholder for the addon version.
Creating a Folder for the SAP Best Practices
Activation
1. 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), many variant files (*.txt) and one bitmap file (smb40_leaf.bmp).
3.6
Activation Sequence of Scenarios
When activating the complete Services Industries Package (all scenarios) or just selected scenarios, the necessary technical building blocks are activated in the correct sequence when using the SAP Best Practices solution builder. However if you would like deviate from the normal activation procedure, additional information has to be taken into account for the scenarios
Activate Document Splitting, Segment Reporting and Cost Of Sales Accounting, as outlined in the
following section.
Document Splitting, Segment Reporting and Cost of Sales Accounting
If you are modifying one of the SAP-shipped scopes, and plan to use the scenarios Activate Document Splitting (165), Segment Reporting (166) ) ,Cost of Sales Accounting (161) and Services Industries (280). 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, 166 then activate 280.
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) , Cost of Sales Accounting (161) and Services Industries (280) 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.
3.7
Scoping and Activation of Scenarios
You 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.
For an instruction on how to get information on all scenarios included in the Services Industries Package, see section Decision on the Scope to be Activated above.
Step 1: Import the Solution File
1. To run the SAP Best Practices solution builder, from the Command field, enter /n/smb/bbi and choose Enter.
2. On the Solution builder – solution editor screen, from the menu, choose Solution
Import.
3. In the Select one format to import dialog box, choose the Import XML file button.
4. In 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
Use
This 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.
Procedure
6. 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.
10. Make the following entries:
Parameter Value
DOCUMENTATION http://help.sap.com/saap/sap_bp/BBLIBRARY/HTML/ 11. Choose Save.