Solution Builder Quick Start V4

7/16/2019 Solution Builder Quick Start V4

http://slidepdf.com/reader/full/solution-builder-quick-start-v4 1/20

J une 2008

English

Solut ion Builder for SAPBusiness All-in-One

SAP AGDietmar-Hopp-Allee 1669190 Walldorf Germany

Quick Start Guide



SAP Best Practices Solution Builder for SAP Business All-in-One

© SAP AG Page 2 of 20

Copyright

©Copyright 2008 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the expresspermission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400,iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9,

z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+,OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.

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

Oracle is a registered trademark of Oracle Corporation.

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

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

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

J ava is a registered trademark of Sun Microsystems, Inc.

J avaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented andimplemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service namesmentioned are the trademarks of their respective companies. Data contained in this document servesinformational 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, andSAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAPGroup products and services are those that are set forth in the express warranty statements accompanyingsuch products and services, if any. Nothing herein should be construed as constituting an additional warranty.





Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

External Process

Business Process Alternative/Decision Choice

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, forexample, SELECT and INCLUDE.

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

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

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

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





Contents

Solution Builder Quick Start Guide............................................................................................................5

1 Purpose................................................................................................................................................5

2 Prerequisites........................................................................................................................................5

2.1 Installation of the Solution Builder..............................................................................................5

2.2 Post Installation Activities............................................................................................................5

2.3 Required Content Files................................................................................................................6

3 Structure of Solution Builder Content and User Interfaces ..............................................................9

3.1 Overview......................................................................................................................................9

3.2 Solution Editor (Managing Solutions).......................................................................................10

3.3 Implementation Assistant (Managing Scenarios)....................................................................10

3.4 Building Block Builder (Managing Building Blocks).................................................................10

4 Tool Procedures................................................................................................................................11

4.1 Getting Started and Navigation ................................................................................................11

4.2 Importing a Solution...................................................................................................................11

4.3 Upload Installation Data............................................................................................................12

4.4 Scoping of a Solution ................................................................................................................13

4.5 Enterprise Structure Personalization........................................................................................16

4.6 Generic Personalization............................................................................................................17

4.7 Download Installation data........................................................................................................18

5 Implementing a Solution...................................................................................................................19

5.1 Activation of a Solution..............................................................................................................19





Solution Builder Quick Start Guide

1 Purpose Thesolution builder for SAP Business All-in-One is a tool developed by SAP Best Practices todevelop and deploy offerings such as SAP Best Practices packages or SAP Business All-in-Onesolutions. It is the successor to the SAP Best Practices installation assistant, including the samefunctions provided in the installation assistant with additional enhancements and improvements.

Thesolution builder enables you to:

o Create a scope based on the scenarios of an SAP Best Practices package or SAP

Business All-in One offeringo Personalize settings (for example, the required enterprise structure)

o Activate the solution scope rapidly.

The tool automates implementation steps, saving time during implementation and reducingpossibility of errors. The solution builder provides activity tracking and logging, so that you can easilytroubleshoot any problems using a transparent record of the status of the activation of the solution.

This document is intended for consultants working with ready-to-use packages like SAP BestPractices or SAP Business All-in-One offerings. A developer guide will be available as separatedocument.

2 Prerequisites

2.1 Installation of the Solut ion Builder

Thesolution builder is delivered as technical add-on available free of charge within the SAP BestPractices deliverables. The name of the technical add-on is BP-INSTASS. A technical installationguide is provided with the technical Add-on.

Release Strategy, Current Solution Builder Version, Overview Note

You can check the release strategy of the solution builder in SAP Note 846029. Hereyou get more information about the available versions and the respective overview notesproviding specific information and procedures for your solution builder version.

2.2 Post Installation ActivitiesIn addition to the installation of the solution builder add-on in the system, post installation activitiesmust be performed. Review the overview note of yoursolution builder version for details. In general,the following post-processing steps must be performed. For all steps, review the detailed instructionsin the overview note of yoursolution builder version.

Post Installation Activity Remark

Apply SAP Notes (if existing) to correct possible issues Listed in the overview note





Post Installation Activity Remark

Activate ICF framework Required for scoping functionality,description is attached to the overviewnote

Copy bitmap files to local SAPgui folder of (local)presentation server

Graphic files are required for display of graphical Enterprise StructurePersonalization. See SAP note 1120773and extract the attached archive filelocally in the folder mentioned in thenote

2.3 Required Content Files

Thesolution builder is an independent tool that allows users to develop and activate an SAP BestPractices package or SAP Business All-in-One offering. For implementation purposes, the content of each package or offering (such as preconfigured settings, building blocks and scenarios) must beuploaded into the solution builder before you can work with it.

This content is provided in two different types of files that you will use during activation:

o Solution definition file

o Installation data files

2.3.1 Solution Defini tion File

The Solution Definition file is an XML file that contains the complete structural definition of apackage/offering you want to use. Some of the information in the file includes:

o Definition of solution, scenarios, and building blocks

o Definitions required for scoping (selection templates, application areas, assignments,and layouts)

o Definitions required (or allowed) for personalization (Business Object Mapping andpersonalization activities)

o Technical definitions (implementation task definitions, data references, and activationinformation)

o Other information (links to documentation, referencing mapping information, and so on)

For each package or offering, you will upload one solution definition file that may be about six totwelve megabytes in size. This file is delivered in a compressed format, which is usually less than

one megabyte.

2.3.2 Installation Data Files

For offerings based on SAP Best Practices, the technical framework is usually completely separatedfrom the business content (for example, preconfigured settings or manual configuration steps ortasks). SAP Best Practices use standard SAP Basis tools like eCATTs (enhanced Computer Aided

Test Tools) and BC-Sets (Business Configuration Sets) for activating the settings to the system.

The settings exist as variable parameters in the BC Sets and eCATTs delivered with SAP BestPractices and are populated during activation with values referenced from external data files (.txtfiles). The external data files are delivered with each specific SAP Best Practices package.





The advantage of this design is that the business content can be personalized to individualrequirements (for example, organizational structure settings such as company orplant) before thebusiness content is activated in an SAP system. To a certain extent, different business content doesnot require a different technical framework.

In this document, Installation data refers to the set of external files required during implementationof an SAP Best Practices package. Other terms that may be used in other documents to refer toinstallation data include external variant files, variant files, txt files, and external txt files.

Installation Data are usually shipped as a compressed file containing hundreds or thousands of different .txt files. The size of the compressed file can be several (~1 - 4) megabytes





2.3.3 How to Get the Content Files

For SAP Best Practices offerings, the content files can be obtained as follows:

Content Fi le Type Method to Obtain

SolutionDefinition File

The solution file is attached to the overview SAP note of the SAP BestPractices offering you want to use.

Ins tallation Data SAP Best Practices Solutions shipped starting in 2008 are designed forsolution builder. The installation Data files are available from a central pagein the SAP Service Marketplace.

Overview Notes and Details of SAP Best Practices Packages

Documentation for all available SAP Best Practices packages can be found in the SAPHelp Portal (http://help.sap.com).

In the SAP Help Portal, choose the SAP Best Practices tab, then browse to the desiredSAP Best Practices package.

Linked in the Implementation section of each SAP Best Practices package, the QuickGuide provides you with all required implementation information including the package’sSAP Note (sometimes also called Collective Note).

http://help.sap.com%29./







3 Structure of Solution Builder Content and User Interfaces

3.1 Overview Thesolution builder focuses on the use of solutions based on SAP Best Practices. In this document,solutions are preconfigured SAP ERP systems including related deliverables, such as SAP BestPractices packages.

For ease of understanding, this document will use the term solution to represent anySAP Best Practices package or SAP Business All-in-One offering.

The content in the solution builder is structured as follows:

o Solution : Comprises all Scenarios and Building Blocks of offering; hosts cross-scenarioinformation.

o Scenario: Main solution-level deliverables, smallest unit in scoping process. Scenariosare comprised of a number of Building Blocks in a determined sequence. SAP BestPractices scenarios are designed to be installed separately and independently, so eachscenario contains all required Building Blocks to set them up separately.

o Building Blocks: Reusable, self-contained pieces of business content, or groups of

technical implementation tasks. Contain configuration tasks, settings, or content in awell-defined sequence and structure. The structure mainly is determined by thetechnically-required activation sequence.

o Implementation Activ ities: Elements of a Building Block. Implementation Activitiesinclude:

o Manual Activities/Reports/IMG Activities, and links

o eCATTs (enhanced Computer Aided Test Tool, part of SAP Basis)

o BC Sets (Business Configuration Sets, part of SAP Basis)

In the solution builder, the content items correspond to specific user interfaces:

o The Solution Editor manages the solutions

o The Implementation Assis tant activates and manages the scenarios

o TheBuilding Block Builder creates, edits, and manages Building Blocks

Because the solution builder lets you manage several solutions, before you work with a specificsolution, you must define it as your Favorite solution. This prevents you from editing or activating thewrong solution in the Solution Editor or the Implementation Assistant.

In this section, the user interfaces and their purpose are briefly explained. The following sectiondiscusses the user guides.





3.2 Solut ion Editor (Managing Solut ions) The Solution Editor is the initial screen of thesolution builder . To enter the solution editor, usetransaction code /n/smb/bbi (Solution and Implementation).

Consultants implementing a solution will work primarily with the Solution Editor screen (other workwill be done in the Implementation screen). The most required functions are available as functionbuttons:

Except for the user setting maintenance, other items in the menu bar dropdowns probably will not begenerally required. The function buttons in the above graphic are presented in the most likely

sequence of use.

More advanced features of the Solution Editor are used primarily by users developing a solution. These functions will be further explained in another document intended for developers.

3.3 Implementation Assistant (Managing Scenarios)

For a consultant who is activating a solution, the Implementation Assistant will be used during theimplementation of the solution.

The Implementation Assistant shows all scenarios assigned to the solution you are working with (theFavorite solution).

The Implementation Assistant manages the:

o Activation parameters

o Activation checks

o Activation sequence of Building Blocks and implementation tasks

o Activation status of scenarios and Building Blocks

o Detailed activation logs of the implementation steps.

For users with development focus the default view of the Implementation Assistant (Solution View)can be switched to the Scenario Edit View, providing more options that are required whendeveloping a solution.

3.4 Building Block Builder (Managing Build ing Blocks) The Building Block Builder is the user interface intended for users developing a solution. It managesthe Building Block repository per solution.

Users without development focus (implementation consultants) may find it educational to enter theBuilding Block Builder for reference and details of the covered business content, or duringtroubleshooting.

Like the Implementation Assistant, the Building Block Builder includes two views: the default viewshowing the Building Blocks for a solution with a restricted set of options (Solution View), and a viewfor users with a development focus (Scenario view), showing all Building Blocks (of all solutionswithout the solution assignment details) and providing an extended set of development options.





4 Tool Procedures

4.1 Getting Started and NavigationAfter successful installation, the solution builder is started by the transaction code. There is no menupath in the standard SAP Menu.

1. To start the solution builder, use one of the following navigation options:

Transaction Name Solution and Implementation

Transaction Code /N/SMB/BBI

2. The Solution Editor screen displays, listing all solutions available in the system.

The first time you enter the Solution Editor (if no other users have uploaded or createdsolutions in the system), the solution list is empty.

As mentioned in section 3.2, Solution Editor (Managing Solutions), the button barindicates the sequence of operation for end-users.

3. After finishing all steps in the Solution Editor (as described below), choose the Implementationbutton to go to the Implementation Assistant - Solution View, where theFavorite solution can be

installed.

We strongly recommend to add the transaction for the solution builder ( /SMB/BBI ) tothe favorites of your SAP user menu.

4.2 Importing a Solution

As the button bar suggests, the first activity (if you start with an empty solution builder) is to uploadthe Solution by importing a solution definition file (XML file, sometimes also known as SolutionScope file).

See chapter 2.3.1 how to get the solution definition file for your solution

Procedure

1. Choose the Import button.

2. On theSelect one format to import dialog box, choose the Import XML file button.

3. Select the solution definition file and choose Open.





4. After the solution is uploaded (dependent on the size of the solution a few seconds up to oneminute), an information box about the uploaded scenarios and Building Blocks is displayed.Choose OK to confirm.

Result

The uploaded solution is visible in the solution list and is marked as your favorite solution

The Favorite solution (indicated by in front of the solution in solution list) determineswhich solution any subsequent activities (from the button bar) affect. If you have morethan one single solution available and you want to work with reference to anothersolution in your solution list, select the solution in the list and choose the Favorite button.

If the file path is too long, the system will display an error message. If you receive thiserror message, either rename folders in the path to shorten the file path, or copy the fileto a folder closer to the root folder of the hard drive.

4.2.1 Maintain User Settings: Path to Installation Data

The solution definition (as uploaded as XML file) and the installation data (see chapter 2.3.2) definethe solution that will be implemented.

To simplify the procedure and to avoid confusion with different sets of installation data, we stronglyrecommend assigning the path to the installation data to the solution. This is done in the usersettings (path information very often is user-dependent).

This is an important step for consultants that have imported multiple solutions in the solution builder.

Procedure

1. On theSolution Builder – Solution Editor screen, choose Goto User Settings.

2. On theSolution Specific tab, enter the folder where you have stored your installation data.

The solution ID of theFavorite solution is fixed. To maintain it for another solution, selectanother solution as a Favorite before maintaining the solution-specific part of the usersettings.

3. Confirm the changes.

Result

The installation data path assigned to the solution is always set as default entry for the particularsolution.

4.3 Upload Installation Data

If you are using the default delivered settings for the implementation of a solution, this step isoptional. However, we recommend the upload of installation data mainly for two reasons:





o To make use of the personalization capabilities of the solution builder as describedbelow (Enterprise Structure Personalization)

o To review the installation data for the tasks in the Building Block Builder for bettertransparency, troubleshooting, or to maintain installation data

The step of activating a solution is independent of the step of uploading the installationdata. The activation step will use the files in the installation data folder on thepresentation server, so ensure that you have uploaded the correct installation data filesand pointed to the correct folder location.

Procedure

1. Choose the button.2. If you maintained the user settings according to 4.2.1, the installation data folder is already set

as default in the following dialog box.

3. Select the Overwrite Data radio button.

4. Confirm the entries. Dependent on the number of files, the upload of the installation data cantake several minutes.

Result

The installation data is uploaded in the solution builder. The personalization capabilities of thesolution builder are ready for use (if supported by your solution provider).

The upload of installation data requires high quality and consistency in the data files andis mandatory if you are using the internal personalization capabilities of the solutionbuilder. Hence, the data upload is probably not supported by the solution you are using.For more information, refer to the information material provided with your solution.

The data upload of several thousand installation data files can take some time (about 10minutes for 2000 files). Slow network connections can negatively affect the performanceof the data upload from the presentation server (system where the files are located) tothe application server. The data upload from the presentation server to the applicationserver should be performed within the same local network domain.

4.4 Scoping of a Solution

All scenarios of an uploaded solution represent the maximum scope that can be implemented.Based on target group and individual requirements, a smaller solution scope might be sufficient. Thescoping tool provides an easy to use graphical user interface that provides additional details abouteach scenario, and provides an easy select/deselect function to add or remove scenarios in a scope.





To use the scoping functionality, make sure that the ICF framework is enabled accordingto the instructions of the overview note of the solution builder. Otherwise, the functionwill quit with an error message.

4.4.1 Selection Templates

The scoping process is always based on a template. The template can be a subset of scenarios in asolution, and is created by your solution provider. It represents an example scope selection basedon considerations such as:

Target groups (scenarios relevant for manufacturing, service, trade, and so on)

Implementation time (scenario selections for implementations within a certain timeframe; forexample, 60 days implementation time for a solution)

In addition to a predefined scope of scenarios in a template, the solution designer can also restrictthe scope by:

Placing certain scenarios in scope

Taking certain scenarios out of scope

For details about the templates delivered with your solution, review the information material fromyour solution provider.

4.4.2 Scoping Screen

The scoping tool displays all scenarios that are defined as relevant for scoping in a view similar to a

solution map. The scenarios are generally classified according to functional areas or applicationareas (application areas are used in the following as example).

If a scenario covers more than one application areas, a primary application area is defined to showthe color/assignment to the application area unambiguously.

In the scoping screen, each scenario appears as a box in the color of the assigned (primary)application area. The color can be:

Solid (in case a scenario is selected)

Framed (in case a scenario is not selected)

Clicking on a scenario opens the box providing the options to

Select a scenario that is not selected (if allowed by the template, otherwise grayed out)

Deselect a selected scenario (if allowed by the template, otherwise grayed out)

See more information (using the Details button, if supported by your solution)

Clicking on the application area box shows a list of all scenarios that are assigned to this applicationarea. This list also includes scenarios with a different primary application area (can be identified bycolor). Clicking on a scenario in the list opens the scenario box (like clicking on the scenario boxitself). If a scenario is not visible on the screen, the screen is scrolled automatically to the position of the scenario.

If using the regular layout of the scoping screen (defined by the service provider of your solution),you can see if there is one or more scenario of an application area in scope (solid application areabox) or none (framed application area box).





4.4.3 Create a Custom Solut ion

Once you have scoped your solution, save the scope. Saving a selected Scope leads to the creationof a custom solution with all the scenarios in scope that were selected during the scoping process.

The custom solution acts different as the standard solution like the one delivered by your solutionprovider. For a custom solution a number of operations are disabled that are no relevant for end-user operation.

The custom solution keeps the relationship to the standard solution of its origin. Changing thecustom solution reenters the scoping screen and allows adding or removal of scenarios (scenarioscan only be removed if they have not already been activated).

Copying a custom solution turns it to a standard solution.

For a custom solution, we recommend maintaining the user settings as described inchapter 4.2.1.

4.4.4 How to Use the Scoping Tool

Procedure

1. Choose the button.

2. In the list box on the next screen, select an available selection template.

3. Select the Scope button.

4. In the Scoping screen, select or deselect the scenarios you want to take in or out of scope.

5. When you are done, choose the Save Data button.

6. Enter a meaningful Solution ID and Solution Description.

Result

The custom solution with the selected scope of scenarios is created.

If you uploaded the installation data before the scoping process (as described in thisdocumentation), the installation data is copied automatically to the custom solution. Theupload of installation data does not need to be performed in that case for the customsolution.

To continue the following operations with reference to your custom solution, ensure thatyou set it as a Favorite solution (choose the Favorite button).

If no selection templates are delivered by your solution provider, scoping is notsupported. You will receive a respective error message in that case.





If you copy a solution, selection templates are not copied. This is by design, to avoidissues and unexpected behavior due to a mismatch between the scenarios in thesolution and the scenarios in a template. A separate functionality for copying templatesfrom one solution to another is therefore provided within the selection templatemaintenance for users with development focus. This copy function provides a check toavoid possible inconsistencies.

4.5 Enterprise Structure Personalization

The Enterprise Structure Personalization shows a graphical representation of the enterprisestructure as it is defined by the installation data files.

The business object model in thesolution builder is aligned to the standard business object model of SAP. A mapping – included in the solution design – assigns attributes of the business objects to therespective parameters in the installation data files.

The Enterprise Structure Personalization requires the installation data upload and the support of thisfunctionality by your solution provider. Otherwise the Enterprise Structure Personalization shows anerror message or does not display an enterprise structure.

To use the graphical enterprise structure personalization, ensure that the graphic files

are uploaded to the presentation server according to the instructions in the overviewnote of the solution builder. Otherwise, the function will quit with an error message.

4.5.1 Target Language

The target language must be specified to display and personalize the enterprise structure. The targetlanguage determines the language of texts displayed for attributes that are not language-dependentin a technical sense.

An example is the plant description that is shown in the same language for all logon languages. SAPBest Practices solutions provide these parameters in all languages supported by the solution. Thetarget language determines the language of these attributes as it is shown in the system for all logonlanguages.

For technical language-dependent texts, the target language is not relevant. Technical language-

dependent attributes are always activated in all supported languages.

4.5.2 Display/Personalization Mode

The Enterprise Structure Personalization provides a display mode and a personalization (change)mode. In the personalization mode, settings can be changed according to individual requirements.

The graphical enterprise structure is structured according to navigation areas listed on the left sideon the screen such as Financial Accounting, General Logistics, Sales and Distribution, and so on.

Each navigation area displays a respective graphical structure that indicates assignments orrelationships between the items. You can double-click any enterprise structure item to see thedetails. In the personalization mode, you can adapt these values according your requirements.





Screen layout and navigation corresponds to the respective enterprise structure item in thecustomizing screen, but the values completely refer to the installation data.

To prevent changes during the personalization that are not supported by the solution, some valuesare not changeable (grayed out) even in personalization mode.

4.5.3 How to Use the Enterpr ise Structure Personalization

Procedure


2. Choose the target language and choose the Change button.

3. Choose the required navigation area from the upper left screen.

4. Double-click any enterprise structure item to make the desired changes.

For larger structures, you can change zoom factor and visible area by selective therespective area in the right part of the screen.

5. When finished, choose the Save button.

Result

The Installation data uploaded to thesolution builder are changed.

From the menu, an additional expert mode is available to have unrestricted access toany settings of the enterprise structure. This mode is restricted to experienceddevelopers only.

4.6 Generic Personalization

The generic personalization functionality provides additional personalization tasks if supported byyour solution. For selected personalization tasks, it displays values that correspond to the respectiveuploaded installation data.

Within the definition of personalization tasks, only selected parameters are displayed or changeable

to simplify personalization for end-users.

Procedure


2. On the left hand side of the screen, the system displays a list of available personalization tasks.On the right hand side, the system displays the respective change options for the selectedpersonalization task.

3. Change the values according to your requirements.

4. Save your changes.





Result

The Installation data uploaded to thesolution builder is changed.

If the generic personalization is not supported by your solution provider or if theinstallation data is not uploaded to the system, the generic personalization is notpossible and quits with an error message.

4.7 Download Installation data

After personalization and before implementation, the changed installation data must be downloaded

to a folder on the presentation server. During the implementation, the installation data are retrievedfrom an external folder.

This step can be skipped if no personalization was performed. In this case, the installation will bebased on the default values as delivered with your solution.

Procedure


2. If you maintained the user settings according to 4.2.1, the folder of the installation data is alreadyset as default in the following dialog box.

3. You can choose the option to download changed dataif you download the data to a folder

that already contains a complete set of ins tallation data (otherwise installation data ismissing during the implementation step).

Result

The personalized installation data are downloaded to the folder that contains all installation filesrequired during the implementation of a solution.

It is strongly recommended to download the installation data to a folder that alreadycontains the complete set of installation data as delivered by your solution provider(confirm overwrite in case of a warning message). Otherwise required files that are notcovered by the up- and download process (such as graphic files) will be missing.

The data download can take some time. Slow network connections can negatively affectthe performance of the data download between the presentation server and theapplication server. The data download should be performed within the same localnetwork domain.





5 Implementing a Solut ion The implementation of a solution is performed in the Implementation Assistant. End users shouldalways activate in the Solution View (standard view) of the Implementation Assistant

The Implementation Assistant screen provides the scenario list of a solution on the left hand side.Expanding the scenario shows the Building Blocks the Scenario is based on in the correct sequence.

Expanding a Building Block shows the implementation activities of each Building Block in the correctsequence.

On the right hand side, you see in the upper part of the screen the Building Block repository for yoursolution.

The lower part shows all messages and message details that are generated during checks andimplementation.

5.1 Activation of a Solution

To activate a solution, the following activation information must be provided:

Target language (the language of text fields for system parameters that are not languagedependent in a technical sense (see 4.5.1 for details). After starting the installation, thetarget language can not be changed.

Folder containing installation data (it is recommended to use already-determined folderretrieved from the user settings (see 4.2.1 for details)

A workbench and customizing request (these can be created using the respective createbuttons at the bottom of the activation dialog box)

Other options

o Skip this screen – During activation, if the system stops due to a manual task orerror, you must start activation again. This option prevents the activation dialog boxfrom displaying again. The system uses the same settings from the first activation.

To redisplay this activation option screen, you can right-click the solution node, andchoose Display Activation Option.

o If the Activation Options are skipped, you can make the Implementation Assistant

stop the activation after the installation of each scenario and to display the activationoptions screen (Choose optionStop activation by the end of each Scenario)

o With Demo data (default setting). If you deselect the Demo Data option, allimplementation steps that are marked as demo data are skipped (for example, if asetup without demo data is required). Refer to the information from your solutionprovider to see if this option is supported (otherwise the setting has no effect).

Procedure


2. In the Implementation Assistant - Solution view choose the button.





3. Specify the activation options as described above.

4. Confirm the Activation dialog box.

Result

The activation starts. Depending on the number of manual activities and possible errors duringimplementation, the activation may stop occasionally, waiting for manual input or troubleshooting.

Refer to the information provided with your solution for any specific information that mustbe considered for prerequisites or during implementation. This will also provide you withinformation of the expected implementation time and specific troubleshootingprocedures.

If several people are involved in the implementation, make sure to take activation

ownership (choose the button). Otherwise, the solution is locked.

5.1.1 Checking activation log

After activation, the status of each implementation activity of a Building Block and theimplementation status of a scenario is displayed.

Selecting an implementation activity shows detailed information in the message area (lower rightarea of the screen).

By choosing theDetails button, the detailed logs of the activity can be reviewed.

For details about troubleshooting refer to the information provided with your solution.

Date post:	30-Oct-2015
Category:	Documents
Upload:	hamdy
View:	148 times
Download:	0 times

Solution Builder Quick Start V4

Documents