quick guide to installing the sap best practicesbaseline package

7/28/2019 Quick Guide to Installing the SAP Best PracticesBaseline Package

http://slidepdf.com/reader/full/quick-guide-to-installing-the-sap-best-practicesbaseline-package 1/16

EHP6 for SAP ERP6.0

April 2012

English

SAP Best Practices Tools

SAP AGDietmar-Hopp-Allee 1669190 Walldorf Germany



SAP Best Practices SAP Best Practices Tools

© SAP AG of 16

Copyright

© 2012 SAP AG. All rights reserved.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,

StreamWork, SAP HANA, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions,Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as wellas their respective logos are trademarks or registered trademarks of Business Objects Software Ltd.Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products andservices mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc. Sybase is an SAP company.

Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Datacontained in this document serves informational purposes only. National product specifications mayvary.

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




© SAP AG of 16

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include fieldnames, screen titles, pushbuttons as well as menu names, paths andoptions.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.EXAMPLE TEXT Names of elements in the system. These include report names,

program names, transaction codes, table names, and individual keywords of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths,messages, source code, names of variables and parameters as well asnames of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the

ENTER key.

Example text Exact user entry. These are words or characters that you enter in the

system exactly as they appear in the documentation.

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




© SAP AG of 16

Content

1 Essential Information .......................................................................................................... 5 1.1 Purpose .................................................................................................................... 5 1.2 SAP Best Practices: Overview ................................................................................. 5

1.2.1 Building Blocks: Concept ..................................................................................... 6 1.2.2 Building Blocks: Activation ................................................................................... 6 1.2.3 Technical Prerequisites for Activation .................................................................. 6

1.3 SAP Best Practices: Documentation ........................................................................ 7 1.3.1 Document Types and Content ............................................................................. 7

1.4 SAP Best Practices: Tools ....................................................................................... 8 1.4.1 Activation ............................................................................................................. 8

1.4.1.1

SAP Best Practices Solution Builder ............................................................... 8

1.4.2 eCATT Procedures .............................................................................................. 8 1.4.2.1 eCATT Objects ................................................................................................ 8 1.4.2.2 Executing eCATT Procedures ......................................................................... 9 1.4.2.3 Running an eCATT in Foreground Mode ...................................................... 10 1.4.2.4 Displaying and Printing eCATT Logs ............................................................ 10

1.5 Analyzing the Master Data Installed ...................................................................... 10 1.5.1 Master Data Implemented by eCATTs .............................................................. 11 1.5.2 Maintaining Master Data created by eCATTs .................................................... 12

1.6 Business Configuration Sets .................................................................................. 13 1.6.1 Displaying BC Set Contents .............................................................................. 14 1.6.2 Comparing BC Set Content with Customizing Tables ....................................... 14 1.6.3 Activating a BC Set ............................................................................................ 14 1.6.4 Displaying the Activation Log ............................................................................. 16




© SAP AG of 16

1 Essential Information

1.1 PurposeThis document:

Is a generic document applying to all SAP Best Practices. For specific Activationinformation, such as which SAP Notes or Support Packages are required, refer to theQuick Guide for the SAP Best Practices in question. The Quick Guide is available onthe documentation DVD/CD.

Is intended for consultants and system administrators who are involved in an SAPBest Practices Activation

Introduces the concept of SAP Best Practices and provides an overview of thebuilding block approach

Shows you how to use the configuration tools, such BC Sets, eCATTs, thePersonalization Wizard, and the SAP Best Practices solution builder

Shows you how to use the documentation delivered

SAP Best Practices Activations can be modified. For detailed instructions on how tomodify SAP Best Practices deliverables, see the documentation provided in theVertical Solution Development Kit (VSDK).

1.2 SAP Best Practices: OverviewSAP Best Practices provide a time-saving and cost-saving methodology for implementing SAPsolutions. SAP Channel Partners can benefit from this methodology by using SAP BestPractices 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 thedocumentation that you need for a fast and smooth implementation.

The Activation time is reduced considerably by the use of automated configuration toolssuch as the Best Practices solution builder , which utilizes other technologies (BC Sets andeCATTs) for rapid Activation.

The transfer and generation of master data is accelerated and facilitated by the use of automated procedures known as eCATT procedures (extended CATT ). This tool allows youto modify and import customer-specific master data into an SAP system.

The Best Practices solution builder accelerates implementation time by automating systemconfiguration steps. Instead of clicking through roles, you can activate a project that willperform the Activation of a SAP Best Practices in a fraction of the time it used to take.

Comprehensive documentation is provided for all Activation activities.

The deliverables for SAP Best Practices are provided on a documentation DVD/CD and aconfiguration CD.

The documentation DVD/CD contains:

Scenario overviews

Building block/scenario descriptions




© SAP AG of 16

Configuration guides

Business Process Documentations

Best Practices solution builder

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

1.2.1 Building Blocks: Concept

The building block concept offers substantial benefits with respect to the development,distribution, and sale of solutions.

Building blocks:

Are reusable, business process-oriented, preconfiguration units, which you simply have toassemble to obtain your desired Activation.

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 canbe used in many solutions, such as the building block for Financial Accounting. Thesegeneric building blocks belong to the so-called layer 0 (see SAP Best Practices BaselinePackage below) and help to reduce redundancy.

Enable SAP Channel Partners to focus on the development of the specific verticalconfiguration requirements of each customer.

1.2.2 Building Blocks: Activation

To install SAP Best Practices using building blocks, you install a number of building blocks in apredefined sequence using the various tools and documentation provided.

1.2.3 Technical Prerequisites for Activation

Details on the technical prerequisites for Activation of SAP Best Practices can be found in theQuick Guide document.




© SAP AG of 16

1.3 SAP Best Practices: Documentation

1.3.1 Document Types and Content

Each building block has various documents that describe the business content, Activation, andtesting procedures.

The following table gives you an overview of the documentation delivered on the SAP BestPractices documentation DVD/CD.

DocumentType

Purpose FileFormat

Scenario

Overview

Provides a graphical overview of a scenario. MSPowerPoint

Scenario/Building

Block Descr ipt ion

Briefly describes the content of a scenario or building block

and shows its benefits. This is not a document as such, butappears as HTML content on the documentation DVD/CD.

HTML

Conf igurat ion

Guide

Each building block has a configuration guide, whichdescribes:

The manual configuration steps you have to perform if you do not want to use the automated Activation tools,but prefer to set up the configuration of a building blockmanually.

Configuration details for reviewing the system settingsand obtaining additional information on the automated

Activation procedures.

For each step in the SAP Best Practices solution builder scenario, you can find the corresponding manualimplementation information in the configuration guide. AsBC Sets are packages of Customizing settings, you mayfind several sections in the configuration guidecorresponding in total to one step in the solution builder scenario.

The configuration guide describes the activities in thelogical order of the implementation process.

MS Word

Business

Process

Documentat ion

End-user documentation providing detailed, application-focused descriptions of business processes. Used for testing scenarios.

MS Word

In addition to these documents found on the documentation DVD/CD, there is also adocument on the configuration CD entitled Importing Best Practices Add-Ons and Add. Transports for mySAP All-in-One (file name ADDONINS.PDF). This documentcontains essential technical information required before installing any buildingblocks.




© SAP AG of 16

1.4 SAP Best Practices: Tools

1.4.1 Activation

Using the SAP Best Practices solution builder, you can activate the complete SAP BestPractices Baseline Package easily and quickly. Of course, you can also choose to install onlyselected SAP Best Practices scenarios. The Activation process is guided by a step-by-stepapproach, and is easy to understand. Large parts of the Activation have been automated andcan be run unattended.

1.4.1.1 SAP Best Practices Solution Builder

The SAP Best Practices solution builder is a tool that enables you to personalize and install theSAP Best Practices rapidly. The tool automates Activation of SAP Best Practices packages,saving time during implementation and reducing possibility of errors. By importing predefinedscenarios, you can quickly activate SAP Best Practices in your system. The solution builder provides activity tracking and logging, so that you can easily troubleshoot any problems.

1.4.2 eCATT Procedures

The Extended Computer Aided Test Tool (eCATT) is a new automated testing tool that allowsyou to create automated functional test cases for the majority of applications running in the SAPGUI for Windows and SAP GUI for Java environments. Like other test tools, it works by makinga recording of an application, which you can then parameterize and replay with differing sets of input values. You can test the behavior of the application by reading and testing the valuesreturned by the application.

The eCATT differs from external tools in that it provides full access to the application server anddatabase layers of the system, allowing you test function modules and BAPIs, perform checksagainst the database, and interrogate or simulate changes to customizing settings.

1.4.2.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 withoutfurther 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 testscript. This item is not used with SAP Best Practices, but is mentioned on the initial eCATTscreen.




© SAP AG of 16

Versions and Variants

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

Transport and Download

All eCATT objects are Repository objects. Therefore, you can take advantage of the standardSAP transport tools.

You can also download an eCATT object to a file, which can be later uploaded into another system.

BC Sets and eCATTs

A recent change to the eCATT technology allows BC Sets to be run from an eCATT. Thismethod allows for greater automation of Activation and customization. Variable field values thatwere formerly entered in a dialog box during task execution (such as company code, plant, and

so on) can now be maintained in text files prior to Activation.

Naming Convention

There is no specific naming convention for eCATT objects. Names are alphanumeric strings upto 30 characters long, and are not case-sensitive.

1.4.2.2 Executing eCATT Procedures

Use

eCATT (extended Computer Aided Test Tool) procedures enable you to create and executefunctional 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.40.

Procedure

1. Access the transaction choosing one of the following navigation options:

Menu path Tools ABAP Workbench Test Test Workbench Test

Tools Extended CATT

Transaction code SECATT

2. On the Extended Computer Aided Test Tool: Initial Screen, in the Test Configuration field,enter the technical object name of the eCATT.

The eCATT's technical object name can be found in the building block ‟s activity(solution builder). You can expand a project or building block in the Best Practicessolution builder, look for the eCATT task, then highlight the technical object nameand copy it to the clipboard with CTRL-C.

To determine if your eCATT has an internal variant, in the Best Practices solutionbuilder, right-click the eCATT task in the project and choose Details. A dialog box

will display the filename of the external text file, or in the case of internal variants, anasterisk (*). If your eCATT has an internal variant (*), pay attention to step 5 below.

http://help.sap.com/sapdocu/core/47x200/HELPDATA/EN/63/77c13b9e6c2623e10000000a11402f/content.htm

http://help.sap.com/sapdocu/core/47x200/HELPDATA/EN/63/77c13b9e6c2623e10000000a11402f/content.htm




© SAP AG of 16

3. Choose Execute.

4. On the Start Options screen, choose the Variants tab.

5. If your eCATT has internal variants, deselect ECATTDEFAULT in the lower pane.

6. Choose Execute.

7. If any error messages appear within the log, you will need to correct them before being ableto execute the procedure successfully.

1.4.2.3 Running an eCATT in Foreground Mode

Use

This activity provides instructions on how to run the eCATT in the foreground mode.

Procedure

1. On the Start eCATT Testconfiguration screen, select Display Start Options.

2. Choose the Execute button.

3. On the following screen, choose the UI Control tab.

4. In the TCD box, in Start Mode for Command TCD, use the dropdown to select A Process inForeground, Synchronous Local .

1.4.2.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, choose Logs. The eCATT Log Selection screen appears.

2. Enter your selection criteria and choose Execute. A list of all the logs that satisfy theselection criteria is displayed.

3. In the Activity no column, click the number of the log that you want to display. The log isdisplayed 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 onthe 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.

1.5 Analyzing the Master Data Installed

Master data is very individual data, which has to be adapted to customer needs on a projectbasis. For this reason, no dedicated documentation for the sample master data delivered bySAP Best Practices is provided. However, all activities for implementing the various kinds of master data can easily be identified in the Business Process Documentation documents.




© SAP AG of 16

This section explains how to retrieve information about the sample master data based on thetype of tool used for the automated Activation (eCATT; encapsulated data).

1.5.1 Master Data Implemented by eCATTs

An eCATT is called by a parameter transaction within the Best Practices solution builder. Theobject called is usually an eCATT test configuration (see eCATT Objects for further information).

The sample data is encapsulated in eCATT objects. The following procedures explain how youcan identify the master data that is included in eCATT objects.

Procedures

The data applied by an eCATT test configuration is defined in the variants of the testconfiguration. These variants can contain either the explicit data values or references to valuesin a test data container. These two alternatives are explained in the following procedures.

A: Explicit Data in Test Configurations

1. In the Best Practices solution builder, locate the eCATT task you want to display. Expandthe project node, highlight the task, then copy the name to the clipboard using CTRL-C.

2. Access the transaction choosing one of the following navigation options:

Menu path Tools ABAP Workbench Test Test Workbench Test Tools Extended CATT

Transactioncode

SECATT

3. Select Test Configuration and paste the name of the test configuration in the field using

CTRL-V.

4. Choose Display Object .

5. On the Variants tab, the data applied is displayed as a table. The column Variant corresponds to the field Variant described in step 2 (an asterisk „*‟ means all variants).

B: Referenced Data in Test Configurations

1. Perform steps 1-5 above.

2. Some values in the variant may have the format<Parameter Name>(<Test Data Container Alias>, <Variant>). This is a reference to a valuein a test data container and is read as follows: Insert the value of the cell from the test datacontainer <Test Data Container Alias> that is identified by the parameter <Parameter

Name> (column) and the variant <Variant> (line).

3. Choose the Configuration tab.

4. The test data container(s) linked to the test configuration is/are displayed in the lower section of the tab page. Both the alias and the technical name of each test data container are displayed.

5. Double-click the technical name of the test data container that corresponds to the test datacontainer alias of step 2. The test data container opens.

6. Choose the Variants tab.

7. Identify the referenced value of step 2 as intersection of <Variant> and <Parameter Name>.




© SAP AG of 16

By referencing parameter values in the test configuration to test data containers,you can maintain central data sets without redundancy (relational data model).

See Personalizing eCATT Procedures for a description of how to modify test datacontainers.

1.5.2 Maintaining Master Data created by eCATTs

External variant files contain the data you want to upload into the system. Here, you have theoption to use the sample data delivered by SAP Best Practices. In this case you do not have tomake any changes to the data. Alternatively, you have the option to use the eCATTs to uploadyour own master data. In this case, you have to maintain the external variants first, before youproceed with the eCATT execution.

External variants are stored in a spreadsheet file and can easily be modified using spreadsheetapplications.

Activities

First, you decide whether you are going to work with your own master data or the master datadelivered by SAP Best Practices. If you want to use you own master data, you will have tomaintain the relevant external variants before you start with the Activation. To avoidunnecessary delays during the Activation, it is recommended to maintain the eCATT variantsbefore you start the Activation procedure.

The external variants are delivered as a .txt file. After editing, always save the file in .txt format.

The files for the external CATT variants can be found on the documentation DVD/CD in the

relevant subfolder of the Variants folder.

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, toensure a successful data import, there are a few rules that you should follow:

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. Thefirst 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 columnis not the same as the name of a variable in the CATT, the system will ignorethis column. Therefore, you may add a column called COMMENT, for example.

There must be no duplicate variables in the Excel worksheet.




© SAP AG of 16

You can delete columns as you like. If the CATT does not find any value for avariable, it uses the default value defined in the CATT. If the column for avariable is empty, the CATT will not pick anything. If you set „ „ then the CATTsets 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 astext-fields.

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

1.6 Business Configuration Sets

Use

A Business Configuration Set (BC Set) is a package of Customizing settings. BC Sets are usedto accelerate the Activation process of the building blocks and scenarios delivered with SAPBest Practices.

In SAP Best Practices starting with release ECC 5.00, BC Sets are embedded inside eCATTs toallow for greater automation of Activation activities. In previous Best Practices deliveries,variable field values were entered in a dialog box for each task during Activation (such ascompany code, production plant, and so on). Those values are now maintained in global textfiles that are read by the eCATTs that implement the BC Sets.

The following section only describes how to activate BC Sets during the SAP Best Practices

Activation. If you want to find out more information about BC Sets (how to create your own BCSets, and so on), refer to the Vertical Solution Development Kit .

BC Sets are used to accelerate the Activation process. For each BC Set step in themaster list or BPIA project, there is corresponding information in the configurationguide 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 containsfixed 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 settings can bechanged in the /SMB99/ text files included on the Documentation DVD/CD.

BC Sets are stored inside of eCATTs, which are on the configuration CD together with other objects. Installing the SAP Best Practices Add-On imports the configuration into the relevantsystem. 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.

The Best Practices solution builder handles activation of BC Sets by using eCATTs. However, if you want to activate a BC Set manually, or you are troubleshooting a BC Set failure, thefollowing information may be useful:

Display the BC Set contents

Compare BC Set content with the Customizing table




© SAP AG of 16

Activate the BC Set

Check the activation log to confirm the successful activation

These steps are described in detail below.

1.6.1 Displaying BC Set Contents1. From the SAP Best Practices solution builder, in an eCATT display log, expand the

Customizing changes with BC-Sets node.

2. Locate the BC-Set you want to view, then click it.

3. The Business Configuration Set: Display Only screen is displayed.

4. On the right pane, locate the BC Set you want to view, then double-click it. The right panedisplays table and view data.

1.6.2 Comparing BC Set Content with Customizing Tables

1. In the Business Configuration Set: Display only screen, choose Compare with system

tables and variable query (Ctrl + F9).

2. Compare the values of the BC Set to those of the Customizing table(s). Depending onwhether you are comparing a BC Set with fixed or with variable values, one of the followingdescriptions applies:

BC Sets with fixed values BC Sets with variable values

If you are comparing a BC Sets withoutvariable values, the view BC Set: Comparewith customizing table contents isdisplayed.

Different colors in the table view indicate

various details about a field and its values,for example, whether the fields copied fromthe BC Set into your Customizing tables aredata fields or key fields and whether theycontain fixed or variable values.

Choose Display color legend from theapplication toolbar for details. The first linein the table shows the BC Set data, thesecond line the existing entries in theCustomizing table.

If you are comparing a BC Set with variablevalues, the Enter Variable Fields Values table is displayed.

The Fields column lists the fields into whichthe BC Set will insert variable values. In the

Value section, the default values which willbe entered by the BC Set are displayed.

Choose Display color legend from theapplication toolbar for details. The first linein the table shows the BC Set data, thesecond line the existing entries in theCustomizing 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 manuallyaccording to the corresponding instructions in the building block‟s configurationguide.

1.6.3 Activating a BC Set

Prerequisites

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

You must also activate the languages that are to be used when you activate BC Sets in the

Activation process. The system displays language-dependent values only in the languages youselect. In addition, only these languages are installed. To do this, proceed as follows:




© SAP AG of 16

1. Access the following transaction:

Transaction Code SCPR20

2. Choose Utilities System Settings.

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

5. Choose Save.

Note that this language setting is client-specific.

Procedure

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

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

BC Sets with fixed values BC Sets with variable values

If a request for Customizing is displayed,proceed with step 3.

If the Enter Variable Field Values table isdisplayed, you can copy or change thedefault values in the Value column.

1. Change the default values, if necessary.

2. 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 inadvertentlyoverwrite existing entries. The message Activation successfully completed is displayed.

5. The message Activation successfully completed appears.

Sometimes the BC Set activation ends with a warning message. If you check theactivation 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.

The warning message View cluster table XY does not contain data at all levels can

also be ignored. During the creation of a BC Set, all views/tables for the selectedCustomizing activity are assigned to the BC Set. However, only some of theseviews/tables may be relevant and the others remain empty. These emptyviews/tables will cause this error.

The warning message Not all data was activated in all languages can be ignored aslong as your language has been activated. If languages are selected in your user

settings which are not defined in the BC Set, you may receive this error. Complete acomparison between the table and the BC Set to show if a difference in your




© SAP AG of 16

languages exists. To avoid these errors, change your user settings to include onlyyour relevant language. For example, the Baseline Package (Germany) BC Setsmay contain only English and German languages. If another language is alsoselected in your user settings, you may receive this error.

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 Sethierarchies, a BC Set activation may end with warnings or errors. In case of error messages, you may repeat the activation of the BC Set. You can, however, alsoactivate each of the lower-level BC Sets of a hierarchical BC Set individually toactivate the settings successfully.

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

If there are differences, repeat the activation. You may find that only descriptionfields differ that had been set during a previous activation of a BC Set or manualconfiguration step. In this case the differences are not critical.

Error messages and warnings during the activation process can be ignored if thecomparison shows no differences.

1.6.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 indicate successful activation. If there is ayellow or red traffic light in the log overview structure, double-click on the relevant

node and check the details on the right-hand side of the screen.

Result

You have checked the successful configuration in your Customizing tables for the specificbusiness configuration that the BC Set covers and can proceed with the next activity of the BPIAproject.

quick guide to installing the sap best practicesbaseline package

Documents