1

In this presentation, we provide an overview of the development concepts of

preconfigured solutions. The presentation consists of five chapters. The first
chapter gives you an overview of the development concepts. The second chapter
covers the building block concept. The third describes the idea of data storage in
text files. The fourth describes the tools for customizing and master data import,
and the fifth chapter provides an explanation of the detailed SAP documentation.

Lets start with an overview of the technical concepts.

It is important to understand the architecture and technical concepts of the SAP

Rapid Deployment Solutions in order to successfully process the step Deploy
Activate.

We followed different development philosophies during the creation of

preconfigured packages. Due to this, there are big differences between an SAP
RDS package and a preconfigured solution delivered via one big transport or client
copy.

The packages are divided into building blocks. The import of the sample
customizing and sample master data values are automated and executed via
tools. The customizing and master data values are stored in external text files.
Thus, the technical framework and the content are separated, allowing the content
to be easily adapted. These sample settings can be modified easily with the
solution builder tool.

Another great advantage of SAP rapid deployment solutions is the detailed

documentation. For example, every single customizing and master data setting is
documented. This enables the user to understand and re-use settings of separate
building blocks for their own purposes.

The above-mentioned building block concept allows easy and flexible installation
of the implementation content. Its advantage is that you do not have to install one
big block, but you can select building blocks containing settings that are relevant
to you. You can even change the data before installation if you want to run the
demo with your own data or use the sample data.

The Solution builder speeds up installation and makes it possible to install an

entire solution in one go. You can install only those selected processes you
choose. The involved technical objects, eCATTs and BC Sets, start automatically
via the solution builder, allowing you to avoid single BC Sets and eCATTs
activation.

The documentation provided explains how to extend or change the solutions. The
same documentation can serve as a guideline for partners in case they use a
preconfigured package as a foundation for their own solution.

Now that we have reviewed the development concepts, we will look at the building
block concept in more detail.

Here we will provide a basic overview of building blocks, and explain their content,
sequence, and architecture.

Lets begin with a definition of building blocks

Building blocks are logical units with structured settings of customizing and master
data delivered by SAP Rapid Deployment Solutions. For example, Building Block
101 contains the enterprise structure of the Baseline Package with settings for the
organizational structure.

Building blocks contain customizing and master data steps as well as forms and/or
reports, as needed. Each building block is fully documented and contains a
Configuration Guide. Scenario building blocks also include a business process
document.

10

Building blocks need certain other building blocks to be installed in the system as
a prerequisite. If you install a complete solution or a selected process via the
solution builder, the information for the necessary prerequisite is already stored in
the solution builder. In that case, you do not have to investigate which building
blocks are required as prerequisites, as this has been done for you by the solution
builder.

11

For rapid deployment solutions you find the prerequisite matrix via the Step-ByStep Guide. In the Deploy phase navigate to Manual or Automated Activation.

12

Then select Content Library and go to the Prerequisites Matrix Link.

13

Here you see a list of Scenarios which are part of the Rapid Deployment Solution
and for each of these scenarios a list of building blocks which have to be activated
before you activate the actual scenario block.

14

Here you see the architecture of an PLM Rapid Deployment Solution.

15

the Baseline building blocks are structured in a layered architecture.

The first layer of blocks is called layer 0 and contains basic settings, for example,
the organizational structure or the chart of accounts.

The next layer, layer 1 (or foundation layer) contains more detailed settings in the
areas of manufacturing, service, trade, and financials.

In the last layer (layer 2 or Baseline library), you can find even more detailed
settings for these four areas.

A combination of all layer 0 blocks, layer 1 blocks of a particular area, and

selected blocks of layer 2 make up the entry level of trade, manufacturing, service,
and finance, accordingly. These entry-level scopes can be changed depending on
your needs; you can select additional process blocks or deselect processes.

16

Lets now move on to data storage in external text files.

17

In this chapter you will learn about the content and availability of external text files.

18

Here you see examples of the text files that contain the sample data belonging to
the implementation content.

19

The structure of most SAP Rapid Deployment Solutions is stored in an xml file.

20

During the installation process, sample customizing and sample master data is
imported. This data is stored in external text files.

Remember that these data is not stored in tools like eCATTs or BC Sets.

In the external text files, the data can be accessed and checked easily. The
content and the technical framework are separate.

The external text files are provided on the SAP Best Practices homepage in the
SAP Service Marketplace in dedicated folders per version and country.

21

Next, lets focus on the tools for customizing and master data import.

22

The solution builder enables partners to select, personalize, and activate a

preconfigured processes in the SAP system, thereby reducing implementation
time and cost. In addition, partners can create their own business content using
this tool as a development and deployment platform.

23

A Solution ManagFor Rapid Deployment solutions (RDS) content is provided as

templates with the regular Solution Manager implementation content add-on (STICO, ICO-RDS).

Solution Manager template and a Solution Builder Solution are interrelated

enabling a seamless integration of both tools during the deployment phase of an
RDS.

24

The tools used during the activation process of a preconfigured package are
called eCATTs and BC Sets.

Whereas eCATTs import the sample master data, BC Sets import customizing
settings.

25

Lets look at our last topic: Detailed documentation supplied with each SAP Rapid
Deployment Solution.

26

In the Step-by Step Guide go to Deploy -> Activate. Select Manual Activation and
then Content Library. A list with the documentation deliverables of the
preconfigured content is displayed.

27

Detailed documentation makes the settings delivered by SAP Rapid Deployment

Solutions very clear and transparent.

A central document for the activation is the Configuration Guide.

The configuration guide is used as:

A step-by-step instruction to configure a package manually, if the user does not want to take
advantage of the automated procedures

And a reference document for manual steps or error solving in the solution builder

A detailed description on transaction level of each scenario is delivered in the business process
documents. These documents can be used for demo, training, testing, and as a basis for enduser documentation.

The Quick Guide is a central document to support the actual activation activities.

28

Next, lets focus on the necessary software.

29

To find out which software is needed to configure the content of the SAP Rapid
Deployment Solution successfully in your system, go to the Step-by-Step Guide :
Start -> Confirm Installation. Then select the Software Requirements document.

30

The Software Download Center (SWDC) is the central place to find the Step-by-Step
Guide and all tool and content add-ons which are needed for the technical implementation
tool accelerators

Up from Q2/2012 delivery the SAP Solution Manager content add-on ST-RDS 100 is
listed in the SWDC. Up from Q3/2013 delivery directly underneath the appropriate
solution package (SAP Solution Manager content is available for each solution package).
Before Q2/2012 the SAP Solution Manager templates were delivered within content addon ST-ICO which is also accessible on top of the page

SAP Solution Builder add-ons are also listed if available for the solution package

After the download of the tool and content add-ons

The SAP Solution Manager content is useable and an implementation project will be
created choosing the appropriate Solution Package out of the list. The result is that the
complete structure and implementation content (inclusive all documentation links) are
copied into the project. There you will use the structure, Business Process Descriptions
and transactions (if offered) to understand the solution package). In case of optional
scope items which should not be implemented scope adjustments will be done

SAP Solution Builder tool and technical objects (e.g. raw BC Sets and eCATTs are in the
system). To load the solution file and installation data will be done within an own step
afterwards

Doing nothing more than these few clicks the package would be documented in a
sustainable way. That means we already did the documentation for you within the SAP
Solution Manager template. Only the additional deltas will be documented in addition
afterwards (Implement Options)

31

To configure the preconfigured content of an SAP Rapid Deployment Solution you

need to apply the necessary software and download the corresponding
documentation. In the case of SAP Rapid Deployment Solutions which can be
activated automatically, the necessary installation data files and solution files
need to be downloaded.

32

33

34