Icons

Icon

Meaning Caution Example Note Recommendation Syntax

Typographic Conventions

Type Style Example text

Description 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 EXAMPLE TEXT

Emphasized words or phrases in body text, titles of graphics and tables. 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. 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. Keys on the keyboard, for example, function keys (such as F2) or the ENTER key. Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Pointed brackets indicate that you replace these

Example text

EXAMPLE TEXT

Example text

<Example text>

words and characters with appropriate entries.

Content

J00 Essential Information

1.

Purpose

Target Group
This document is intended for consultants and system administrators who are involved in an SAP Best Practices installation.

Content
The information in this document enables you to use the tools, configuration, and documentation delivered with SAP Best Practices. The section SAP Best Practices: Installation Preparation describes a number of generic installation considerations. To ensure a successful installation, read this Essential Information document in full before you start with any installation activities. This Essential Information document: Introduces the concept of SAP Best Practices installations and provides an overview of the building block approach Shows you how to use the documentation delivered with SAP Best Practices Shows you how to use the configuration tools, such as user roles, BC Sets, and CATT procedures Highlights which SAP Notes you need to install for a specific solution

SAP Best Practices installations can be modified. For detailed instructions on how to modify SAP Best Practices deliverables, see the documentation provided in the Vertical Solution Development Kit (VSDK).

2.

SAP Best Practices: Overview

SAP Best Practices provide a time-saving and cost-saving methodology for implementing SAP solutions. SAP Channel Partners can benefit from this methodology by using SAP Best Practices as the basis for developing vertical solutions for their customers. The key benefits are:

SAP Best Practices provide the preconfigured business content, the tools, and the documentation that you need for a fast and smooth implementation. The installation time is reduced considerably by the use of automated configuration tools known as Business Configuration Sets (BC Sets). The transfer and generation of master data is accelerated and facilitated by the use of automated procedures known as CATT procedures (Computer Aided Test Tool) and eCATT procedures (extended CATT), as well as the LSMW (Legacy System Migration Workbench). These tools allow you to modify and import customer-specific master data into an SAP system. Comprehensive documentation is provided for all installation activities.

The deliverables for SAP Best Practices are available on a documentation CD and a configuration CD. The documentation CD contains: Scenario overviews Building block/scenario descriptions Development master lists Installation guides Configuration guides Business process procedures Installation roles Master data variant files

The configuration CD contains all the technical deliverables (add-ons and special transports), as well as accompanying documentation, such as Installing Best Practices Add-On (ADDONINS.PDF), which provides details of technical prerequisites and gives import guidelines.

1. Building Blocks: Concept

The building block concept offers substantial benefits to SAP Channel Partners with respect to the development, distribution, and sale of solutions. Building blocks: Are reusable, business process-oriented, preconfiguration units, which you simply have to assemble to obtain your desired installation. Can be used flexibly as the basis for many vertical solutions. Vary in size and content. Some building blocks cover only a small range of very specific, scenario preconfiguration, whereas others cover complex, generic preconfiguration that can be used in many solutions, such as the J03 building block for Financials. These generic building blocks belong to the so-called Layer 0 (see Baseline Package below) and help to reduce redundancy. Enable SAP Channel Partners to focus on the development of the specific vertical configuration requirements of each customer.

2. Building Blocks: Installation

To install SAP Best Practices using building blocks, you install a number of building blocks in a predefined sequence using the various tools and documentation provided. The number and sequence of the building blocks depends on what you are installing. The installation guides and installation roles guide you through the installation. Each building block has its own installation role and installation guide. The role has to be uploaded into the system from the documentation CD. The guide is available on the documentation CD. To perform the installation activities for a building block in the system, you follow the installation role you have uploaded reading the description of the corresponding steps in the installation guide. Additional information is available in the configuration guide of the building block where details of the Customizing settings are provided. After installation, you can test the whole scenario using the document known as the business process procedure (BPP). This document is also available on the documentation CD. You can also use CATT test catalogs. These are recorded transactions that perform the transactions and data entry. For training purposes, the SAP Tutor tool is available for playing and creating interactive learning units. These tutorials record all Windows applications and can be used to simulate the users working environment, thus enabling the user to familiarize himself or herself with new programs and processes without affecting a productive system.

3.

SAP Best Practices: Baseline Package (KR)

1. Baseline Package (KR): Concept

Layer Concept
The Baseline Package (KR) consists primarily of mandatory layer 0 building blocks and optional layer 1 building blocks. These building blocks can be put together and also supplemented with additional industry-specific configuration to achieve a vertical industry solution, as depicted below. For more information on the installation procedure and building block sequence, see Baseline Package (KR): Installation. Baseline Package as Foundation

Mandatory Layer 0 Building Blocks

These following are the mandatory layer 0 building blocks, which provide fundamental preconfiguration:

Building Block ID J02

Name Organizational Structure

J03 J04 J05 J06 J07 J08

Financial Accounting Sales and Distribution Materials Management Production Planning and Control Quality Management Controlling

Optional Layer 1 Building Blocks

The following are the optional layer 1 building blocks, which provide scenario-specific preconfiguration:

Building Block ID J10 J11 J17 J19 J49 J50 J51 J53 J55 J57 J58

Name Asset Management Cash Management Profitability Analysis Batch Management Procurement of Stock Material Procurement - Contract Internal Procurement (Stock Transfer With Delivery) Internal Procurement (Cross-Company Stock Transfer) Third Party Without Shipping Notification Standard Sales Process Customer Consignment Processing

J59 J60 J61 J62 J64 J65 J66 J67 J70 J71 J72 J73 J74 J75

Returns and Complaints Returnable Processing Batch Recall Cross-Company Sales Order Processing PP and Discrete Manufacturing Make-to-Stock PP and Process Manufacturing Make-to-Stock Make-to-Order Quotation Processing/Order Processing Repetitive Manufacturing Procurement for consumables Credit Control in sales order processing SOP Physical inventory Standard cost estimation Third Party Order procurement with subcontracting

Other Building Blocks

The following building blocks are also delivered. These building blocks have special functions.

Building Block ID J00

Name Essential Information

Function This document. Provides information that is essential for any SAP Best Practices installation. Explains the concepts and provides instructions for using the tools. Contains documentation only.

 J01 Express Installation

Contains the installation role and installation guide for express installation. Enables you to install the complete Baseline Package.

2. Baseline Package (KR): Installation

Installation Options
When considering installation of the Baseline Package (KR), you must decide whether you want to install the complete package or only certain scenarios of your choice. Installation of the complete package is the recommended option and is also supported by an express installation role and installation guide contained in building block J01.

Option A: Installation of complete Baseline Package (KR)

To install the complete Baseline Package, you use the express installation role and installation guide contained in J01. This installs all mandatory level 0 building blocks and all optional layer 1 building blocks in the predefined sequence.

Option B: Selective installation of certain scenarios

To install only certain scenarios, you first install all the mandatory layer 0 building blocks in the correct sequence (see below). Second, you check the installation guides of your chosen scenarios (layer 1 building blocks) for any other layer 1 building blocks that are prerequisites of your chosen building blocks. Third, you install these prerequisite building blocks. Finally, you install your chosen layer 1 building blocks. The installation sequence of the mandatory layer 0 building blocks is as follows:

Building Block ID J02 J03 J08 J05 J04 J06 J07

Name Organizational Structure Financial Accounting Controlling Materials Management Sales and Distribution Production Planning and Control Quality Management

If you want to install the scenario Internal Procurement (Stock Transfer With Delivery) (building block J51), you first install all the mandatory layer 0 building blocks in the sequence shown in the table above. Second, you refer to the installation guide for J51 and discover that J17 Profitability Analysis is a prerequisite for J51. Third, you install J17. Finally, you install J51.

4.

SAP Best Practices: Documentation

1. Document Types and Content

Each building block has various documents, which describe the business content, installation, and testing procedures. It is important that you read these documents carefully in the appropriate order, as illustrated in Using the Document Types. The following table gives you an overview of the documentation delivered with SAP Best Practices.

Document Type Purpose

Scenario Overview Scenario/Building Block Description Provides a graphical overview of a scenario. Briefly describes the content of a scenario or building block and shows its benefits. This is not a document as such, but appears as HTML content on the documentation CD.

File Format
MS PowerPoint HTML

Building Block Installation Guide

Each building block has an installation guide, which describes in detail how to install the building block using automated MS Word installation tools. Some of the procedures may have to be carried out manually. The installation guide describes the activities in the logical order of the installation process. Use this document along with the installation role if you want to use installation tools for a fast implementation.

Building Block Configuration Guide

Each building block has a configuration guide, which describes: The manual configuration steps you have to perform if you do not want to use the automated installation tools, but prefer to set up the configuration of a building block manually. Configuration details for reviewing the system settings and obtaining additional information on the automated installation procedures.

MS Word

For each step in an installation guide, you can find the corresponding manual installation information in the configuration guide. As BC Sets are packages of Customizing settings, you may find several sections in the configuration guide corresponding in total to one step in the installation guide. The configuration guide describes the activities in the logical order of the installation process. Development Master The development master list provides a comprehensive, MS Excel List transparent, and structured overview of all necessary installation steps in the logical order of application, as well the consolidated deliverables, such as user roles. Business Process Procedure End-user documentation providing detailed, applicationMS Word focused descriptions of business processes. Used for testing scenarios.

2. Using the Document Types

The various document types should be used as illustrated below:

You can also use the building block configuration guides for more details of the settings during installation.

5.

SAP Best Practices: Tools

1. Installation Roles

Installation roles are specific user menus delivered with SAP Best Practices. Each building block has its own installation role, which is supported by an installation guide. The installation role is used for automated installation and enables you to access and execute all the required installation transactions and configuration activities in the correct order. The default initial screen of an SAP system displays the SAP menu. To install a specific building block, you must upload the installation user role in the SAP system and activate it on the screen, hence replacing the default SAP menu. The installation roles are delivered in the misc folder on the documentation CD. For more information on how to set up installation roles, see Importing Installation Roles. If you store the user roles in a local directory, make sure there are no more than four subdirectories from the first level to the directory that contains your roles. If the directory path or the path description is too long, you may encounter problems when you are uploading the roles.

1. Importing Installation Roles

Use
This procedure describes how to import installation roles into an SAP system. Refer to the installation guide of the building block in question to find out which role needs to be imported.

Procedure
1. To import the user role into the SAP system, choose one of the following navigation
options:

Transaction code SAP Menu R/3

PFCG Tools Administration User maintenance Role Administration Roles

2. Choose Role Upload. 3. Confirm the warning message. 4. Select the relevant *.SAP file from the misc directory on the documentation CD and 5. 6. 7. 8. 9.
choose Open. Confirm the information screen indicating which roles already exist in the system. Import the appropriate user role into the system. To assign the role to a user, choose Change and go to the User tab. Enter the user ID of your (or another) installation user. Save the user role.

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

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.

Procedure
1. Choose one of the following navigation options:

Transaction code

SU01

SAP Menu

Tools Administration User Maintenance Users

3. In the User Maintenance screen, enter the user ID of your installation user. 4. Choose Change.
5. In the Maintain User view, choose the Roles tab. 6. 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.

7. Choose Enter, save, and go back to the SAP Easy Access view. The SAP Easy Access
view displays the SAP menu. The User menu function is still inactive.

8. To activate the user menu function, choose SAP Menu. The function User menu is now
active.

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

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

2. Business Configuration Sets

Use
A Business Configuration Set (BC Set) is a package of Customizing settings. BC Sets are used to accelerate the installation process of the building blocks and scenarios delivered with SAP Best Practices. The following section only describes how to activate BC Sets during the SAP Best Practices installation. If you want to find out more information about BC Sets (how to create your own BC Sets, and so on), refer to the Vertical Solution Development Kit. BC Sets are used to accelerate the installation process. For each BC Set step in the installation guide, there is corresponding information in the configuration guide describing how to perform this step manually.

Features
There are two types of BC Set: Single BC Sets: These contain the selected settings of one IMG activity. Hierarchical BC Sets: These group a number of single BC Sets together.

Single and hierarchical BC Sets can contain fixed and variable values. If a BC Set only contains fixed values, the user does not have to adapt the settings. If a BC Set contains variable values, the user can adapt the default settings according to their requirements. The BC Sets are stored on the configuration CD together with other objects. Installing the SAP Best Practices Add-On imported the BC Sets into the relevant system. However, the configuration settings delivered within the BC Sets are not effective yet. Only after you have activated the BC Set is the content written to the Customizing table. In your SAP Best Practices installation role, you find the transactions to call up the BC Sets and activate them. To activate a BC Set, you have to carry out following steps: Display the BC Set contents Compare BC Set content with the Customizing table Activate the BC Set Check the activation log to confirm the successful activation

These steps are described in detail below.

1. Displaying BC Set Contents

1. In the installation role, double-click on the activity whose BC Set details you want to
check. 2. The Business Configuration Set: Activate view is displayed. 3. To display the details of the BC Set, choose Display. The BC Set: Overall view is displayed, providing information on tables, views and data records that are involved in the activity.

If you are displaying a hierarchical BC Set, you can display the list of single BC Sets included in this hierarchical BC Set. To do this, choose Display. From the list of the single BC Sets, doubleclick on a single BC Set to display detailed information.

4. After you have checked the BC Set details in the BC Set: Overall View, choose Back. 2. Comparing BC Set Content with Customizing

Tables
1. In the Business configuration set: Activate view, choose Compare with system tables and 2.
variable query (Ctrl + F9). Compare the values of the BC Set to those of the Customizing table(s). Depending on whether you are comparing a BC Set with fixed or with variable values, one of the following descriptions applies:

BC Sets with fixed values If you are comparing a BC Sets without variable values, the view BC Set: Compare

BC Sets with variable values If you are comparing a BC Set with variable values, the Enter Variable Fields Values table

with customizing table contents is displayed. Different colors in the table view indicate various details about a field and its values, for example, whether the fields copied from the BC Set into your Customizing tables are data fields or key fields and whether they contain fixed or variable values. Choose Display color legend from the application toolbar for details. The first line in the table shows the BC Set data, the second line the existing entries in the Customizing table.

is displayed. The Fields column lists the fields into which the BC Set will insert variable values. In the Value section, the default values which will be entered by the BC Set are displayed. Choose Display color legend from the application toolbar for details. The first line in the table shows the BC Set data, the second line the existing entries in the Customizing table

If you do not want to activate a BC Set and overwrite the contents of your Customizing tables, go back and perform the relevant Customizing step manually according to the corresponding instructions in the building blocks configuration guide.

3. Activating a BC Set

Prerequisites
Before you activate a BC Set, always compare the values contained in the BC Set to the existing entries in your Customizing tables.

Procedure
1. In the BC Set: Compare with customizing table contents view, choose Activate / Put BC Set in customizing tables.

3. Depending on the kind of BC Set you have activated, there are two alternatives for
proceeding with the activation:

BC Sets with fixed values If a request for Customizing is displayed, proceed with step 3.

BC Sets with variable values If the Enter Variable Field Values table is displayed, you can copy or change the default values in the Value column.

1. 2.

Change the default values, if necessary. Choose Apply Values.

3. A request for Customizing appears. Select an existing request or create a new one if necessary. Choose Continue.

4. In the Activation Options dialog box, choose Continue. Make sure you do not 5.
inadvertently overwrite existing entries. The message Activation successfully completed is displayed. The message Activation successfully completed appears.

Sometimes the BC Set activation ends with a warning message. If you check the activation log and find the information No Business Configuration Set exists for view, you can ignore the message, because the BC Set activation has been successful. If you activate a hierarchical BC Set, you activate all settings contained in the lower-level BC Sets that belong to that hierarchical BC Set. Especially for larger BC Set hierarchies, a BC Set activation may end with a warning or error message different from the warnings mentioned above or in the respective chapter of the installation guide. In case of error messages, you may repeat the activation of the BC Set. You can, however, also activate each of the lower-level BC Sets of a hierarchical BC Set individually to activate the settings successfully.

6. After activation, always compare the values contained in the BC Set to the existing
entries in your Customizing tables. There should be no differences.

If there are differences, repeat the activation. You may find that only description fields differ that had been set during a previous activation of a BC Set or manual configuration step. In this case the differences are not critical. Error messages and warnings during the activation process can be ignored if the comparison shows no differences.

4. Displaying the Activation Log

Use
To verify whether a BC Set was successfully activated, you can display its activation log.

Procedure
To do this, choose Display Log on the Business configuration set: activate screen. In the log overview, green traffic lights signalize the successful activation. If there is a yellow or red traffic light in the log overview structure, double-click on the relevant node and check the details on the right side of the screen.

Result
You have checked the successful configuration in your Customizing tables for the specific business configuration that the BC Set covers and can proceed with the next activity of the installation guide.

3. eCATT Procedures 1. eCATT Objects

Test Configuration
This object contains a set of references to a test script and possibly several test data containers. A test configuration contains all the information necessary to run an automatic test without further user interaction. The separation of test script and test data allows for a considerable degree of reuse.

Test Script
This object consists of an executable script and an interface for data transfer.

Test Data Container

This object contains a set of parameters that can be maintained independently of a test script. Parameters can be ABAP simple types, structures, or tables.

System Data Container

This object identifies instances of SAP systems. It can be maintained independently of the test script. This item is not used with SAP Best Practices, but is mentioned on the initial eCATT screen.

Versions and Variants

A test script can have several versions. This allows different implementations for different releases. Test data containers and test configurations can have variants. Variants are different sets of data.

Transport and Download

All eCATT objects are Repository objects. Therefore, you can take advantage of the standard SAP transport tools. You can also download an eCATT object to a file, which can be later uploaded into another system.

Naming Convention
There is no naming convention specifically for eCATT objects. A name is an alphanumeric string up to 30 characters long. A name is not case-sensitive.

2. Executing eCATT Procedures

Use
eCATT (extended Computer Aided Test Tool) procedures enable you to create and execute functional tests of business processes within SAP Best Practices. The test produces a log that documents the test process and results.

Prerequisites
The system must be based on SAP Basis Release 6.20 (with patch level 39 or above) or later. Enable scripting in local layout options. Profile parameter (TA RZ11) sapgui/user_scripting value: TRUE

Procedure
1. On the Extended Computer Aided Test Tool: Initial Screen screen, enter the names for the Test Configuration, Test Script, and Test Data fields. 2. Choose Execute. 3. If any error messages appear within the log, you will need to correct them before being able to execute the procedure successfully.

3. Personalizing eCATT Procedures

Use
You can personalize eCATT objects, such as test data containers, test scripts, and variants, to customize your data. You must first create copies of the various eCATT objects needed before proceeding. If not, you will overwrite the objects provided. The procedure is described below.

Procedure
1. In the Test Data field, enter the name of the test data container you want to copy. 2. Choose Copy Object. 3. In the Copy dialog box that appears, enter the new name for the copy of the data 4. 5. 6. 7.
container in the to Test Data Container field. Choose Copy. In the Create Object Directory Entry dialog box that appears, enter the package name and choose Save. Return to the initial screen. Display the new data container by entering the name in the Test Data field and choose Display. In the new screen that appears, choose Display <-> Change to customize your data.

Do not change the variant names themselves, as this will invalidate parts of the test script and will cause an error. If you need to change the variant name, you have to use the Variant Maintenance Assistant in order to reassign it to the test script.

8. Choose Save to save your changes.

Result
Your eCATT data has been customized.

4. Displaying and Printing eCATT Logs

Use
You can display an existing log. You can print out a view of your choice.

Procedure
1. On the Extended Computer Aided Test Tool: Initial Screen screen, choose Logs. The
eCATT Log Selection screen appears. 2. Enter your selection criteria and choose Execute. A list of all the logs that satisfy the selection criteria is displayed. 3. In the Activity no column, click the number of the log that you want to display. The log is displayed as a hierarchical structure in which you can navigate. 4. To see the elements under a node, select the node and choose Expand nodes, or click on the symbol in front of the node. 5. Expand and collapse nodes until the log looks the way you want it for printing. 6. Choose Print. 7. Choose Print. The Print Screen List dialog box appears. 8. Enter the required information and choose Choose.

4. Legacy System Migration Workbench

Use
Primarily, the Legacy System Migration Workbench (LSMW) is used to migrate data from a legacy system into an SAP system. With SAP Best Practices, however, the LSMW is used to create master data examples for the business scenarios provided. This document describes only activities that relate directly to SAP Best Practices. For more general information on the LSMW, see the general SAP Library. Within SAP Best Practices, you can use the LSMW either with an eCATT or without an eCATT (manually).

1. LSMW With eCATT

In the individual building block installation guides, the LSMW procedures described are started by an eCATT. This is the automated procedure and therefore the recommended option.

Prerequisites
Ensure 6.20 SAP GUI and the SAP GUI Scripting component is installed. Ensure that the required support packages are installed. For information about which support packages to use, see SAP Note 519858. Ensure that eCATTs are allowed in the relevant clients. Go to transaction SM31. In the Table/View field, enter T000. Choose Maintain. In the Change View Clients: Overview screen, select the relevant client and choose Details. In the Restrictions when Starting CATT and eCATT field, select an entry that allows eCATT. Choose Save. Enable GUI Scripting on the back end and on the front end.

For the back end: Go to transaction RZ11. On the Maintain Profile Parameters screen, enter sapgui/user_scripting. Choose Display. On the Display Profile Parameter Attributes screen, choose Change value. Enter TRUE in the New value field. Choose Save. For the front end: Choose Customizing of local layout (Alt + F12) -> Options. Then go to the Scripting (tab), select Enable Scripting and choose OK.

Procedure
1. Import the LSMW project (see Importing LSMW Project below). 2. Refer to the individual building block installation guides for details of the master data
creation. For further details of warning messages and color symbols, see the section Warning Messages and eCATT Log below.

1. Importing LSMW Project

Use
This procedure describes the general process of importing the LSMW project for SAP Best Practices.

Prerequisites
The LSMW project only needs to be imported once. Check whether the LSMW project BP_AIO already exists.

Procedure
To import the LSMW project into the SAP system, choose:

Transaction code Then carry out the following steps:

LSMW

1. Choose the menu item Extras Import Projects. 2. Select the LSMW_BP_AIO.txt file from the MISC directory on the SAP Best Practices
documentation CD and choose Open.

3. Confirm the information screen. 4. Import the LSMW project SAP Best Practices Master Data into the system.

Existing projects or subprojects are marked with a cross and overwritten during the import.

Result
The LSMW project SAP Best Practices Master Data has been created in the system. If you are using eCATT with LSMW, proceed as described in the individual building block installation guides bearing in mind the information in the section Warning Messages and eCATT Log below. If you are using the LSMW manually, proceed as described under Importing Master Data in the subsection for the object type in question.

2. Warning Messages and eCATT Log

Use
When you are executing the activities that use eCATT with the LSMW, a number of messages and colored symbols in the eCATT log may appear. The following explains these messages and what action, if any, is to be taken.

Message/Color Warning: files already imported

Circumstance

Action/Consequence

Appears if the master data Choose Cancel. The eCATT has already been imported. procedure is terminated. Choose OK.

Dialog box saplogon concerning the SAP GUI Dialog box Status: Completed please check the results eCATT procedure has finished successfully.

Check whether the master data has been imported, as indicated in the dialog box either using transaction SM35 or using the relevant transaction depending on the master data object, such as MM03.

Green symbols in the eCATT log eCATT procedure has been This does not mean that the LSMW display executed without errors. has successfully imported the master data. To check the master data import, see above. Red symbols in the eCATT log display eCATT procedure has errors. Import the master data using the LSMW directly without the eCATT, as described below in the section

LSMW Without eCATT.

3. LSMW External File Folder

Use
For each user, a file folder should be created locally to centrally store the LSMW external files.

Procedure
Create a local file folder and copy all the LSMW external files you want to use into this folder. Later this folder is assigned to the LSMW at execution.

2. LSMW Without eCATT

If you want to use the LSMW without the eCATT automation, you can perform the LSMW activities manually.

Procedure
1. Import the LSMW project (see Importing LSMW Project below).
2. Refer under Importing Master Data to the subsection that applies to the object type in question.

1. Importing LSMW Project

Use
This procedure describes the general process of importing the LSMW project for SAP Best Practices.

Prerequisites
The LSMW project only needs to be imported once. Check whether the LSMW project BP_AIO already exists.

Procedure
To import the LSMW project into the SAP system, choose:

Transaction code

LSMW

Then carry out the following steps:

1. Choose the menu item Extras Import Projects.

2. Select the LSMW_BP_AIO.txt file from the MISC directory on the SAP Best Practices 3. 4.
documentation CD and choose Open. Confirm the information screen. Import the LSMW project SAP Best Practices Master Data into the system.

Existing projects or subprojects are marked with a cross and overwritten during the import.

Result
The LSMW project SAP Best Practices Master Data has been created in the system. If you are using eCATT with LSMW, proceed as described in the individual building block installation guides bearing in mind the information in the section Warning Messages and eCATT Log below. If you are using the LSMW manually, proceed as described under Importing Master Data in the subsection for the object type in question.

2. Importing Master Data

Refer to the subsection below that is relevant for the object type in question.

1. Importing Material Master Data

Use
The purpose of this activity is to import material master data via LSMW using direct input.

Prerequisites
You have imported the LSMW project BP_AIO into your system.

Specifying LSMW Project Details

1. Access the activity as follows:

Transaction Code

LSMW

2. Confirm the information message Welcome to the Legacy System Migration Workbench.

3. On the Legacy System Migration Workbench screen, enter the following values:

Field name

Description

User action and values

Notes

PROJECT

Name of data transfer project

Enter BP_AIO

More than one subproject can be assigned to a project. A subproject can have an unlimited number of objects An object is assigned to a subproject

SUBPROJ

Specifies the name of the subproject

Enter MM

OBJECT

Object name. An object Enter MATREC corresponds to a business object.

4. Choose Continue. The LSM Workbench: BP_AIO, MM, <MATREC> screen is displayed.
You can change the default view from display mode to change mode. To do this, choose Double Click=Display.

Specifying an External File

If an external file has already been specified, only change the file name of the existing file. Do not add or create any additional files.

1. In the LSM Workbench: BP_AIO, <subproject>, <object> screen, start the process step
Specify Files and go into change mode, if you are in display mode.

2. In the LSM Workbench; Specify Files (Change) view, go to the structure item Legacy
Data - On the PC (Frontend). Double-click on the object file entry that is located directly under Legacy Data - On the PC (Frontend). The File on Front End: Maintain Properties entry screen is displayed. Enter the following values:

Field name File

Description LSMW data file name Object type

User action and values Specify the path and name of the external data file or browse for the external data file Specify the name of the object Select the radio button Data for Multiple Source Structures (Seq. File) Select the radio button Tabulator

Notes

Name File Contents

Separators

Check file for separators, if necessary

File Structure

Select the checkbox Field Order Matches Source Structure Definition Select the radio button Record End Marker (Text File) Select ASCII

File Type

Code Page

3. Choose Continue, save your file settings and choose Back.

Assigning a File

Omit this activity if an external file has already been specified and assigned. 1. To assign an external file, double-click on the process step Assign File. 2. In the LSM Workbench: Assign File view, select the first line highlighted in yellow (Legacy Data - On the PC (Frontend)) and choose Assignment. The file you have specified in the previous step is assigned. Repeat this for each entry highlighted in yellow until you have assigned the file assigned to each structure.

Importing Data from Files

1. To import the data from the assigned files, double-click on the process step Import Data.
2. Choose Execute without entering any values. Go back to the Process Step list

Converting Imported Data

1. To convert the imported data, double-click on the process step Convert Data. 2. Choose Execute without entering any data. Go back to the Process Step list.

Starting Direct Input Program Data

1. Start the process step Start Direct Input Program. 2. In the Direct Input Session dialog box, select Program RMDATIND and proceed with
Enter.

3. Maintain the following values and execute.

Field name

User action and values

Notes

Using physical file BP_AIO_MM_MATREC.lsmw.conv default value name Message level 2 Display of critical messages only

Lock Mode

Fields not ready for W input Status control Check required fields

4. Confirm the following messages and check the results.

Please check whether error messages, marked as red lines, are shown in the result list. Warning messages will not be displayed using message level 2. These warning messages can be ignored. They will not have an impact on the quality of the data.

Result
You have created the material master data.

2. Importing Customer Master Data

Use
The purpose of this activity is to import customer master data via LSMW using Batch Input.

Prerequisites
You have imported the LSMW project BP_AIO into your system.

Specifying LSMW Project Details

1. Access the activity using the following transaction code:

Transaction Code

LSMW

2. Confirm the information message Welcome to the Legacy System Migration Workbench. 3. On the Legacy System Migration Workbench screen, enter the following values:

Field name PROJECT

Description Name of data transfer project

User action and values BP_AIO

Notes More than one subproject can be assigned to a project.

SUBPROJ

Specifies the name of the subproject

SD

A subproject can have an unlimited number of objects An object is assigned to a subproject

OBJECT

Object name. An object CUSTOMERS_FINAL corresponds to a business object.

4. Choose Continue. The LSM Workbench: BP_AIO SD CUSTOMERS _FINAL screen is

displayed. You can change the default view from display mode to change mode. To do this, choose Double Click=Display.

Specifying an External File

If an external file has already been specified, only change the file name of the existing file. Do not add or create any additional files.

1. In the LSM Workbench: BP_AIO, SD, CUSTOMERS_FINAL screen, start the process
step Specify Files and go into change mode, if you are in display mode.

2. In the LSM Workbench; Specify Files (Change) view, go to the structure item Legacy
Data - On the PC (Frontend). Double-click on the object file entry that is located directly under Legacy Data - On the PC (Frontend). The File on Front End: Maintain Properties entry screen is displayed. Enter the following values:

Field name File

Description LSMW data file name Object type

User action and values Specify the path and name of the external data file or browse for the external data file Specify the name of the object type Select the radio button Data for One Source Structure Tabulator

Notes

Name File Contents

Separators

Check file for separators, if necessary

File Structure File Type

Choose Field Names at start of File Select the radio button

Record End Marker (Text File) Code Page Select ASCII

3. Choose Continue, save your file settings and choose Back.

Assigning a File

Omit this activity if an external file has already been specified and assigned. 1. To assign an external file, double-click on the process step Assign File. 2. In the LSM Workbench: Assign File view, select the first line highlighted in yellow and choose Assignment. The file you have specified in the previous step is assigned. Repeat this for each entry highlighted in yellow until you have assigned the file assigned to each structure.

Importing Data from Files

1. To import the data from the assigned files, double-click on the process step Import Data.
2. Choose Execute without entering any values. Go back to the Process Step list

Converting Imported Data

1. To convert the imported data, double-click on the process step Convert Data. 2. Choose Execute without entering any data. Go back to the Process Step list.

Creating Batch Input Session

1. Double-click the step Create Batch Input Session.
2. In the Batch Input interface for Vendors screen, choose Execute, confirm the messages which are displayed. If a batch input session was created successfully, the message Session 1 session name CUSTOMERS_FINA was created is displayed.

Running Batch Input Session

1. Double-click the step Run Batch Input Session. 2. On the Batch Input: Session Overview screen, select the session you have created in the 3. 4. 5. 6. 7.
step before. If the batch input session was created correctly, New is displayed in the column Status. Choose Process. In the dialog box Process Session Customers_Final, choose a processing mode. Choose Process. In case of foreground processing, select Enter till the data is imported. In case of background processing, the system message 1 session transferred to background processing is displayed.

8. To refresh the list, press Enter. 9. In case of errors, solve them and run through the process again.

Possible problems might be: o o o Configuration does not fulfill the master data requirements (CATT and manual processing of the transaction would also fail) External master data file is not stored as tab separated file Other data inconsistencies

Result
You have created customers master data.

3. Importing Vendor Master Data

Use
The purpose of this activity is to import vendor master data via LSMW using Batch Input.

Prerequisites
You have imported the LSMW project BP_AIO into your system.

Specifying LSMW Project Details

1. Access the activity using the following transaction code:

Transaction Code

LSMW

2. Confirm the information message Welcome to the Legacy System Migration Workbench. 3. On the Legacy System Migration Workbench screen, enter the following values:

Field name PROJECT

Description Name of data transfer project

User action and values BP_AIO

Notes More than one subproject can be assigned to a project. A subproject can have an unlimited number of objects

SUBPROJ

Specifies the name of the subproject

MM

OBJECT

Object name. An object VENDORS_FINAL corresponds to a business object.

An object is assigned to a subproject

4. Choose Continue. The LSM Workbench: BP_AIO MM, VENDORS_FINAL screen is

displayed. You can change the default view from display mode to change mode. To do this, choose Double Click=Display.

Specifying an External File

If an external file has already been specified, only change the file name of the existing file. Do not add or create any additional files.

1. In the LSM Workbench: BP_AIO, MM, VENDORS_FINAL screen, start the process step
Specify Files and go into change mode, if you are in display mode.

2. In the LSM Workbench; Specify Files (Change) view, go to the structure item Legacy
Data - On the PC (Frontend). Double-click on the object file entry that is located directly under Legacy Data - On the PC (Frontend). The File on Front End: Maintain Properties entry screen is displayed. Enter the following values:

Field name File

Description LSMW data file name Object type

User action and values Specify the path and name of the external data file or browse for the external data file Specify the name of the object type Select the radio button Data for One Source Structure Tabulator

Notes

Name File Contents

Separators

Check file for separators, if necessary

File Structure File Type

Choose Field Names at start of File Select the radio button Record End Marker (Text File) Select ASCII

Code Page

3. Choose Continue, save your file settings and choose Back.

Assigning a File

Omit this activity if an external file has already been specified and assigned. 1. To assign an external file, double-click on the process step Assign File. 2. In the LSM Workbench: Assign File view, select the first line highlighted in yellow and choose Assignment. The file you have specified in the previous step is assigned. Repeat this for each entry highlighted in yellow until you have assigned the file assigned to each structure.

Importing Data from Files

1. To import the data from the assigned files, double-click on the process step Import Data.
2. Choose Execute without entering any values. Go back to the Process Step list

Converting Imported Data

1. To convert the imported data, double-click on the process step Convert Data. 2. Choose Execute without entering any data. Go back to the Process Step list.

Creating Batch Input Session

1. Double-click the step Create Batch Input Session.
2. In the Batch Input interface for Vendors screen, choose Execute, confirm the messages which are displayed. If a batch input session was created successfully the message Session 1 session name VENDORS_FINA was created is displayed.

Running Batch Input Session

1. Double-click the step Run Batch Input Session. 2. On the Batch Input: Session Overview screen, select the session you have created in the 3. 4. 5. 6. 7. 8.
step before. If the batch input session was created correctly, New is displayed in the column Status. Choose Process. In the dialog box Process Session vendors_Fina, choose a processing mode. Choose Process. In case of foreground processing, select Enter till the data is imported. In case of background processing, the system message 1 session transferred to background processing is displayed. In case of errors, solve them and run through the process again.

Possible problems might be:

Configuration does not fulfill the master data requirements (CATT and manual processing of the transaction would also fail) External master data file is not stored as tab separated file Other data inconsistencies

Result
You have created vendor master data.

4. Importing Condition Master Data

Use
The purpose of this activity is to import condition master data via LSMW using Batch Input.

Prerequisites
You have imported the LSMW project BP_AIO into your system.

Specifying LSMW Project Details

1. Access the activity using the following transaction code:

Transaction Code

LSMW

2. Confirm the information message Welcome to the Legacy System Migration Workbench. 3. On the Legacy System Migration Workbench screen, enter the following values:

Field name PROJECT

Description Name of data transfer project

User action and values BP_AIO

Notes More than one subproject can be assigned to a project. A subproject can have an unlimited number of objects An object is assigned to a subproject

SUBPROJ

Specifies the name of the subproject

SD

OBJECT

Object name. An object Conditions corresponds to a business object.

4. Choose Continue. The LSM Workbench: BP_AIO SD Conditions screen is displayed.

You can change the default view from display mode to change mode. To do this, choose Double Click=Display.

Specifying an External File

If an external file has already been specified, only change the file name of the existing file. Do not add or create any additional files.

1. In the LSM Workbench: BP_AIO, SD, Conditions screen, start the process step Specify
Files and go into change mode, if you are in display mode.

2. In the LSM Workbench; Specify Files (Change) view, go to the structure item Legacy
Data - On the PC (Frontend). Double-click on the object file entry that is located directly under Legacy Data - On the PC (Frontend). The File on Front End: Maintain Properties entry screen is displayed. Enter the following values:

Field name File

Description LSMW data file name Object type

User action and values Specify the path and name of the external data file or browse for the external data file Specify the name of the object type Select the radio button Data for One Source Structure (Table) Tabulator

Notes

Name File Contents

Separators

Check file for separators, if necessary

File Structure File Type

Field names at start of file Select the radio button Record End Marker (Text File) Select ASCII

Code Page

3. Choose Continue, save your file settings and choose Back.

Assigning a File

Omit this activity if an external file has already been specified and assigned.

1. To assign an external file, double-click on the process step Assign File. 2. In the LSM Workbench: Assign File view, select the first line highlighted in yellow and choose Assignment. The file you have specified in the previous step is assigned. Repeat this for each entry highlighted in yellow until you have assigned the file assigned to each structure.

Importing Data from Files

1. To import the data from the assigned files, double-click on the process step Import Data.
2. Choose Execute without entering any values. Go back to the Process Step list

Converting Imported Data

1. To convert the imported data, double-click on the process step Convert Data. 2. Choose Execute without entering any data. Go back to the Process Step list.

Creating Batch Input Session

1. Double-click the step Create Batch Input Session. 2. On the Batch Input Interface for Conditions screen, enter the file name BP_AIO_SD_COND.lsmw.conv, which contains the converted data you have imported in the step Importing Data from Files. 3. Choose Execute. 4. The message Session 1 COND open is displayed by the system. Confirm and on the next screen choose Back.

Running Batch Input Session

1. On the Batch Input: Session Overview screen, select the session you have created in the 2. 3. 4. 5. 6. 7.
step before. If the batch input session was created correctly, New is displayed in the column Status. Choose Process. In the dialog box Process Session COND, choose a processing mode. Choose Process. In case of foreground processing, select Enter until the data is imported. In case of background processing, the system message 1 session transferred to background processing is displayed. In case of errors, solve them and run through the process again.

Possible problems might be: Configuration does not fulfill the master data requirements (CATT and manual processing of the transaction would also fail) External master data file is not stored as tab separated file. Other data inconsistencies

Result
You have created the conditions master data in your system.

5. Importing Routing Master Data

Use
The purpose of this activity is to import routing master data via LSMW using Direct Input.

Prerequisites
You have imported the LSMW project BP_AIO into your system.

Specifying LSMW Project Details

1. Access the activity using the following transaction code:

Transaction Code

LSMW

2. Confirm the information message Welcome to the Legacy System Migration Workbench. 3. On the Legacy System Migration Workbench screen, enter the following values:

Field name PROJECT

Description Name of data transfer project

User action and values BP_AIO

Notes More than one subproject can be assigned to a project. A subproject can have an unlimited number of objects An object is assigned to a subproject

SUBPROJ

Specifies the name of the subproject

PP

OBJECT

Object name. An object ROUTING corresponds to a business object.

4. Choose Continue. The LSM Workbench: BP_AIO PP ROUTING screen is displayed.

You can change the default view from display mode to change mode. To do this, choose Double Click=Display.

Specifying an External File

If an external file has already been specified, only change the file name of the existing file. Do not add or create any additional files.

1. In the LSM Workbench: BP_AIO, PP, ROUTING screen, start the process step Specify 2.
Files and go into change mode, if you are in display mode. In the LSM Workbench; Specify Files (Change) view, go to the structure item Legacy Data - On the PC (Frontend). Double-click on the object file entry that is located directly under Legacy Data - On the PC (Frontend). The File on Front End: Maintain Properties entry screen is displayed. Enter the following values:

Field name File

Description LSMW data file name Object type

User action and values Specify the path and name of the external data file or browse for the external data file Specify the name of the object type Select the radio button Data for Multiple Source Structures (Sequential Files) Tabulator

Notes

Name File Contents

Separators

Check file for separators, if necessary

File Structure

Choose Field Order matches source structure definition Select the radio button Record End Marker (Text File) Select ASCII

File Type

Code Page

3. Choose Continue, save your file settings and choose Back.

Assigning a File

Omit this activity if an external file has already been specified and assigned. 1. To assign an external file, double-click on the process step Assign File. 2. In the LSM Workbench: Assign File view, select the first line highlighted in yellow and choose Assignment. The file you have specified in the previous step is assigned. Repeat this for each entry highlighted in yellow until you have assigned the file assigned to each structure.

Importing Data from Files

1. To import the data from the assigned files, double-click on the process step Import Data.
2. Choose Execute without entering any values. Go back to the Process Step list

Converting Imported Data

1. To convert the imported data, double-click on the process step Convert Data. 2. Choose Execute without entering any data. Go back to the Process Step list.

Running Direct Input Session

1. 2. 3. 4.
Double-click the step Start Direct Input Program. On the Data transfer of Routings via Direct input screen, choose Execute. A log is displayed by the system. Choose back. In case of errors, solve them and run the process again.

Possible problems might be: Configuration does not fulfill the master data requirements (CATT and manual processing of the transaction would also fail) External master data file is not stored as tab separated file. Other data inconsistencies

Result
You have created the desired routing (s).

6. Importing Workcenter Master Data

Use
The purpose of this activity is to import workcenter master data via LSMW using Direct Input.

Prerequisites
You have imported the LSMW project BP_AIO into your system.

Specifying LSMW Project Details

1. Access the activity using the following transaction code:

Transaction Code

LSMW

2. Confirm the information message Welcome to the Legacy System Migration Workbench. 3. On the Legacy System Migration Workbench screen, enter the following values:

Field name PROJECT

Description Name of data transfer project

User action and values BP_AIO

Notes More than one subproject can be assigned to a project. A subproject can have an unlimited number of objects An object is assigned to a subproject

SUBPROJ

Specifies the name of the subproject

PP

OBJECT

Object name. An object WCENTER corresponds to a business object.

4. Choose Continue. The LSM Workbench: BP_AIO PP Workcenter & Resource screen is
displayed. You can change the default view from display mode to change mode. To do this, choose Double Click=Display.

Specifying an External File

If an external file has already been specified, only change the file name of the existing file. Do not add or create any additional files.

1. In the LSM Workbench: BP_AIO, PP, Workcenter & Resource screen, start the process
step Specify Files and go into change mode, if you are in display mode.

2. In the LSM Workbench; Specify Files (Change) view, go to the structure item Legacy
Data - On the PC (Frontend). Double-click on the object file entry that is located directly under Legacy Data - On the PC (Frontend). The File on Front End: Maintain Properties entry screen is displayed. Enter the following values:

Field name File

Description LSMW data file name Object type

User action and values Specify the path and name of the external data file or browse for the external data file Specify the name of the object type Select the radio button Data for Multiple Source Structures (Sequential Files)

Notes

Name File Contents

Separators

Tabulator

Check file for separators, if necessary

File Structure

Choose Field Order matches source structure definition Select the radio button Record End Marker (Text File) Select ASCII

File Type

Code Page

3. Choose Continue, save your file settings and choose Back.

Assigning a File

Omit this activity if an external file has already been specified and assigned. 1. To assign an external file, double-click on the process step Assign File. 2. In the LSM Workbench: Assign File view, select the first line highlighted in yellow and choose Assignment. The file you have specified in the previous step is assigned. Repeat this for each entry highlighted in yellow until you have assigned the file assigned to each structure.

Importing Data from Files

1. To import the data from the assigned files, double-click on the process step Import Data.
2. Choose Execute without entering any values. Go back to the Process Step list.

Converting Imported Data

1. To convert the imported data, double-click on the process step Convert Data. 2. Choose Execute without entering any data. Go back to the Process Step list.

Running Direct Input Session

1. Double-click the step Start Direct Input Program. 2. On the Data transfer of Routings via Direct input screen, enter the file name 3. 4. 5.
BP_AIO_PP_WCENTER.lsmw.conv, which contains the converted data you have imported in the step Importing Data from Files. Choose Execute. A log is displayed by the system. Check error messages. Choose Back. In the event of errors, solve the errors and run through the process again.

Possible problems might be:

Configuration does not fulfill the master data requirements (CATT and manual processing the transaction would also fail) External master data file is not stored as tab separated file Other data inconsistencies

Result
You have created the desired workcenters.

7. Importing QM Workcenter Master

Data Use
The purpose of this activity is to import QM workcenter master data via LSMW using Direct Input.

Prerequisites
You have imported the LSMW project BP_AIO into your system.

Specifying LSMW Project Details

1. Access the activity using the following transaction code:

Transaction Code

LSMW

2. Confirm the information message Welcome to the Legacy System Migration Workbench. 3. On the Legacy System Migration Workbench screen, enter the following values:

Field name PROJECT

Description Name of data transfer project

User action and values BP_AIO

Notes More than one subproject can be assigned to a project. A subproject can have an unlimited number of objects An object is assigned to a subproject

SUBPROJ

Specifies the name of the subproject

PP

OBJECT

Object name. An object WCENTER corresponds to a business object.

4. Choose Continue. The LSM Workbench: BP_AIO PP Workcenter & Resource screen is
displayed.

You can change the default view from display mode to change mode. To do this, choose Double Click=Display.

Specifying an External File

If an external file has already been specified, only change the file name of the existing file. Do not add or create any additional files.

1. In the LSM Workbench: BP_AIO, PP, Workcenter & Resource screen, start the process
step Specify Files and go into change mode, if you are in display mode.

2. In the LSM Workbench; Specify Files (Change) view, go to the structure item Legacy
Data - On the PC (Frontend). Double-click on the object file entry that is located directly under Legacy Data - On the PC (Frontend). The File on Front End: Maintain Properties entry screen is displayed. Enter the following values:

Field name File

Description LSMW data file name Object type

User action and values Specify the path and name of the external data file or browse for the external data file Specify the name of the object type Select the radio button Data for Multiple Source Structures (Sequential Files) Tabulator

Notes

Name File Contents

Separators

Check file for separators, if necessary

File Structure

Choose Field Order matches source structure definition Select the radio button Record End Marker (Text File) Select ASCII

File Type

Code Page

3. Choose Continue, save your file settings and choose Back.

Assigning a File

Omit this activity if an external file has already been specified and assigned. 1. To assign an external file, double-click on the process step Assign File. 2. In the LSM Workbench: Assign File view, select the first line highlighted in yellow and choose Assignment. The file you have specified in the previous step is assigned. Repeat this for each entry highlighted in yellow until you have assigned the file assigned to each structure.

Importing Data from Files

1. To import the data from the assigned files, double-click on the process step Import Data.
2. Choose Execute without entering any values. Go back to the Process Step list.

Converting Imported Data

1. To convert the imported data, double-click on the process step Convert Data. 2. Choose Execute without entering any data. Go back to the Process Step list.

Running Direct Input Session

1. Double-click the step Start Direct Input Program. 2. On the Data transfer of Routings via Direct input screen, enter the file name 3. 4. 5.
BP_AIO_PP_WCENTER.lsmw.conv, which contains the converted data you have imported in the step Importing Data from Files. Choose Execute. A log is displayed by the system. Check error messages. Choose Back. In the event of errors, solve the errors and run through the process again.

Possible problems might be: Configuration does not fulfill the master data requirements (CATT and manual processing the transaction would also fail) External master data file is not stored as tab separated file. Other data inconsistencies

Result
You have created the desired QM workcenters.

8. Importing Resource Master Data

Use
The purpose of this activity is to import resource master data via LSMW using Direct Input.

Prerequisites
You have imported the LSMW project BP_AIO into your system.

Specifying LSMW Project Details

1. Access the activity using the following transaction code:

Transaction Code

LSMW

2. Confirm the information message Welcome to the Legacy System Migration Workbench. 3. On the Legacy System Migration Workbench screen, enter the following values:

Field name PROJECT

Description Name of data transfer project

User action and values BP_AIO

Notes More than one subproject can be assigned to a project. A subproject can have an unlimited number of objects An object is assigned to a subproject

SUBPROJ

Specifies the name of the subproject

PP

OBJECT

Object name. An object WCENTER corresponds to a business object.

4. Choose Continue. The LSM Workbench: BP_AIO PP Workcenter & Resource screen is
displayed. You can change the default view from display mode to change mode. To do this, choose Double Click=Display.

Specifying an External File

If an external file has already been specified, only change the file name of the existing file. Do not add or create any additional files.

1. In the LSM Workbench: BP_AIO, PP, Workcenter & Resource screen, start the process
step Specify Files and go into change mode, if you are in display mode.

2. In the LSM Workbench; Specify Files (Change) view, go to the structure item Legacy
Data - On the PC (Frontend). Double-click on the object file entry that is located directly under Legacy Data - On the PC (Frontend). The File on Front End: Maintain Properties entry screen is displayed. Enter the following values:

Field name

Description

User action and values

Notes

File

LSMW data file name Object type

Specify the path and name of the external data file or browse for the external data file Specify the name of the object type Select the radio button Data for Multiple Source Structures (Sequential Files) Tabulator Check file for separators, if necessary

Name File Contents

Separators

File Structure

Choose Field Order matches source structure definition Select the radio button Record End Marker (Text File) Select ASCII

File Type

Code Page

3. Choose Continue and save your file settings and choose Back.

Assigning a File

Omit this activity if an external file has already been specified and assigned. 1. To assign an external file, double-click on the process step Assign File. 2. In the LSM Workbench: Assign File view, select the first line highlighted in yellow and choose Assignment. The file you have specified in the previous step is assigned. Repeat this for each entry highlighted in yellow until you have assigned the file assigned to each structure.

Importing Data from Files

1. To import the data from the assigned files, double-click on the process step Import Data.
2. Choose Execute without entering any values. Go back to the Process Step list.

Converting Imported Data

1. To convert the imported data, double-click on the process step Convert Data. 2. Choose Execute without entering any data. Go back to the Process Step list.

Running Direct Input Session

1. Double-click the step Start Direct Input Program. 2. On the Data transfer of Routings via Direct input screen, enter the file name 3. 4. 5.
BP_AIO_PP_WCENTER.lsmw.conv, which contains the converted data you have imported in the step Importing Data from Files. Choose Execute. A log is displayed by the system. Check error messages. Choose Back. In the event of errors, solve the errors and run through the process again.

Possible problems might be: Configuration does not fulfill the master data requirements (CATT and manual processing of the transaction would also fail) External master data file is not stored as tab separated file. Other data inconsistencies

Result
You have created the desired resources.

5. CATT Procedures

Use
A CATT (Computer Aided Test Tool) procedure is a series of recorded transactions. CATTs are used by SAP Best Practices because they enable the automated creation and maintenance of master data during installation. The following section only describes how to execute CATTs during the installation of SAP Best Practices. If you want to find out more about CATTs (how to create CATTs, and so on), refer to the Vertical Solution Development Toolkit.

Features
There are two types of CATT procedures: CATTs that run with external variants and CATTs that run with internal variants. External CATT variants

External CATT variants contain the data you want to upload into the system. Here, you have the option to use the sample data delivered by SAP Best Practices. In this case you do not have to make any changes to the data. Alternatively, you have the option to use the CATTs to upload your own master data. In this case, you have to maintain the external variants first, before you proceed with the CATT execution. External variants are stored in a spreadsheet file and can easily be modified using spreadsheet applications. Internal CATT variants

Internal CATT variants are attached to the CATTs themselves. They contain predefined values, which the CATT will use during the execution. The user is not supposed to change the internal variants.

Activities
First, you decide whether you are going to work with your own master data or the master data delivered by SAP Best Practices. If you want to use you own master data, you will have to maintain the relevant external variants before you start with the installation. Then you go to the installation role, open the desired transaction and start the CATT execution. If errors occur during the execution, you can check them in the CATT activation log.

1. Maintaining External Variants

Use
To enable the CATT procedure to import your own master data into the system, you need to maintain the external variants delivered for your scenario. To avoid unnecessary delays during the installation, it is recommended to maintain the CATT variants before you start the installation procedure. To help you maintain external variants of CATT procedures, master data conversion forms are delivered for every CATT procedure. Conversion forms describe the basic function of the CATT procedure and provide detailed information for the parameters included in the external variant. The external variants are delivered as a .txt file and as an .xls file. Use the .xls file to edit the CATT variants. After editing, always save the file in .txt format. The files for the external CATT variants can be found on the documentation CD in the Variants directory.

Procedure
1. Open the file with MS Excel.
2. Fill or modify the tables with your own specific data. MS Excel enables you to maintain your master data very flexibly. However, to ensure a successful data import, there are a few rules that you should follow: o The first three rows of the worksheet must not contain any master data. The fourth row in the worksheet is the first that the CATT will read for real data. The first three lines contain: Line 1: the variable name (do not change) Line 2: the variable description (you can change the description) Line 3: the variable default value (you can change the value) The sequence of the columns is not fixed. You can move the sequence if necessary. You can add columns as you like. If the name of the variable in the new column is not the same as the name of a variable in the CATT, the system will ignore this column. Therefore, you may add a column called COMMENT, for example. There must be no duplicate variables in the Excel worksheet!!!

o o

You can delete columns as you like. If the CATT does not find any value for a variable, it uses the default value defined in the CATT. If the column for a variable is empty, the CATT will not pick anything. If you set then the CATT sets a blank value in this field. All Excel fields should be formatted as TEXT. Otherwise, for example, fields that contain 0001 will be converted to 1, and 01-01-01 will be converted to January 1, 2001. Even fields that contain numbers should be formatted as textfields.

3. After entering all your master data in the external variant file, choose Save As to save
your changes and save in .txt format.

2. Executing CATT Procedures

Use
You activate CATT procedures to import the master data contained in the CATT variants. You will start the CATT by opening a transaction in the installation role. The CATT will run in the background. It is sometimes possible to run a CATT in the foreground, but this alternative is not recommended. The CATTs are not tested for running in the foreground. This option is timeconsuming and is only used for troubleshooting purposes.

Prerequisites
If you want to activate a CATT procedure with an external variant, make sure that you have maintained the external CATT variant file with your own master data in advance.

Using External CATT Variants

1. In the installation role, run the installation role activity to start the CATT procedure.
The Start CATT Procedure using external variants view is displayed.

2. In the File Name for Variants field, enter the correct path description for the .txt file that
you have modified, for example C:\BP_txt_files\ATP_C002_Agro.txt. You can also use the browser to select the required .txt file. To do this, choose Choose and browse for the directory where you have stored the .txt files.

If the path description is too long and contains more than four or five subdirectories, the CATT procedure may not run successfully. To avoid this problem, store your .txt files in a directory that does not exceed the fourth level in the folder structure.

Please make sure that the path defined is in English, in case of Korean path there may be errors for some CATT,

3. Double-click on the relevant .txt file.

4. Choose Execute to start the CATT procedure /SMB02/RBA04_C002. 5. Check the CATT log and go back to the installation role.

Using Internal CATT Variants

1. In the installation role, double-click on the activity to start the associated CATT
procedure.

2. The CATT procedure is usually processed in the background. 3. Alternatively, you will have to press Execute to start the CATT procedure. When the import has been completed, the CATT log is displayed. 4. Check the CATT log and go back to the installation role.

Result
You have imported the master data contained in the CATT variant and covered by the activity you have chosen from the installation role. You can now proceed with the next activity.

3. Displaying the CATT Log

Use
To analyze the CATT procedure results, you can display the logs of the various CATT procedures by executing the report RSCATPRO.

Procedure
1. To execute this report, choose one of the following options:

SAP Menu path

SAP Easy Access Menu Tools ABAP Workbench Development ABAP Editor SE38

Transaction Code

2. Enter the following values:

Field Program

Value RSCATPRO

Source code

3. Choose Execute and enter your selection criteria. 4. Choose Execute.

Result
A list of CATT procedures is displayed from which you can select those you are interested in and display the corresponding logs.

4. Analyzing the CATT Log

If there are any error messages in the CATTs final log file, you can analyze them as follows.

Procedure
1. Position the cursor on the log entry with the error (marked red in the log file) on the 2.
Transaction Code level (TCD). Restart the CATT procedure directly from the log file by choosing Restart (F8).

5. Run the selected CATT with the processing mode Foreground and the log type Long. 7. Choose Enter. Go through the procedure step by step by choosing Enter. 8. Analyze the problems that appear and check for additional information in the related
documents and SAP Notes.

6.

SAP Best Practices: Installation Preparation

Prior to the installation of any individual building blocks, you must refer to and follow the instructions in the document Importing Best Practices Add-Ons (ADDONINS.PDF) on the configuration CD. This explains the installation of the objects required for the installation of the building blocks. In addition, this following section contains certain activities that have to be performed before installation of building blocks.

1. Support Package Level

The deliverables of SAP Best Practices were developed and tested in a system landscape with a specific support package level. If the support package level in your system is different, there could be errors during the SAP Best Practices installation. For details of the support package in question, see the document Importing Best Practices Add-Ons (ADDONINS.PDF) on the configuration CD. If you have a different support package level, you may be able to perform the installation activities manually using the configuration guides, but errors are still possible.

Component SAP_BASIS SAP_ABA SAP_APPL SAP_HR EA-IPPE PI PI_BASIS EA-APPL EA-FINSERV EA-GLTRADE EA-HR EA-PS EA-RETAIL

Release 620 620 470 470 200 2003_1_470 2003_1_620 110 110 110 110 110 110

Patch Level 32 32 15 23 8 5 5 15 15 15 23 15 15

2. SAP Notes
The following SAP Notes must be implemented for this installation.

SAP Note #

Description

Component

556497 619986 625525 633185 634574 642899

ALV grid and fullscreen: Short dump with colors Several digital signatures in the PI sheet Termination in SAPMC29C Cost analysis: Authorization check for valuation view BC Sets: Error when writing activation links (293) Data_length_0 dump when activating or comparing BC Sets Cost analysis: authorization check for valuation view Short dump with BC Set activation: CX_SY_OFFSET_NOT_ALLOWED BC Set activation: Message VT328 and VT329 Menu texts and title texts in incorrect language Short dump in the BC Set overall view through conversions Short dump of document flow display in SD Short dump during billing w/ down payment clearing Short dump if BADI method AT-Release is not implemented Final confmtn: W-Mssg BS013 System status & is active (&) Short dump / syntax error in function group CRMA Correction to BC Sets: Transporting data after

BC-SRV-ALV PP-PI-PMA-RCP LO-ECH CO-PC-IS BC-CUS-TOL-BCD BC-CUS-TOL-BCD

646404 647964

CO-PC-IS BC-CUS-TOL-TME

650035 624095 631075

SD-SLS-GF-CU BC-DWB-TOO-MEN BC-CUS-TOL-BCD

627961 635350 631353

SD-SLS-GF-RE SD-BIL-IV-DP SCM-EM-AS

638826

CO-OM-ACT-E

677788 679702 687685

SD-SLS BC-CUS-TOL-BCD

AW01N: Termination w/ error message in Asian logon FI-AA-IS

It may be that other issues become apparent after shipment of SAP Best Practices (and this document). An additional SAP Note exists to cover such eventualities. Before you start the

installation process, check the latest version of SAP Note 695326 to obtain updates and corrections for problems that do not become apparent until after shipment. If you cannot find a solution for the problem this way, open a customer message specifying the component SV-SMB-AIO-BP-KR.

3. Activating Extension Sets

Use
The purpose of this activity is to activate extension sets. This makes various technical settings including extensions to menus, the application component hierarchy, and the IMG.

Procedure
1. Access the activity as follows:

Transaction Code IMG Menu Continue.

SPRO Activation Switch for SAP R/3 Enterprise Extension Set

2. Confirm the message Caution: The table is cross-client by choosing 3. In the table displayed, select the check boxes in the Active column for the following
applications:

EA-PLM EA-SCM EA-TRV

PLM Extension SCM Extension Travel Management Extension

4. Choose Save. 4. Activating Languages for BC Set Activation

Use
The purpose of this activity is to define and activate the languages that are to be used when you activate BC Sets in the installation process. The settings described in the procedure are client-specific.

Procedure

1. Access the following transaction in your SAP System:

Transaction Code 2. Choose Utilities System Settings.

SCPR20

3. In the BC Sets: Display System Settings view, choose Change. 4. In the Languages section, select the languages that are required for BC Set activation in your system. 5. Save.

Result
When you activate BC Sets during the installation process, the system displays languagedependent values only in those languages that you have selected. In addition, only these languages will be installed.

5. Setting Up Printer

If printer LOCL has not yet been set up in the system, you can set it up directly using transaction SPAD.