June 2008 English

Solution Builder for SAP Business All-in-One
Quick Start Guide

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany

SAP Best Practices

Solution Builder for SAP Business All-in-One

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 express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, 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 or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves 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 20

SELECT and INCLUDE. and individual key words of a programming language. Names of elements in the system. messages.SAP Best Practices Solution Builder for SAP Business All-in-One Icons Icon Meaning Caution Example Note Recommendation Syntax External Process Business Process Alternative/Decision Choice Typographic Conventions Type Style Example text Description Words or characters that appear on the screen. upgrade and database tools. for example. source code. for example. function keys (such as F2) or the key. © SAP AG Page 3 of 20 . Screen output. titles of graphics and tables. paths and options. These include field names. Example text EXAMPLE TEXT Emphasized words or phrases in body text. Variable user entry. when surrounded by body text. Example text <Example text> Exact user entry. ENTER Example text EXAMPLE TEXT Keys on the keyboard. program names. These include report names. Pointed brackets indicate that you replace these words and characters with appropriate entries. pushbuttons as well as menu names. table names. These are words or characters that you enter in the system exactly as they appear in the documentation. names of variables and parameters as well as names of installation. screen titles. transaction codes. This includes file and directory names and their paths. Cross-references to other documentation.

........................................................................................................................11 Importing a Solution.....................................................................................................................19 5............................................5 1 2 Purpose......................................................................................................................................5 Post Installation Activities...........3 3....................................................................6 Structure of Solution Builder Content and User Interfaces .....................................................................................................................................................................................................5 Prerequisites...3 4............................................................................................................................................................................................1 Activation of a Solution................................................................................................4 4........................11 4..........................................13 Enterprise Structure Personalization.................................5 Required Content Files.......................................................................17 Download Installation data............................3 3 Installation of the Solution Builder ...................19 © SAP AG Page 4 of 20 .............................9 3.....12 Scoping of a Solution ....................................................................................2 4...................................................................................................................................................1 2........................2 3.................................................10 Implementation Assistant (Managing Scenarios).........................................................................5 4..............................................................................................18 5 Implementing a Solution ....................6 4............................10 Building Block Builder (Managing Building Blocks)..............................................................................................................................2 2....1 4........................................................................................................................................5 2......7 Getting Started and Navigation ............1 3......................................10 4 Tool Procedures ............................4 Overview .....16 Generic Personalization .............................................11 Upload Installation Data .9 Solution Editor (Managing Solutions)...................................SAP Best Practices Solution Builder for SAP Business All-in-One Contents Solution Builder Quick Start Guide ..................................

2 Prerequisites 2. post installation activities must be performed. It is the successor to the SAP Best Practices installation assistant. Review the overview note of your solution builder version for details. Release Strategy. The solution builder enables you to: o o o Create a scope based on the scenarios of an SAP Best Practices package or SAP Business All-in One offering Personalize settings (for example. In general. review the detailed instructions in the overview note of your solution builder version.1 Installation of the Solution Builder The solution builder is delivered as technical add-on available free of charge within the SAP Best Practices deliverables. so that you can easily troubleshoot any problems using a transparent record of the status of the activation of the solution. The tool automates implementation steps.2 Post Installation Activities In addition to the installation of the solution builder add-on in the system. 2. The solution builder provides activity tracking and logging. Current Solution Builder Version. This document is intended for consultants working with ready-to-use packages like SAP Best Practices or SAP Business All-in-One offerings. Here you get more information about the available versions and the respective overview notes providing specific information and procedures for your solution builder version.SAP Best Practices Solution Builder for SAP Business All-in-One Solution Builder Quick Start Guide 1 Purpose The solution builder for SAP Business All-in-One is a tool developed by SAP Best Practices to develop and deploy offerings such as SAP Best Practices packages or SAP Business All-in-One solutions. the required enterprise structure) Activate the solution scope rapidly. The name of the technical add-on is BP-INSTASS. the following post-processing steps must be performed. A technical installation guide is provided with the technical Add-on. Post Installation Activity Apply SAP Notes (if existing) to correct possible issues Remark Listed in the overview note © SAP AG Page 5 of 20 . Overview Note You can check the release strategy of the solution builder in SAP Note 846029. saving time during implementation and reducing possibility of errors. A developer guide will be available as separate document. including the same functions provided in the installation assistant with additional enhancements and improvements. For all steps.

and building blocks Definitions required for scoping (selection templates.SAP Best Practices Solution Builder for SAP Business All-in-One Post Installation Activity Activate ICF framework Remark Required for scoping functionality. This file is delivered in a compressed format.txt files). The settings exist as variable parameters in the BC Sets and eCATTs delivered with SAP Best Practices and are populated during activation with values referenced from external data files (. and layouts) Definitions required (or allowed) for personalization (Business Object Mapping and personalization activities) Technical definitions (implementation task definitions. referencing mapping information. See SAP note 1120773 and extract the attached archive file locally in the folder mentioned in the note Copy bitmap files to local SAPgui folder of (local) presentation server 2. description is attached to the overview note Graphic files are required for display of graphical Enterprise Structure Personalization. which is usually less than one megabyte. data references. and so on) For each package or offering. preconfigured settings or manual configuration steps or tasks). 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.3. the content of each package or offering (such as preconfigured settings. 2. This content is provided in two different types of files that you will use during activation: o o Solution definition file Installation data files 2.1 Solution Definition File The Solution Definition file is an XML file that contains the complete structural definition of a package/offering you want to use. the technical framework is usually completely separated from the business content (for example. For implementation purposes. building blocks and scenarios) must be uploaded into the solution builder before you can work with it. you will upload one solution definition file that may be about six to twelve megabytes in size. Some of the information in the file includes: o o o o o Definition of solution. scenarios.3 Required Content Files The solution builder is an independent tool that allows users to develop and activate an SAP Best Practices package or SAP Business All-in-One offering.2 Installation Data Files For offerings based on SAP Best Practices. application areas. The external data files are delivered with each specific SAP Best Practices package.3. and activation information) Other information (links to documentation. assignments. © SAP AG Page 6 of 20 .

Installation Data are usually shipped as a compressed file containing hundreds or thousands of different .txt files. different business content does not require a different technical framework. variant files. Other terms that may be used in other documents to refer to installation data include external variant files. The size of the compressed file can be several (~1 . To a certain extent. In this document. organizational structure settings such as company or plant) before the business content is activated in an SAP system. and external txt files.SAP Best Practices Solution Builder for SAP Business All-in-One The advantage of this design is that the business content can be personalized to individual requirements (for example. Installation data refers to the set of external files required during implementation of an SAP Best Practices package.4) megabytes © SAP AG Page 7 of 20 . txt files.

com). choose the SAP Best Practices tab. then browse to the desired SAP Best Practices package.sap. SAP Best Practices Solutions shipped starting in 2008 are designed for solution builder. The installation Data files are available from a central page in the SAP Service Marketplace. In the SAP Help Portal. © SAP AG Page 8 of 20 . the content files can be obtained as follows: Content File Type Solution Definition File Installation Data Overview Notes and Details of SAP Best Practices Packages Documentation for all available SAP Best Practices packages can be found in the SAP Help Portal (http://help.SAP Best Practices Solution Builder for SAP Business All-in-One 2. For SAP Best Practices offerings.3. Linked in the Implementation section of each SAP Best Practices package. the Quick Guide provides you with all required implementation information including the package’s SAP Note (sometimes also called Collective Note).3 How to Get the Content Files Method to Obtain The solution file is attached to the overview SAP note of the SAP Best Practices offering you want to use.

Building Blocks: Reusable. you must define it as your Favorite solution. © SAP AG Page 9 of 20 .SAP Best Practices Solution Builder for SAP Business All-in-One 3 Structure of Solution Builder Content and User Interfaces 3. solutions are preconfigured SAP ERP systems including related deliverables. settings.1 Overview The solution builder focuses on the use of solutions based on SAP Best Practices. edits. such as SAP Best Practices packages. In this section. self-contained pieces of business content. the user interfaces and their purpose are briefly explained. part of SAP Basis) BC Sets (Business Configuration Sets. this document will use the term solution to represent any SAP Best Practices package or SAP Business All-in-One offering. the content items correspond to specific user interfaces: o o o The Solution Editor manages the solutions The Implementation Assistant activates and manages the scenarios The Building Block Builder creates. Scenario: Main solution-level deliverables. or content in a well-defined sequence and structure. Implementation Activities include: o o o Manual Activities/Reports/IMG Activities. hosts cross-scenario information. SAP Best Practices scenarios are designed to be installed separately and independently. so each scenario contains all required Building Blocks to set them up separately. part of SAP Basis) o o In the solution builder. For ease of understanding. Scenarios are comprised of a number of Building Blocks in a determined sequence. Contain configuration tasks. or groups of technical implementation tasks. before you work with a specific solution. and links eCATTs (enhanced Computer Aided Test Tool. In this document. smallest unit in scoping process. The following section discusses the user guides. The structure mainly is determined by the technically-required activation sequence. Implementation Activities: Elements of a Building Block. and manages Building Blocks Because the solution builder lets you manage several solutions. The content in the solution builder is structured as follows: o o Solution: Comprises all Scenarios and Building Blocks of offering. This prevents you from editing or activating the wrong solution in the Solution Editor or the Implementation Assistant.

These functions will be further explained in another document intended for developers. The function buttons in the above graphic are presented in the most likely sequence of use.SAP Best Practices Solution Builder for SAP Business All-in-One 3. showing all Building Blocks (of all solutions without the solution assignment details) and providing an extended set of development options. The most required functions are available as function buttons: Except for the user setting maintenance.3 Implementation Assistant (Managing Scenarios) For a consultant who is activating a solution. or during troubleshooting. Users without development focus (implementation consultants) may find it educational to enter the Building Block Builder for reference and details of the covered business content.2 Solution Editor (Managing Solutions) The Solution Editor is the initial screen of the solution builder. To enter the solution editor. Like the Implementation Assistant. © SAP AG Page 10 of 20 . the Building Block Builder includes two views: the default view showing the Building Blocks for a solution with a restricted set of options (Solution View). providing more options that are required when developing a solution. 3. The Implementation Assistant manages the: o o o o o Activation parameters Activation checks Activation sequence of Building Blocks and implementation tasks Activation status of scenarios and Building Blocks 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.4 Building Block Builder (Managing Building Blocks) The Building Block Builder is the user interface intended for users developing a solution. 3. Consultants implementing a solution will work primarily with the Solution Editor screen (other work will be done in the Implementation screen). More advanced features of the Solution Editor are used primarily by users developing a solution. other items in the menu bar dropdowns probably will not be generally required. use transaction code /n/smb/bbi (Solution and Implementation). The Implementation Assistant shows all scenarios assigned to the solution you are working with (the Favorite solution). It manages the Building Block repository per solution. and a view for users with a development focus (Scenario view). the Implementation Assistant will be used during the implementation of the solution.

choose the Implementation button to go to the Implementation Assistant . the first activity (if you start with an empty solution builder) is to upload the Solution by importing a solution definition file (XML file. The first time you enter the Solution Editor (if no other users have uploaded or created solutions in the system). To start the solution builder. There is no menu path in the standard SAP Menu. We strongly recommend to add the transaction for the solution builder ( /SMB/BBI ) to the favorites of your SAP user menu. listing all solutions available in the system.3. See chapter 2. 2. 4. Solution Editor (Managing Solutions). 3. Select the solution definition file and choose Open. The Solution Editor screen displays.SAP Best Practices Solution Builder for SAP Business All-in-One 4 Tool Procedures 4. Choose the Import button. 1. where the Favorite solution can be installed. use one of the following navigation options: Transaction Name Transaction Code Solution and Implementation /N/SMB/BBI 2. 3.2 Importing a Solution As the button bar suggests. the button bar indicates the sequence of operation for end-users. the solution builder is started by the transaction code. After finishing all steps in the Solution Editor (as described below).1 Getting Started and Navigation After successful installation. the solution list is empty. sometimes also known as Solution Scope file). As mentioned in section 3.Solution View. On the Select one format to import dialog box.1 how to get the solution definition file for your solution Procedure 1. © SAP AG Page 11 of 20 .2. choose the Import XML file button.

or copy the file to a folder closer to the root folder of the hard drive. either rename folders in the path to shorten the file path.1 Maintain User Settings: Path to Installation Data The solution definition (as uploaded as XML file) and the installation data (see chapter 2. select the solution in the list and choose the Favorite button. Result The installation data path assigned to the solution is always set as default entry for the particular solution. To maintain it for another solution. choose Goto User Settings. 4. If the file path is too long. On the Solution Specific tab.2. However. 2.SAP Best Practices Solution Builder for SAP Business All-in-One 4. 3. This is done in the user settings (path information very often is user-dependent).3 Upload Installation Data If you are using the default delivered settings for the implementation of a solution. On the Solution Builder – Solution Editor screen.2) define the solution that will be implemented. To simplify the procedure and to avoid confusion with different sets of installation data. 4. enter the folder where you have stored your installation data.3. select another solution as a Favorite before maintaining the solution-specific part of the user settings. an information box about the uploaded scenarios and Building Blocks is displayed. Procedure 1. Confirm the changes. this step is optional. This is an important step for consultants that have imported multiple solutions in the solution builder. we strongly recommend assigning the path to the installation data to the solution. After the solution is uploaded (dependent on the size of the solution a few seconds up to one minute). 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) determines which solution any subsequent activities (from the button bar) affect. Choose OK to confirm. If you receive this error message. the system will display an error message. The solution ID of the Favorite solution is fixed. If you have more than one single solution available and you want to work with reference to another solution in your solution list. we recommend the upload of installation data mainly for two reasons: © SAP AG Page 12 of 20 .

© SAP AG Page 13 of 20 . The data upload of several thousand installation data files can take some time (about 10 minutes for 2000 files). Select the Overwrite Data radio button. the data upload is probably not supported by the solution you are using. 3. The activation step will use the files in the installation data folder on the presentation server.SAP Best Practices Solution Builder for SAP Business All-in-One o o To make use of the personalization capabilities of the solution builder as described below (Enterprise Structure Personalization) To review the installation data for the tasks in the Building Block Builder for better transparency. Hence. If you maintained the user settings according to 4. The personalization capabilities of the solution builder are ready for use (if supported by your solution provider). Confirm the entries. 4. so ensure that you have uploaded the correct installation data files and pointed to the correct folder location. The scoping tool provides an easy to use graphical user interface that provides additional details about each scenario. the upload of the installation data can take several minutes. 4. 2. Dependent on the number of files. refer to the information material provided with your solution. or to maintain installation data The step of activating a solution is independent of the step of uploading the installation data. For more information. The data upload from the presentation server to the application server should be performed within the same local network domain. Slow network connections can negatively affect the performance of the data upload from the presentation server (system where the files are located) to the application server. Procedure 1. the installation data folder is already set as default in the following dialog box. troubleshooting. The upload of installation data requires high quality and consistency in the data files and is mandatory if you are using the internal personalization capabilities of the solution builder.4 Scoping of a Solution All scenarios of an uploaded solution represent the maximum scope that can be implemented. Choose the button. a smaller solution scope might be sufficient. and provides an easy select/deselect function to add or remove scenarios in a scope. Based on target group and individual requirements.1.2. Result The installation data is uploaded in the solution builder.

the screen is scrolled automatically to the position of the scenario. make sure that the ICF framework is enabled according to the instructions of the overview note of the solution builder. The template can be a subset of scenarios in a solution.SAP Best Practices Solution Builder for SAP Business All-in-One To use the scoping functionality. for example. If a scenario covers more than one application areas.1 Selection Templates The scoping process is always based on a template. 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. If using the regular layout of the scoping screen (defined by the service provider of your solution). 4.4. review the information material from your solution provider.2 Scoping Screen The scoping tool displays all scenarios that are defined as relevant for scoping in a view similar to a solution map. In the scoping screen. otherwise grayed out) Deselect a selected scenario (if allowed by the template. you can see if there is one or more scenario of an application area in scope (solid application area box) or none (framed application area box). and is created by your solution provider.4. Otherwise. © SAP AG Page 14 of 20 . each scenario appears as a box in the color of the assigned (primary) application area. the function will quit with an error message. Clicking on a scenario in the list opens the scenario box (like clicking on the scenario box itself). otherwise grayed out) See more information (using the Details button. 4. It represents an example scope selection based on considerations such as: Target groups (scenarios relevant for manufacturing. service. The scenarios are generally classified according to functional areas or application areas (application areas are used in the following as example). This list also includes scenarios with a different primary application area (can be identified by color). if supported by your solution) Clicking on the application area box shows a list of all scenarios that are assigned to this application area. a primary application area is defined to show the color/assignment to the application area unambiguously. 60 days implementation time for a solution) In addition to a predefined scope of scenarios in a template. and so on) Implementation time (scenario selections for implementations within a certain timeframe. the solution designer can also restrict the scope by: Placing certain scenarios in scope Taking certain scenarios out of scope For details about the templates delivered with your solution. If a scenario is not visible on the screen. trade.

The upload of installation data does not need to be performed in that case for the custom solution. The custom solution acts different as the standard solution like the one delivered by your solution provider.4. Select the Scope button. 2. Copying a custom solution turns it to a standard solution.2. choose the Save Data button. select or deselect the scenarios you want to take in or out of scope. button. For a custom solution. we recommend maintaining the user settings as described in chapter 4. 4. select an available selection template.3 Create a Custom Solution Once you have scoped your solution. For a custom solution a number of operations are disabled that are no relevant for enduser operation.SAP Best Practices Solution Builder for SAP Business All-in-One 4. If no selection templates are delivered by your solution provider. In the Scoping screen.4 How to Use the Scoping Tool Procedure 1.1. In the list box on the next screen. the installation data is copied automatically to the custom solution. When you are done. To continue the following operations with reference to your custom solution. ensure that you set it as a Favorite solution (choose the Favorite button). Result The custom solution with the selected scope of scenarios is created. You will receive a respective error message in that case. scoping is not supported.4. Saving a selected Scope leads to the creation of a custom solution with all the scenarios in scope that were selected during the scoping process. © SAP AG Page 15 of 20 . 4. Choose the 3. Changing the custom solution reenters the scoping screen and allows adding or removal of scenarios (scenarios can only be removed if they have not already been activated). 6. The custom solution keeps the relationship to the standard solution of its origin. 5. If you uploaded the installation data before the scoping process (as described in this documentation). Enter a meaningful Solution ID and Solution Description . save the scope.

An example is the plant description that is shown in the same language for all logon languages. the function will quit with an error message. the target language is not relevant. selection templates are not copied.2 Display/Personalization Mode The Enterprise Structure Personalization provides a display mode and a personalization (change) mode. A mapping – included in the solution design – assigns attributes of the business objects to the respective parameters in the installation data files. This copy function provides a check to avoid possible inconsistencies. You can double-click any enterprise structure item to see the details.5 Enterprise Structure Personalization The Enterprise Structure Personalization shows a graphical representation of the enterprise structure as it is defined by the installation data files. and so on. 4. In the personalization mode. For technical language-dependent texts.5. to avoid issues and unexpected behavior due to a mismatch between the scenarios in the solution and the scenarios in a template. Otherwise the Enterprise Structure Personalization shows an error message or does not display an enterprise structure. In the personalization mode.5. The graphical enterprise structure is structured according to navigation areas listed on the left side on the screen such as Financial Accounting. A separate functionality for copying templates from one solution to another is therefore provided within the selection template maintenance for users with development focus.1 Target Language The target language must be specified to display and personalize the enterprise structure. 4.SAP Best Practices Solution Builder for SAP Business All-in-One If you copy a solution. you can adapt these values according your requirements. 4. General Logistics. settings can be changed according to individual requirements. © SAP AG Page 16 of 20 . ensure that the graphic files are uploaded to the presentation server according to the instructions in the overview note of the solution builder. Otherwise. Each navigation area displays a respective graphical structure that indicates assignments or relationships between the items. Sales and Distribution. The target language determines the language of texts displayed for attributes that are not language-dependent in a technical sense. This is by design. The target language determines the language of these attributes as it is shown in the system for all logon languages. SAP Best Practices solutions provide these parameters in all languages supported by the solution. Technical languagedependent attributes are always activated in all supported languages. The Enterprise Structure Personalization requires the installation data upload and the support of this functionality by your solution provider. To use the graphical enterprise structure personalization. The business object model in the solution builder is aligned to the standard business object model of SAP.

only selected parameters are displayed or changeable to simplify personalization for end-users. This mode is restricted to experienced developers only. Change the values according to your requirements. choose the Save button. Within the definition of personalization tasks.SAP Best Practices Solution Builder for SAP Business All-in-One Screen layout and navigation corresponds to the respective enterprise structure item in the customizing screen. When finished. you can change zoom factor and visible area by selective the respective area in the right part of the screen. 5. Choose the required navigation area from the upper left screen. Result The Installation data uploaded to the solution builder are changed. On the right hand side. 2.3 How to Use the Enterprise Structure Personalization Procedure 1. Change button. Choose the button. the system displays a list of available personalization tasks. For selected personalization tasks. From the menu. © SAP AG Page 17 of 20 . some values are not changeable (grayed out) even in personalization mode. Choose the target language and choose the 3. For larger structures. an additional expert mode is available to have unrestricted access to any settings of the enterprise structure. 2. 4.5. Save your changes. To prevent changes during the personalization that are not supported by the solution. 4. Double-click any enterprise structure item to make the desired changes. On the left hand side of the screen. but the values completely refer to the installation data. the system displays the respective change options for the selected personalization task. 3.6 Generic Personalization The generic personalization functionality provides additional personalization tasks if supported by your solution. Procedure 1. 4. 4. Choose the button. it displays values that correspond to the respective uploaded installation data.

During the implementation.7 Download Installation data After personalization and before implementation. Slow network connections can negatively affect the performance of the data download between the presentation server and the application server. You can choose the option to download changed data if you download the data to a folder that already contains a complete set of installation data (otherwise installation data is missing during the implementation step). 2. the installation data are retrieved from an external folder. 3. 4.1. Result The personalized installation data are downloaded to the folder that contains all installation files required during the implementation of a solution. the folder of the installation data is already set as default in the following dialog box. In this case. the installation will be based on the default values as delivered with your solution. the generic personalization is not possible and quits with an error message.SAP Best Practices Solution Builder for SAP Business All-in-One Result The Installation data uploaded to the solution builder is changed. Procedure 1. This step can be skipped if no personalization was performed. The data download can take some time. Otherwise required files that are not covered by the up. Choose the button. It is strongly recommended to download the installation data to a folder that already contains the complete set of installation data as delivered by your solution provider (confirm overwrite in case of a warning message).and download process (such as graphic files) will be missing. © SAP AG Page 18 of 20 . If you maintained the user settings according to 4. The data download should be performed within the same local network domain.2. If the generic personalization is not supported by your solution provider or if the installation data is not uploaded to the system. the changed installation data must be downloaded to a folder on the presentation server.

Solution view choose the © SAP AG Page 19 of 20 . Folder containing installation data (it is recommended to use already-determined folder retrieved from the user settings (see 4. 2. Refer to the information from your solution provider to see if this option is supported (otherwise the setting has no effect). If you deselect the Demo Data option. you see in the upper part of the screen the Building Block repository for your solution. Expanding a Building Block shows the implementation activities of each Building Block in the correct sequence. To redisplay this activation option screen. o o Procedure 1. if the system stops due to a manual task or error. you must start activation again. 5. if a setup without demo data is required). you can right-click the solution node. Choose the button.1 Activation of a Solution To activate a solution.SAP Best Practices Solution Builder for SAP Business All-in-One 5 Implementing a Solution The implementation of a solution is performed in the Implementation Assistant. button. and choose Display Activation Option.1 for details) A workbench and customizing request (these can be created using the respective create buttons at the bottom of the activation dialog box) Other options o Skip this screen – During activation. After starting the installation. the following activation information must be provided: Target language (the language of text fields for system parameters that are not language dependent in a technical sense (see 4. If the Activation Options are skipped.2. End users should always 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. On the right hand side. the target language can not be changed. This option prevents the activation dialog box from displaying again. Expanding the scenario shows the Building Blocks the Scenario is based on in the correct sequence. you can make the Implementation Assistant stop the activation after the installation of each scenario and to display the activation options screen (Choose option Stop activation by the end of each Scenario) With Demo data (default setting). In the Implementation Assistant . The system uses the same settings from the first activation. The lower part shows all messages and message details that are generated during checks and implementation.1 for details). all implementation steps that are marked as demo data are skipped (for example.5.

make sure to take activation ownership (choose the button).SAP Best Practices Solution Builder for SAP Business All-in-One 3. © SAP AG Page 20 of 20 . Depending on the number of manual activities and possible errors during implementation. If several people are involved in the implementation. Refer to the information provided with your solution for any specific information that must be considered for prerequisites or during implementation. Otherwise.1 Checking activation log After activation. the detailed logs of the activity can be reviewed. 4.1. Specify the activation options as described above. Confirm the Activation dialog box. For details about troubleshooting refer to the information provided with your solution. Selecting an implementation activity shows detailed information in the message area (lower right area of the screen). the status of each implementation activity of a Building Block and the implementation status of a scenario is displayed. Result The activation starts. waiting for manual input or troubleshooting. the solution is locked. 5. the activation may stop occasionally. This will also provide you with information of the expected implementation time and specific troubleshooting procedures. By choosing the Details button.

Sign up to vote on this title
UsefulNot useful

Master Your Semester with Scribd & The New York Times

Special offer for students: Only $4.99/month.

Master Your Semester with a Special Offer from Scribd & The New York Times

Cancel anytime.