RDS Solution Builder

7/21/2019 RDS Solution Builder

http://slidepdf.com/reader/full/rds-solution-builder 1/1061











The Solution Manager can be used for the administration of the blueprint,

configuration, test , training and documentation. Adjustments to the

configuration after the activation via the Solution Builder are documented here.The Solution Manager supports the whole life-cycle of an implementation

project: implementation, Enterprise Support, upgrade etc. The rapid

deployment solutions are delivered via templates. Configuration Guides, IMG

Objects, customizing transactions etc are assigned to the configuration steps.

The Solution Builder enables the automated activation of a Rapid Deployment

Solution. It offers personalisation options before the activation of the

organisational structure and generic personalization, it also gives a detailed

Status control during an activation.

The Building Block technique which is sued provides a transparent and flexible

activation of the settings.

The activation of settings is supported by BC Sets, eCATTs and manual

activities and attached documentation

Outlook: Conflict checks will be available for installed base activation and also

an upgrade management.

6



In the Step-by-step navigate to the Deploy phase and select Activate Solution.

To activate the solution you need to run the Solution Builder in the target

system.

7









Go to the Step-by –Step Guide deploy phase and then to Accelerators. Here

you find links to the different documentation accelerators.

11



Under Activation and and Manual Activation you find the Quick Guide.

12



Start with the Quick Guide, because it is always kept up to date and is your first

aid in case of questions. The Quick Guide is attached to the SAP Note

belonging to the respective RDS package.

The Quick Guide contains a detailed step-by-step description on how to

prepare a system, which support package level you need, which notes should

be implemented, and how to use the SAP solution builder.

13







The add on installation will be done by an system administrator in an earlier

phase of the Step-by-Step Guide. They can be downloaded from the Software

distribution center. You can also navigate in the Step-By-Step Guide to Start ->Confirm Installation-> Download Software.

Navigate in the Step-By-Step Guide to Start -> Confirm Installation-> Download

Software.

16



Check the system according to the Quick Guide. All add-ons for each package

are available in the preconfiguration download. To find out which add-on is the

right one for your solution, you need to read the Quick Guide and ADDONINSTdocumentation, also available in the preconfiguration download. It is

recommended to have a Basis consultant or a system administrator import the

add-ons, as documented in SAINT.PDF, also available in the preconfiguration

download.

17





Start with the Quick Guide, because it is always kept up to date and is your first

aid in case of questions. The Quick Guide is attached to the SAP Note

belonging to the respective Rapid Deployment Solution.

The Quick Guide contains a detailed step-by-step description on how to

prepare a system, which support package level you need, which notes should

be implemented, and how to use the SAP solution builder.

19





If you have transferred the scope via the Solution Manager to the Solution

Builder, you do not have to do any scoping in the Solution Builder.

21



After passing the data from the Solution Manager to the Solution Builder you

will find an imported xml Solution file in the Implementation Assistant of the

Solution Builder containing the scope you have defined in the SolutionManager. Furthermore the txt files belonging to the rapid deployment solution

are automatically uploaded.

22



If you work have not transferred the scope automatically from the Solution

Manager you can also do the scoping and its preparation manually in the

Solution Builder. This is normally done if you have the Solution ManagerVersion 7.0 with which the functionality “Pass data to Solution Builder “ is not

possible.

To do this proceed in the following way:

Download solution file (xml) from note

Upload solution file to Solution Builder

Do the scoping in the Solution Builder

23



Before using the solution builder, ensure that the necessary files were

downloaded from the SAP Service Marketplace and the SAP Note.

Start the solution builder with transaction /n/smb/bbi.

24



In the Deploy phase select Manual activation or automated activation and the

navigate to the corresponding note via the link to the Quick Guide. From the

note attachment the solution file can be downloaded.

25



Here you can see how to import the scope file.

The scope file has been downloaded from the SAP Note belonging to the RapidDeployment Solution in a previous step.

26



Now you can conduct the scoping. For some packages like for example the

Business – All-in-One Baseline packages different entry levels are offered.

Normally in the case of a rapid deployment solution the scoping has alreadybeen done in the Solution Manager.

27



The scoping is performed in the Solution Editor component of the solution

builder. The user can select or deselect scenarios and create an individual

scope.

By clicking on the scenario titles, the user navigates to the scenario

descriptions in the SAP Help Portal. This documentation helps the user to

decide if a particular scenario is needed for a personalized solution scope.

After the scope definition, the user must enter a solution ID and a description of

the new scope in the fields shown here.

28



For some Rapid Deployment Solutions it is also possible to navigate in the

Solution Builder to the option Import Solution from Web. These solutions have

be available on the webserver to use this functionality.

29





The next action you perform is personalizing your master data and adapting the

organizational structure.

Here you can change keys and descriptions of the elements of the

organizational structure according to your needs.

31



After passing the data from the Solution Manager to the Solution Builder you

will find an imported xml Solution file in the Implementation Assistant of the

Solution Builder containing the scope you have defined in the SolutionManager. Furthermore the txt files belonging to the rapid deployment solution

are automatically uploaded. The upload of the txt files is a mandatory

prerequisite to run the personalization.

32



Then, you can conduct the personalization of the organizational structure via a

graphical adaptation.

This is possible because business objects are mapped to the installation data.

Make sure that you have downloaded the necessary bitmap files for the

organizational structure composer on your C drive. You can find these graphic

files in the note belonging to the solution builder.

33



After switching to change mode, it is possible to navigate through the graphical

display of the sample organizational structure.

First, select the icon for the personalization of the organizational structure.

Second, enter your target language and choose enter.

Next, double click the elements you would like to change.

In step five, enter your new description and key in the dialog box and confirm

with enter (6).

34



Dialogue boxes are displayed, where you change the description and the keys

of the different elements of the organizational structure. Choose Enter and

then, after finishing your personalization activities, choose Save.

35



Further data, like master data, can be personalized apart from the

organizational structure.

Choose the highlighted icon and perform the personalization. This type of

personalization is especially important for the activation of rapid deployment

solutions in an installed base. Here the necessary adaption can be done before

the activation of the rapid deployment solution so that the settings correspond

to the existing settings.

36



If you work have not transferred the scope automatically from the Solution

Manager you can also do the scoping and its preparation manually in the

Solution Builder. This is normally done if you have the Solution ManagerVersion 7.0 with which the functionality “Pass data to Solution Builder “ is not

possible.

To do this proceed in the following way:

Download solution file (xml) from note

Upload solution file to Solution Builder

Do the scoping in the Solution Builder

37



In the note attachment you will find a zip file containing the installation data files

for your rapid deployment solution.

38



Before starting the personalization, upload the installation data files for the

activation into the solution builder.

Enter the path where your text files are stored.

If you do not plan to activate with internal data afterwards, you can upload only

the files required for personalization.

39



RDS solution should be available in Q4 2011 on the webserver.

40





Now, you activate the selected scope in the Implementation Assistant.

42



The Configuration Guide is the central document for manual configuration of

the scenarios. It is a step-by-step description for all necessary configuration

activities.

The counterpart to the Configuration Guide inside the system is the

Implementation Assistant. Every step in the Configuration Guide corresponds to

a step in the Implementation Assistant. With the SAP Best Practices

Implementation Assistant, it is possible to perform the activation automatically.

After the activation has been successfully performed, the selected SAP Best

Practices scenarios are up and running.

43



The solution builder enables the user to quickly activate an SAP Best Practices

package and control the status with minimal user interaction.

44



Press the Activate button and in the displayed dialogue box enter a path for

supplemental data. Enter a workbench request and customizing request,

decide if you would like to activate with or without demo data and then pressEnter. The Solution Builder will use the uplaoded installation data files for the

activation.

45



BC Sets are activated in the solution builder and serve as placeholders to

import customizing. The customizing is stored in text files.

46



In the solution builder, eCATTs are responsible for the import of sample master

data of the SAP Best Practices packages that are activated. The sample

master data is stored in text files.

47



The solution builder activation stops and needs the user’s interaction if a

manual activity has to be executed, an eCATT has to be run in the foreground,

or an error occurred. In these cases, documentation or an error log is displayedto give guidance to the user.

48



If the activation is interrupted because a manual step must be performed, a

corresponding performance assistant text with detailed instructions will appear.

After execution of the manual step, you must confirm this activity.

49



If the activation is interrupted because a step must be performed in the

foreground, a corresponding performance assistant text with detailed

instructions will appear. After execution of the foreground step, you mustconfirm this activity.

50



To stop a running activation, open a second session and use the Stop button.

The current step is finished and the complete activation is stopped.

51



To navigate to the latest note, select the Information button in the upper right

corner of the solution builder entry screen.

52



After successful activation, a green check mark is set on scenario level and the

building blocks that have been activated are highlighted in the building block

library.

53



During SAP Best Practices activation via the solution builder, errors might

occur. In that case, the solution builder stops and an error log is displayed in

the lower-right corner of the solution builder. You can navigate directly to the logto check the error details. In addition, you can refer to the relevant Quick Guide

and the corresponding note belonging to the SAP Best Practices package. As a

first step, you should check if you are running the appropriate release and

Support Package levels in your system.

After you have checked the error log, Quick Guide, and SAP note, try to find a

solution by using your application knowledge. If this doesn’t help, create a

message in the support portal.

54



Your first step should be to read the error log in the solution builder.

55



If the activation is interrupted because of an activation error, a detailed error log

is provided in the bottom-right area of the screen.

Do not manually set the status of this activity to OK before the problem is

solved. After the problem is solved, you must activate the project again.

56



By clicking on the error message in the log area, you navigate directly to a

detailed view of the eCATT log. You can drill down to every screen level. To get

valuable information about the error, go to the TCD node, and then expand theMessages section.

57



Let’s take a look at the solution builder log of a BC Set activation. The line

external path shows the location of the text file that contains the data that was

imported in this step.

In the Variants folder, the values that are imported during the BC Set activation

are displayed.

The highlighted link is the link to the actual BC Set log. Follow this link to get

detailed information about the error.

58



It is a good idea to compare the data used to execute the eCATT or BC Set

with the data in the Configuration Guide.

Access the corresponding Configuration Guide via the documentation DVD or

the Help portal and compare the values actually imported by the eCATT or BC

Set, which are displayed in the log under Import, with the values described in

the Configuration Guide. Then try to enter the data manually. If this leads to no

error, the set of data is correct, but then there is something wrong with the

eCATT or BC Set.

59



If the solution builder error log hast not helped to solve the error, check the

relevant Quick Guide and SAP Note.

60



If you receive errors, we recommend that you check the Quick Guide and the

collective note for the corresponding SAP Best Practices solution.

61



If the error and appropriate solution cannot be found in the listed sources of

information, try to find your own solution using your application knowledge.

62



When trying to find your own solution, first try to understand why the error

occurred in an eCATT or in a BC Set.

Do the following to verify the origin of the message:

Compare system settings in the system with the required system settings in

the Quick Guide.

Check the information of the corresponding SAP Note.

If everything mentioned above is correct, drill down in the error log and find out

what the actual message is. Then, in case of an eCATT, run the eCATT in the

foreground and check the values that are described in the Configuration Guide.

In the case of a BC Set, check the details of the BC Set log inside the solutionbuilder log and compare the settings with the corresponding step described in

the Configuration Guide.

63



To get more information about an eCATT error, run the eCATT in the

foreground. To run a master data eCATT in the foreground, set the flag for

Foreground and check the screen sequence, screen fields, and issued systemmessages during the eCATT run.

64



The solution builder offers some additional features for troubleshooting .

65



The solution builder offers some more features, which help during the

activation, and especially during troubleshooting. To get a complete activation

log covering the activation of the entire scope, select and right-click on thesolution and choose Export Log .

66



It is also possible to reactivate single BC Sets. Right-click on the BC Set step in

the structure and select Reactivate.

67



For each BC Set step in the structure, it is now possible to compare the content

of the text file containing the customizing data and the actual content of the

system. Right-click on the BC Set step in the structure and chooseComparison.

Then enter the correct path where your text files for the activation are stored.

68



By selecting and right-clicking an activity in the structure and choosing

Installation Data, you can check the content of the text file containing the

customizing and master data values before and after the activation.

69



To find out which scenario building block is included in the scenario, right-click

the respective building block in the building block library and select the Where-

Used List . A dialogue box appears, which lists the solutions and scenarioscontaining this block.

70



If you cannot solve the issue, create a message in the support portal on the

correct component.

71



If you encounter an unknown error that you cannot solve on your own, contact

SAP support.

Create a message for component

SV-RDS-<xx>, where <xx> is the solution , for example, SV-RDS-FIN for SAP

FIN rapid-deployment solution.

Describe the error and list the package you are working with and the step of the

building block that cause the problem. Also be prepared to open an OSS

connection.

72













The rapid deployments solution is activated in an empty prototype system or an

empty development system.

78





* Conflict check will be available Q4 this year. See Appendix for more details.

* See Appendix for a description how to create a BC SET out of a transport

request

80



Other rapid deployment solutions are more designed to be activated in an

installed base. E.g SRM One-Client, Treasury+ Risk Management, HCM.

81









There are numerous advantages to using BC Sets:

They can easily be re-used for many installations.

It is possible to set customizing settings as default, variable, or fixed values.In the case of variable settings, the values can be changed before each

activation so that a personalized installation is possible for each

implementation project.

Furthermore, a simple consistency check is possible via the Customizing

Cross-System Viewer. The BC Sets can be quickly uploaded and

downloaded as local files. Documentation about a certain piece of

customizing can be attached to a BC SET. This way BC Sets can be used as

an archive for customizing for a simple re-use in the next project.

The disadvantage is a higher development effort compared to using transports.

85



An alternative to be considered is the use of Business Configuration Sets to

package the new customizing.

We will now have a look at the use of BC Sets before continuing with thepackaging process steps.

86



Next, we will show you how to create BC Sets out of transport requests in the

transaction SCPR3. Please follow the instructions.

87



Select the transport object related to your customizing which you have created

before in the IMG choose Enter then Save.

Then Create an object directory entry by entering the package and chooseSave.

Finally create a workbench request or assign your BC Set to an existing

workbench request and choose Enter .

88



Now you have captured your customizing in a BC Set and you can continue

with further processing, for example, assigning attributes to the customizing

fields.

89



Double-click the BC Set ID.

Then double-click the description of the BC Set, which is displayed in the

central area of the tool.On the right-hand side, check which tables are involved.

Double-click on one of the tables that has a green dot on the right-hand side.

Check the content of these tables in the lower area of the screen

Go to change mode, select the Field Selection Attributes tab, set the field

description storage location to Variable, and save.

90



In the transaction SCPR20 enter the technical name of the BC SET and run a

conflic check and a comparison between BC SET and database table.

91



To confirm select Copy Values.

92



Finally activate the BC SET by selecting Enter in the Activation Options

dialogue box.

93





Soon a conflict check will be available which will list the conflicts between

existing settings and the content which is going to be activated.

95



Go to the Solution Editor and select Solutions-> Procedures-> Find Conflicts.

96



Then proceed to Goto -> Change Management ->Data Changes. Then you

select the change group conflict and display the differences between the IMG

and the uplaoded data form the installation data files. Finally you decide if youwant to apply a change or not.

97



Business Configuration ApplicationProcessingInterface is the successor of BC-

Sets

Read/Write capability offers a solid technical foundation for content lifecycle

management tasks, eg, content upgrade, content enhancement.

Elimination of technical objects simplifies content development

98





In the activation monitor the user can check the status of activations,

personalization, scoping etc.

100



After selecting the Activation Monitor in the Solution Launch Pad activation

progress information is displayed. E.g “Activation has stopped” because of a

manual step. An e-mail is sent to the user who is logged on containing thisinformation.

101



Soon a new UI is available where the scoping can be conducted in a

webdynpro interface via drag and drop. At the moment this is not relevant for

the Rapid Deployment Solutions.

102



Soon a new UI is available where the personalization can be conducted in a

webdynpro interface

103



Some steps can be activated via a BC API which is connected with the BC SET

and accelerates the activation. At the moment the use is restricted due to

challenges concerning conversion rules e.g currencies and dates. The user canselect this option via the User Settings in the Solution Editor.

104



You should now be able to:

Describe the integration of the Solution Manager tool and the Solution Builder

tool in an implementation project and the relevant phase in the Ste-by-StepGuide

Run the basic steps how to activate a SAP Rapid Deployment Solution using

the Solution Builder tool

Use the right procedures for the different use cases for the activation of a

SAP Rapid Deployment Solution.

Describe further planned enhancements of the Solution Builder functionalities

Create a BCSET out of a transport, run a conflict check and activate the

BCSET

105



Documents

RDS Solution Builder