B32_BB_ConfigGuide_EN_HR

8/6/2019 B32_BB_ConfigGuide_EN_HR

http://slidepdf.com/reader/full/b32bbconfigguideenhr 1/9

SAP ECC 6.00

July 2007

English

B32 SAP Best Practices

Installation

SAP AGDietmar-Hopp-Allee 1669190 Walldorf Germany

Building Block Configuration Guide



SAP Best Practices B32 Best Practices Installation: Configuration Guide

Copyright

© Copyright 2006 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without theexpress 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 softwarecomponents of other software vendors.

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

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390,OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli,and Informix are trademarks or registered trademarks of IBM Corporation.

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 trademarksor registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide WebConsortium, 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 technologyinvented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and servicesmentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AGin Germany and in several other countries all over the world. All other product and service namesmentioned are the trademarks of their respective companies. Data contained in this document servesinformational purposes only. National product specifications may vary.

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

© SAP AG Page 2 of 9




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 fieldnames, screen titles, pushbuttons as well as menu names, paths andoptions.

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 keywords 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 asnames 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 thesystem exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace thesewords and characters with appropriate entries.





Contents

B32 SAP Best Practices Installation .........................................................................................5

1 Configuration Guide ............................................................................................................5.1.1 Preparation .................................................................................................................5

1.1.1 Prerequisites ........................................................................................................5

.1.1.1.1 Check Logon Language ..............................................................................5

.1.1.1.2 Check Currency ..........................................................................................5

.1.1.1.3 Confirmation of Euro Currency Customizing ...............................................5

.1.2 User Settings ..............................................................................................................5

1.2.1 Enable SAP-Scripting ............................................................................................6

1.2.2 Set Decimal Notation and Date Format................................................................. 6

.1.3 Client Maintenance .....................................................................................................7

1.3.1 Client Settings .......................................................................................................7

.1.3.1.1 Create Logical System ................................................................................7

.1.3.1.2 Maintain Client Settings ..............................................................................7

1.3.2 Copy Standard Texts into Current Client............................................................... 8

1.3.3 Maintain Forms of Address ....................................................................................9





B32 SAP Best Practices Installation

1 Configuration Guide

.1.1 PreparationBefore starting the installation of the building block, some preparation activities must beperformed. Some of these activities can only be performed manually, while others areautomated in the installation role. All of these activities are described on the following pages.

1.1.1 Prerequisites

Before starting the installation, complete the following activities:

• Read the documentation building block Essential Information, which you need for a BestPractices for mySAP All-in-One installation.

•

Install all required notes

.1.1.1.1 Check Logon Language

Logon language has to be EN

.1.1.1.2 Check Currency

1. Run the following activity:

Transaction Code SM30 table V_CURC

IMG-Menu SAP Netweaver General SettingsCurrenciesCheck CurrencyCodes

2. On the screen <Change View “Currencies” :Overview> check the currency entries for completeness. The currency table must have entries for all currencies which occur in your business transactions.

.1.1.1.3 Confirmation of Euro Currency Customizing


Transaction Code EWCF

IMG-Menu

2. Check Euro Currency Customizing

.1.2 User Settings





1.2.1 Enable SAP-Scripting

Use

In order to allow eCATT processing, the profile parameter “sapgui/user_scripting” has to beset. The value for “Enable or disable user scripting on the front-end” has to be set true.

Procedure


SAP R/3Role Menu

Preparation Maintain Profile Parameters – SAP Scripting

Transaction Code RZ11

2. On the screen <Maintain Profile Parameters> make the following entries

Field name Description R/O/C User action and values Note

PARANAME Profile parameter

name

sapgui/user_scripting

Display

3. On the screen <Display Profile Parameters Attributes> select Change values.

4. On the screen <Change Parameter Value> make the following entries.

Field name Description R/O/C User action andvalues

Note

New Value TRUE Enable SAPScripting

Save change

1.2.2 Set Decimal Notation and Date Format

Use

Perform this activity to set up the installation user ID.

Procedure


SAP R/3Role Menu

Installation User Settings Set Decimal Notation - DateFormat – Printer

Transaction Code SU3

2. Choose the tab strip Defaults.

3. Make sure Decimal Notation is set up according to your country’s default, like1.234.567,89.

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

5. Make sure to assign your printer in the field output device. Recommended entry for installation is LOCL.

6. Save your settings.





7. When the complete installation procedure is finished, you may change these values asdesired.

Result

The decimal notation and date format have been set up according to your country specific

format. The standard printer has been defined.

.1.3 Client Maintenance

1.3.1 Client Settings

Use

Some clients settings have to be done to ensure that the environment for the implementationhas been set up correctly.

.1.3.1.1 Create Logical System

Use

The logical system identifies you the client within a system..

Procedure

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

Transaction Code SM30, table V_TBDLS

IMG Menu

2. On the screen <Change View “Logical Systems2> make the following entry:

Log.System Name

<Log. System>, likeXYZCLNT999

<your logical System description>

3. Save the settings.

.1.3.1.2 Maintain Client Settings

Use

You need to maintain the client settings to ensure that the implementation activities toimplement your solution will be supported.

Procedure


Transaction Code SCC4 Client Overview

IMG Menu

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

3. Select your current client and choose Details.

4. Maintain the following settings:






Note

ORT01 City R <Your Location>

LOGSYS Logical System R Select the logicalsystem of the current

client

Definedbefore

MWAER Std Currency R Select the currency of your country

Like EUR,USD, GBPetc.

CCCATEGORY Clinet Role R Customizing

CCCOR_ACTV AutomaticRecording of Changes

R select

CCNOCLIIND Cross-ClientObject Changes

R Changes to Cross-Client Customizing and

Repository Objectsallowed

5. Save your settings.

1.3.2 Copy Standard Texts into Current Client

Use

The texts (in namespace /SMB15/) imported in client 000 are copied to the developmentclient. With copying the texts into the development client they can used in the developmentenvironment.

This activity is relevant for Baseline Package Croatia in case automatedinstallation only.

Procedure


SAP R/3Role Menu

Installation Maintenance Client Copy Standard Texts intoCurrent Client

Transaction Code SO10

IMG Menu

2. On the screen <Standard Text: Request> make the following entries:


Note

Select Utilities in menu

Select Copy from client

3. On the screen <Copy Texts Between Clients> make the following entries:


Note

QUELNAME Text Name /SMB15/*






Note

TEXTID Text ID *

TDSPRAS Language *

QUELMAND Source Client 000

Mark action log

Execute

Result

After processing this step the texts are available in your client.

1.3.3 Maintain Forms of Address

UseThe address company is added for further selection in maintaining address data of companies.

Procedure


SAP R/3Role Menu

Installation Client Maintenance Maintain Forms of Address

Transaction Code SPRO

IMG Menu Cross Application Components SAP Business Partner

Business Partner Basic Settings Forms of AddressMaintain Forms of Address

2. On the screen <Change View “Titles (Business Address Services)”: Overview> select“New Entries”.

3. On the screen <New Entries: Overview of Added Entries> make the following entries:


Note

TITLE Key BP01

TITLE_MEDI Title Company

ORGANIZATN Organization SelectSave


Documents

B32_BB_ConfigGuide_EN_HR