2 - RDS Technical Concepts

Embed Size (px)

Citation preview

  • 8/10/2019 2 - RDS Technical Concepts

    1/34

  • 8/10/2019 2 - RDS Technical Concepts

    2/34

    In this presentation, we provide an overview of the development concepts ofpreconfigured solutions. The presentation consists of five chapters. The firstchapter gives you an overview of the development concepts. The second chaptercovers the building block concept. The third describes the idea of data storage intext files. The fourth describes the tools for customizing and master data import,and the fifth chapter provides an explanation of the detailed SAP documentation.

    2

  • 8/10/2019 2 - RDS Technical Concepts

    3/34

  • 8/10/2019 2 - RDS Technical Concepts

    4/34

    Lets start with an overview of the technical concepts.

    4

  • 8/10/2019 2 - RDS Technical Concepts

    5/34

    It is important to understand the architecture and technical concepts of the SAPRapid Deployment Solutions in order to successfully process the step Deploy Activate.

    5

  • 8/10/2019 2 - RDS Technical Concepts

    6/34

    We followed different development philosophies during the creation ofpreconfigured packages. Due to this, there are big differences between an SAPRDS package and a preconfigured solution delivered via one big transport or clientcopy.

    The packages are divided into building blocks. The import of the samplecustomizing and sample master data values are automated and executed viatools. The customizing and master data values are stored in external text files.Thus, the technical framework and the content are separated, allowing the contentto 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 detaileddocumentation. For example, every single customizing and master data setting isdocumented. This enables the user to understand and re-use settings of separatebuilding blocks for their own purposes.

    6

  • 8/10/2019 2 - RDS Technical Concepts

    7/34

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

    The Solution builder speeds up installation and makes it possible to install anentire solution in one go. You can install only those selected processes youchoose. The involved technical objects, eCATTs and BC Sets, start automaticallyvia the solution builder, allowing you to avoid single BC Sets and eCATTs

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

    7

  • 8/10/2019 2 - RDS Technical Concepts

    8/34

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

    8

  • 8/10/2019 2 - RDS Technical Concepts

    9/34

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

    9

  • 8/10/2019 2 - RDS Technical Concepts

    10/34

    Lets begin with a definition of building blocks Building blocks are logical units with structured settings of customizing and masterdata delivered by SAP Rapid Deployment Solutions. For example, Building Block101 contains the enterprise structure of the Baseline Package with settings for theorganizational structure.

    Building blocks contain customizing and master data steps as well as forms and/orreports, as needed. Each building block is fully documented and contains aConfiguration Guide. Scenario building blocks also include a business processdocument.

    10

  • 8/10/2019 2 - RDS Technical Concepts

    11/34

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

    11

  • 8/10/2019 2 - RDS Technical Concepts

    12/34

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

    12

  • 8/10/2019 2 - RDS Technical Concepts

    13/34

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

    13

  • 8/10/2019 2 - RDS Technical Concepts

    14/34

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

    14

  • 8/10/2019 2 - RDS Technical Concepts

    15/34

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

    15

  • 8/10/2019 2 - RDS Technical Concepts

    16/34

    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 theareas of manufacturing, service, trade, and financials.

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

    A combination of all layer 0 blocks, layer 1 blocks of a particular area, andselected blocks of layer 2 make up the entry level of trade, manufacturing, service,and finance, accordingly. These entry-level scopes can be changed depending onyour needs; you can select additional process blocks or deselect processes.

    16

  • 8/10/2019 2 - RDS Technical Concepts

    17/34

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

    17

  • 8/10/2019 2 - RDS Technical Concepts

    18/34

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

    18

  • 8/10/2019 2 - RDS Technical Concepts

    19/34

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

    19

  • 8/10/2019 2 - RDS Technical Concepts

    20/34

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

    20

  • 8/10/2019 2 - RDS Technical Concepts

    21/34

    During the installation process, sample customizing and sample master data isimported. 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. Thecontent and the technical framework are separate.

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

    21

  • 8/10/2019 2 - RDS Technical Concepts

    22/34

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

    22

  • 8/10/2019 2 - RDS Technical Concepts

    23/34

    The solution builder enables partners to select, personalize, and activate apreconfigured processes in the SAP system, thereby reducing implementationtime and cost. In addition, partners can create their own business content usingthis tool as a development and deployment platform.

    23

  • 8/10/2019 2 - RDS Technical Concepts

    24/34

    A Solution ManagFor Rapid Deployment solutions (RDS) content is provided astemplates with the regular Solution Manager implementation content add-on (ST-ICO, ICO-RDS).

    Solution Manager template and a Solution Builder Solution are interrelatedenabling a seamless integration of both tools during the deployment phase of anRDS.

    24

  • 8/10/2019 2 - RDS Technical Concepts

    25/34

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

    Whereas eCATTs import the sample master data, BC Sets import customizingsettings.

    25

  • 8/10/2019 2 - RDS Technical Concepts

    26/34

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

    26

  • 8/10/2019 2 - RDS Technical Concepts

    27/34

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

    27

  • 8/10/2019 2 - RDS Technical Concepts

    28/34

    Detailed documentation makes the settings delivered by SAP Rapid DeploymentSolutions 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 takeadvantage 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 end-user documentation.

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

    28

  • 8/10/2019 2 - RDS Technical Concepts

    29/34

    Next, lets focus on the necessary software.

    29

  • 8/10/2019 2 - RDS Technical Concepts

    30/34

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

    30

  • 8/10/2019 2 - RDS Technical Concepts

    31/34

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

    Up from Q2/2012 delivery the SAP Solution Manager content add-on ST-RDS 100 islisted in the SWDC. Up from Q3/2013 delivery directly underneath the appropriatesolution package (SAP Solution Manager content is available for each solution package).Before Q2/2012 the SAP Solution Manager templates were delivered within content add-on 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 thecomplete structure and implementation content (inclusive all documentation links) arecopied into the project. There you will use the structure, Business Process Descriptionsand transactions (if offered) to understand the solution package). In case of optionalscope 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 thesystem). To load the solution file and installation data will be done within an own stepafterwards

    Doing nothing more than these few clicks the package would be documented in asustainable way. That means we already did the documentation for you within the SAPSolution Manager template. Only the additional deltas will be documented in additionafterwards (Implement Options)

    31

  • 8/10/2019 2 - RDS Technical Concepts

    32/34

    To configure the preconfigured content of an SAP Rapid Deployment Solution youneed to apply the necessary software and download the correspondingdocumentation. In the case of SAP Rapid Deployment Solutions which can beactivated automatically, the necessary installation data files and solution filesneed to be downloaded.

    32

  • 8/10/2019 2 - RDS Technical Concepts

    33/34

  • 8/10/2019 2 - RDS Technical Concepts

    34/34