sap solution manager 4

7/31/2019 SAP Solution Manager 4

http://slidepdf.com/reader/full/sap-solution-manager-4 1/32

SAP Solution Manager 4.0 ProjectManagement - Business Blueprint Phase (Part III)

Posted by Sapna Modi in sapna.modi on Jun 28, 2007 3:58:58 AM

The part I of the SAP Solution Manager 4.0 series of weblogs targets on the functionality of SAPSolution Manager - Roadmaps Introduction (Part I). The Part II of the weblog series targets onProject Administration. In Part III, the Business Blueprint Phase is explained in detail. Insubsequent parts, other features of Solution Manager will be explained.

What is SAP Solution Manager:SAP Solution Manager is a tool, which assists in application management as per ITIL (ITInfrastructure Library) environment. The tool supports the entire lifecycle of solutions mainlyhaving six phases Requirements, Design, Build, Deploy, Operate & Optimize as per ITILstandard.It runs in a separate central system to which all the other SAP systems are connected. Theseother systems are called as Satellite Systems.

Latest Version:SAP Solution Manager 4.0.

Features of SAP Solution Manager:

• Solution Manager helps in all types of project management like Implementation,Upgrade, Maintenance, Rollout etc. by providing the project specific template.

• It is in line with SAPs AcceleratedSAP. And provide Roadmaps for the differenttypes of projects.

• It has Business Process Repository, which talks about SAPs best practice of running the business.

• It has eLearning feature, which offers the training along with feedback over web.

• It has test management feature, which offers the central storage repository for storingthe automated eCATT scripts along with manual scripts. The results of testing arecentrally stored and always available.

• It has its own standard Helpdesk feature, which is both SAPGUI based and web based.

• The Helpdesk feature is totally linked with Change Request Management, which helpsin transport for changes required in production issues.

• It has Solution Monitoring as well as Diagnostic feature, which helps in Operation Phaseof project.

• Solution Manager has lots of inbuilt reports, which server the different areas of it.

• It is linked with SAP Service Market Place.

• It can generate Installation/Upgrade key.

• It has its own Knowledge Warehouse for central documentation storage.

• It can integrate with ARIS, a detailed graphical business process modeling tool

• It can also integrate with Mercury tools like QTP for testing in web based environment.

Phases of Project Management As per AcceleratedSAP (ASAP) Model:

• Project Preparation Phase• Business Blueprint Phase

• Realization Phase

• Testing Phase

• Final Preparation for Cutover Phase

• Production Go Live Phase

• Support Phase

http://scn.sap.com/people/sapna.modi/blog/2007/06/28/sap-solution-manager-40-project-management--business-blueprint-phase-part-iii



http://scn.sap.com/people/sapna.modi

http://scn.sap.com/people/sapna.modi/blog


http://scn.sap.com/people/sapna.modi/blog/2007/05/06/sap-solution-manager--roadmaps-introduction-part-i











What is Business Blueprint Phase:In any SAP Project, first the project is planned out in terms of scope, roles, resources,landscape, time line, documentation templates, quality processes to be followed etc. Once theinitial administration happens, the details of the business is planned and worked out in theBusiness Blueprint phase. All the business scenarios related documentation also happens inthis phase following quality standards and templates. The complete documentation is placedon central file server for further reference. Once the scope is designed and frizzed, Business

Blueprint document is prepared finally and signed off from the client. The Microsoft Project willbe then designed depending on the outcome of this phase, which will be used in the furtherphases. Business Blueprint acts as a prerequisite for Realization & Testing Phase. This isclassical way of doing Business Blueprint if no Solution Manager is in picture.Above activates are now available in Solution Manager with all the required features of Business Blueprinting in advanced way along with lots of other key utilities.

Transaction for Business Blueprint Phase:SOLAR01Menu Path for Business Blueprint Phase:SAP Menu -> Tools -> SAP Solution Manager -> SOLAR01 Business Blueprint

Prerequisite of using Business Blueprint in Solution Manager:Project created in Solution Manager using SOLAR_PROJECT_ADMIN transaction in the ProjectAdministration phase.Key Features of Business Blueprint Phase in Solution Manager:

• In Business Blueprint phase of Solman, following items can be organized in hierarchicalstructure

o Organization Units

o Master Data

o Business Scenarios

o Business Processes

o Process Steps

• In the Business Blueprint, the Business Scenarios/Processes structure can be plannedout referring the standard SAPs Business Process Repository (BPR).

• Business Process Repository (BPR): Standard SAPs Business ProcessRepository is a repository of reusable predefined business scenarios/processes. Thecontents are Industry specific Best Practices for the given landscape. Landscape isavailable from Project Preparation Phase. BPR also includes Scenario Documentation, Transaction assignments, IMG Assignments, Configuration Guides, and PreconfiguredProcess delivered through BC Sets, Predefined Test Cases. Latest content of BPR canbe downloaded from SAPs Service Market Placefrom www.service.sap.com/solutionmanager

• The business scenarios can also be taken from other existing solution manager projectand/or from existing Solution Directory.

• Also, the Business Scenarios/Processes will be automatically available if any template(custom or standard) is selected during Project Administration phase.

• In this phase, the integration of ARIS can be done with Solution Manager for getting thedetailed business process modeling done out of ARIS. And further the Solman BusinessBlueprint features can be used.

•Custom Business Scenarios/Processes can be added & positioned as per requirement.

• Graphically the business scenarios are available.

• Maximum of three level hierarchies of the business scenarios/processes can beinserted into Solman.

• Project specific documents can be created here specific to businessscenarios/processes.

• The documentation is stored in the central Knowledge Warehouse of Solman.

• Support Desk messages can be created.

http://www.service.sap.com/solutionmanager

http://www.service.sap.com/solutionmanager



• Transaction specific to the given scenario/process can be launched in the satellitesystem via Business Blueprint.

• Automatic generation of Business Blueprint Document is featured.

• Automatic generation of MS Project is also featured.

• User specific settings can be done in terms of visibility of tabs, sequencing of tabs etc.

• Translation of project specific documents, URLs, knowledge warehouse documents,project structure can be done depending on the target language. If the standarddocuments are not available in the target language than they are displayed in theoriginal language.

• Document Management, which is one of the key features of Solution Manager, can beimplemented here in Business Blueprint Phase.

• Lots of standard reports are available for Business Blueprint Phase.

Business Blueprint in Detail:

• Log in to Solution Manager with a user ID having authorization of SOLAR01 transaction.

• Goto transaction SOLAR01.

• The Business Blueprint transaction will open with the last worked project in changemode.

• Click on Other Project ..(Shift+F5) button from the application toolbar.

• From the list of projects displayed, select the required project. And click on Select Project (Enter) button at the bottom.

• The selected project will open in change mode. There are different tabs in the BusinessBlueprint like Structure, Gen. Documentation, Proj. Documentation, Transactions,Messages, Graphics & End User Roles on right side. On the left side, the hierarchy of Organization Units, Master Data & Business Scenarios appear. The Business Scenarios

http://scn.sap.com/servlet/JiveServlet/showImage/38-44307-49914/img2.JPG




will further drill to Business Process & actual steps (i.e. transaction in SAP).

• Structure Tab:

o In the Organization Units, Structure tab helps to add Organization Area/Unit

from the BPR below a business scenario. In case of Master Data, Structure tabhelps to add Master Data Records from BPR below a business scenario. TheOrganization Units/Master Data Records are only used if they are exclusivelyrelevant to the Business Scenarios/Processes.

o Select the Business Scenarios option from the left side, click on Structure tabon the right side.

o From the Source dropdown, select Business Process Repository .

o Now, click on the Search Help (F4 Help) of Scenario Name.

o The search helps shows, industry specific details mapping to the logicalcomponent of the current project. Select SAP for Retail -> Instore Customer





Relationship Management & click on Continue (Enter).

o This will add the selected Business Scenario along with all the underlying

processes into it in the Structure tab.

o Click on Save button from the standard SAP toolbar to save the project.

o Now drill down the Business Scenario node on the left side, it will show the

underlying Business Processes.

o The level of hierarchy of Business Scenarios/Processes is restricted to level 3on left side. After third level, system doesnt allow to add any morestructure elements. And system shows a message in the Structure tab as you





cannot maintain any more structure node below this hierarchy level.

o The execution icon before the business process on the left side indicates thatthere is a standard SAP transaction in the Transactions tab to carry out thatstep.

o One can add custom business scenarios in the Structure tab. Also the standard

SAP Scenarios can be deleted. The sequence of business scenarios/processescan be planned as per requirement of project.

o Select the Business Scenarios at the top level on the left side. On the right sidein the Structure tab, add custom business scenario as per requirement.

o After adding the custom scenarios, click on Save button from the standard SAP

toolbar.o The Business Scenarios can be moved up/down depending on the required

sequence of scenarios in Structure tab. Select the Custom Scenario 2 in theStructure tab and click on Move Up button.






o The scenario will be moved one position up in the tab. Click on Save buttonfrom the standard SAP toolbar.

o The History of the Structure tab is also available here.

o At the Business Processes level, the name of the standard process can bechanged and if needed adjusted back to original.

• Gen. Documentation Tab:

o General Documentation tab contains the standard SAP delivered documents if the business scenario is selected from BPR.

o It also contains the documents from the template project.

o For the business scenarios, which are not taken from standard SAP BPR,wont have any documentation in this tab. Their documentation need to

be created in Proj. Documentation tab.

o No document can be added or deleted in this tab. Also the feature of Changing

the document, Check In/Check Out etc. are not available in this tab. Onlydocuments can be opened in display mode in this tab.

o Features of Where Used List, Export, Attributes etc are available.

o There is feature of copying document to Proj. Documentation tab. This is useful

in case if the document needs any changes. For this, first change the project inDisplay mode. Now, select the document & click onCopy Link-> Copy to Proj.







Documentation Tab button.

o A popup appears for Documentation Type to be used for the new copied

document in the Proj. Documentation tab. Select the appropriate type from thesearch help & click on Copy button at the bottom.

o The document gets copied into the Proj. Documentation tab.

o Also, user specific settings are available here to open document in the Gen.Documentation tab or in separate window. Refer the Menu Settings -> User

Specific -> General Settings.o The Gen. Documentation tab documentation is stored in the Solution Manager

Knowledge Warehouse.

• Proj. Documentation Tab:

o Proj. Documentation tab is used to store the documentation for the current

project specific to business scenario/process on the left side.

o The documentation is stored in the Context of Knowledge Warehouse, which isspecified in the Project Administration phase.






o In case of Template project, the documentation specified in the Proj.Documentation tab doesnt appear in the rolled out implementationproject.

o The document can be created using the template following all the required

quality standards. These are the different templates like functionalspecification template, technical specification template etc. It also has lots of standard SAP delivered templates.

o The document can be either created or copied to existing Solman document orlinked to existing Solman document or uploaded from desk or linked to weblink.

o The documents added here can be made Business Blueprint Relevant. This

means that the contents of the documents will be taken while generating theBusiness Blueprint Document in the sequence in which they are added.

o To add a document, select the business scenario/process on the left side &click on Insert Document button on the right side in Proj. Documentation tab.

o In the Add Document popup, give the Title for the document; selectthe Documentation Type as Customer Input Template (standard SAP template)from the dropdown. This dropdown will contain the custom documentationtemplates added during Project Administration phase. Click on Enter tocontinue.





o The document will open using the template of the specified document type inthe tab itself. Edit the document as per requirement and click on Close.

o Click on Yes to save the changes in the document.

o The document will be saved in the Proj. Documentation tab.

o The document can also be created by uploading it from desk. For this, selectthe business scenario/process on left side & click on Insert Document button in






the Proj. Documentation tab on right side.

o In the Add Document popup, give Title as Demo for Documentation

Upload File, select the Upload File radio button and click on Ok (Enter) tocontinue.





o Select the Document from the Desktop & click on Open button to upload it inSolman.

o The document gets stored in the Solution Manager under Proj. Documentation

tab. Further the document can be viewed/changed as per the requirement.

o The document can also be linked to any existing Solman document. For this,

select the business scenario/process on the left side & click on Insert Document button.






o In the Add Document popup, select the radio button for Link to a SolutionManager Document . And click onOk (Enter) button.

o Give the project name whose the document needs to be linked & click

on Execute button.





o From the displayed documents, select the required document for linking andclick on Ok (Enter).

o The document gets linked to the business scenario/process in Proj.

Documentation tab.

o During the documentation, lots of changes happen to the document and

different versions are maintained normally. These different versions are placedon the centralized file server. During these modifications by multiple people,multiple copies are made. This results in duplication of documents for thesame scenario. Also the integrity of the document is also lost. To overcomesuch classical situation, there is feature given in Solution Managerfor Document Check In/Out . If any document is checked out for modificationthen for other users that document is available only for display. The documentneeds to be checked in again so that it can be made available to other forediting.

o For Checking out a document for modification, select the document from theProj. Documentation tab, click on button Check Document Out/In & select the





option Check Document Out from the dropdown.

o Give the path on local desk to save the file. Click on Save button.

o Message is displayed at the bottom in the project as File Demo for

Documentation Upload File.txt has been checked out .






o Now, try to modify the same document in Solman, which was just checked out.Select the document and click on Change button.

o System prompts a message saying The document is locked by user SAPNA.

The document is opened in display mode. This means the document is notavailable for editing if it is checkedout by somebody. Click onCancel.

o Do the necessary modification in the document on desk and then check it

again in the Solman. For this, select the document in Solman first & then clickon button Check Document Out/In & select the option Check Document In fromthe dropdown.






o Give the path & click on Open button to get the document back into Solman.

o The document gets checked in the system and message is displayed at the

bottom in the Solman project asFile Demo for Documentation UploadFile.txt has been checked in.

o Now, the document is available for others to edit. To do so, select the same

document & click on Changebutton.

o The document will be opened in change mode. Do the necessary modification& click on Close. The document status is shown as Copy Editing here. This






status is part of document attribute.

o Click on Yes to save the changes to document.

o There are attributes associated with each document. A document status

schema can be configured for the planned life cycle of document.E.g. this means first the document may have some default status linked sayCopy Editing. A Solman consultant responsible say Mr. A can be given for thisstatus. The Solman consultant Mr. A can draw a report for getting the work tobe done by him. He will then edit the document as per requirement. Now thenext document status will be available like In Process, Review. He will set thedocument to In Process and will put another person say Mr. B responsible forthis status. Mr. B will do the further changes in the document and will set thestatus next available. This way the document will flow and complete its lifecycle till it reaches to a status where the document is locked for editing. This status flow can be configured in document status schema.

o

To view the attribute of document, select any document & clickon Attribute button.

o

The Maintain Attribute window has four tabs General, Comments, Link & History . Comments can be maintained inthe Comments tab. The History tab shows the history of changes on thedocument.In the General tab, select the Document Status as In Process from dropdown.Click on Check & then Savebutton at the bottom.






Here Priority, Person Responsible, Business Blueprint Relevant checkbox, Keywords etc can also be maintained. Here a URL link canalso be generated by Generate button at the bottom and this when executedin browser opens the document on web.

o The status is reflected back in the Proj. Documentation tab.

• Transaction Tab:

o Transaction tab is used to assign transaction or programs or URL etc to the

business scenario/process. These programs, transactions can be executed inthe satellite system from Solman directly provided System Landscape withlogical components is defined in Project Administration phase.

o When executed, the transaction or program or URL will result into the desired

functionality of that process step.

o If the business scenarios/processes are taken from BPR then Transaction tab

may contain the relevant transaction or program etc to carry out that processstep.

o Each individual transaction will be taken as unit test case, when test plan will

be generated from this project.





o Select any of the business process taken from BPR on left side havingexecution icon along with it & click on Transactions tab on the right side.

o Here the Transactions tab contains the standard SAP transactions to carry out

the selected business process on left side i.e. Billing in ERP. The LogicalComponent is automatically selected when the process is inserted from BPR. To execute the transaction in the satellite system, select the transaction &click on Start Transaction execute button.

o The system will prompt for the user Id & password of satellite system. Give the

necessary details.

o Now, the transaction VF01, which was selected in the Solman Transactions tab,is opened in the Satellite System having Logical Component Z_FOX in Solman.Work with the transaction as per requirement & click on Back till Solman is






reached.

o If nothing is specified in the Transactions tab for scenarios/processes which areeither from BPR or custom, one can manually add the required transaction orprogram etc. For this, select any process on left side not having execution iconalong with it & click on Transactions tab on the right side.

o Select Transactions from the Type dropdown, ZFOX from Logical

Component dropdown, select the checkbox of In Scope for making thetransaction in the current project scope; select the radio buttonof Standard option. And now click on search help icon of Object to select a





transaction.

o Select VA01 transaction from the search help. And click on Save button from

application toolbar for saving the project. Now an execution icon will comebeside the business Scenario Custom Scenario 2.

o In the above case, even if the transaction or program etc. wont exist inthe satellite system, system will just prompt that information and will allow foradding it in Solman.

o The radio button for Standard option in the Transactions tab is used for

identifying the transaction, which will first execute among all the transactionsfor that scenario/process. This will happen when the execution icon presentbeside the scenario/process is clicked.

• Messages Tab:

o In the Messages tab, helpdesk message can be created in case of any issue

occurred during Business Blueprint phase. These messages can be monitoredand addressed by helpdesk team. Effective reports are preset for messagesmonitoring.





o To create a message, select the business scenario/process on left side againstwhom the issue will be logged & click on Create button.

o Give the necessary details like System/Base number, Component, Short Text,

Long Text, Attachment if any in the popup Create Support Message and clickon Save button at the bottom.

o A unique message number will be generated and the message will be stored in

Solman.

• Graphic Tab:






o The Graphic tab displays the hierarchy of business scenarios/processes, logicalcomponent, transaction assignment, documentation etc. graphically. It makessimple to understand the complete business scope graphically. Smoothnavigation is possible between the process steps, processes & scenarios.

o The prerequisite of using Graphic tab is availability of Internet Explorer 5.5 or

more, active activex controls in the browser, settings from the Menu Settings-> User Specific for viewing the transaction, documentation etc. in the graphics.

Also, changes to graphic is only possible in Business Blueprint phase & isavailable in display mode in Realization phase as we can not change thebusiness scope in Realization phase.

o To view graphic, select any business scenario/process on the left side and clickon Graphic tab on right side.

o Click on any of the displayed graphics, it will drill down to the lower level steps.

o Different features are available like exporting graphic to MS Word or MS

PowerPoint, font change for look & feel, zoom up/out, print etc.

• End User Roles Tab: The End User Roles tab has significance for assigning the roles to end users, which willbe used in filtering the training material in eLearning phase of project. This will becovered in Realization phase of project management.

Generating Business Blueprint Document:





• Business Blueprint document can be generated in this phase after completing all theactivities.

• This can be done from the Menu Business Blueprint -> Generate Blueprint Document

• Select the checkboxes for Graphics & click on Execute icon at the bottom.





• The system will show the message for downloading the file at the path specified. Clickon Continue to download the file.

• Then system will show that the download is complete and execute aMacro SAP_BUSINESS_BLUEPRINT in the downloaded MS Word file. Click on Ok tocontinue.





• Execute the Macro in the MS Word file from the menu Tools -> Macro -> Macros ->SAP_BUSINESS_BLUERPINT . It will automatically generate the blueprint document.

Generating Microsoft Project:

• Similar to Blueprint document, Microsoft Project can be generated from themenu Business Blueprint -> MS Project Download..





• Select the appropriate path on desk to store the MS Projct. Click on Save button.

• System shows the Path at which the file is downloaded. Click on Continue to open theMS Project.





• The MS Project opens with all the details about Project Administration in terms of dateetc along with the business scenarios/processes details.

• Now this can be used ahead for the entire project related activates.

483 Views Average User Rating(1 rating)My Rating:

• 15 Comments

•

sud v Jun 30, 2007 7:59 AM

Guru

This presentation is awesome. If you have any thing on CIC with IS Media- request you

to send to my email id [email protected]

Due RegardsSuddu

Like (0)

•

Pravin Atluri Jun 30, 2007 8:16 AM

Dear Sapna

Thanks for the Detailed information on the subject "SAP Solution Manager 4.0 ProjectManagement - Business Blueprint Phase (Part III)" Your blogs on eCATT was alsoinformative.

I was looking for the Previous blogs on the Solution Manager 4.0 Project Management,but could not get hand on it. It a kind request for giving the link of the Part 1 and Part2 and also any other links which are useful for Project Managers to work with SolutionManager.

U can also mail the links or material to [email protected]

Thanks and Regards




http://scn.sap.com/people/sud.v

http://scn.sap.com/people/sapna.modi/blog/2007/06/28/sap-solution-manager-40-project-management--business-blueprint-phase-part-iii#comment-229671


mailto:[email protected]



http://scn.sap.com/people/pravin.atluri

















Pravin

Like (0)

o

Sapna Modi Jul 3, 2007 11:51 PM (in response to Pravin Atluri)

Hi,

The link for Part I is now added in this business blueprint blog at the start only.Part II is yet to publish and will take some time to come on SDN.

Any time, you can just click on my name, which appears at the top of the blogand you will be directed to a page showing all my weblogs.

Thanks & RegardsLike (0)

Torsten Hübsch Sep 4, 2007 12:44 AM (in response to Sapna Modi)

Hi, is part II now available. If so, could you post the link? Thanks

Torsten

Like (0)

Easwaran Krishnamurthy Nov 1, 2007 12:06 PM (in response to Sapna Modi)

Hi,

We plan to use SolMan for our project, but we need more than 3 levelsin our BPML, any idea how we increase the BPML levels in Solutionmanager.

Is there any settings or user exit available ?

EKY

Like (0)

Matt Mills Jul 17, 2009 9:01 AM (in response to Easwaran

Krishnamurthy)

SAP does not allow more than 3 levels however if you build

logic into the names of the processes you can flatten levels 3and below into one level.

For Example:01 - Level 1 Description

01.01 - Level 2 Description01.01.01 - Level 3 Description01.01.01.01 - Level 4 Description01.01.01.02 - Level 4 Description

In solution manager:Business Scenarios

01 - Level 1 DescriptionOrganizational UnitsMaster Data








http://scn.sap.com/people/torsten.hbsch3





http://scn.sap.com/people/easwaran.krishnamurthy





http://scn.sap.com/people/matt.mills2





























Business Processes01.01 - Level 2 Description01.01.01 - Level 3 Description01.01.01.01 - Level 4 Description01.01.01.02 - Level 4 Description

This way you can see what level each process / task is at andthey can be sorted in the correct sequence / hierarchyreadily.

Cheers Matt

Like (0)

•

Marilyn Pratt Jun 30, 2007 11:18 AM

Hi Sapna,I suggest tagging this content for Business Process Experts as Solution Manager andBusiness Blueprining may be especially helpful to less "technically" focused folks aswell.Marilyn

Like (0)

o

Sapna Modi Jul 3, 2007 11:53 PM (in response to Marilyn Pratt)

Thanks Marilyn.

I will surely take care for such tagging going ahead and will try to address BPX

guys also :-).

Thanks & Regards

Like (0)

•

Sudhan Shan Jul 1, 2007 9:07 AMHi Sapna,

Great stuff for people trying to learn SolMan. I am trying to find link to Part II ProjectAdministration. Can you send the link to that weblogs?

ThanksSudhan Shan

Like (0)

o

Sapna Modi Jul 3, 2007 11:46 PM (in response to Sudhan Shan)

Hi,

The detailed Part II will be published but will take some time. Meanwhile, I will just publish the mandatory steps to create Solman Project.

Thanks & Regards

Like (0)

•

RAHUL GHOSH Sep 19, 2007 4:57 AM


http://scn.sap.com/people/marilyn.pratt










http://scn.sap.com/people/sudhan.shan










http://scn.sap.com/people/rahul.ghosh



























hi sapna,

I'm looking forward to the configuration part. Any posts made by you regarding that?

- Rahul

Like (0)

•

Mohan Madaiah Oct 1, 2007 5:26 AM

hi sapna,

thanks for adequate info on solu mgr, plz extend same for other forums also, so otherfriends also get benifited from this,

bye,

mohan madaiah

Like (0)

•

Apr 14, 2008 9:41 AM

Hi-

Thanks for the blog. When I select the document and click the attributes button, theGenerate button in the subsequent pop up is missing. Do you know why?

Thanks,Nathan

Like (0)

•

sandeep akella Jan 19, 2009 9:44 PM

the three blogs of SAP Solution Manager are very good...are the blogs for next phases

comming up?

Like (0)

•

m dre Jun 30, 2010 8:26 AM

I am looking forward to Configuration Part IV but am not able to find a link. Can youplease let me know where to find it?

Like (0)


http://scn.sap.com/people/mohan.madaiah






http://scn.sap.com/people/sandeep.akella




http://scn.sap.com/people/m.dre


















sap solution manager 4

Documents