100_bb_configguide_en_br

8/6/2019 100_BB_ConfigGuide_EN_BR

http://slidepdf.com/reader/full/100bbconfigguideenbr 1/14

EHP4 for SAP ERP 6.0

March 2010

English

SAP Best Practices

Installation (100)

SAP AGDietmar-Hopp-Allee 1669190 Walldorf Germany

Building Block Configuration Guide



SAP Best Practices SAP Best Practices Installation (100): Configuration Guide

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 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 software componentsof 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, SystemStorage, 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 IBMCorporation.

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 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 technology inventedand 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, WebIntelligence, 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. Datacontained 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 14




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 theENTER 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 these

words and characters with appropriate entries.

© SAP AG of 14




Content

1 Preparation ..................................................................................................................................5

1.1 Prerequisites ...................................................................................................................... ..5

1.1.1 Checking Logon Language .............................................................................................5

1.1.2 Checking Currency .........................................................................................................5

1.1.3 Confirmation of Euro Currency Customizing ...................................................................5

1.1.4 Checking Holiday and Factory Calendar .........................................................................6

2 User Settings ....................................................................................................................... ........7

2.1 Enabling SAP-Scripting ....................................................................................................... ..7

2.2 Setting Decimal Notation and Date Format...........................................................................7

3 Client Maintenance ......................................................................................................................8

3.1 Client Settings .......................................................................................................................83.1.1 Creating Logical System .................................................................................................8

3.1.2 Maintaining Client Settings ................................................................................ .............8

3.2 Maintaining Forms of Address ...............................................................................................9

3.3 Specify Structure for Tax Jurisdiction Code .........................................................................10

3.4 Define Tax Jurisdiction Codes .............................................................................................11

3.5 Assign Postal Codes to Tax Jurisdiction Codes ..................................................................11

3.6 Consolidated Changes in CUNI...........................................................................................12

3.7 Change Description of Units of Measurement.....................................................................12

3.8 Upload Graphic File .............................................................................................................13

© SAP AG of 14




SAP Best Practices Installation

1 Preparation

Before the installation of the building block, some preparatory activities must be performed. Someof these activities can only be performed manually, while others are automated. All of theseactivities are described on the following pages.

1.1 PrerequisitesBefore you start installing this building block, you must install prerequisite building blocks. For more information, see the Building Block Prerequisite Matrix for Baseline. The matrix (an Excelfile) is linked on the solution's DVD/website in one of the following two locations:

• Content Library

• Site Map

1.1.1 Checking Logon Language

The logon language must be EN.

1.1.2 Checking Currency

1. Carry out the following steps:

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

IMG Menu SAP Netweaver → General Settings → Currencies → Check Currency Codes

Menu IMG SAP NetWeaver Configurações gerais Moedas

Verificar códigos de moeda

Transaction Code SM30

3. Enter V_CURC in the Table/View field, and choose Display .

4. On the Change View “Currencies”: Overview screen, check the currency entries for completeness. The currency table must have entries for all currencies that occur in your business transactions.

1.1.3 Confirmation of Euro Currency Customizing



Transaction Code EWCF

3. Check the Euro Currency Customizing.

© SAP AG of 14




1.1.4 Checking Holiday and Factory Calendar

Use

The validity of the holiday and factory calendars need to be checked and extended if necessary.The some of the standard settings are valid until year 2010 only and need to extended. Several

business functions are using the calendar information.

The validity of the Holiday Calendar and the holidays have to be checked accordingto the legal requirements of the related country.

Procedure



IMG-Menu SAP Netweaver → General Settings → Currencies→MaintainCalendar

Transaction Code SCAL

2. Select the Holiday calendar and click on Change .

3. On the Change Public Holiday Calendar: Overview screen, select the Holiday Calendar entryspecific for your country and region.

4. Click on Change .

5. On the Change Public Holiday Calendar: Details screen, check and change the Valid to fieldto a future year (like +3 years).

6. Check the validity range of every public holiday assigned to the holiday calendar. Extend thevalidity if necessary.

7. Click on Save to save the entries. Confirm the message regarding transporting of holidayand fabric calendar settings.

8. Click on Back to the SAP Calendar: Main Menu screen.

9. Select the Factory calendar and click on Change .

10. On the Change Factory Calendar: Overview screen, select the Factory Calendar entryspecific for your country and region.

11. Click on Change .

12. On the Change Factory Calendar: Details screen, check and change the Valid to field to afuture year (like +3 years).

13. Click on Save to save the entries and leave the IMG activity.

Result

The validity of both Holiday and Factory Calendar, and the public holidays have been checkedand extended to a future year.

© SAP AG of 14




2 User Settings

2.1 Enabling SAP-Scripting

Use

To allow eCATT processing, the profile parameter sapgui/user_scripting has to be set. The valuefor Enable or disable user scripting on the front-end must be set to true.

Procedure



Transaction Code RZ11

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

Field Name Description User Action and Values Comment

PARANAME Profile parameter name sapgui/user_scripting

Display

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

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

Field Name Description User Action andValues

Comment

New Value TRUE Enable SAP Scripting

Save change

2.2 Setting Decimal Notation and Date Format

Use

Perform this activity to set up the installation user ID.

Procedure

1. Carry out the following steps:2. Access the activity using one of the following navigation options:

SAP ECC Menu System User Profile → Own Data

Transaction Code SU3

3. Choose the Defaults tab.

4. Make sure that Decimal Notation is set up according to your country’s default, like, for example, 1.234.567,89.

© SAP AG of 14




5. Make sure that the Date Format is set up according to your country’s default, like, for example, DD.MM.YYYY.

6. Make sure that you assign your printer in the field output device. The recommended entryfor the installation is LP01.

7. Save your settings.

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

3 Client Maintenance

3.1 Client Settings

Use

You need to make certain client settings to ensure that the environment for the implementationhas been set up correctly.

3.1.1 Creating Logical System

Use

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

Procedure



Transaction Code SM30, table V_TBDLS

3. On the Change View “Logical Systems2 screen make the following entry:

Log.System Name

<Log. System>, like XYZCLNT999 <your logical System description>

4. Save the settings.

3.1.2 Maintaining Client Settings

Use

You need to maintain the client settings to ensure that the implementation activities to implementyour solution are supported.

© SAP AG of 14




Procedure



Transaction Code SCC4 Client Overview

3. On the Display View: “Clients”: Overview screen, switch to the change mode.

4. Select your current client, and choose Details.

5. Maintain the following settings:

Field name Description User action andvalues

Comment

ORT01 City <Your Location>

LOGSYS Logical System Select the logicalsystem of the currentclient

Defined before

MWAER Std Currency Select the currency of

your country

Like BRL, USD, etc.

CCCATEGORY Client Role Customizing

CCCOR_ACTV AutomaticRecording of Changes

select

CCNOCLIIND Cross-ClientObject Changes

Changes to Cross-Client Customizing andRepository Objectsallowed

6. Save your settings.

3.2 Maintaining Forms of Address

Use

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

Procedure



SAP Menu Tools →Customizing →IMG→Execute Project

Menu SAP Ferramentas Customizing IMG Processamento de projeto

Transaction Code SPRO

IMG Menu Cross Application Components → SAP Business Partner →

Business Partner → Basic Settings → Forms of Address →Maintain Forms of Address

© SAP AG of 14




Menu IMG Componentes válidos para várias aplicações Parceiro de

negócios SAP Parceiro de negócios Configurações

globais Formas de tratamento Atualizar formas detratamento

3. Check whether an entry Company exists. If the entry already exists, you can skip this

activity, otherwise proceed with step 3.4. On the Change View “Titles (Business Address Services)”: Overview screen, choose

New Entries.

5. On the New Entries: Overview of Added Entries screen make the following entries:


Comment

TITLE Key <key>

TITLE_MEDI Title Company

ORGANIZATN Organization Select

Save

3.3 Specify Structure for Tax Jurisdiction Code

Use

The Tax Jurisdiction Code Structure must be defined according to the Brazilian layout.

Procedure



IMG Menu Financial Accounting (New) → Financial Accounting Global Settings (New → Tax on Sales/Purchases →Basic Settings

→Specify Structure for Tax Jurisdiction Code

Menu IMG Contabilidade financeira (nv.) Configurações globais

contabilidade financeira (novo) IVA Configurações

globais Determinar estrutura p/código de domicílio fiscal


3. On the Change View “Jurisdiction Code Structure”: Overview screen, enter the followinginformation:


Comment

Schema TAXBRA

Name

Lg 3

Lg 3

Tx Ln X

4. Save your entry.

© SAP AG of 14




5. Choose Back .

3.4 Define Tax Jurisdiction Codes

Use

The Tax Jurisdiction Coded must be maintained according to the Brazilian layout.

Procedure



IMG Menu Financial Accounting (New) → Financial Accounting Global

Settings (New → Tax on Sales/Purchases →Basic Settings

→Brazil →Define Tax Jurisdiction Codes



globais Brasil Atualizar códigos de domicílio fiscal


3. On the Determine Work Area: Entry screen, enter Country Key BR and choose Continue.

4. On the Change View “Tax Jurisdiction Codes for Brazilian Tax Calculation”: Overview screen, choose New Entries.

5. Enter the Jurisdiction Codes according to the documentSMB41_J_1BTXJURV_B020_NFE.TXT.

6. Save your entries.

7. Choose Back.

3.5 Assign Postal Codes to Tax Jurisdiction Codes

Use

The Tax jurisdiction codes must be assigned to the Postal Codes Ranges.

Procedure



IMG Menu Financial Accounting (New) → Financial Accounting Global

Settings (New → Tax on Sales/Purchases →Basic Settings→ Specify Structure for Tax Jurisdiction Code→ AssignPostal Codes to Tax Jurisdiction Codes



globais Brasil Atribuir códigos postais aos códigos dedomicílio fiscal


© SAP AG of 14




3. On the Determine Work Area: Entry screen, enter Country Key BR and choose Continue.

4. On the Change View “Assign Tax Jurisdiction Codes to Ranges of Postal Codes”:Overview screen, choose New Entries.

5. Make the entries according to the documentSMB41_J_1BTREG_CITYV_B019_NFE.TXT.

6. Save your entries.

7. Choose Back.

3.6 Consolidated Changes in CUNI

Use

You need to maintain certain units of measurement.

Procedure



SAP Menu Tools →Customizing →IMG→Execute Project

Menu SAP Ferramentas Customizing IMG Processamento de projeto


IMG Menu SAP NetWeaver → General Settings → Check Units of Measurement

Menu IMG SAP NetWeaver Configurações gerais Moedas Verificar códigos de moeda

3. Check the settings, especially missing conversions between language-dependent units of

measure, like, for example, PC ST. Make sure that the units of measurements are inthe language of the country.

3.7 Change Description of Units of Measurement

Use

This activity will change the descriptions of units of measurement

Procedure


IMG Menu SAP NetWeaver -> General Settings -> Check Units of Measurement

Menu IMG SAP NetWeaver ->Configurações gerais ->Verificar unidades de medida

Transaction Code CUNI

© SAP AG of 14




2. On the Units of Measurement: Initial Screen, choose AAAADL (No dimensions) andselect Units of Measurement.

3. Select the Unit of Measurement ST and maintain the following settings:

Unit of Measurement in Commercial Format: PEC

Unit of Measurement in Technical Format: PEC

Unit of Measurement Text: Piece

4. Select Unit of Measurement PC and maintain the following settings:

Unit of Measurement in Commercial Format: PC

Unit of Measurement in Technical Format: PC

Unit of Measurement Text: Items

5. Choose Save.

For the next steps, it is necessary to logon on your Target Language (PT).6. On the 1ª tela unidades de medida screen, choose AAAADL (Sem dimensão) and select

Unidades de Medida.

7. Select the Unidade de Medida ST and maintain the following settings:

Unidade de Medida Comercial: PEC

Unidade de Medida Apresentação Técnica: PEC

Texto Unidade de Medida: Peça

8. Select Unidade de Medida PC and maintain the following settings:

Unidade de Medida Comercial: PC

Unidade de Medida Apresentação Técnica: PCTexto Unidade de Medida: Items

9. Choose Save.

3.8 Upload Graphic File

Use

To personalize the print forms, your own company logo as bitmap can be loaded into the system.

Procedure1. Carry out the following steps:


SAP ECC Menu Tools →Form Printout →Administration→Graphic

Transaction Code SE78

3. Run the transaction.

© SAP AG of 14




4. On the Administration of Form Graphics screen, expand the structure Form Graphics andselect the BMAP Bitmap Images element.

5. Select the radio button Black and White Bitmap Image or Color Bitmap Image dependingon the format of the bitmap file of your company logo.

6. Choose the menu Graphic Import (F5) and enter the following values:


Comment

FILENAME File name Select the file andfolder of the bitmap file

TDNAME Name Company

PROP_VALUE Description /SMBA0/AA_LEAF Use this name to get thelogo updated in all forms

Save

7. Choose Enter to import the graphic file.

ResultYour company logo has been imported into the system and is available as /SMBA0/AA_LEAFobject. The print forms are now displaying the logo of your company.

© SAP AG of 14

100_bb_configguide_en_br

Documents