j00 Bptools En

SAP

September 2012

English

SAP Best Practices Tools

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

SAP Best Practices SAP Best Practices Tools

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 well as 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 and services 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. Data contained in this document serves informational purposes only. National product specifications may vary.

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

© SAP AG Page 2 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 field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

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

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

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

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



Content1 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



1 Essential Information

1.1 PurposeThis document:

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

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

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

Shows you how to use the configuration tools, such BC Sets, eCATTs, the Personalization 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 to modify SAP Best Practices deliverables, see the documentation provided in the Vertical Solution Development Kit (VSDK).

1.2 SAP Best Practices: OverviewSAP 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 Activation time is reduced considerably by the use of automated configuration tools such as the Best Practices solution builder, which utilizes other technologies (BC Sets and eCATTs) 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 you to modify and import customer-specific master data into an SAP system.

The Best Practices solution builder accelerates implementation time by automating system configuration steps. Instead of clicking through roles, you can activate a project that will perform 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 a configuration CD.

The documentation DVD/CD contains:

Scenario overviews

Building block/scenario descriptions



Configuration guides

Business Process Documentations

Best Practices solution builder

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.2.1 Building Blocks: ConceptThe 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 to assemble 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 can be used in many solutions, such as the building block for Financial Accounting. These generic building blocks belong to the so-called layer 0 (see SAP Best Practices 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.

1.2.2 Building Blocks: ActivationTo 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.

1.2.3 Technical Prerequisites for ActivationDetails on the technical prerequisites for Activation of SAP Best Practices can be found in the Quick Guide document.



1.3 SAP Best Practices: Documentation

1.3.1 Document Types and ContentEach building block has various documents that describe the business content, Activation, and testing procedures.

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

Document Type

Purpose File Format

Scenario Overview

Provides a graphical overview of a scenario. MS PowerPoint

Scenario/Building Block Description

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 DVD/CD.

HTML

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

For each step in the SAP Best Practices solution builder scenario, you can find the corresponding manual implementation 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 solution builder scenario.

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

MS Word

Business Process Documentation

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 a document on the configuration CD entitled Importing Best Practices Add-Ons and Add. Transports for mySAP All-in-One (file name ADDONINS.PDF). This document contains essential technical information required before installing any building blocks.



1.4 SAP Best Practices: Tools

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

1.4.1.1 SAP Best Practices Solution BuilderThe SAP Best Practices solution builder is a tool that enables you to personalize and install the SAP Best Practices rapidly. The tool automates Activation of SAP Best Practices packages, saving time during implementation and reducing possibility of errors. By importing predefined scenarios, 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 ProceduresThe Extended Computer Aided Test Tool (eCATT) is a new automated testing tool that allows you to create automated functional test cases for the majority of applications running in the SAP GUI for Windows and SAP GUI for Java environments. Like other test tools, it works by making a 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 values returned by the application.

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

1.4.2.1 eCATT Objects

Test ConfigurationThis 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 ScriptThis object consists of an executable script and an interface for data transfer.

Test Data ContainerThis 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 ContainerThis 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 VariantsA 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 DownloadAll 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.

BC Sets and eCATTsA recent change to the eCATT technology allows BC Sets to be run from an eCATT. This method allows for greater automation of Activation and customization. Variable field values that were 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 ConventionThere is no specific naming convention for eCATT objects. Names are alphanumeric strings up to 30 characters long, and are not case-sensitive.

1.4.2.2 Executing eCATT Procedures

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

PrerequisitesThe 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 Practices solution builder, look for the eCATT task, then highlight the technical object name and copy it to the clipboard with CTRL-C.

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


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


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

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 able to execute the procedure successfully.

1.4.2.3 Running an eCATT in Foreground Mode

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

Procedure1. 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 in Foreground, Synchronous Local.

1.4.2.4 Displaying and Printing eCATT Logs

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

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

1.5 Analyzing the Master Data InstalledMaster data is very individual data, which has to be adapted to customer needs on a project basis. For this reason, no dedicated documentation for the sample master data delivered by



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

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

1.5.1 Master Data Implemented by eCATTsAn eCATT is called by a parameter transaction within the Best Practices solution builder. The object 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 you can identify the master data that is included in eCATT objects.

ProceduresThe data applied by an eCATT test configuration is defined in the variants of the test configuration. These variants can contain either the explicit data values or references to values in 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. Expand the 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

Transaction code

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 value in a test data container and is read as follows: Insert the value of the cell from the test data container <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 data container 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>.



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

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 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 eCATTs to upload your own master data. In this case, you have to maintain the external variants first, before you proceed with the eCATT execution.

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

ActivitiesFirst, 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 Activation. To avoid unnecessary delays during the Activation, it is recommended to maintain the eCATT variants before 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.

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

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.



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

UseA Business Configuration Set (BC Set) is a package of Customizing settings. BC Sets are used to accelerate the Activation process of the building blocks and scenarios delivered with SAP Best Practices.

In SAP Best Practices starting with release ECC 5.00, BC Sets are embedded inside eCATTs to allow 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 as company code, production plant, and so on). Those values are now maintained in global text files 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 BC Sets, 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 the master list or BPIA project, there is corresponding information in the configuration guide describing how to perform this step manually.

FeaturesThere 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 settings can be changed 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 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.

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, the following information may be useful:

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.6.1 Displaying BC Set Contents 1. 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 pane displays 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 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 BC Sets with variable values

If you are comparing a BC Sets without variable values, the view BC Set: Compare 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.

If you are comparing a BC Set with variable values, the Enter Variable Fields Values 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 block’s configuration guide.

1.6.3 Activating a BC Set

PrerequisitesBefore you activate a BC Set, always compare the values contained in the BC Set to the existing entries 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 you select. In addition, only these languages are installed. To do this, proceed as follows:



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 in your 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 is displayed, you can copy or change the default 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 inadvertently overwrite 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 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.

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 selected Customizing activity are assigned to the BC Set. However, only some of these views/tables may be relevant and the others remain empty. These empty views/tables will cause this error.

The warning message Not all data was activated in all languages can be ignored as long 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 a comparison between the table and the BC Set to show if a difference in your



languages exists. To avoid these errors, change your user settings to include only your relevant language. For example, the Baseline Package (Germany) BC Sets may contain only English and German languages. If another language is also selected 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 Set hierarchies, 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, 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.

1.6.4 Displaying the Activation Log

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

ProcedureTo 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 a yellow 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.

ResultYou 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 BPIA project.


Documents

j00 Bptools En