BL Quick Guide en BRok

EHP5 for SAP ERP 6.0

June 2011

English

Quick Guide to Implement the SAP Best Practices Baseline Package - V1.605 (BR)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

SAP Best Practices Quick Guide to Implement the SAP Best Practices Baseline Package (BR)

Copyright

© 2010 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without 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, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, 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, SAP NetWeaver, Duet, PartnerEdge, ByDesign, Clear Enterprise, SAP BusinessObjects Explorer, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP France in the United States and in other countries.

All other product and service 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 75


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 75


Contents

1 Purpose................................................................................................................. 7

2 System Setup & Preparation – System Administrator...........................................7

2.1 Install SAP ERP....................................................................................................7

2.1.1 Release and Support Package Level.....................................................................8

2.1.2 Installation of Additional Language........................................................................8

2.1.3 Required SAP Components...................................................................................9

2.2 SAP Best Practices Add-On................................................................................11

2.3 NetWeaver Business Client System Settings......................................................11

2.3.1 Activate Context Menu Additional Details............................................................11

2.4 SAP Enterprise Extensions Sets and Enterprise Business Functions.................12

2.5 Creation of Client for SAP Best Practices Activation...........................................14

2.6 System Status of Client Roles.............................................................................15

2.7 SAP Notes and Messages..................................................................................15

2.7.1 Prerequisite SAP Notes for NF-e.........................................................................19

2.8 Pre-Activation Activities.......................................................................................20

2.8.1 Set Up of http and https Services........................................................................20

2.8.2 Activation of Services for SAP Best Practices Solution Builder and SAP NWBC 21

2.8.3 Generation of RV13xxxx Reports........................................................................21

2.8.4 Generation of Financial Accounting Programs....................................................21

2.8.5 Creation of Consistent Business Transaction Groups.........................................22

2.8.6 Generation of Characteristic VRTNR...................................................................22

2.8.7 Deactivation of CRMAPO....................................................................................23

2.8.8 Deselection of Activation Links in BC Sets..........................................................24

2.9 Printer Settings....................................................................................................24

2.9.1 Default Printer......................................................................................................24

2.9.2 Optional: Set up Printer Environment..................................................................24

2.9.3 Printing Bar Codes...............................................................................................25

2.10 Maintain Profile Parameters................................................................................25

2.10.1 Maximum Work Process Run Time.....................................................................25

2.10.2 SAP Scripting......................................................................................................26

2.10.3 Authentication using SAP Logon Tickets.............................................................27

2.10.4 Set Default Timeout for http and https Services..................................................28

2.11 Creating User for Activation of SAP Best Practices Content...............................29

3 Activation of Business Content / Scenarios – Activation consultant....................31

3.1 Initial Check of System Readiness......................................................................31

3.2 Decision on the Scope to be Activated................................................................31

© SAP AG of 75


3.3 Activation Language............................................................................................31

3.4 User Settings for Activation.................................................................................31

3.4.1 SAP Software Change Registration (SSCR): Developer Key..............................32

3.4.2 Unicode Settings.................................................................................................32

3.4.3 Allow GUI Scripting..............................................................................................32

3.4.4 Set Decimal Notation and Date Format...............................................................33

3.5 Getting the Business Content for Activation........................................................33

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 Specific Information on Scenarios.......................................................................36

3.8 Scoping and Activation of Scenarios...................................................................36

3.9 Error Handling: Installation Errors during activation............................................44

3.9.1 Error Occurs During Activation of Automated Task.............................................44

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

3.9.3 Warnings in BC-Set Logs....................................................................................46

3.9.4 eCATT Error Variable xyz does not exist….........................................................46

3.9.5 Window Appears During Activation Start Options – Test Configuration /SMB99/BMSM_O237_J01..................................................................................46

3.9.6 Window Appears During Activation A script is trying to attach to the GUI...........46

3.9.7 Window Appears During Activation Asking to Confirm that Text Was Changed..47

3.9.8 Issue with SAP GUI.............................................................................................47

3.9.9 Description of Manual Steps in Installation Process............................................47

3.9.10 Processing of Scenario Specific Errors................................................................48

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

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

4.3.4 Optional User Parameter.....................................................................................58

4.4 Creation and Change of Queries in Personal Object Worklists (POWLs)...........60

4.4.1 Create Query.......................................................................................................60

4.4.2 Change Query.....................................................................................................62

4.5 Download and Installation of Easy Document Management...............................62

4.5.1 Download (Manual Step).....................................................................................63

© SAP AG of 75


4.5.2 Installation (Manual Step)....................................................................................63

4.5.3 Trouble Shooting.................................................................................................65

4.6 Errors during Usage of Activated Package.........................................................65

4.6.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............................................................................................65

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

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

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

4.6.5 Scenario Reporting with SAP Business Explorer (132): Error Invalid File Format............................................................................................................................ 67

4.6.6 Scenario SAP ERP Reports for Accounting (221): Selection Screen in wrong language..............................................................................................................68

4.6.7 Scenario General Cost Center Planning (175) and Overhead Cost Accounting - Actual (184): Only use overhead rates with application 'KA'................................69

4.6.8 Scenario General Ledger (156): Transaction FB50: Field ‘Assignment no.’ is too large..................................................................................................................... 69

4.6.9 Scenario Internal Product Development (210): Logon to SAP Easy Document Management System is not Possible...................................................................71

4.7 Errors with SAP NetWeaver Business Client (SAP NWBC)................................71

4.7.1 Queries Show No Data / No Columns.................................................................71

4.7.2 Printing functionality.............................................................................................71

4.7.3 Scenario 137: Physical Inventory – POWL for Physical Inventory Documents: Buttons Do Not Work Correctly............................................................................71

4.7.4 Scenario 132: Reporting with SAP Business Explorer: Characteristic 0TCAACTVT does not exist. Check authorizations.............................................72

5 Security Aspects – System Administrators..........................................................73

5.1 User Administration and Authentication..............................................................73

5.2 Roles Management.............................................................................................73

5.3 RFC Destinations................................................................................................73

© SAP AG of 75


Quick Guide to Implement the SAP Best Practices Baseline Package (BR)

1 PurposeThis quick guide provides the information you need to activate the complete SAP Best Practices Baseline Package for Brazil 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 CD/DVD.

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

2 System Setup & Preparation – System Administrator

Always check the SAP Best Practices Baseline package (BR) - V1.605 Note for updates regarding the implementation of SAP Best Practices.

2.1 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 chapter and the SAP notes as specified in detail in section SAP Notes and Messages in this guide. For SAP BP Baseline packages (SAP BP BL packages) this is SAP ERP AS ABAP.

© SAP AG of 75

http://service.sap.com/bestpractices


2.1.1 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 on the documentation DVD in the section Technical information area Tools and Concept.

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 Baseline package is listed together with the required components in the next chapter.

Receiving the Software at the Correct SP Level

If the support level needed for the SAP Best Practices installation 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).

2.1.2 Installation of Additional LanguageYou need to import PT (Portuguese) 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 PT with EN, depending to your needs. This should be performed before you copy client 000 to your activation client.

© SAP AG of 75

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


2.1.3 Required SAP Components Component Information1) SAP ERP Core Component 6.0 (SAP ECC 6.0)

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.

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

NOTE: As SAP Enhancement Package 5 is not yet generally available but only in ramp-up phase, configuration content (SAP Best Practices) for SAP Enhancement Package 5 will not be available to all customers. Only customers who have been nominated for ramp-up process will be able to receive configuration content. Nomination for ramp-up process is subject to a nomination process. Any communicated dates for general availability are non-binding and subject to change without notice.

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 AG of 75

https://service.sap.com/swdc




SAP GUI:

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

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.

Regarding the SAP Netweaver Business Client, do NOT download NWBC NW Business Client 1.0. This version is not designed to be used with the current SAP Best Practices Baseline Package.

Instead, download the version SAP Netweaver Business Client 3.0. This version is the correct one.

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.

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.

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.

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, then choose Installations and Upgrades Browse our Download Catalog SAP Best Practices SAP BP BASELINE PACKAGE SAP BP Baseline Package I Baseline Package – V1.605.

© SAP AG of 75





2.2 SAP Best Practices Add-OnThe following SAP Best Practices Add-ons must be imported into the system:

BP-ERP 605V[xy]

This Add-On 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

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-on BP-ERP 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 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.

2.3 NetWeaver Business Client System Settings

2.3.1 Activate Context Menu Additional DetailsTo be able to use the specific functions in SAP NetWeaver Business Client, you must activate the context menu Additional details for transaction PFCG. For this, maintain the client-independent table SSM_CUST:

Transaction SM30:

- Table/View: ssm_cust

- Button [Maintain]

- Button [New entries]

- Description: ADD_MENU_DETAILS

Value to be set: YES

© SAP AG of 75


Save your settings.

2.4 SAP Enterprise Extensions Sets and Enterprise Business Functions

Use

After installing SAP ERP, the following SAP ECC extension sets need to be activated before you start activation of the SAP Best Practices Baseline 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 Extensions 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 chapter Creation of Client for SAP Best Practices Activation below).

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

Procedure

1. 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 (by marking the column Planned Status) and then choose the Activate Changes button.:

Enterprise Extensions

Planned Status

Remarks

EA-FIN On Needed for scenario Cash Management

EA-FS On Needed for scenario Cash Management

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

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

Business Functions Planned Status

Remarks

LOG_PP_LMAN On Lean Manufacturing, Better MRP Evaluation (Stock/Req. List for Material Group)

© SAP AG of 75


Required for all Manufacturing scenarios (BB 142)

LOG_PP_MIS On Manufacturing Information System: Order Info System and Planning Evaluations


LOG_PP_PRSP On Business Package for Production Supervisor


LOG_PP_SRN_CONF On Shift Report and Notes, Confirmation


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-ment (BB 104) Scenarios

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

Required for Service Scenario (BB 196)

© SAP AG of 75


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:

© SAP AG of 75


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_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)

SD_01 On Logistics S&D Simplification


LOG_PP_INTELI_01 On Technically required for all scenarios that use configuration BB 142; content related required for scenario 146

OPS_PS_CI_1 On Required for all Service Scenarios (BB 192)

PRS_ERP_CPILS_1 On Required for all Service Scenarios (BB 192)

LOG_WM_ROLES On Trade, Warehouse Operations Manager Role; required for scenario 137

LOG_WM_ROLES_2 On Warehouse Operations Manager Role via NWBC (Reversible); required for scenario 137

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

4. Choose Back.

2.5 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 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:

© SAP AG of 75


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

The client role must not be empty to avoid activation errors; SAP recommends to choose the client role Customzing.

2.7 SAP Notes and MessagesIf issues become apparent after shipment of this Baseline 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

1591558 SAP Best Practices Baseline Package BR V1.605

INFO SAP NOTE ONLY.

SV-SMB-AIO-BP-LA

© SAP AG of 75


PLEASE CAREFULLY READ ITS CONTENT

PAY ATTENTION TO THE ATTACHMENTS. SOME ARE REQUIRED TO PERFORM THE ACTIVATION OF THE SCENARIOS (TOPIC 2.10 OF SAP NOTE).

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

SAP Note #

Description Component Area Remark

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

SV-SMB-AIO-BP Activation 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.

1605994 AS ABAP 7.02.08: eCATT/Error in parser of ABAP statemt.

BC-TWB-TST-CATT Program error Error in script parsing

70038 VPRS is not generated for batch items

SD-BF-PR Usage 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 needs 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_TKOMPinsert the following additional line before the existing line ENDFORM:

tkomp-evrwr = tvap-evrwr.

497850 Condition maintenance reports and Unicode

SD-MD-CM Usage

1173675 TABLE_FREE_IN_LOOP and error 26296 in CV01N

CA-DMS Usage This note is only required if you want to activate and use the Easy Document Management System (EasyDM) (Building Block 223).

1276914 Advanced Installation Options of SAP Best Practices

Usage 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 As for clarification of the information provided in this SAP Note, you can use the following information on how to proceed: Choose

© SAP AG of 75


SAP Note #


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 .

Delete all entries available in the table layout, but not in ML81N column list using SM30 for T162V.

Entries need to be deleted for all layouts - six layouts - six entries to be deleted if one is not included in ML81N.

1514615 FAGLFLEXT: FM integration in report writer reports

PSM-FA Usage

1508472 CJB1: Termination during generation of settlement

CO-PA Usage

1539815 Timeout in CJB2 PS-COS-PER Usage

1541888 Frequent/repeated accesses to the table REPOSRC

BC-ABA-LA Usage 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).

1523380 SAPScript: Wrong result of TEXT_CONTROL_REPLACE

BC-SRV-SCR Usage

1529914 SAPscript: #-Character in replaced symbols

BC-SRV-SCR Usage

0916003 Brazil : Withholding tax accumulation for CBT

PERFORM MANUAL STEPS!

ONLY CREATE THE FORMULAS 900 AND 901 AS REQUESTED IN THE SAP NOTE

XX-CSC-BR Installation

1116243 Jump ALV -> BEX: Small enhancements

BW-BEX-OT-OLAP Usage

1097455 NFE: Bank files should accomodate Doc. numbers with 9 digits

PERFORM MANUAL STEPS TOO!

XX-CSC-BR-NFE Usage

1061205 Brazil: Customer tax classification for CBT


© SAP AG of 75


SAP Note #



1032346 TR IA06: Unable to add components to the generic TL


PM-PRM-TL Usage

0981123 PIS / Cofins Tax Law and Tax Situation



0958243 CBT: Customer is ICMS exempted and BX12 is wrong ca


XX-CSC-BR-SD Installation

0719246 REPORTWRITER: Texts not in logon language


FI-SL-IS-A Usage

0497850 Condition maintenance reports and Unicode

SD-MC-DM Usage

0078109 Report Writer: Regeneration after adv. Correction

FI-SL-IS-A Usage

1290153 IPI,PIS and Cofins fixed base value



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

SAP Note #


1069540 Printer Configuration for PDF Display in NWBC

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

1127957 SPS 14: WD ABAP ALV: Export BEx Analyzer -

BW-BEX-ET-WB Usage This SAP Note is only needed if you want to use SAP Business Explorer Analyzer (scenario 132).

1388279 Initialization of Sales Order Type per BADI in NWBC

SV-SMB-AIO-BP Usage

© SAP AG of 75


SAP Note #


1433603 NWBC causes locks in WebDynpro applications

BC-WD-CLT-BUS Usage

1353538 SAP NetWeaver Business Client 3.0 - Patch Collection

BC-WD-CLT-BUS Usage

1400383 SAP BAiO: SAP NWBC 3.0 & EhP5 for SAP ERP 6.0 (ABAP), Config

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.

1508439 Correction of translation XX-TRANSL-EN Usage

1524223 Success message shown twice in SPPR

EP-PCT-PUR-BP Usage

1524776 Change Order opens order in display mode

EP-PCT-PUR-BP Usage

1477686 Business Explorer: duplicate usage of file extension

BW-BEX-ET-WB Usage This SAP Note is only needed if you want to use SAP Business Explorer Analyzer (scenario 132). Only the frontend correction mentioned in the note is relevant.

1586295 IFbA: unnecessary call of ADS

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

2.7.1 Prerequisite SAP Notes for NF-eThe following SAP Notes must be implemented before starting the activation of the scenarios.

Before you start the building block activation 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.

In transaction SNOTE, some notes may present the status “cannot be implemented”. This means that the source-code attached to the note might be already implemented or included into the current support package level. Pay attention, however, to its manual steps. In several cases, the manual steps must be performed.

SAP Note # Description

1145148 NFe: Cancellation for Contingency NFes

© SAP AG of 75


1298283 NF-e: Skip for NF-e with validation error1358891 Local time / local date in NF header by changing a NF/NF-e1394627 NF-e: J_1BNFE_INVALID contains too many entries1370016 NFe: Posting date change for manual incoming NFe1376324 NF-e: Skip for NF-e with validation error1377873 NF-e: House number reported twice in XML file1377879 NF-e: Report J_BNFECALLRFC aborts with message A0981390976 NF-e: Cancel incoming NF-e - contingency and history tab1391782 NF-e: J_1BNFECHECKNUMBERRANGES gives duplicate results1393560 NF-e: Reference field for Incoming Entrada not to be used1396498 NF-e: sending incoming documents should not be allowed1400235 NF-e: short dump in NFe monitor when numbering a NF-e1401296 NF-e: wrong reference NF for return of stock transfer1401337 NF-e: Leading zeros for NFe Number in Reference Field1403333 NF-e: Cancellation of Component Shipment for Subcontracting1403811 NF-e: Disabling switch to contingency for MSS 'V' and 'G'1403819 NF-e: Number range check reports the year in a wrong format1404094 NF-e: reset rejected nf-e and send again - wrong J_1BNFEDOC1404301 NF-e: View J_1BNFENUMCHECK does not allow new entries1406421 NF-e: exclude rejected & reset NF-es from batch run1411196 NF-e: Reference for Return of Incoming or for Entrada (MIRO)1288677 Pis&Cofins tax laws not transferred into Nota Fiscal1173018 NF-e: Field control for Random Number and Check Digit1444121 NF-e: Customizing Field Control Random Number, Check Digit1153965 NF-e: Improvement of the customizing views for NF-e1514723 NF-e: Conversion routine for field NCM - missing for XML 2.01533948 Nf-e: Message BL 203 in nota fiscal monitor J1BNFE1454408 Nf-e: Change of access key: tpEmis and random number1569165 NF-e XML-Tag <vBC> is zero for taxes with "other base"1569877 NF-e Issuing type empty for incoming return nota fiscais1572180 NF-e: XML is not filled with PO Number for Sched. Agreements1572220 NF-e: NF-e is not cancelled due to delivery not found1577955 NF-e: Partner Address data is not filled1583096 MBSU: erroneous message 8B 020 appears in the NF-e log1585366 NFe: Cancellation of material document with batch classes1580061 Professional Services: Mitarbeiterzuordnung Verkaufsbeleg1587263 NFe-in: suggest purchase order and scheduling agreement only1565110 NF-e in: step "create goods receipt" sends picking request1533008 NF-e incoming: Corrections for EhP5 SP03

© SAP AG of 75


2.8 Pre-Activation Activities

Use

After 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.8.1 Set Up of http and https Services

Use

http and https services have to be set up.

Procedure


Transaction Code SMICM

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

3. Activate http and https services.

2.8.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 bc bsp smb sc_scoping_tool

default_host sap public myssocntl

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

4. Choose Back.

2.8.3 Generation of RV13xxxx Reports 1. 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).

© SAP AG of 75


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, VK770), you can ignore these errors.

5. Choose Back and leave the transaction.

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

2.8.5 Creation of Consistent Business Transaction Groups

For the execution of assessments, distributions, periodic reportings 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.8.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

© SAP AG of 75


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.

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

© SAP AG of 75


If application CRMAPO is not listed you can skip this section.


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

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

Procedure


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.9 Printer Settings

2.9.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 Baseline 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 chapter Scoping and Activation of Scenarios, step 5: Personalize the Solution, below.

© SAP AG of 75


2.9.2 Optional: Set up Printer EnvironmentThe 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: 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

Inform the users to assign printer LOCL 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 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.

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

© SAP AG of 75




2.10 Maintain Profile Parameters

2.10.1 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


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 AG of 75


2.10.2 SAP Scripting

Use

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

Procedure




Field name Description User action and values

Note

Param. Name Profile parameter name sapgui/user_scripting

3. Choose Display.




New Value New Value for user scripting

TRUE Enable SAP Scripting

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

2.10.3 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:

© SAP AG of 75


Procedure





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

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.

2.10.4 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):

© SAP AG of 75


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

Procedure



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.

2.11 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

© SAP AG of 75


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.



Password <initial password>

User type Dialog




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.


Result

An user to activate SAP Best Practices content has been created.

© SAP AG of 75


3 Activation of Business Content / Scenarios – Activation consultant

The following chapters 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 ReadinessIt 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 chapter System Setup & Preparation – System Administrator.

Only if these prerequisites are met, continue with the following steps.

3.2 Decision on the Scope to be ActivatedBefore you activate the Baseline 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 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 Baseline package. Select the scenarios map for overviews, process flows and details of individual scenarios.

3.3 Activation LanguageMake 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 AG of 75

http://help.sap.com/bp_bl603/BL_DE/html/preconfigured_scenarios_full_scope_EN_DE.htm


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

3.4.2 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 720 pad, select your system ID. Then choose the Change Item button.

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

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

6. Choose OK.

3.4.3 Allow GUI Scripting

Use

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

Procedure

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

2. Select the menu item Options.

© SAP AG of 75

http://service.sap.com/sscr


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. Choose the OK button at the bottom.

3.4.4 Set Decimal Notation and Date Format

Use

Perform this activity to set up the activation user ID.

Procedure


SAP Menu System à User Profile Own Data



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 chapter Printer Environment above).


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 them at different times, you may encounter errors due to mismatch reasons.

© SAP AG of 75


3.5.1 Getting the Solution Scope File

Use

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

Procedure

1. The solution scope file can be found as attachment to the SAP Best Practices Baseline Package 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:

<Mat-Nr Config DVD>_Scope_<Solution_ID><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.

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

Example: 5XXXXXXX _SCOPE_BL_BR_V1605_605V#.zip

3.5.2 Getting the Installation Data Files

Use

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

Procedure

1. 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 SAP Best Practices Packages and then choose Installation Data Files - SAP ECC 6.0 EhP5 and select the country Brazil.

© SAP AG of 75

http://service.sap.com/bestpractices


2. Download installation data ZIP-file package

<Mat-Nr Config DVD>_BP_FILES_<country>_<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.

or the SAP Best Practices Add-On Version e.g. 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).

Example: 5XXXXXXX _BP_FILES _BR_605V#.zip

3.5.3 Creating a Folder for the SAP Best Practices Activation1. Create a folder on a hard drive (for example, on your local hard drive) that can be

accessed from within the SAP system where you want to activate the SAP Best Practices Baseline 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 ZIP files you downloaded in the previous task into the folder you created in step 1. You should have one solution scope file (*.xml), many variant files (*.TXT) and one bitmap file (smb40_leaf.bmp).

3.6 Activation Sequence of ScenariosWhen activating the complete Baseline 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) 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.

© SAP AG of 75


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.

3.7 Specific Information on Scenarios

Cross-Company Scenarios: Cross Company Sales Order Processing and Internal Procurement: Cross-Company Stock Transfer

The cross company code scenarios Cross Company Sales Order Processing (123) and Internal Procurement: Cross-Company Stock Transfer (141) demonstrate intercompany logistics processes in sales and procurement, and are not fully integrated into Financial Accounting, Controlling, and CO-PA, and thus are optional.

Check if you require these scenarios. Even if you are not planning to use the functionality of these two scenarios, they can be activated without affecting any other functionality. However, if you do not want to activate these scenarios, you can deselect them as per Step 3: Scope the Solution section below in chapter Scoping and Activation of Scenarios.

SAP recommends to put these scenarios out-of-scope.

If these scenarios are planned to be used in final implementation projects, they must be adapted and integrated into the Financials and Controlling area as necessary for the specific implementation project.

Also check note 1276914 if you are going to activate these scenarios. Attached to this note you can find a guide which provides the how to adapt the keys for the second company code and related entities in case you want to set up all enterprise structure keys without any logical overlap of the keys.

3.8 Scoping and Activation of ScenariosYou can choose to activate the entire Baseline 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 Baseline 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 press Enter.

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

© SAP AG of 75


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

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.


Parameter Value

DOCUMENTATION http://help.sap.com/

11. Choose Save.

12. Choose Back.

Step 3: Scope the Solution

You have 2 options:

Option 1: If you want to activate the complete Baseline Package scope including the cross-company scenarios (see chapter Specific Information on Scenarios above), you can skip now to step 5 Personalize the Solution below.

Option 2: If you want to activate a subset of the complete Baseline Package scope, follow the steps in this section. Choosing this option, you can decide if you put the cross-company scenarios in scope or out-of-scope.

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

14. 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, then choose Scope.

Full Scope: Select 05 All Scenarios from the dropdown.

© SAP AG of 75


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

15. The system displays the Scoping for Solution screen. The screen displays all of the available scenarios that are part of the Baseline Package.

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

The Full Scope (05 All Scenarios) does not include the cross-company scenarios!

If you want to activate the cross company scenarios 123 and/or 141 as per the information in the Specific Information on Scenarios 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.

16. Choose the Save Data button.

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

18. Choose Back twice.

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

20. Maintain flag multiple activations for building block 142.

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 Baseline 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 4: Upload the Installation Data

The purpose of this step is to upload the installation data to the solution builder. This step is mandatory even if you do not want to personalize your solution.

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

© SAP AG of 75


On the Upload installation 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 5: Personalize the Solution (optional)

Check if you require personalized values – if you want to activate SAP Best Practices using default values, no action is required.

22. Ensure that the graphic files have been imported into the system. These graphics are attached to the 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).

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

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

Do NOT switch to expert mode and do NOT create any additional organizational data, for example an additional plant. This functionality is NOT supported in the SAP Best Practices Baseline Package and will cause serious errors.

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

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

27. Make any personalized entries on the detail screens.

28. If you want to personalize the printer, proceed as follows:

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

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

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

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

29. Optional: Use the SAP Best Practices documentation mapping list which helps you to run through the Business Process Documentations (BPDs) using the personalized values.

For a detailed description on how to proceed, see below chapter Step 8: Mapping List for Documentation (optional).

© SAP AG of 75


Step 6: Starting Activation

30. Ensure that your solution is set as a favorite solution.

31. From the menu, choose Goto Implementation Assistant (Ctrl + Shift + F3).

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

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

Field name User action and values

Comments

Target language

PT You can also use target language EN. As consequence selected language independent fields will be filled with English description texts instead of German texts.

Supplemental data

<location of folder with graphic file smb40_leaf.bmp >

e.g. Z:\sme\files

Use the folder that was created in step Creating a Folder for the SAP Best Practices Activation. In that folder the graphic file smb40_leaf.bmp is available.

You can also select another folder if you ensure that the graphic file smb40_leaf.bmp is available in that folder.

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.

Activation w/o demo data – What does this mean?

If you want to activate the Baseline package without demo data, you can deselect the checkbox to turn off activation of demo data.

© SAP AG of 75


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 file for this scenario to determine the required prerequisite building blocks.

Goto the Solution Builder Building Block Builder – Scenario Edit View.

For all Building Blocks that belong to the scenario have a look at the steps that have the check box activated in column De (Demo).

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

Errors occur during activation – Where can I find more information to solve the issue?

In case of any issues during activation always check chapter: Error Handling: Installation Errors during activation

34. Choose Continue.

Manual Step handling

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 to process the step. The table below lists these manual steps as they are part of the default full scope activation:

BBID Manual Step Description

100 (BR) Change Description of Units of Measurement

102 (BR)

Number Range for SPED Reporting Define Number Range for Electronic Accounting File History

Historical Description in Livro Diário

DEFINE AND ACTIVATE NON-LEADING LEDGERS

104 (BR)

MM Period Closing

Generating Condition Table

Delete condition type BXWT from step 901

105 (BR)

Activation of Tax Codes

Maintain Specific TAX Type ICMO

Delete repeated Conditions Type from YVABRA

Smart Forms for NFE

Maintain Number Ranges for NF-e

Defining Business Places

Defining Screen Control Groups

110 (BR) CREATE TABLE 501

© SAP AG of 75


BBID Manual Step Description

Assign G/L Accounts

CREATE TABLE 502

Assign G/L Accounts

119 (BR)Cash Account Determination - Assign G/L Accounts

Revenue Account Determination - Assign G/L Accounts

123 (BR)Enhance Material Master for New Plant

Maintain Number Ranges for NF-e

141 (BR) Enhance Material Master for New Plant

152 (BR)Migration: Tax groups in Access Sequence

Migration: Tax Tables to Conditions

161 (BR)Assign scenarios and customer fields to ledgers (Message)

Creating a Library with a Template

162 (BR) CIAP PROGRAM

165 (BR) Assign scenarios and customer fields to ledgers (Message)

166 (BR) CYCLE ADJUSTMENT

169 (BR)

MATERIAL LEDGER STARTUP

CHECK CUSTOMIZING FOR PLANT AFTER ML ACT

CONVERT ALL PROD.MAT.(ROH,HALB,FERT)

216 (BR)

Use of Text Modules for sender, letter header and footer texts

MATERIAL LEDGER STARTUP

CHECK CUSTOMIZING FOR PLANT AFTER ML ACT

CONVERT ALL PROD.MAT.(ROH,HALB,FERT)

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 7: Concluding Activities

After 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

© SAP AG of 75


scope. Then, in the information box Scenarios – by Business Areas select Integration Processes Other Prerequisite Process Steps.

Step 8: Mapping List for Documentation (optional)

If you have personalized the solution (see step 5) you can create a mapping lists which helps you to run through the Business Process Documentations (BPDs) using the personalized values.

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

This is a task that is usually carried out together with the business consultant who will take over the steps as described in chapter Evaluate Business Content / Scenarios – Business Consultant below.

Procedure1. From the menu choose menu Goto Personalization Export as CSV file2. Select a folder for exporting the list. The list will be exported to the selected folder as .csv

file.3. Open the file using e.g. Microsoft Excel and print it out for future reference.

For details on how to create the mapping list check the solution builder user guide.

The SAP Best Practices solution builder is updated continuously; for details check the release strategy of the solution builder as outlined in SAP Note 1301301. Depending on the solution builder version you have installed in your system, appropriate solution builder user guides are available. Check the SAP Note 1301301 to identify the relevant solution builder SAP Note for your solution builder version; the solution builder user guide is attached to the respective SAP note.

© SAP AG of 75


3.9 Error Handling: Installation Errors during activation

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.

3.9.1 Error Occurs During Activation of Automated Task

Use

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

Procedure

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

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

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

4. In this log information check entries with a red light to identify the reason for the error.

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, 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 -> Tools and Concepts.

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

© SAP AG of 75


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.

3.9.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 Menu Human Resources Personnel Management Administration HR Master Data Maintain

Transaction Code PA30

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

© SAP AG of 75


5. On the Delete Personnel Data screen press Select All, and then press Delete.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.10. If the eCATT runs with status green, no further activities are needed. If the eCATT still runs

with status red, start transaction SE38 and run report RPUDELPN. On the screen Delete Personnel Numbers enter the personnel numbers that are supposed to be created by the specific eCATT /xxxxxx/PA40_O001_xxx. Finally, start eCATT /xxxxxx/PA40_O001_xxx again.

3.9.3 Warnings in 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.

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

3.9.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 6: 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.

3.9.6 Window Appears During Activation 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 75


3.9.7 Window Appears During Activation Asking to Confirm that Text Was Changed

If such a window appears during the activation process with the solution builder, confirm the information dialog box with Yes.

3.9.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) or if you get the error message scripting engine not installed you need to update your SAP GUI to solve this issue. Do not continue with the activation unless you have updated your SAP GUI and have installed the latest scripting engine. If you continue serious errors will occur.

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

© SAP AG of 75


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.

3.9.10 Processing of Scenario Specific Errors

BB 104 (Materials Management): Error in eCATT /SMB99/CHARACTERISTIC_O209_J01; Some Variants Run RedIf 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.

BB 104 (Materials Management): Error in eCATT /SMB99/CL20N_PO_O001_J01; Some Variants Run RedIf 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.

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 0302If 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.

© SAP AG of 75


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 1000If 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 the SCCR developer key, see above the chapter User Settings for Activation, section SAP Software Change Registration (SSCR): Developer key.

After you got the SSCR developer key, set the Foreground checkbox in the SAP Solution Builder for the respective eCATT and start the activation again. When the eCATT runs in foreground, enter the developer key when prompted.

BB 152 (Central Master Data (for Foundation Manufacturing)): Error in eCATT /SMB99/MM01_ALL_VIEWS_O015_J01, Variants for Material L001 Run RedIf the eCATT /SMB99/MM01_ALL_VIEWS_O015_J01 Create Material Master - all Views shows the error S00344 No batch input data for screen SAPLMGMM 4000 for one or more variants for material L001, proceed as follows to correct the error:

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

IMG Menu Materials Management Valuation and Account Assignment - Account Determination - Account Determination Without Wizard - Define Valuation Classes

Transaction Code OMSK

7. On the Account Category Reference/Valuation Classes screen, choose Material type/account category reference.

8. On the Change View: Account Category Reference/Material Type: Overview, check if the following entry exists:

MTyp Material type descr. ARef Description

LEIH Returnable packaging 0004 Reference for packaging

9. If the value for ARef is not 0004 (for example 0007), change the value to 0004.

10. Choose Save.

11. Restart the activation of the scenario in the solution builder again. The error in the activity Create Material Master - all Views should not occur anymore.

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.

© SAP AG of 75


BB 168: (Profitability analysis): Error executing transaction KEA0 or KES1Only 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 SAP 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 SAP Note 942785.

BB 147 (Make-to-Order Production with Variant Configuration): Error eCATT /SMB15/MM02_O002_I78: Error: No batch input data for screen SAPMSSY0 0120If the eCATT /SMB15/MM02_O002_I78 Change Material - Classification view shows an error (the eCATT variants run on red status), restart the solution builder scenario again. The error should then not occur anymore.

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.

BB 161 (Cost of Sales Accounting): Error eCATT /SMB15/KS02_O010_N74 – Error in eCATT command TCD KS02If 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.


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

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.

© SAP AG of 75


4 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 Download and Installation of Easy Document Management describes the activities to be performed if Easy Document Management shall be used. These activities are necessary if the scenario Internal Product Development (210) and/or the scenario Make-to-Order Production w/o Variant Configuration (148) are in scope of the activated scenarios. Note that for the scenario Make-to-Order Production w/o Variant Configuration (148) the Easy Document Management is optional: it can also be run without having Easy Document Management installed.

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.

4.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 Baseline 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 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.

© SAP AG of 75


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.

4.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 8: 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.

4.3 User Maintenance and Settings

4.3.1 Activate SAP GUI Option Show Keys With Dropdown Lists

All system users have to adapt their local SAP GUI options in order to have the key information displayed in the SAP GUI dropdown lists. This has to be done to avoid ambiguities and errors when selections have to be done using the SAP F4-Help in SAP GUI.

Use

This section describes how system users can adapt their local SAP GUI settings to have the keys shown in SAP GUI.

Procedure

1. In the SAP GUI screen choose the button Customize Local Layout (Alt + F12).

2. Choose Options.

3. In the SAP GUI Options – CSR screen choose Interaction Design and then Visualization & Interaction in the left navigation pane.

© SAP AG of 75

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


4. In the screen area Controls on the right side, activate the checkboxes for the following two entries:

Show keys with dropdown lists, and

Sort by keys within dropdown lists for most efficient keyboard input.

5. Choose the button OK.

ResultThe system user has adapted the local SAP GUI option so that the key information is displayed in the SAP GUI dropdown lists.

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

Use

This section describes how you can assign roles for users.

Procedure

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

© SAP AG of 75


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

Information on which SAP Best Practices roles have to be assigned

Option A)

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. In addition to the roles specific to the scenario, always assign the role Employee (SAP_NBPR_EMPLOYEE_S). The assignment of this role is necessary for basic functionality.

Option B)

You assign all roles needed for the SAP Best Practices Baseline package (Brazil). In this case, assign the Collective role Baseline package Brazil (technical name: SAP_NBPR_BR_COLLECTIVE_ROLE).This role contains the single roles as listed in the roles overview table below in the column Technical role name (single roles).

The SAP Best Practices Baseline Package delivers composite roles which consist of one or several single roles. The single roles and composite roles can be differentiated by the different endings: Single roles always have a dash in front of the suffix (for example SAP_NBPR_TRAVEL-S1) whereas the composite roles contain an underscore in the respective place (for example SAP_NBPR_TRAVEL_S).

Always assign the composite role(s) to the system users. Composite roles can be understood as containers, which help to organize multiple single roles, and bring the different menus of the single roles in such a container into one streamlined menu.

When you assign composite roles to the users, you have the advantage that you can add a new role to an existing composite role, if you want to add additional activities. Of course, you can also add additional predefined single roles to the composite role.

The roles overview table lists all single and composite roles that are used in the SAP Best Practices Baseline package (Brazil):

Role name Technical role name (composite roles) Technical role name (single roles)Accounts Payable Manager

SAP_NBPR_AP_CLERK_M SAP_NBPR_AP_CLERK-M1SAP_NBPR_AP_CLERK-M2SAP_NBPR_AP_CLERK-M3SAP_NBPR_AP_CLERK-M4SAP_NBPR_AP_CLERK-M5SAP_NBPR_AP_CLERK-M6

Accounts Payable Accountant

SAP_NBPR_AP_CLERK_S SAP_NBPR_AP_CLERK-S1SAP_NBPR_AP_CLERK-S2SAP_NBPR_AP_CLERK-S3SAP_NBPR_AP_CLERK-S4SAP_NBPR_AP_CLERK-S5SAP_NBPR_AP_CLERK-S6SAP_NBPR_AP_CLERK-S7SAP_NBPR_AP_CLERK-S8

Accounts Receivable Manager

SAP_NBPR_AR_CLERK_M SAP_NBPR_AR_CLERK-M1SAP_NBPR_AR_CLERK-M2SAP_NBPR_AR_CLERK-M3SAP_NBPR_AR_CLERK-M4

Accounts Receivable SAP_NBPR_AR_CLERK_S SAP_NBPR_AR_CLERK-S1

© SAP AG of 75


Role name Technical role name (composite roles) Technical role name (single roles)Accountant SAP_NBPR_AR_CLERK-S2

SAP_NBPR_AR_CLERK-S3SAP_NBPR_AR_CLERK-S4SAP_NBPR_AR_CLERK-S5SAP_NBPR_AR_CLERK-S6

Accounts Receivable Account - FI Only

SAP_NBPR_AR_FI_ONLY_S SAP_NBPR_AR_FI_ONLY-S1SAP_NBPR_AR_FI_ONLY-S2

Asset Accountant SAP_NBPR_ASSET_S SAP_NBPR_ASSET-S1SAP_NBPR_ASSET-S2SAP_NBPR_ASSET-S3SAP_NBPR_ASSET-S4

Bank Accountant SAP_NBPR_BANKACC_S SAP_NBPR_BANKACC-S1SAP_NBPR_BANKACC-S2SAP_NBPR_BANKACC-S3SAP_NBPR_BANKACC-S4

Billing Administrator SAP_NBPR_BILLING_S SAP_NBPR_BILLING-S1SAP_NBPR_BILLING-S2

Enterprise Controller BR SAP_NBPR_BR_CONTROLLER_M SAP_NBPR_BR_CONTROLLER-M

Employee (Brazil Localization)

SAP_NBPR_BR_LOCBR_S SAP_NBPR_BR_LOCBR-S

Enterprise Controller SAP_NBPR_CONTROLLER_M SAP_NBPR_CONTROLLER-M1SAP_NBPR_CONTROLLER-M2SAP_NBPR_CONTROLLER-M3SAP_NBPR_CONTROLLER-M4

Customs Agent SAP_NBPR_CUSTOMSAGENT_S SAP_NBPR_CUSTOMSAGENT-S

Employee (Professional User)

SAP_NBPR_EMPLOYEE_S SAP_NBPR_EMPLOYEE-S1SAP_NBPR_EMPLOYEE-S2SAP_NBPR_EMPLOYEE-S3

Engineering Specialist SAP_NBPR_ENGINEER_S SAP_NBPR_ENGINEER-S1SAP_NBPR_ENGINEER-S2SAP_NBPR_ENGINEER-S3SAP_NBPR_ENGINEER-S4SAP_NBPR_ENGINEER-S5SAP_NBPR_ENGINEER-S6

Finance Manager SAP_NBPR_FINACC_M SAP_NBPR_FINACC-M1SAP_NBPR_FINACC-M2SAP_NBPR_FINACC-M3SAP_NBPR_FINACC-M4SAP_NBPR_FINACC-M5SAP_NBPR_FINACC-M6

General Ledger Accountant

SAP_NBPR_FINACC_S SAP_NBPR_FINACC-S1SAP_NBPR_FINACC-S2SAP_NBPR_FINACC-S3SAP_NBPR_FINACC-S4SAP_NBPR_FINACC-S5SAP_NBPR_FINACC-S6

IT Administrator (Professional User)

SAP_NBPR_IT_ADMIN_S SAP_NBPR_IT_ADMIN-S1SAP_NBPR_IT_ADMIN-S2SAP_NBPR_IT_ADMIN-S3SAP_NBPR_IT_ADMIN-S4SAP_NBPR_IT_ADMIN-S5SAP_NBPR_IT_ADMIN-S6SAP_NBPR_IT_ADMIN-S7SAP_NBPR_IT_ADMIN-S8SAP_NBPR_IT_ADMIN-S9 SAP_NBPR_IT_ADMIN-S10SAP_NBPR_IT_ADMIN-S11

Maintenance Employee SAP_NBPR_MAINTENANCE_S SAP_NBPR_MAINTENANCE-S1SAP_NBPR_MAINTENANCE-S2

Product Cost Controller SAP_NBPR_PRDCOST_CONTRLR_S SAP_NBPR_PRDCOST_CONTRLR-S

Production Supervisor SAP_NBPR_PRODPLANNER_M SAP_NBPR_PRODPLANNER-M1SAP_NBPR_PRODPLANNER-M2

Production Planner SAP_NBPR_PRODPLANNER_S SAP_NBPR_PRODPLANNER-S1

© SAP AG of 75


Role name Technical role name (composite roles) Technical role name (single roles)SAP_NBPR_PRODPLANNER-S2SAP_NBPR_PRODPLANNER-S3

Project Manager SAP_NBPR_PROJECTMANAGER_M SAP_NBPR_PROJECTMANAGER-M1SAP_NBPR_PROJECTMANAGER-M2SAP_NBPR_PROJECTMANAGER-M3

Purchasing Administrator

SAP_NBPR_PURCHASER_K SAP_NBPR_PURCHASER-K

Purchasing Manager SAP_NBPR_PURCHASER_M SAP_NBPR_PURCHASER-M1SAP_NBPR_PURCHASER-M2

Purchaser SAP_NBPR_PURCHASER_S SAP_NBPR_PURCHASER-S1SAP_NBPR_PURCHASER-S2

Quality Specialist SAP_NBPR_QUALMGR_S SAP_NBPR_QUALMGR-S

Sales Manager SAP_NBPR_SALESPERSON_M SAP_NBPR_SALESPERSON-M

Sales Administrator SAP_NBPR_SALESPERSON_S SAP_NBPR_SALESPERSON-S1SAP_NBPR_SALESPERSON-S2SAP_NBPR_SALESPERSON-S3SAP_NBPR_SALESPERSON-S4

Service Agent SAP_NBPR_SERVAGENT_S SAP_NBPR_SERVAGENT-S

Service Employee SAP_NBPR_SERVEMPLOYEE_S SAP_NBPR_SERVEMPLOYEE-S1SAP_NBPR_SERVEMPLOYEE-S2

Shop Floor Specialist SAP_NBPR_SHOPFLOOR_S SAP_NBPR_SHOPFLOOR-S1SAP_NBPR_SHOPFLOOR-S2

Strategic Planner SAP_NBPR_STRATPLANNER_S SAP_NBPR_STRATPLANNER-S

Travel Accountant SAP_NBPR_TRAVEL_S SAP_NBPR_TRAVEL-S1SAP_NBPR_TRAVEL-S2SAP_NBPR_TRAVEL-S3SAP_NBPR_TRAVEL-S4

Treasurer SAP_NBPR_TREASURER_S SAP_NBPR_TREASURER-S

Warehouse Clerk SAP_NBPR_WAREHOUSECLERK_S SAP_NBPR_WAREHOUSECLERK-S1SAP_NBPR_WAREHOUSECLERK-S2

Warehouse Manager SAP_NBPR_WAREHOUSEMANAGER_M SAP_NBPR_WAREHOUSEMANAGER-M1SAP_NBPR_WAREHOUSEMANAGER-M2SAP_NBPR_WAREHOUSEMANAGER-M3

Consulting Agency Client Manager

SAP_NBPR_CNSLT_CLNTMGR_S SAP_NBPR_CNSLT_CLNTMGR-S1SAP_NBPR_CNSLT_CLNTMGR-S2SAP_NBPR_CNSLT_CLNTMGR-S3

Consulting Agency Project Manager

SAP_NBPR_CNSLT_PROJMGR_S SAP_NBPR_CNSLT_PROJMGR-S1SAP_NBPR_CNSLT_PROJMGR-S2SAP_NBPR_CNSLT_PROJMGR-S3

Do NOT ASSIGN any other SAP Best Practices roles (SAP_NBPR* roles that are not listed in the table above). Since other roles are not designed to be used with the SAP Best Practices Baseline package (Brazil), the assignment of those roles will result in corrupted display of user menus in the SAP NetWeaver Business Client interface and wrong double entries.

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

© SAP AG of 75


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 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: Select SAP Netweaver in the left side menu bar, then select Search Documentation. In the search entry field enter the term Identity Management User and Role Administration of AS ABAP as search term and confirm your entry. Finally, in the search results select the link to User and Role Administration of AS ABAP.

The SAP Best Practices roles are not designed to be used as productive roles. Instead, these roles only serve the purpose to be used as demo roles that enable system users to make use of the SAP Netweaver Business Client interface to try out the predefined business processes delivered by the SAP Best Practices Baseline package.

For productive use, never use the roles delivered directly; instead, copy them and adjust them as necessary. In addition, an authorization concept has to be defined and implemented accordingly.

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.

4.3.3 Mandatory User Parameter

Procedure


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,

© SAP AG of 75

http://help.sap.com/


Parameter-ID

Parameter Value

Note

WExx, WFxx) you have to maintain the following parameter in the user settings.

Print via output control in MM - Inventory management

CAC

1000

Controlling areaIf you use PERSONALIZED values (for example controlling area 9999 instead of the default value 1000) enter your personalized value instead of the value 1000.

Make sure to use capital letters only.


4.3.4 Optional User Parameter

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

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.

Procedure


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

© SAP AG of 75



Note

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

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 X Upper and lower case in source code: 'X'

© SAP AG of 75



Note

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

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 enter the DEFAULT values as listed in the above table, but use your personalized values wherever applicable.


4.4 Creation and Change 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 or change queries. In such cases refer to the description as outlined below and provide system users with the relevant information, respectively.

4.4.1 Create Query

Use

You want to create a completely new query.

© SAP AG of 75


Procedure

To show the procedure how to define a new query we use the Production area.

1. Access the activity choosing the following navigation option:

SAP NetWeaver Business Client Menu

Production 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 PP operation worklist 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.



Comment

Enter Query Description Test Example of Query Description

Activate Query Select checkbox to activate the query.

10. Then choose pushbutton Finish.

© SAP AG of 75


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.

Result

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

4.4.2 Change Query

Use

You want to change an exisitng query.

Procedure

To show how to change an exisitng query we use the POWL List for Billing Documents.

1. Access the activity choosing the following navigation option:

SAP NetWeaver Business Client Menu

Accounts Receivable Billing

2. Select the POWL Billing Documents by choosing the tab strip Billing Documents.

3. Choose the link Change Query.

4. Enter or adjust selection criteria to your requirements.

5. Via pushbutton Preview you can get a test view of the list. This preview can be exported to a Microsoft Excel worksheet.

6. Next to the Preview button you find the link Criteria Personalization where you can select additional fields for the Quick Search.

7. Then choose Apply.

Result

The query has been changed to your requirements.

4.5 Download and Installation of Easy Document Management

The Installation of Easy Document Management has to be done for all local PCs from which system users want to run the scenario Internal Product Development (210) and/or the scenario Make-to-Order Production w/o Variant Configuration (148). Note that for the scenario Make-to-

© SAP AG of 75


Order Production w/o Variant Configuration (148) the Easy Document Management is optional: it can also be run without having Easy Document Management installed.

4.5.1 Download (Manual Step)

Use

In this activity, you download the front-end installation for Easy Document Management.

Prerequisites

You need Internet access and a user (e.g. S-user) to log on to the SAP service market place.

Procedure

Perform the following steps to download the Easy Document Management Interface (version 6.0).

1. Go to SAP service market place (http://www.service.sap.com).

2. Choose Software Download available under the SAP Support Portal Group.

3. On the left-hand menu, choose Support Packages and Patches, then choose Browse our Download Catalog.

4. On the right-hand frame, navigate to Supplementary Components for Cross Industry Solutions Life-Cycle Data Management SAP EASY DOCUMENT MANAGEMENT SAP EASY DOCUMENT MGMT 7.1.

5. You now find the link to download the installation files under EASY DOCUMENT MGMT 7.1 Win32. You should choose the newest version of SAP Easy Document Management 7.1. The installation was tested with patch level 1 (EasyDMS71SP00P_1-20006126.zip).

4.5.2 Installation (Manual Step)

Use

In this activity, you install the Easy Document Management on your local PC.

Prerequisites

Administrator rights in MS Windows are advisable but not necessary.

A prior installation of SAP Logon (WinGUI) is advisable. The list of available systems in EasyDM is taken from the SAP-Logon-installation. If no SAP Logon is installed, the system needs to be added manually to the list of systems in EasyDM.

System requirements are with regard to the local PC on which SAP Easy Document Management is installed:

Requirement Type Requirement

Hardware requirements Free disk space: 20 MB in the standard program folder, for example C:\Program Files

RAM: 128MB

Screen resolution: at least 1024x768 pixels

© SAP AG of 75

http://www.service.sap.com/


Requirement Type Requirement

Software requirements Microsoft Windows 2000 with SP 3 or higher

or

Microsoft Windows XP with SP1 or higher

and

Microsoft Internet Explorer 5.0 or higher

Microsoft Office is supported as of version 2000, but this is not a prerequisite for installation

Procedure

1. Unzip the zip file in any folder and then run the SetupAll.exe by double-clicking it. Now the EasyDM Interface is installed on your system. For more information about the installation of SAP Easy Document Management 7.1, see SAP Service Marketplace at http://service.sap.com/instguides SAP Business Suite Applications SAP PLM SAP Easy Document Management 7.1 Master, Implementation, and Operation Guide for SAP Easy Document Management 7.1

2. Click OK to finish the installation.

3. Start SAP Easy Document Management using one of the following options:

Windows Desktop Right-click the new icon SAP Easy Document Management on your desktop and choose Logon.

4. Log on to the SAP system in which you want to work. You need the following information:

System name

Client

User

Password

Language

You need to enter the language, e.g. EN for English.

5. Upon first start the system displays the following message: No public root folder found. Do you want to create one? (If this message does not appear, continue with step 9.)

6. Choose Yes.

7. On the next screen, change the following entry:

Field name Description User action and values Comment

Document Type <Choose Folder (FOL) from the dropdown list>

Leave the rest unchanged

8. Choose OK.

9. The system displays the message No private root folder found. Do you want to create one? If this message does not appear, continue with step 11.

10. Repeat the instructions from step 6, 7 and 8 above.

© SAP AG of 75


11. A Windows Explorer window shows the following three entries:

Private Root Folder

Public Root Folder

Search Result

Result

You have successfully installed and started SAP Easy Document Management.

4.5.3 Trouble ShootingFor trouble shooting and further information, refer to the following SAP Notes:

SAP Note 1440749: Release Information Note

SAP Note 1467697: Restriction Note

SAP Note 1465763: FAQ Note

SAP Note 1439220: SAP Easy Document Management 7.1 with WTS

In general, search for notes within the application area CA-DMS-EUI.

4.6 Errors during Usage of Activated Package

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

If you want to perform the step Period End Processing the following error appears:

Field use for mandatory field OCURR is not maintained correctly (T811I). Message no. GA404

Diagnosis

During checks of the allocation field use, it was determined that obligatory field OCURR is not available.

System Response

Assessment/distribution does not function properly.

Error Solution Procedure

1) Access the transaction SPRO.

2) Choose Financial Accounting (New) -> General Ledger Accounting (New) -> Periodic Processing -> Allocation -> Check Settings for Allocation.

3) On the Check Customizing Settings for the Allocation screen enter faglflext in the field table and select Assessment in the area Allocation type and actual in the area Record type.

4) Choose Execute.

© SAP AG of 75


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

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.

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

Use

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

Procedure


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 75


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


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

4.6.5 Scenario Reporting with SAP Business Explorer (132): Error Invalid File Format

Problem Description

When you want to use the SAP Business Explorer Reporting, you might encounter an error stating that the file format is invalid. This error is caused by a missing file assignment of the SAP Business Explorer file format.


To fix this problem, perform the two steps as described below:

Step 1: Make sure you have the SAP Business Explorer Analyzer installed on your system by launching file BExAnalyzer.exe which is located in the following folder:C:\Program Files\SAP\Business Explorer\BI\

Step 2a (valid for Windows XP): Assign the SAP Business Explorer extension to the BExAnalizer.exe program by executing the following steps:

1. Open the Windows Explorer.2. Choose Tools, then Folder Options.3. In the Folder Options window choose the File Types tab.4. From the list select the BEX extension then choose the Advanced button.5. In the Actions section of the Edit File Type window select Open then choose Edit.6. In the Editing action for type: SAP BEx Shortcut window enter the following values:

Action: openApplication used to perform action: C:\Program Files\SAP\Business Explorer\BI\BExAnalyzer.exeUse DDE: SelectedDDE Message: <Empty>Application: BEx AnalyzerDDE Application Not Running: <Empty>Topic: System

7. Choose OK.8. Choose OK.9. Choose Close.

© SAP AG of 75


Step 2b (valid for Windows Vista): Assign the SAP Business Explorer extension to the BExAnalizer.exe program by executing the following steps:

1. Open via Start the Control Panel.2. Change to Classic View.3. Select Default Programs.4. Select Associate a file type or protocol with a program.5. Select the .bex item from the list and choose Change program….6. Choose Browse….7. Double click the SAP folder.8. Double click the Business Explorer folder.9. Double click the BI folder.10.Double click BExAnalyzer.exe.11.From the list of recommended programs select SAP BExAnalyzer application and choose

OK. 12.Choose Close.13.Choose Close.

Step 2c (valid for Windows 7): Assign the SAP Business Explorer extension to the BExAnalizer.exe program by executing the following steps:

1. Open via Start the Control Panel.2. Choose Programs.3. In the section Default Programs choose Make a filetype always open in a specific

program.4. On the Associate a file type or protocol with a specific program screen select the file

extension .bex.5. Choose Change program….6. Choose Browse….7. Navigate to the file BExAnalyzer.exe (default path: C:\Program Files (x86)\SAP\

Business Explorer\BI)8. Double click BExAnalyzer.exe.9. From the list of recommended programs select SAP BExAnalyzer application and

choose OK. 10. Choose Close.11. Choose Close.

4.6.6 Scenario SAP ERP Reports for Accounting (221): Selection Screen in wrong language

Problem Description

When you execute reports in the Controlling area (e.g. Reports for Cost Center Accounting S_ALR_87013613, S_ALR_87013612) you might encounter the problem that the selection screen uses a language different from your logon language (e.g. logon language is EN, selections screen is in DE).


To fix this problem, the report groups have to be generated in logon language. Perform the steps as described below:


Transaction Code GR55

SAP Menu Accounting Controlling Cost Center Accounting

© SAP AG of 75


Information System Tools Report Writer Report Group Execute

2. On the Execute Report Group: Initial Screen choose Utilities Mass Generator.

3. Make the following entry on the Report Writer: Generate Report Groups screen:

Field Name User Action and Values

Report Group *

4. Choose Execute (F8).5. Select the required report groups (e.g. select all) on the Report Writer: Generate Report

Groups screen.6. Choose Generate (F7).

4.6.7 Scenario General Cost Center Planning (175) and Overhead Cost Accounting - Actual (184): Only use overhead rates with application 'KA'

Problem Description

You execute transaction KSA3 (Actual Accrual Calculation for Cost Centers) or KSA8 (Plan Accrual Calculation for Cost Centers). You enter the required selection data and choose Execute (F8). The error message Only use overhead rates with application 'KA' (message no. KA466) is displayed. This message only appears if there are postings on the referenced accounts.


Confirm the message and choose Execute (F8) again.

4.6.8 Scenario General Ledger (156): Transaction FB50: Field ‘Assignment no.’ is too large

Problem Description

When you start the ENJOY transaction FB50 the field ‘Assignment no,’ can be too large (more than 18 digits). In this case you can use a workaround to correct the length of this field so that the field is shown with 18 digits. This error can be caused by a delivery defect.


To fix this problem, perform the steps as described below:

Be sure you have the authority rights of administrator functions (authorization object S_ADMI_FCD).


Transaction Code FB50

SAP Menu Accounting Financial Accounting General Ledger Posting Enter G/L Account Document

© SAP AG of 75


2. On the Enter G/L Account Document: Company Code 1000 screen choose Configuration.

You can find the respective button in the header line of the line item list (in the middle of the screen, on the right).

Do not enter any data in the screen.

3. On the pop-up Table Settings choose Administrator. Now you can see the current settings of the single columns.

4. On the Edit System Settings screen set all previous fields of field Asssignment No. to invisible:

Column Fld Name Invisible

Status ACGL_ITEM-STATE select

G/L acct ACGL_ITEM-HKONT select

Short Text ACGL_ITEM-KONTO_TXT select

D/C ACGL_ITEM-SHKZG select

Amount in doc.curr. ACGL_ITEM-WRBTR select

Loc.curr.amount ACGL_ITEM-DMBTR select

Tax code ACGL_ITEM-MWSKZ select

Tax jurisdictn code ACGL_ITEM-TXJCD select

W/o Cash Dscnt ACGL_ITEM-XSKRL select

…. (further fields, if available) …. select

Asssignment No. ACGL_ITEM-ZUONR Do not select

5. Select Activate.

6. Select close (twice) and go back to Enter G/L Account Document: Company Code 1000 screen. Scroll left until field assignment no. is displayed.

7. Decrease field length with the left mouse button by changing the separator line of the column (similar to Excel function). Decrease it to the minimum length of 18 digits.

8. Choose Configuration again.

9. Choose Administrator again.

10. Deselect all invisible settings.

11. Chose Activate.

12. Select close (twice) and leave the transaction.

Result

A system variant is created. All users in the current client will see this variant of the table control.

© SAP AG of 75


4.6.9 Scenario Internal Product Development (210): Logon to SAP Easy Document Management System is not Possible

Problem Description

You want to start SAP Easy Document Management System but it is not possible to logon.


To fix this problem, perform the steps as described in SAP Note 1409494.

Result

The problem is fixed and you can logon.

4.7 Errors with SAP NetWeaver Business Client (SAP NWBC)

4.7.1 Queries Show No Data / No Columns

Problem Description

A query shows no data.


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

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

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.

© SAP AG of 75


4.7.3 Scenario 137: Physical Inventory – POWL for Physical Inventory Documents: Buttons Do Not Work Correctly

Problem Description

The buttons in the POWL for Physical Inventory Documents do not work correctly. If you choose a button, you will not get to the correct screen, but a window will appear that refers to a non-related area. For example, you choose Display PI (Physical Inventory) and then the window WIP status report opens.

Error Reason

The error is caused by OBNs not working correctly.

Solution Procedure

This issue does not occur anymore if you have applied the latest SAP Netweaver Patch as outlined in SAP Note 1353538 (see above chapter SAP Notes and messages).

4.7.4 Scenario 132: Reporting with SAP Business Explorer: Characteristic 0TCAACTVT does not exist. Check authorizations

Problem Description

If you try to export the content of a POWL to the BEx Analyzer the error message “Characteristic 0TCAACTVT does not exist. Check authorizations” is shown.

Error Reason

Currently unknown.

Solution Procedure

To activate info object 0TCAACTVT carry out the following steps:


Transaction Code RSD1

2. On the screen Edit InfoObjects:Start Screen make the following entries in the blank field next to InfoObject:

Info Object Blank field

Radio button selected 0TCAACTVT

3. Select the Business Content button.

4. Further select Copy InfoObjects.

5. Further select Subsequently Activate.

© SAP AG of 75


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

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

Password is defined by your System Admin.

Authorization is defined by your System Admin.

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

You can check the user using transaction SU01.

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

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

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 75

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

BL Quick Guide en BRok

Documents

Transcript of BL Quick Guide en BRok