bl quick guide en th

SAP ECC 6.00

August 2007

English

Quick Guide to Installing the SAP Best Practices Baseline Package (TH)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

SAP Best Practices Quick Guide to Installing the SAP Best Practices Baseline Package (TH)

Copyright

© Copyright 2007 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, Outlook, Excel, and PowerPoint are registered trademarks of Microsoft Corporation.

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

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

Oracle is a registered trademark of Oracle Corporation.

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

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

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

Java is a registered trademark of Sun Microsystems, Inc.

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

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves information 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.and services, if any. Nothing herein should be construed as constituting an additional warranty.

© SAP AG of 32


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 32


ContentsQuick Guide to Installing the SAP Best Practices Baseline Package (TH)...............................6

1 Purpose............................................................................................................................ 6

2 Technical Prerequisites for Installation.............................................................................6

2.1 Best Practices Add-On and Transport.........................................................................6

2.2 System Status of Client Roles......................................................................................6

2.3 Releasing and Supporting Package Level...................................................................6

2.3.1 SAP ECC components.........................................................................................6

2.3.2 SAP Java Components........................................................................................7

2.4 SAP Extension Sets.....................................................................................................8

2.5 SAP Notes and Messages...........................................................................................8

2.6 Activating Virtual Host and Services............................................................................9

2.7 Generating RV13xxxx Reports.....................................................................................9

2.8 Deactivating CRMAPO.................................................................................................9

2.9 Printer Settings............................................................................................................9

2.10 Creating Installation Folder for the SAP Best Practices Installation Files (*.txt files)..10

2.11 User Settings for Installation......................................................................................10

2.11.1 Maintaining Profile Parameters - SAP Scripting.................................................10

2.11.2 Allowing GUI Scripting.......................................................................................11

2.11.3 Setting Decimal Notation and Date Format........................................................12

2.11.4 User Settings for Installing Scenarios that Use Variant Configuration...............12

2.11.5 User Settings for Uploading Encoding...............................................................13

2.12 Installation and Usage of the SAP Best Practices Installation Assistant....................13

2.12.1 Technical Installation.........................................................................................13

2.12.2 Running the Installation Assistant......................................................................13

2.12.3 Interface.............................................................................................................13

2.12.4 SAP Best Practices Installation Assistant User Guide.......................................13

2.12.5 SAP Best Practices Installation Assistant Attachment.......................................14

3 Installation....................................................................................................................... 14

3.1 Installing Baseline for Thailand..................................................................................14

3.2 Installation Sequence.................................................................................................15

3.3 Error Handling............................................................................................................17

3.3.1 Processing General Errors during Installation....................................................18

3.3.2 Processing of Specific Errors.............................................................................19

3.4 Installation of SAP NetWeaver Business Client (NWBC) Roles.................................27

3.4.1 Prerequisites for NWBC Roles Installation.........................................................27

3.4.2 Installation Procedure........................................................................................27

3.4.3 NWBC Supported Scenarios..............................................................................27

© SAP AG of 32


3.5 Fully Qualified Domain Names (FQDN).....................................................................28

3.6 Internet Communication Framework (ICF).................................................................28

3.7 Scripting Settings.......................................................................................................28

3.8 NWBC Configuration..................................................................................................28

4 Usage............................................................................................................................. 29

4.1 SAP GUI User Roles for Service Scenarios...............................................................29

4.1.1 Importing User Roles.........................................................................................29

4.1.2 Assigning a Role to Other Users........................................................................30

Appendix................................................................................................................................. 31

© SAP AG of 32


Quick Guide to Installing the SAP Best Practices Baseline Package (TH)

1 PurposeThis quick guide provides the information you need to install the complete SAP Best Practices Baseline Package for TH (hereinafter known simply as Baseline Package) using the SAP Best Practices Installation Assistant. It also explains how to proceed if you want to install individual scenarios instead.

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

2 Technical Prerequisites for Installation

2.1 Best Practices Add-On and TransportThe Best Practices Addon and special transport with additional objects have to be imported into the system. For more details, see the document Importing Best Practices Add-Ons (ADDONINS.PDF) on the configuration CD.

2.2 System Status of Client RolesThe system must not comprise any client that is set to status productive client role. If the system contained a productive client, extension sets can not be activated as required and the automatic installation of SAP Best Practices content using the SAP Best Practices Installation Assistant is not possible due to the impossibility to activate BC sets in the system. You can use the transaction SCC4 to check the client roles in your system.

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

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

If you need a higher support package level in your system, for example because of additional functionality, FIRST install Best Practices on the system SP levels as mentioned above, AND THEN upgrade your system to the latest support package level.

The basic support package levels relevant for SAP Best Practices Baseline Package (TH) are as follows:

© SAP AG of 32


2.3.1 SAP ECC componentsSoftware Component

Release Level Support Package Description

SAP_BASIS 700 0011 SAPKB70007 SAP Basis Component

SAP_ABA 700 0011 SAPKA70007 Cross-Application Component

PI_BASIS 2005_1_700 0011 SAPKIPYJ77 PI_BASIS 2005_1_700

ST-PI 2005_1_700 0003 SAPKITLQI1 SAP Solution Tools Plug-In

SAP_BW 700 0012 SAPKW70007 SAP NetWeaver BI 7.0

SAP_AP 700 0008 SAPKNA7004 SAP Application Platform

SAP_HR 600 0013 SAPKE60004 Human Resources

SAP_APPL 600 0008 SAPKH60004 Logistics and Accounting

EA-IPPE 400 0008 SAPKGPID04 SAP iPPE

EA-APPL 600 0008 SAPKGPAD04 SAP R/3 Enterprise Add-On PLM, SCM, Financials

EA-FINSERV 600 0008 SAPKGPFD04 SAP R/3 Enterprise Financial Services

EA-GLTRADE 600 0008 SAPKGPGD04 SAP R/3 Enterprise Global Trade

EA-HR 600 0013 SAPKGPHD04 SAP R/3 Enterprise Add-On HR

EA-PS 600 0008 SAPKGPPD04 SAP R/3 Enterprise Public Services

FINBASIS 600 0008 SAPK-60004INFINBASIS

Fin. Basis

BI_CONT 702 0005 SAPKIBIHP4 Business Intelligence Content

BP-ERP05 * * * SAP Best Practices All-in-One based on ERP 2005 (ECC 600)

BP-INSTASS * * * Best Practices Installation Assistant based on SAP_BASIS 700

* The release of the software components BP-ERP05 and BP-INSTASS depend on the SAP Best Practices configuration CD you use for your installation. The appropriate release information is listed in the document Importing Best Practices Add-Ons (ADDONINS.PDF) on the configuration CD.

For more details of the support packages in question, see the document Importing Best Practices Add-Ons (ADDONINS.PDF) on the configuration CD.

© SAP AG of 32


2.3.2 SAP Java Components

2.3.2.1 Adobe Document ServicesIn addition to the components mentioned above, Adobe Document Services (ADS) have to be installed and configured. The following prerequisites must be fulfilled:

An instance of Adobe document services deployed and configured on the SAP J2EE Engine. You find information on installing and configuring the ADS on the SAP Service Marketplace at http://service.sap.com/adobe -> Media Library -> Documentation.

A local installation of Adobe LiveCycle Designer. Adobe LiveCycle Designer is shipped with SAP NetWeaver on a separate CD.

A local installation of Adobe Reader 7.0 or higher. You can download Reader for free from the Adobe website at http://www.adobe.com/products/acrobat/readstep2.html.

You need to have the PSE certificates between J2EE and ABAP in your system installed and the configuration settings set to no logon required.

2.4 SAP Extension SetsThe following SAP ECC extension sets need to be activated before you start installation:

EA-FIN Financials Extension

EA-FS Financial Services

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

Use the transaction SFW5 to activate the extensions.

2.5 SAP Notes and Messages

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

SAP Note # Description Area Component

438160 Thailand: Payee address for petty cash(RFIDYYWT & RFUMSV00)

Usage XX-CSC-TH-AC

323742 PRRW post with business place Usage FI-TV-COS

962459 Node incorrectly displays in Scope View on tree

Installation SV-SMB-AIO-BP

964525 CAT2: Short dump during navigation to 'Travel Expenses'

Usage CA-TS

1008717 HTML Viewer: Post data of length more than 255 gets truncated

Usage BC-FES-CTL

923867 BAdI HRSYNC_P causes dump Installation PA-ER

1025049 Numerous transport requests in task Installation CRM-WFD-RTL

© SAP AG of 32

http://www.adobe.com/products/acrobat/readstep2.html


SAP Note # Description Area Component

configuration

64490 Syntax error in L0KEAT00 Installation CO-PA-MD

1050082 Incorrect split w/ partially maintained constant definition

Installation FI-GL-FL

It may be that 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 building block installation process, check the latest version of the SAP Note below to obtain updates and corrections for problems that do not become apparent until after shipment.

SAP Note # Description Component

1057558 SAP Best Practices Baseline Package TH V1.600SV-SMB-AIO-BP-TH

2.6 Activating Virtual Host and ServicesActivate the virtual host and services using the transaction SICF. For details refer to SAP note 517484.

2.7 Generating RV13xxxx Reports1. Call transaction SE38.

2. Enter RV12A001 in the field Program.

3. Choose Execute (F8) .

4. In the screen Condition tables: Subsequent generation - online, leave every field blank except the fields Reports and Screens and Online; mark the checkbox for these two fields.

5. Choose Execute (F8) .

The report starts to generate the reports RV13xxxx. It might take up to two hours until every report is generated.

2.8 Deactivating CRMAPO 1. Call transaction BF11.

2. Deactivating the checkbox for the application CRMAPO CRM-APO Adapter.

3. Save.

4. Enter a workbench request in the dialog box.

5. Leave the transaction with Back.

© SAP AG of 32


Deactivating the application CRMAPO CRM-APO Adapter prevents to get dumps when saving a sales order with configurable items (scenario J66).

2.9 Printer SettingsFor installation of SAP Best Practices, the standard default printer LP01 is used that is generated during the SAP standard system set up.

For actual printing (generating output) after you have finalized the SAP Best Practices installation, this printer LP01 can NOT be used (for details, see SAP note 573309). Instead, an existing printer at your side has to be selected for generating output.

Your printer needs to 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.

In case of a personalized installation: During the personalization step 1, Preparation Installation Parameters Printer and Development Class, a default printer has to be maintained. The default printer LP01 can only be replaced by a printer already existing in your system. If no printer exists, the value LP01 has to be kept to avoid errors during the following installation.

2.10 Creating Installation Folder for the SAP Best Practices Installation Files (*.txt files)

1. Create a folder on a server that can be accessed from within the SAP system where you want to install the SAP Best Practices Baseline Package. Ensure that the persons who will install SAP Best Practices have the necessary user rights to access this folder.

2. Copy all the files (*.txt.files) that are needed for the SAP Best Practices installation into the folder you created in step 1.

How to get the files

The installation files can be found as attachment to the SAP Best Practices Baseline Package support note (for details on the note number see above section SAP Notes and Messages).

Installation using the SAP Best Practices Personalization Assistant

If you want to use the SAP Best Practices Personalization Assistant for installation, follow the guided installation procedure as outlined in the respective section Installation on the documentation DVD.

© SAP AG of 32


2.11 User Settings for Installation

2.11.1 Maintaining Profile Parameters - SAP Scripting

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

Only those installation users have to perform this activity that do not install the building block B32 (for example, someone else installed Layer 0 including BB B32 and you want to install the BB J60).

Procedure1. Run the following activity:

SAP system menu Preparation Maintain Profile Parameters – SAP Scripting

Transaction code RZ11

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

Field name Description 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.


New Value TRUE Enable SAP Scripting

Save change

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.11.2 Allowing GUI Scripting

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

© SAP AG of 32


Only those installation users have to perform this activity that does not install the building block B32 (for example, someone else installed Layer 0 including BB B32 and you want to install the BB J61).

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

Layout or type ALT + F12.

2. Select the menu item Options.

3. Choose the tab Scripting.

4. Select the checkbox enable scripting.

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

6. Choose the OK button at the bottom.

2.11.3 Setting Decimal Notation and Date Format

UsePerform this activity to set up the installation user ID.

Only those installation users have to perform this activity that does not install the building block B32 (for example, someone else installed Layer 0 including BB B32 and you want to install the BB J61).


SAP ECC menu Installation User Settings Set Decimal Notation - Date Format – Printer

Transaction code SU3

2. Choose the tab Defaults.

3. Make sure you set Decimal Notation according to your country’s default, like 1,234,567.89.

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

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

6. Save your settings.

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

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

© SAP AG of 32


2.11.4 User Settings for Installing Scenarios that Use Variant Configuration

UseBefore you can install those business scenarios that use variant configuration, you need to assign a specific parameter to your user profile.

ParametersCheck the user data in transaction SU3. Ensure that you set the following parameters in your user master record:

Parameter Value

CUQ 001

Make sure that your logon language is English.

2.11.5 User Settings for Uploading Encoding

UseIn order to upload the correct Thai language, you need to make the following settings.

Procedure1. Check the properties of the system from SAPGUI by right click on the system id.

2. Choose Properties from the context menu.

3. Choose Code Page.

4. Change the Encoding to Thai (Windows).

5. Choose OK.

2.12 Installation and Usage of the SAP Best Practices Installation Assistant

2.12.1 Technical InstallationSAP delivers the SAP Best Practices Installation Assistant program as a separate add-on (BP-INSTASS) on the SAP Best Practices solution configuration CD. Your system administrator will handle installation of the SAP Best Practices Installation Assistant.

2.12.2 Running the Installation Assistant

UseThis activity runs the SAP Best Practices Installation Assistant.

ProcedureAccess the activity using the following option:

Transaction code /n/SMB/BBI

© SAP AG of 32


2.12.3 InterfaceThe Best Practices Installation Assistant consists of two main screens:

Building Block Installer

Building Block Builder

The Building Block Installer screen is the first screen you see when you run the transaction; this is the relevant screen for the installation of the SAP Best Practices Baseline Package.

The Building Block Builder screen is where you create or building blocks for use in the projects in the Building Block Installer screen.

2.12.4 SAP Best Practices Installation Assistant User GuideThis document describes all the functionalities of the SAP Best Practices Installation Assistant. It explains how to import the SAP Best Practices Baseline Package scope and activate building blocks. The user guide can be found on the documentation DVD in the area Installation.

Do NOT delete Installation Assistant projects ONCE they have been activated. If you delete projects, 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.

2.12.5 SAP Best Practices Installation Assistant Attachment

UseThere are some MS office documents attached to the SAP Best Practices Installation Assistant. Before you can read these MS office documents, you need to maintain menu path parameter.


Transaction code /n/SMB/BBI

2. Choose menu Goto Parameter Maint.

3. On the Define Parameter screen, choose Display <-> Change button, and make the following entries:


Parameter - %FOLDER%

Value C:\Documents and Settings\BLP_TH

Input your file folder in which you keep the MS Office documents

4. Choose Continue.

© SAP AG of 32


3 Installation Before installation, you must upload Baseline Package scope file into system

Installation of each Building Block has to carried out with certain sequence

You can decide whether you want to install the complete package or only certain scenarios.

You can find detail instructions outlined below.

3.1 Installing Baseline for ThailandStep 1:

Upload the Baseline package scope file as follows: Start the Installation Assistant with transaction code /n/SMB/BBI and go to the scope editor (menu Goto Scope Editor). Then, import the scope file Baseline_TH_scope.bps.

The Baseline package scope file (*.bps file) can be found on the documentation DVD in the directory: \Misc\Baseline_Package\ Thailand \BPIA .

Step 2:

Leave the Scope editor using the Back (F3).

Step 3:

On the Best Practices Installation Assistant – Project View screen, you now see all projects delivered with the Baseline package.

To start the project installation, choose the selected project, and then choose (Shift +F4) to activate it and monitor the process.

The BPIA user guide can be found on the documentation DVD in the area Installation.

3.2 Installation Sequence

You must install project Baseline TH Layer 0 as the first step.

You can decide scenario(s) to be installed from table Project Layer 1 Scenario below. Or you can choose project for BASELINE_TH_LAYER1, activate it, and then activate project COMPLETE_INSTALLATION_TH. Then you will install the complete Baseline Package TH.

Building Block J15 is a special building block, in which we put all the translation related activities there. It includes all the translations for FI and CO. It is recommended to install J15 at the end of Layer 1 building blocks. You can also install J15 without the installation of CO building block, but you may get error during the installation. This is because you have not install related CO objects. In such cases, please ignore the error.

Project: BASELINE TH LAYER 0Project ID Building

Block IDName

© SAP AG of 32


BASELINE TH LAYER 0 B32 Best Practices Installation

J02 Organizational Structure

N69 External Financial Accounting Basics

N70 External Financial Accounting Local

N71 Central Cost Center Accounting

J05 Materials Management

J04 Sales and Distribution

J30 Central Master Data

Projects Layer 1 Project ID Building

Block IDName Prerequisite BBs

(L0 = all Layer 0 BBs)

BASELINE TH J06 J06 Production Planning and Control L0

BASELINE TH J18 J18 Product Cost Planning L0

BASELINE TH J19 J19 Batch Management L0

BASELINE TH J07 J07 Quality Management L0 + J06

BASELINE TH J17 J17 Profitability Analysis L0 + J18

BASELINE TH J20 J20 Cost Object Controlling – Make-to-Order SP L0 + J18 + J17

BASELINE TH J21 J21 Cost Object Controlling – Make-to-Stock L0 + J18 + J17

BASELINE TH J22 J22 Cost Object Controlling – Repetitive L0 + J18 + J17

BASELINE TH J14 J14 Human Resources L0 + J18 + J17 + J20

BASELINE TH J09 J09 Travel Management L0 + J18 + J17 + J20 + J14

BASELINE TH J24 J24 SD/MM Services L0 + J18 + J17 + J20 + J14 + J09

BASELINE TH J13 J13 Customer Service/Plant Maintenance L0 + J18 + J17 + J20 + J14 + J09 + J24

BASELINE TH J12 J12 Project System L0 + J18 + J17 + J20 + J14 + J09 + J24

BASELINE TH J15 J15 Accounting: Text Translation L0 + J18 + J17 + J20 + J14 + J09 + J24 + J12

Projects Layer 1 ScenarioProject ID Building

Block IDName Prerequisite BBs

(L0 = all Layer 0 BBs)

BASELINE TH B46 B46 Cash Management L0

BASELINE TH N72 N72 Asset Management L0

BASELINE TH N73 N73 Period End Closing for Fin. Accounting L0, J15

BASELINE TH N74 N74 Cost of Sales Accounting L0

BASELINE TH D41 D41 On-Site Repair Services L0, J18, J17, J20, J14, J09, J24, J13,

© SAP AG of 32


BASELINE TH D42 D42 Returns and Repairs at Plant L0, J18, J17, J20, J14, J24, J13,

BASELINE TH D43 D43 Preventive Maintenance L0, J18, J17, J20, J14, J09, J24, J13, J12,J15

BASELINE TH D44 D44 Internal Maintenance L0, J18, J17, J20, J14, J09, J24, J13, J12

BASELINE TH J45 J45 Spot Consulting L0, J18, J17, J20, J14, J09, J24

BASELINE TH J46 J46 Project w. Fixed Price & Time/Mat. Billing L0, J18, J17, J20, J14, J09, J24, J13, J12

BASELINE TH J47 J47 Contract With Autocreation of Project, Down payment

L0, J18, J17, J20, J14, J09, J24, J13, J12

BASELINE TH J49 J49 Procurement of Stock Material L0, J06, J07, J19

BASELINE TH J50 J50 Procurement – Contract L0, J19

BASELINE TH J51 J51 Internal Procurement (Stock Transfer w. Del.) L0, J18, J17, J06, J19, J07

BASELINE TH J52 J52 Internal Procurement (Stock Transf. w/o Del.) L0, J18, J17, J06, J19, J07

BASELINE TH J53 J53 Internal Procurement (X-Comp. Stock Transf.) L0, J18, J17, J06, J19, J07

BASELINE TH J56 J56 Bought-In Item L0

BASELINE TH J57 J57 Extended Sales Order Processing L0, J06, J18, J19, J17

BASELINE TH J58 J58 Customer Consignment Processing L0, J19

BASELINE TH J59 J59 Returns and Complaints L0, J19, J06, J07, J18, J17

BASELINE TH J60 J60 Returnable Processing L0, J19

BASELINE TH J61 J61 Batch Recall L0, J19, J06, J07, J18, J17, J59

BASELINE TH J63 J63 Sales Order Processing w. Dummy Customer L0, J19

BASELINE TH J64 J64 PP and Discrete Manuf.– Make-to-Stock L0, J06, J18, J19, J17, J21

BASELINE TH J65 J65 PP and Process Manuf.– Make-to-Stock L0, J06, J18, J19, J07, J17, J21,

BASELINE TH J66 J66 Make-to-Order Quotation Processing/Order Processing

L0, J19, J06

BASELINE TH J67 J67 Repetitive Manufacturing L0, J19, J06, J18, J17, J22

BASELINE TH J73 J73 Phys. Inventory w. Balance Sheet Valuation L0

BASELINE TH J75 J75 Third party Procurement and subcontract without sales

L0, J06, J07, J18, J17

BASELINE TH J79 J79 Long term Service Order w. Settlement L0, J06, J18, J20, J21, J17

© SAP AG of 32


Use the SAP Best Practices Installation Assistant user guide that can be found on the documentation DVD to learn how to create and work with personalized scopes.

Specific files for installation of J65

During the installation of the scenarios J65 – PP and Process Manufacturing – Make-to-Stock you are asked for the files Valuate _Characteristics_MR10000_XX.txt (for example PPPI_Characteristics_MR10000_EN.txt for English language file) and Valuate PPPI_Characteristics_MR30000_XX.txt. These files are located on the Baseline Package documentation DVD in the folder Misc\Baseline_Package\Thailand .

3.3 Error HandlingThe following information helps you to solve problems that might occur during the installation process.

3.3.1 Processing General Errors during Installation

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

Procedure1. On the Building Block Installer 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.

5. In case the error can be solved based on the log information choose run the eCATT or BC set 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 Concept.

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

© SAP AG of 32


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


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


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

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

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

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

12. Choose Activate to continue with the installation of the Building Block.

3.3.2 Processing of Specific Errors

3.3.2.1 BBs N70/ J05/ J04/ N73: Error message for Ecatt /SMB99/SE38_O001_J05.

The Ecatt which is to copy SAPSCRIPT FORM from Client 000 is supposed to be activated successfully in the empty system. But for the second time in the same system, user is required to remove this object with FORM from change request. It’s an easy way for user to run this Ecatt in foreground again if he encounters with some errors whether for first time or second time.

1. In the screen ‘Best Practices Installation Assistant – Project view’, Mark ‘X’ in the field ‘FG’ of the step.

2. After activating the project and going to the Ecatt screen, choose tab view of ‘UI Control’, change N to A in the sub-screen ‘TCD’ and execute.

3. After completing the Ecatt in foreground then choose Back to switch to the project view, choose SET OK to continue for the installation.

© SAP AG of 32


3.3.2.2 BB J17 (Profitability analysis): Error executing transaction KES1

Only in the case if you get an error executing transaction KES1 (J17 installation step Maintain Characteristic Values), install the SAP notes 64490 and 942785. Then as final step, after you executed report RKEAGENV as described in both notes above, reactivate the operating concern (transaction KEA0, Tab Environment, cross-client and client-specific part).

3.3.2.3 BB J13: Error message for eCATT /SMB15/IP11_T005_J13 SAPMSSY0, Actual Program: SAPLSDH4. Expected Screen Number: 120, Actual Screen Number: 200

If you get the error Screen Check Error: Expected Transaction: IP11, Actual Transaction: IP11. Expected Program: SAPMSSY0, Actual Program: SAPLSDH4. Expected Screen Number: 120, Actual Screen Number: 200. There Is Probably an Error in Previous SAPGUI Command or Processed Screen proceed as follows:

1. Choose transaction SE38.

2. Enter the report RSCPINST in the field program.

3. Choose Execute (F8).

4. In the area Enter languages add choose the button Add and then enter the value TH.

5. Choose the button Activate.

3.3.2.4 BB J19: Error message for eCATT /SMB15/BMSM_O001_J19 No Batch input data for screen

If you get the error No Batch input data for screen proceed as follows:

1. In the Installation Assistant mark the foreground checkbox (in the column FG of the Installation Assistant project view) of this specific eCATT.

2. Activate the project again.

3. Run the eCATT in foreground.

3.3.2.5 BB J64: Error message for eCATT /SMB15/V_T399DT438M_U_O415_J64

If you get an error you will have to perform this installation activity in the following way:

Exit the SAP Best Practices Installation Assistant and enter it again. Then activate the project again. It the error still occurs, activate the project a third time.




© SAP AG of 32





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

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

Example for this error:

3.3.2.10 BB J05: Error message for eCATT /SMB15/SFP_O002_J05 Error in eCATT command TCD SFP; No batch input data for screen SAPLSHTTP 0100

If the eCATT /SMB15/SFP_O002_J05 runs on status red (error) and lists the error Error in eCATT command TCD SFP; No batch input data for screen SAPLSHTTP 0100, you might have the wrong settings in your J2EE-ABAP connection. To solve this error, you need to have the PSE certificates between J2EE and ABAP in your system installed and the configuration settings set to no logon required.

3.3.2.11 BB J14: Error Message for eCATT /xxxxxx/PA40_O001_J14 Field PSPAR-PERSK. is not an input field

If eCATT /xxxxxx/PA40_O001_J14 is run more than one time, you get the error message Field PSPAR-PERSK. is not an input field, because employee numbers have already been created during the first run.

To solve this issue, delete existing and not completely installed personnel numbers manually using the following steps:

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

SAP ECC menu Human Resources Personnel Management Administration HR Master Data Maintain

Transaction Code PA30

© SAP AG of 32


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 1750. Personnel data is shown in the right-hand half of the screen.

4. Select Utilities Delete Personnel Data from the menu bar.

5. On the Delete Personnel Data screen press Select All, and then press Delete.

6. Confirm the dialog box Delete Personnel Data.

7. Enter or confirm Customizing Request.

8. Repeat steps 3 to 7 for all existing personnel numbers.

9. Start eCATT /xxxxxx/PA40_O001_J14 again.

3.3.2.12 BB J14: Error message for eCATT /SMB15/PA30_O006_J14 (Assign Qualifications to Personnel) Error in eCATT function SAPGUI

If you get the error Error in eCATT function SAPGUI you will have to perform this installation activity (assign qualifications to personnel) manually.

You assign the qualifications to personnel using the following procedure.

Procedure

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

SAP ECC menu Human Resources Personnel Management Personnel Development Profile Change

Transaction code PPPM

2 Select an employee to assign qualifications as specified in the master document of building block J14 in the sheet qualifications.

ResultThe qualifications have been assigned to employees.

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

If such a window appears during the installation process with the Installation Assistant, choose OK.

© SAP AG of 32


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

If such a window appears during the installation process with the Installation Assistant, confirm the information dialog box with Yes (example: BB J14).

3.3.2.15 The installation stops showing the Generate features screen

If the installation stops showing the Generate features screen (example BB J14, BB J09, see screenshot below), continue the installation by choosing Back twice.

© SAP AG of 32


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

3.3.2.17 Status of activation of Installation Assistant project is still red although all installation steps are on status green

If the last activity of your project is a manual activity and after you have successfully performed this manual activity, you can set the status of this manual activity on green. Setting this manual activity on green will not set the status of the complete project on green. Note that you have to activate the project again, to set the overall project status on green.

Example: BB J06: After you have set the last step Define parallel processing in MRP on green, activate the project Baseline TH J06 again to set the overall status on green.

© SAP AG of 32


3.3.2.18 Activities not flagged as mandatory show status red

Some projects contain one or more activities that are not flagged as mandatory. If these activities show the status red after activation, you have to activate the project again, to set these activities and the overall project status on green.

Example: BB J56: After the first activation of this project, the first activity Bought-In Tem 1. activation shows the status red. Activate the project Baseline TH J56 again to set this activity and the overall status on green.

If the activities not flagged as mandatory still show status red after second activation, see above section 3.4.1 and 3.4.2.

3.3.2.19 All scenarios in which classification views are generated

If you have already performed this activity within one of the other scenarios you do not need to perform it again. You might get the following error message: No Batch Input Data for screen…. Or you might get the following dialog box during installation:

Ensure that the classification view has been created successfully before and then set the status of this installation activity on green.

3.3.2.20 Runtime Errors (MESSAGE_TYPE_X) when Creating Models for Easy Cost Planning (BBs J46 and D48)

If you get a runtime error when creating the models for easy cost planning, retry the model creation by using a shorter path to the files <directory path on your local system>ECP_Model_CONS.xml / ECP_Model_STUDY.xml. For example, put the files directly on your root directory: <C:\>ECP_Model_CONS.xml / ECP_Model_STUDY.xml.

The files ECP_Model_STUDY.xml and ECP_Model_CONS.xml are located on the Baseline Package documentation DVD in the folder ..\Misc\Baseline_Package\Thailand.

© SAP AG of 32


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

This error might occur in building block D41, 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.

3.3.2.22 Building Block N71: Activation of eCATT /SMB15/KP26_O023_N71 and/or eCATT /SMB15/KP26_O025_N71

If the eCATT /SMB15/KP26_O023_N71 and/or eCATT /SMB15/KP26_O025_N71 runs on red, use TA SE11 to regenerate the tables ACCIT_SUB and ACCIT_SUB_T.

3.3.2.23 Building Block N72: Activation of eCATT /SMB15/AS91_O030_N72

During the installation of the scenario Asset Management (building block N72) the eCATT /SMB15/AS91_O030_N72 might run into an error. If this is the case, proceed as follows to solve the error:

1) Start transaction secatt.

2) In the field test configuration, enter the value /SMB15/AJRW_O104_N72.

3) Choose Execute (F8).

4) On the next screen Start option – Test Configuration /SMB15/AJRW_O104_N72, choose Execute (F8).

5) After successful activation of the eCATT go back to the Installation Assistant and activate the project BASELINE TH N72 (Asset Management) again.

3.3.2.24 Building Block N73 Post Goods Issue: Error Message GLT2 201 'Balancing field &1 in line item, &2 not filled'

During the goods issue posting, if you got an error message GLT2 201 ‘Balancing field & 1 in line item, &2 not filled’. Try to implement note 1050082.

© SAP AG of 32


3.3.2.25 Manual Steps in Installation ProcessIn the SAP Best Practices Installation Assistant, 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 Installation Assistant projects in the system. However, if a description should be missing in the Installation Assistant you can refer to the description in the configuration guide of the respective building block.

3.3.2.26 BB J14: Error message for eCATT /SMB35/PA40_O001_J14 No Batch input data for screen

If you get the error No Batch input data for screen SAPLSTRD 0300 proceed as follows:

1) In the Installation Assistant mark the foreground checkbox (in the column FG of the Installation Assistant project view) of this specific eCATT.

2) Activate the project again.

3) Run the eCATT in foreground.

3.3.2.27 BB J19: Error message for eCATT /SMB15/OMCZ_O001_J19 No Batch input data for screen SAPLSTRD 0300

If you get the error No Batch input data for screen SAPLSTRD 0300 proceed as follows:1) In the Installation Assistant mark the foreground checkbox (in the column FG of the Installation Assistant project view) of this specific eCATT.2) Activate the project again.

3) Run the eCATT in foreground

3.3.2.28 Message SV173 - Function group C002 inconsistent

If such a message appears, it's necessary to do following steps:

1) Call transaction SE54 and enter the table name 'C002'.

2) Press 'Edit Function Group' button and enter 089C as a function

group on subsequent screen.

3) Choose 'Regenerate Group-Specific Programs' and press 'Change'

4) Choose 'Structure spec. data declarations renewal' in the next selection window.

5) Choose Continue.

© SAP AG of 32


3.4 Installation of SAP NetWeaver Business Client (NWBC) Roles

3.4.1 Prerequisites for NWBC Roles InstallationThe business processes delivered with the SAP Best Practices Baseline Package support both the SAP Graphical User Interface (SAPGUI) and the NetWeaver Business Client (NWBC). In order to support the NWBC, various prerequisites have to be fulfilled. For details, check the notes mentioned in the following table:

SAP Note #

Description Details Component

1044426 Enablement Kit for SAP All-in-One

Information on the SAP All-In-One 1.2 Add-on and the NWBC

SV-SMB-AIO-AET-DOC

1059080 SAP Best Practices Role Files for All-In-One

Information on how to install and use the SAP Best Practices roles for the NWBC

SV-SMB-AIO-AET-DOC

3.4.2 Installation ProcedureFollow the installation procedure as outlined below:

1) Install the SAP Best Practices Baseline Package as described above in chapter Installation Sequence of Building Blocks, Installation of Scenarios and Error Handling. Ensure that the installation prerequisites according to chapter Technical Prerequisites for Installation are fulfilled (for example. release and support package levels).

2) Import the SAP All-in-One Add-On and the NWBC according to the note listed in the chapter Prerequisites for NWBC Roles Installation above.

3) Install the SAP Best Practices roles for the NWBC according to the note listed in the chapter Prerequisites for NWBC Roles Installation above.

As a result, the SAP Best Practices roles for the NWBC are ready to be used in several SAP Best Practices scenarios. For an overview of the business scenarios that support the NWBC see the next chapter NWBC Supported Scenarios.

3.4.3 NWBC Supported ScenariosSAP Best Practices Pre-Defined Roles designed to be used in the NetWeaver Business Client (NWBC) are provided for the following SAP Best Practices Baseline Package scenarios:

ACCOUNTING SCENARIOS: External Financial Accounting, Central Cost Center Accounting, Travel Management, Asset Management, Cash Management, Profitability Analysis, Period End Closing (Financial Accounting), Cost of Sales Accounting, Cash Management

MATERIALS MANAGEMENT & PROCUREMENT SCENARIOS: Physical Inventory, Procurement of Stock Material, Procurement with Contract, Internal Procurement: Stock Transfer with Delivery, Internal Procurement: Stock Transfer w/o Delivery, Internal Procurement: Cross-Company Stock Transfer

SERVICE SCENARIO: On-Site Repair Services, Returns and Repairs at Plant, Preventive Maintenance, Internal Maintenance, Spot Consulting, Project w. Fixed Price & Time/Mat. Billing, Contract with Auto Creation of Project, Long-term Service Order w. Settlement

© SAP AG of 32


MANUFACTURING SCENARIOS: Production Planning and Discrete Manufacturing, Production Planning and Process Manufacturing, Make-to-Order Quotation Processing/Order Processing, Repetitive Manufacturing

SALES SCENARIOS: Bought-In Item, Extended Sales-Order Processing, Sales-Order Processing with Dummy Customer, Consignment Processing, Returns and Complaints, Returnable Processing, Batch Recall.

3.5 Fully Qualified Domain Names (FQDN)Fully qualified domain names are strictly required to ensure that the Business Client runs smoothly.It is also the case for BSP and Web Dynpro ABAP.Run Transaction code RZ10, Add parameter:icm/host_name_full = <Hostname>.<XXX>.<XXX>icm/host_name_full = ER6BP00.SAP.COMThe FQDN must be available in network. If not, you have to maintain the hosts file insingle system environment.

3.6 Internet Communication Framework (ICF)Run Transaction code SICF to active those nodes as below:

/sap/bc/DAL/KYKDAL/sap/public/BSP/sap/public/myssocntl/sap/public/bc/sap/public/bc/ur

3.7 Scripting SettingsMake sure that your server is configured for user scripting as described in Note 480149.

sapgui/user_scripting True/FalseThere are 2 options for setting the parameter:In TCODE RZ11. If the parameter is only set in RZ11, the change is lost when you restart the server.In TCODE RZ10, maintain the server profile, the change is permanent and available after restart server.Note: these settings are only required if you need to run an integrated SAP GUI.

3.8 NWBC ConfigurationYou select the current system and configure systems in a configuration dialog box that you reach using the menu in the NWBC.1. Logon system with SAPLOGON.2. Enter TCODE SICF and execute with default settings.3. Choose menu Goto-> Port Information.

© SAP AG of 32


4. Write down the service number/ Host Name , and they will be used as Port /Host in the NWBC configuration dialog window.5. Choose Icon SAP NetWeaver Business Client to setup the connections.6. On the popup window, or choose menu File -> Preferences to do the configuration.7. Fill the connection info of server, such as: Name, Type, Protocol, Host, Port, Path, Client,Language, User.

Note: Host must be FQDN. If not, you have to maintain the hosts file in client system.

4 Usage

4.1 SAP GUI User Roles for Service ScenariosUser roles are specific user menus delivered with SAP Best Practices. Each Service scenario has its own user role.

The user roles are located on the Baseline Package documentation DVD in the folder..\Misc\Baseline_Package\Thailand.

4.1.1 Importing User Roles

UseThis procedure describes how to import user roles into an SAP system. Refer to the business process procedure of the building block in question to find out which role needs to be imported.

Procedure1. To import the user role into the SAP system, choose one of the following navigation

options:

SAP ECC menu Tools Administration User maintenance Role Administration Roles

Transaction code PFCG

2. Choose Role Upload.

3. Confirm the warning message.

4. Select the relevant *.SAP files from the relevant subfolder of the Misc folder on the documentation DVD/CD and choose Open.

5. Confirm the information screen indicating which roles already exist in the system.

6. Import the appropriate user role into the system.

7. To assign the role to a user, choose Change and go to the User tab.

© SAP AG of 32


8. Enter the user ID of your (or another) installation user.

9. Save the user role.

ResultThe installation role can be displayed in the system and any user assigned to it can start using it.

4.1.2 Assigning a Role to Other Users

Use

In the previous step, you uploaded the role and assigned it to your user. This section describes how you can make the role available for other users and thus enable them to work with it for the installation.

Procedure1. Choose one of the following navigation options:

SAP ECC menu Tools Administration User Maintenance Users

Transaction code SU01

1. In the User Maintenance screen, enter the user ID of your user.

2. Choose Change.

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

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

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

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

view displays the SAP ECC menu. The User menu function is still inactive.

6. To activate the user menu function, choose SAP ECC menu. The function User menu is now active.

7. To display the user menu in question, choose User menu. The role you assigned to your user is displayed. Expand it to see its content.

ResultThe user role you assigned to the user it was intended for is now available in the system and the user can start working with it.

© SAP AG of 32


Appendix

Appendix 1: Layer ConceptThe Baseline Package consists of mandatory layer 0 building blocks and optional layer 1 building blocks. The layer 0 building blocks provide fundamental preconfiguration, whereas the layer 1 building blocks provide preconfiguration that is required for either one specific scenario or for several scenarios. These building blocks can be put together and also supplemented with additional industry-specific configuration to achieve a vertical industry solution, as depicted below.

Baseline Package as Foundation

SAP AG 2004, Best Practices Methodology & Tools, Peter Neuer / 1

Baseline Package Architecture (Real Situation)

Baseline Package

Industry Package

Layer 0 Building Blocks

Baseline Layer 1 (optional)

BP Auto

BP FMCG

BP Hi-tech

Industry Layer Building Blocks (BBs)

BaselineBaseline Scenarios (“Generic Industry”)

© SAP AG of 32