ARIS SAP Solution Manager - How to Integrate

(C) 2004 by IDS Scheer AG. All rights reserved.

ARISTM IDSTM YTM

© IDS Scheer AG www.ids-scheer.com

ARIS & SAP Solution ManagerARIS & SAP Solution Manager

How to…How to…

Britta HiltBritta Hilt

September 2004September 2004

© IDS Scheer AG ARIS Process Platform www.ids-scheer.com2

Organizational PreconditionsOrganizational Preconditions

AgendaAgenda

Benefits of ARIS and SolMan IntegrationBenefits of ARIS and SolMan Integration

How do ARIS and SolMan work together?How do ARIS and SolMan work together?

Procedure: ARIS and SolMan IntegrationProcedure: ARIS and SolMan Integration

Database Landscape & Important Tips in HandlingDatabase Landscape & Important Tips in Handling



AgendaAgenda







Process oriented implementation of mySAP Business Suite using SAP NetWeaver

Company processes are based on preconfigured SAP content (SolMan)

i.e. 300 Business Processes for CRM IDS Best Practice models

Company process specifications are a guidance through the entire implementation process: business

blueprint, configuration, testing, training, going live – all cross- component

Reported out of ARIS possible for training requirements, end user documentation

SolMan as platform for the ongoing operation, i.e. monitoring, help desk, …



AgendaAgenda






Organizational preconditionsOrganizational preconditions

1 responsible role for SolMan Which structure is required to support the implementation

project the best way? Based on that, the modelling will be structured in ARIS.

Which procedure will be followed as soon as all relevant information is transferred from ARIS into SolMan?

User management / access rights / ..? Which documents should be integrated in SolMan, which only

in ARIS? Responsibility that all IMG objects and transactions are

allocated in SolMan reference structure; is allocation to BC sets also required?...

Should non-SAP transactions be available in SolMan? (“entire picture” of implementation in SolMan; holistic approach for testing) If yes, non-SAP components must be listed in system landscape.

…


Organizational preconditionsOrganizational preconditions

1 responsible role for ARIS Customizing (method filter / semantic checks / …) User management / access rights / … Modeling conventions

Which information is represented in which way?(models / objects / symbols / attributes / relationships)

Which checks must be executed by each modeler before releasing their models?

Model templates & settings ARIS is the leading system for process specification



AgendaAgenda






How do ARIS & SolMan work together?How do ARIS & SolMan work together?

In ARIS Customer’s processes are described independent of a

software solution (high level) Customer’s processes are

described in detail mapped to “SAP world”



Result Customer’s process models with all relevant process

information, SAP-process steps / manual activities / non-SAP process steps

(if relevant) For each SAP process step, a detailed description can be given

(ARIS report can generate end user documentation & training requirements)

For each process step, the involved role is defined (relevant for training requirements)

For SAP process step, the SAP transaction can allocated

IT landscape (i.e. overview of interfaces), organizational structure, data (if required), …



In SolMan This structure is transferred into project where

further specifications are documented Jump to IMG / transactions / SAP help is realized

Basis for configuration, testing, training, going live and ongoing support



AgendaAgenda






ProcedureProcedure

ConventionsConventions

OverviewOverview

Step 1 – Configure ARIS Server & ClientsStep 1 – Configure ARIS Server & Clients

Step 2 – Prepare customer databaseStep 2 – Prepare customer database

Step 3 – Set up SolMan project in SolMan & ARISStep 3 – Set up SolMan project in SolMan & ARIS

Step 4 – Document level 1 business modelStep 4 – Document level 1 business model

Step 5 – Structure customer databaseStep 5 – Structure customer database

Step 6 – Document level 2 overview modelStep 6 – Document level 2 overview model

Step 7 – Document level 3 process modelStep 7 – Document level 3 process model

Step 8 – Quality checkStep 8 – Quality check

Step 9 – Generate SAP Process Step List via ARIS ReportStep 9 – Generate SAP Process Step List via ARIS Report

Step 10 – Synchronise ARIS SolManStep 10 – Synchronise ARIS SolMan

Step 11 – Add required information in SolManStep 11 – Add required information in SolMan


ProcedureProcedure


Overview Overview













ReferenceModel Structure

ReferenceModel Structure

BestPractice

BestPractice

Step AStep AStep AStep ACompanymodels

Companymodels

SAP SolManStructure

SAP SolManStructure=

OverviewOverview

Step BStep BStep BStep B

L1L1

L3L3

L2L2

SAP APOCo

mpo

ne

nts

Pro

cess

ste

ps

SAP APOCo

mpo

ne

nts

Pro

cess

ste

ps

SAP APOCo

mpo

ne

nts

Pro

cess

ste

ps

Create Forecasts forecast

SNP:InteractivePlanning

Product View



Product View



Product View


11

22

33

44

55

66

77

88

99

1010

1111 1111

OverviewOverview

Step 1 – Configure ARIS Server & ClientsStep 2 – Prepare customer databaseStep 3 – Set up SolMan project in SolMan & ARISStep 4 – Document level 1 business modelStep 5 – Structure customer databaseStep 6 – Document level 2 overview model

Step 7 – Document level 3 process model Step 8 – Quality check Step 9 – Generate SAP Process Step List via

ARIS Report Step 10 – Synchronise ARIS -> SolMan Step 11 – Add required information in SolMan


ProcedureProcedure

Conventions Conventions

OverviewOverview













Conventions - GeneralConventions - General

Folder structure It is important for easy orientation that Reference Models

(SAP / IDS) and Company Models are strictly saved in 2 individual folders!

All models created by ARIS user must be saved in the correct folder.

Reuse of reference models Company models use Reference Structure (SAP / IDS) objects

(occurrence copy) and have new objects. SAP SolMan object is copied and pasted from SAP SolMan

folder structure in company model Company models

Added with relevant information, i.e. per process step: role, textual description, transaction code (if relevant)

Are transferred into SolMan


Level 0 SolMan root model:

no attributes required Project object

attributes SAP function type: project Assigned to level 1

scenario model Level 1

Model attribute SAP model type: project Released on / by / Release

Objects Relevant for SAP

Object attributes SAP function type: scenario Colour: white

Not relevant for SAP No object attribute required Colour: green

Assigned to level 2 scenario models No occurrence copiesNo occurrence copies within models

Responsible: ARIS AdminResponsible: ARIS AdminResponsible: ARIS AdminResponsible: ARIS Admin

Conventions - Level 0 + 1Conventions - Level 0 + 1


Responsible: ARIS AdminResponsible: ARIS AdminResponsible: ARIS AdminResponsible: ARIS Admin

Conventions - Level 2Conventions - Level 2

Level 2 Model attribute

SAP model type: scenario Released on / by / Release

Objects Relevant for SAP

Object attributesSAP function type: process

Colour: white Link to Business Blue Prints

(external files) Not relevant for SAP

No object attribute required Colour: green

Assigned to level 3process models

NO OCCURRENCE COPIESNO OCCURRENCE COPIES within models(except process interface symbols on level 3)

Assigned to level 3 process models



Level 3 Procedure to get model

Copy eEPC template (in libraries)and paste it into correct folder.Legend & model nameplacement available

Assign level 2 object toexisting level 3 eEPC.

Copy level 2 object name(highlight object, F2, copy)

Paste level 2 object name into level 3 model name attribute(open level 3 eEPC, F8, double-click in model name attribute, paste, ensure that no line break in the model attribute name.)

Delete model If model needs to be deleted, rename it in

DEL_DEL_Admin will delete it.



Level 3 Procedure to get model content

Copy & paste from Best Practiceor SAP SolMan reference models(symbol: green or white)

Create new functions if SAP relevant: white symbol if not supported by SAP: green

1 function equals moreor less a TA

Function attribute SAP Component must be maintained accordingto text in library model

Relevant objects are

Layout Display print pages in model

(view – options – model options (global)) Print scaling >= 65 % (recommended) Not larger than 2 DIN A 4 (portrait)

horizontal: 1 page definitely ( intranet publishing) vertical: 2 pages max recommended

event function SAPfunction

persontype

processinterface


Pink

Green

White

Yellow

White

Blue

White

White

White

EPC Process Symbol Conventions - Level 3EPC Process Symbol Conventions - Level 3Symbol Name / Description Colour

Event

Process step(non-SAP)

Process stepSAP function

Organizational responsibility

Preceding process /Following process

Application system(SAP or non-SAP)

Data input / output(within SAP system)

Data input / output(outside of SAP)

Exclusiv Or

And / Or

And

Start of process / End of processPrior to decision merge ANDANDafter a decision split

Must be linked to all functions: role who isexecuting it. Copy from library model

Exactly 1 of the paths is followed

At least 1 of the paths is followed

All paths are followed

Must be linked to all non-manual functionsCopy from library model!


Level 3 - Additional Info for each Process Step Who is executing the process step? (Role) Which application system is supporting the process step?

Which data is required as input or output?


Confirmdocument

receiptSA54 Accountant

Checkcompletenessof remittance

SAP R/3Enterprise

Accountant

Printmaterialdocument

MaterialDocument

MaterialDocument

Data withinData withinSAP systemSAP system

Data outside ofData outside ofSAP systemSAP system



Level 3 Process models

Model attribute SAP model type: process

(for Process Step List eEPC)DO NOT MAINTAIN IF REPORTDO NOT MAINTAIN IF REPORTFOR LIST EEPC IS USED!!FOR LIST EEPC IS USED!!

Released on / by / Release All SAP functions, attribute

SAP function type = process stepSAP function type = process step(or attribute Ready for synchronisationReady for synchronisation, if report forProcess Step List eEPC is used later on)

No occurences copies in customer models for SAP functions Libraries

Move all roles into organisation folder and paste them into“org chart”

Move all data input / output into data folder and paste them into “data model”



Level 3 Delete / move models

Find all models with DEL_and delete them

Move models into folderon request

Allocate reused objects intocorrect folder

Find all SAP SolMan objects &Best practice model objects used in the company models

Move object definition (& assigned FAD) into corresponding company folder(use report Object_AssignedModel_Path.rso, ObjectOccInModel_Path.rsm (with eval filter for SAP functions))


ProcedureProcedure


OverviewOverview

Step 1 – Configure ARIS Server & Clients Step 1 – Configure ARIS Server & Clients

Step 2 – Prepare customer database Step 2 – Prepare customer database

Step 3 – Set up SolMan project in SolMan & ARIS Step 3 – Set up SolMan project in SolMan & ARIS

Step 4 – Document level 1 business model Step 4 – Document level 1 business model

Step 5 – Structure customer database Step 5 – Structure customer database

Step 6 – Document level 2 overview model Step 6 – Document level 2 overview model

Step 7 – Document level 3 process model Step 7 – Document level 3 process model

Step 8 – Quality check Step 8 – Quality check

Step 9 – Generate SAP Process Step List via ARIS Report Step 9 – Generate SAP Process Step List via ARIS Report

Step 10 – Synchronise ARIS SolMan Step 10 – Synchronise ARIS SolMan

Step 11 – Add required information in SolMan Step 11 – Add required information in SolMan



Create method filter / template(Method filter must have value-chain symbols in eEPC)

Define client settings and ensure that they are applied to all client PCs.



Reference models SAP SolMan models

Run import from SolMan Repository to get all SolMan objects & models WITHOUT Project SolMan reference

Merge all relevant IDS Best Practice models into database Folder structure: Processes / Libraries / IDS Best Practice

models / SAP SolMan models

Library models eEPC template with legend for level 2 & 3 and with correct model

attributes SAP components (text according to scenario report run over SAP

SolMan scenario DB) organisational chart for roles data model for data objects


Create customer project in SolMan Create a new project in SolMan / Administration

Name & Title Language = ARIS DB language

Select all components & versions according to scope Initial transfer from SolMan project into ARIS

In ARIS, synchronise in Processes folder Select SolMan project & synchronize Create model and copy project object in the new access model

(otherwise, reorg would delete project object) Rename empty eEPC assigned to project object in

Level 1 Business Model




Empty Level 1 Business Model = eEPC with Value chain symbols

Create level 1 business model together with customer

Set in scope / out of scope of SAP implementation project according to colour code

Maintain legend



Create folder structure according to level 1 business model

Assign level 2 model for each level 1 element in relevant folder; models have no content, only legend

DO NOT have the same value chain element occur more than once in company models!(No occurrence copies)(No occurrence copies)

Integrate all required access objects in access model, i.e. organisation, data, … & assign to library models

User / user groups Read / Write access, no delete access Method filter / functional privileges



Maintain content for level 2 overview model together with customer in assigned level 2 model

Set in scope / out of scope of SAP implementation project according to colour code

DO NOT have the same value chain element occur more than once in company models!(No occurrence copies)(No occurrence copies)



Use eEPC template and assign, as described in conventions above

Reuse SAP / IDS Best Practice reference models and / or create new SAP / non-SAP functions

Copy / paste relevant part of reference objects in level 3 eEPC Allocate person type for functions which require user interaction Define data input / output, if required If required: For new SAP function, assign function with FAD and

model screen(s) Maintain FAD model attribute: SAP model type: process stepSAP model type: process step In screen, maintain transactiontransaction attribute & SAP componentSAP component

Use level 2 overview objects as interfaces in level 3 process models; ensure that end event = start event


Step 8 – Check qualityStep 8 – Check quality

Level 1 & 2: colour coding; Model / object attributes Level 3

Assignment level 2 object name = level 3 model name Semantic / logical flow / all required information allocated

(i.e. roles, ..) Process interfaces from level 2 / start & end event / … Libraries updated (objects moved & pasted into library models) Model / object attributes maintained (SAP component according

to template text, ready for synchronisation, …) Used objects in company folder

Run report on used models which outputs all objects and the path where they are saved in

Move object from SolMan / IDS Best Practice folder into correct company folder

Move assigned FAD with screen into correct company folder SAP ID only existing once in relevant models

(run report to check)


Step 9 – Transfer models into SAP Production databaseStep 9 – Transfer models into SAP Production database

Define settings in Merge, that assignment level is 4 level 1 level 2 level 3 FADs)

Select project model (access model) & merge intoSAP Production Database

ReasonIn the next step, for each relevant level 3 eEPC, an additional list eEPC is generated. This should not be done in the “real” database which is also the basis for web publishing.

Please noteAll required attributesAll required attributes (SAP, release) must be maintainedmust be maintained before this merge is done. No maintenance of attributes in SAP Production DB! (= Inconsistency among databases!)


Report is started on project (or scenario / process) object Report drills down: function eEPC (n times) until it finds an eEPC

which does not have SAP model type maintained Column eEPCs are not taken into consideration In lowest eEPCs, all functions are selected which are ticked with:

Ready for synchronisation = yes Report assigns new eEPC per process object

Name: Z_[name of process object]Z_[name of process object] All process steps which are ready for synchronization and do not yet

have an SAP ID are copied in new eEPC If process step already occurs somewhere in a process step list, it is not

copied anymore decision is taken in which Process Step List the process step should occur SAP process steps only occur onceonce in reference structure

In new eEPC, model attribute SAP model typeSAP model type is maintained with ProcessProcess All objects copied in Process Step list eEPC are maintained with

SAP function type: Process stepSAP function type: Process step andSAP Component: R3 EnterpriseSAP Component: R3 Enterprise(only possible if only 1 SAP Component in scope!)(only possible if only 1 SAP Component in scope!)




Result in ARIS Each level 2 SAP process is assigned to 2 models: level 3 process and

SAP Process Step List eEPC Process Step List eEPC maintained with model attribute: Process Each relevant process step occurs onceonce (!) in the entire reference

structureThus, there are Process Step List eEPCs which do not have all relevant process step for their business process they relate to.

For each relevant process step, attributes Process stepProcess step andSAP componentSAP component maintained (if only R/3if only R/3!!)

Please note Instead of using additional SAP Process Step List eEPCs, it could also be

possible to check if SAP relevant functions are used more than once in the entire synchronization structure

If they are not, then, the generation of List eEPCs is not required In order to check, run analysis “model comparism”

on ALL relevant models


L2-A1 L2-A2 L2-A3

oo

mr

= Ready for synchronization

M = manual process step

O = occurrence copy of the same process step

Z = new SAP process step (customer-specific)

.

p .

z .

z5

.

.

o

pr

z

L2-B1 L2-B2

Model name: z_...Model attribute for SAP model type: process

Result in ARIS

L1-A L1-B L1-C



o

m

p .

.

o

p

Model name: z_...Model attribute for SAP model type: process

Result in SolMan after Synchronisation

Step 11 – Synchronise ARIS -> SolManStep 11 – Synchronise ARIS -> SolMan

Open DB with Entire Method On project object, synchronise ARIS models

Assigned level 1 business model eEPC And their assigned level 2 overview model eEPCs And their assigned level 3 SAP process step list eEPCs

= Ready for synchronization

M = manual process step

O = occurrence copy of the same process step

Z = new SAP process step (customer-specific)



Blue print details, test cases, …



AgendaAgenda






Development DB

Production DB Models are signed off

All attributes are maintained (SAP & Release)

Generate list eEPC

Merge

Delete Z_eEPCs Export with

evaluation filter

Synchronise

Database landscapeDatabase landscape


Important tips in handlingImportant tips in handling

NEVERNEVER EVER use a so-called Definition copyDefinition copy in ARIS!Reason:If SAP relevant objects are duplicated via definition copy, the attribute SAP IDSAP ID is also copied in the new ARIS object.Then, synchronization is not possible anymore because SAP ID must be uniqueunique.

Ongoing synchronizationsBefore 2nd – nth update, run checks

SAP-ID-Report: is SAP ID unique

Delta-Report: is there a process step occurring in a Process Step List eEPC which is not used in any company process eEPC?If yes, only deactivate in Process Step List eEPC; do not delete it!

Documents

ARIS SAP Solution Manager - How to Integrate