SAP Template Management fr Initial Rllut
Cpyright 2011 by SAP AG. Neither this dcument nr any part f it may be cpied r reprduced in any frm r by any means, r translated int anther language, withut the prir cnsent f SAP Active Glbal Supprt. All rights reserved. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and ther SAP prducts and services mentined herein as well as their respective lgs are trademarks r registered trademarks f SAP AG in Germany and ther cuntries. Business Objects and the Business Objects lg, BusinessObjects, Crystal Reprts, Crystal Decisins, Web Intelligence, Xcelsius, and ther Business Objects, prducts and services mentined herein, as well as their respective lgs, are trademarks r registered trademarks f Business Objects S.A. in the United States and in ther cuntries. Business Objects is an SAP cmpany. All ther prduct and service names mentined are the trademarks f their respective cmpanies. Data cntained in this dcument serve infrmatinal purpses nly. Natinal prduct specificatins may vary. These materials are subject t change withut ntice. SAP AG and its affiliated cmpanies ( SAP Grup ) prvide these materials fr infrmatinal purpses nly, withut representatin r warranty f any kind, and SAP Grup shall nt be liable fr errrs r missins with respect t the materials. The nly warranties fr SAP Grup prducts and services are thse that are set frth in the express warranty statements accmpanying such prducts and services, if any. Nthing herein shuld be cnstrued as cnstituting an additinal warranty. Page 2 f 79
Index Cpyright... 2 1 Intrductin... 5 2 General Explanatin... 5 2.1 Prjects and Slutins... 5 2.2 Template Prject... 6 2.3 Implementatin Prject... 6 2.4 Maintenance Prject... 7 2.5 Upgrade Prject fr Existing Systems... 8 2.6 Prjects and Slutins Dependencies... 8 2.7 System Landscape fr Template Management and Rllut... 9 3 Building Templates... 11 3.1 Template Preparatin... 12 3.1.1 Business Prcess Design... 12 3.1.2 Rllut Cntent... 16 3.1.3 Definitin f Cntent Changeability (Glbal Attributes)... 16 3.1.4 Dcument Management... 18 3.1.5 Template as an Infrmatin Prvider... 20 3.1.6 Interface Scenaris in Template... 20 3.1.7 Template Testing... 20 3.2 Template Rllut Prcedure... 21 3.2.1 Implementatin f Predefined Cntent... 21 3.2.2 Methdlgy fr Rllut (Radmap)... 21 3.2.3 Dcument Management... 22 3.2.4 Template Maintenance during Rllut... 22 3.2.5 Rllut Testing... 23 3.2.6 Training Management... 23 3.3 G-Live and Maintenance... 24 3.3.1 Rll-In int Template... 25 4 Change Request Integratin int Template and Rllut... 26 4.1.1 Methd... 26 4.1.2 Change Types... 26 Page 3 f 79
4.1.3 Phase Change (Task List)... 27 4.1.4 Business Prcess Integratin fr Dcument Management... 27 5 Organizatinal Aspects fr Template Rllut... 28 6 Authrizatins... 29 6.1 Prjects... 29 6.2 Dcument Management... 29 7 Setup/Cnfiguratin and Prcedures... 31 7.1 General Cnfiguratin... 31 7.1.1 Definitin f System Landscape SMSY... 31 7.1.2 Prject Standards... 36 7.1.3 Definitin f Dcument Types... 36 7.1.4 Definitin f Status Schema... 39 7.1.5 Adjustments t the Blueprint Dcument... 43 7.1.6 Structure/Object Attributes... 45 7.1.7 Custmer Attributes fr Dcuments... 48 7.1.8 Creatin f a Reference Flder... 51 7.2 Template Prject Creatin... 53 7.3 Rllut... 59 7.3.1 System Landscape... 61 7.3.2 Rllut Prcedure... 65 7.3.3 Template Maintenance during Rllut... 67 7.3.4 Testing... 69 7.3.5 Learning Map... 72 7.3.6 Rll-In int Template... 75 7.3.7 G-Live... 77 7.3.8 Pst G-Live Maintenance... 79 Page 4 f 79
1 Intrductin The SAP Slutin Manager is psitined as an Applicatin Management Platfrm fr SAP centric slutins. The majr fcus f SAP Slutin Manager is n slutin peratin and ptimizatin. It als functins as a cllabrative infrastructure between the custmer and SAP. This includes remte supprt as well as cllabrative scenaris between the custmer peratin and the SAP service rganizatins. Apart frm slutin peratin, the SAP Slutin Manager platfrm als prvides an infrastructure fr verall applicatin management: frm requirement/change request management, thrugh design, build, test, deply, and peratin/ptimizatin, with a majr fcus n change cntrl. Depending n the scpe f the SAP Slutin Manager prcesses being implemented and depending n the structure f the cmpany, the SAP Slutin Manager can be an easy setup r an implementatin prject by itself. The fllwing cntent describes the Applicatin Lifecycle Management (ALM) pssibilities in SAP Slutin Manager fr an example f an initial template rllut with references t test, change and request capabilities, and Business Prcess Mnitring invlvement at the end f the implementatin prcess. 2 General Explanatin 2.1 Prjects and Slutins As shwn in the picture belw, prjects and slutins are simply verviews f business prcess infrmatin. A prject in SAP Slutin Manager prvides infrmatin n the future use f business prcesses: this includes business prcess redesign and new business prcess implementatin. Figure 2-1 Prject and Slutin A slutin, n the ther hand, cntains infrmatin n the current use f business prcesses in a prductive envirnment. Page 5 f 79
2.2 Template Prject A template prject can be used t create and distribute a template. A template defines a prject structure, r parts f it. Its assigned bjects (dcumentatin, test cases, IMG activities, develpment and training material) are available t ther prjects as templates. Templates can be lcked against changes, cmpletely r partially, when used in several prjects. In case several SAP Slutin Manager systems are being used in parallel, templates can be transprted frm ne central system (where the structures and assignments are defined) t anther system. Additinally, the template prject ffers the pssibility t translate the prject structure (cnsisting f business scenaris, prcesses and business prcess steps). It is als pssible t translate the cntent f the dcuments within the Knwledge Warehuse (KW) functinality in which they are stred. Template prjects are especially suited t SAP Partner Slutins r Glbal Rlluts. Typical Use Case in ALM: A template prject can be used fr: 1. Definitin and dcumentatin f glbal business prcesses and their preparatin fr rll-uts. The preparatin f the glbal prcesses can cmprise business prcess flw, transactin assignments, descriptins, dcuments, cnfiguratin and develpment assignments as well as predefinitins f test cases and training material. The mre cntent prepared in the template, the easier the rllut frm a dcumentatin perspective. 2. As business prcess library cnnected t a mdelling tl t manage changes and redesigns f business prcesses. Except fr the business prcess flw, changes all ther assignments like: dcuments, IMG bjects. Test cases will be dne in SAP Slutin Manager. This use case can be cmbined with the rllut use case. 2.3 Implementatin Prject Implementatin prjects can be used t implement business prcesses in an SAP landscape. A prject structure has t be created fr the business prcesses. Yu can either create a new prject structure, r base it n any ne f the fllwing: ne r several templates existing prject(s) scenaris and cnfiguratin structures delivered by SAP (Business Prcess Repsitry) an existing prductin slutin landscape fr lng-term changes t prductively-used business scenaris Page 6 f 79
Typical Use Case in ALM: An implementatin prject can be used fr tw typical use cases: 1. Implementatin f new business prcesses, where the scpe can be defined, based n: a. Predefined business prcesses frm a template prject. Predefined business prcesses can be changed accrding t glbal attributes defined in the template. b. Nrmal implementatin withut template predefinitins (manual business prcess creatin and dcumentatin). Here, the business prcesses can be created and changed independently during the implementatin. 2. Lng-term changes t prductively used business prcesses stred in a slutin. Thse business prcesses can be redesigned in this prject (withut system upgrade) and afterwards all deltas are handed ver t the slutin. 2.4 Maintenance Prject The maintenance prject can be used t keep track f changes in the prductive envirnment (slutin). in Change Request Management. The prject cntains all maintenance activities and urgent crrectins f a slutin. in check-in/ut fr business prcesses, redcumentatin/changes frm the Slutin Directry. These changes are then perfrmed in a maintenance prject linked directly t the slutin. Typical Use Case in ALM: Assignment t a slutin with activated check-ut/in functinality can be used t reflect all changes made t prductively used business prcesses and their dcumentatin, during the maintenance cycles. These are typically small transactinal crrectins r cnfiguratin tasks. Types f pssible changes: Urgent crrectin: errrs and ht fixes; this usually des nt have an impact n the business prcess dcumentatin (back t designed behavir). Nrmal crrectins: pertains t all changes t a business prcess r a business prcess step which can be cmpleted within a shrt f the maintenance cycle. This typically invlves minr recnfiguratin r additinal small develpments (n business prcess redesign). These changes are reflected in business prcess dcumentatin. Page 7 f 79
2.5 Upgrade Prject fr Existing Systems In an upgrade prject yu can: upgrade the custmizatin: upgrade existing functins and/r delta the custmizatin: cpy additinal functins Typical Use Case in ALM: Redesign f business prcesses and their dcumentatin caused by a technical upgrade f the system(s) n which they are running. The upgrade prject is typically based n a slutin with the latest up-t-date prcess dcumentatin. 2.6 Prjects and Slutins Dependencies Using applicatin management in SAP Slutin Manager creates infrmatin flw and data exchange between a prject and its peratinal areas. The infrmatin flw is depicted in Figure 2-2, belw. Figure 2-2 Infrmatin Flw between different Prjects and a Slutin The same cntent (business prcess and attached infrmatin) is reused and passed n t typical prject phases, such as: design, realizatin, test, and g-live and als between the different prject types and the slutin. As such, the requirements n the business prcess design can be very cmplex. Please refer t the chapter Business Prcess Design. Page 8 f 79
2.7 System Landscape fr Template Management and Rllut Depending n the system landscape f the managed systems, the template prcedure in SAP Slutin Manager can be different. Even within ne landscape type, several rllut strategies are pssible with different SAP Slutin Manager designs. Centralized Landscape Figure 2-3 Centralized Landscape Several Clients: Fr cases where several different cuntries r plants have t be available in the same system but in different clients, yu can use the typical template use case with separate template definitin and rllut phases. The rllut phase can be represented in an SAP Slutin Manager system thrugh an implementatin prject. Fr a multiple-client landscape, the template prject can be mapped t a lgical cmpnent where assignment f the cre clients culd represent the DEV, QAS and PRD system types. Hwever, the rllut prject will reflect a different set f clients. This fact has t be mirrred in a separate lgical cmpnent. Thus, ne f the first activities when creating a rllut prject based n a template is the replacement f lgical cmpnents. This can be dne via mass change thrugh transactin SOLAR_PROJECT_ADMIN under tab System Landscape using buttn. Same Client: Fr cases where several cuntries have t be rlled ut ne by ne (n verlapping between rlluts), the first rllut can be used t define the template prject. All succeeding rlluts can be perfrmed in the same template prject and dcumented as delta infrmatin. All the bjects can be flagged by using structure/bject attributes. After every g-live, the relevant cntent will be handed ver t the slutin. There is n need t replace the lgical cmpnents in this case. Decentralized Landscape In cntrast t a centralized system landscape, the decentralized system landscape is much mre cmplex with many different variants and pssibilities. Figure 2-4, belw, illustrates a typical example fr template management necessity. The cmplexity f this landscape can be increased, as befre, by a template-specific landscape (DEV+QAS). Page 9 f 79
Figure 2-4 Decentralized Landscape (1) In case f a decentralized system landscape, the typical rllut use case can be utilized. The template cntent (glbal business prcesses) can be prepared in the template prject. All relevant cnfiguratin r develpment bjects can be assigned t the business prcess structures. After the rllut scpe has been defined, this infrmatin can be used t identify all bjects which are relevant fr the rlled-ut business prcesses. Afterwards, the relevant bjects can be transprted int the apprpriate landscape and activated. The activatin can be dcumented in a rllut prject (implementatin type). Figure 2-4 Decentralized Landscape (2) Thus, hw a SAP Slutin Manager template is used depends n the rganizatinal aspects as well as n the established landscape. Page 10 f 79
3 Building Templates The main idea behind defining templates in SAP Slutin Manager is t accelerate the rllut prcedure and centralize business prcess dcumentatin. All rllut-relevant, end-t-end business scenaris are defined in a general template prject. Scenaris cntain mdule-related business prcesses which are usually executed ne after the ther. The business prcess descriptins and specificatins can be assigned t the apprpriate business prcess structure n tabs prpsed in the unit Dcument Management. Furthermre, the assignment f transactin and cnfiguratin/develpment cntent fr rllut can be dcumented. This cntent will be captured in s-called templates. The rllut prjects will chse these templates as a scpe (1); they are prcessed in the blueprint and cnfiguratin phase. The business prcesses can be blueprinted and changed by the rllut team. During the cnfiguratin phase, the cnfiguratin f the scenaris in the apprpriate system is perfrmed. Relevant custmizing bjects and develpments can be selected based n the scpe/cntent f the rllut prject (2) (assigned end-t-end scenaris). Figure 2-5 Template Usage in a Rllut Prject Page 11 f 79
After activatin, the custmizing will be transprted int the test system (4) where it can be tested centrally frm SAP Slutin Manager (5). After successful testing, the cntent can be transferred int a slutin in SAP Slutin Manager (6), and the transprt requests can be implemented in the prductive system (7). Shw hw this prcedure is executed in SAP Slutin Manager. 3.1 Template Preparatin 3.1.1 Business Prcess Design Prper business prcess design and apprpriate gruping int scenaris are key decisins when starting ALM in SAP Slutin Manager. By chsing the wrng design, reusability is impaired. This affects future use f the cntent fr purpses like testing r Business Prcess Mnitring. Business prcesses shuld be rganized in business scenaris. Here, mduleriented scenaris can be used, r mdule-riented business prcesses can be cmbined int end-t-end business scenaris. Belw, tw methds are described (SAP mdule- r End-t-End riented), fr designing business prcesses in SAP Slutin Manager. Visibility and reprting capabilities can be imprved thrugh structure attributes. 3.1.1.1 Definitins: Business Scenari, Prcess and Step A business prcess step is mst cmmnly related t a transactin, a backgrund jb, a web UI r similar system activities. Smetimes it makes sense t als dcument sme activities within the business prcess flw. A business prcess is a cllectin f business prcess steps, gruped accrding t a certain criterin like business cntent r SAP mdules. A business scenari is a cllectin f business prcesses t be executed ne by ne resulting in the executin f an peratinal prcedure. Scenaris can be rganized by business unit, SAP mdule r ther kinds f gruping (e.g. templaterelated). The SAP Nte 1345599 describes the restrictins t size fr business scenaris. 3.1.1.2 End-t-End Oriented Business Prcess Design In designing end-t-end business prcesses, yu have t answer the questin what end-tend means fr yur business unit(s). This difficulty shws up at the start f business prcess dcumentatin, and is mstly cnnected t rganizatinal aspects (user access, rganizatin f mnitring etc.). Hwever, this is the mst reusable business prcess mdel fr dcumentatin purpses, test capabilities, interface dcumentatin and Business Prcess Mnitring. It is recmmended t use structure attributes r custm attributes fr dcuments when rganizing the business prcess dcumentatin in relatin t SAP mdules. Page 12 f 79
Figure 3-1 End-t-End Oriented Business Prcess Design 3.1.1.3 Mdule-Oriented Business Prcess Design In a mdule-riented business prcess yu typically describe business prcess steps that belng tgether and that are executed ne after the ther in a single mdule. Hwever, t increase the quality and the number f further pssibilities in SAP Slutin Manager, it is recmmended t represent preceding r succeeding steps als (dcumentatin f Interface Scenaris) as shwn in the fllwing graphic. Advantages: Figure 3-2 Mdule-Oriented Business Prcess Design Clear separatin f prcesses by SAP Mdule (mstly cmbined with mdule-based business scenaris) Disadvantages: Additinal wrk t build test-related business prcesses Withut interfaces t ther business prcesses, n pssibility t dcument system interfaces Page 13 f 79
Therefre, a better ptin is t dcument the cnnectins t ther business prcesses, highlighting interfaces, as shwn in the fllwing Figure 3-3. Figure 3-3 Extended Mdule-Oriented Business Prcess Design 3.1.1.4 Business Scenari Definitin T cmbine bth mdels, yu can cmpse end-t-end business scenaris frm a mixture f mdule-riented business prcesses. These are executed ne after the ther in rder t perfrm a business activity. Figure 3-4 Business Scenari Executin T d s, use the Graphic tab at scenari level t dcument the rder in which the business prcesses are t be executed. Hw business scenaris are rganized als determines hw t rll them ut using templates (Template as Infrmatin Prvider). 3.1.1.5 Pssible Surces fr Business Prcess Infrmatin. There are three main pssibilities t bring business prcesses int SAP Slutin Manager: - Manual creatin using transactin SOLAR01. Business prcesses can be detected centrally in SAP Slutin Manager in the template prject itself. In this case, all Page 14 f 79
respnsible departments dcument relevant business prcesses accrding t the quality requirements described in chapter 3.1.2 Rllut cntent - Uplading business prcesses and dcumentatin using XML interface. Using this mst effective migratin slutin, yu can cllect business prcesses, transactins, system infrmatin, and all dcuments which have t be represented in SAP Slutin Manager in an MS excel file. Yu can then cnvert it t XML frmat (cnsulting) and uplad it int a prject using the reprt RS_SA_PROJECT_IMPORT. In the 7.1 release f SAP Slutin Manager, this pssibility is prvided in the standard versin. - Business Prcess Repsitry. SAP Slutin Manager prvides a library f standard business prcesses. These business prcesses can be entered using the transactin SOLAR01, rerganized (if necessary), and newly dcumented. In all three cases, the business prcess cntent can be verified using Slutin Dcumentatin Assistant n the system landscape. Please refer t the infrmatin abut Slutin Dcumentatin Assistant: SAP Help fr SlDcA 3.1.1.6 Structure Attributes As f supprt package 15 (EHP 1) fr SAP Slutin Manager 7.0, it is pssible t define and use structure and bject attributes. Structure attributes can supprt all types f filtering r reprting capabilities during typical prject phases like blueprint, cnfiguratin, testing, r after g-live in maintenance. The biggest advantage f structure and bject attributes is that they can be cpied tgether with the structure, whenever the structure is reused (template Rllut Slutin Maintenance). Once assigned, structure attributes can be adjusted with the Cmpare & Adjust functin using the transactin SA_PROJECT_UPGRADE. This ensures that all changes made t attributes and their assignment t the business prcesses r business prcess steps are current at all times thrughut the entire business prcess lifecycle. Figure 3-5 Business Scenari Executin (2) Shw hw this prcedure is executed in SAP Slutin Manager. Page 15 f 79
3.1.2 Rllut Cntent Business Prcess Structure Apart frm dcumenting the business prcess structure in the template prject, yu can als dcument technical bjects like: Transactins: the assignment f transactin infrmatin t the business prcess steps determines which transactin(s) will be used t perfrm a certain business prcess step in the managed system. This infrmatin is usually defined during the blueprint stage, and is reused fr testing, Business Prcess Mnitring, business prcess change analysis and ther functins. Cnfiguratin Objects: all bjects assigned t the cnfiguratin tab f a business prcess r a business prcess step recrd the custmizing views. These have t be maintained t ensure that the business prcess/step runs as designed during the blueprint stage. Develpment Objects: all mdificatins are dcumented as an assignment f the develped bject t the business prcess/step fr which the mdificatin was created. Additinally, technical dcumentatin fr the mdificatins and extensins can be assigned and cnnected t the develpment bject directly. Test Case Descriptins: The testing prescriptins fr a business prcess step are assigned t apprpriate structures (using the test bject results in a transactin assigned t the business prcess step). During the creatin f a test plan, the test case descriptins can be selected and brught int the test scpe as a test case (tgether with assigned transactins). Training Materials: The training dcuments, which describe hw a transactin is t be used by end users in the cntext f the business prcess, can be assigned t the business prcess step n the Training tab. These dcuments can be used t create Learning Maps and distribute them t end user grups. End User Grups: T dcument which business prcess step is used by which grup, predefined end user grups can be assigned. This assignment can be used as a filtering criterin fr Learning Map creatin. 3.1.3 Definitin f Cntent Changeability (Glbal Attributes) The changeability f the SAP Slutin Manager cntent, assigned t the business prcess structures in any succeeding rllut prject, can be managed by using glbal attributes. These attributes can be assigned t the business scenaris, business prcesses, and t all steps n the Structure tab in the transactin SOLAR01 fr the template prject. Fr better prcessing and t speed up the assignments, yu can use the mass change pssibility using the buttn Pass On Glbal Attributes. Glbal attributes can manage the changeability with respect t changes in the structure: Page 16 f 79
Figure 3-5 Glbal Attributes (1) Or dcuments assigned t the business prcess structures: Figure 3-5 Glbal Attributes (2) The impact f these glbal attributes n the rllut cntent can be changed using BAdI BADI_SA_DEFINE_GLOBAL_ATTR. Alternatively, yu can create yur wn glbal attributes using the same BAdI. The availability f thse attributes in SOLAR01 can be switched fr the prject in its administratin (SOLAR_PROJECT_ADMIN). Page 17 f 79
3.1.4 Dcument Management Dcument Type SAP Slutin Manager uses predefined dcument types t dcument business prcesses and steps. Reusable dcument types can be predefined centrally by uplading dcument templates int SAP Slutin Manager. T this end, all relevant frms and templates can be upladed int SAP Slutin Manager, making them available fr later dcumentatin during the blueprint r cnfiguratin prject phase. Recmmendatin: Define and use custmer-specific dcument types created in a custmer name space (Z* r Y*). Shw hw this prcedure is executed in SAP Slutin Manager. Status Schema Sme dcument types require specific status values assigned t the dcument fr specific situatins. This is enabled thrugh the status schema. Yu can assign exactly ne status schema t exactly ne dcument type. Recmmendatin: All status schemas shuld end with a cmmn released status. This simplifies the handver prcedure t the slutin after g-live f a rllut prject. Shw hw this prcedure is executed in SAP Slutin Manager. Pssible Assignments Using the structure f the dcument types, the dcumentatin f business scenaris, prcesses, r steps can start. T d s, yu can create new dcuments n several tabs in transactins SOLAR01/02 based n the dcument types. The assignment f dcuments t structures and t a specific tab is custmer specific. Hwever, a few rules shuld be fllwed cncerning dcument assignment: The lwer the level f the infrmatin the better. This means that the mre granular a dcument the better suited it is t be reused. Business Prcess Step Example: Create purchasing scheduling agreement (transactin ME31L) General Dcumentatin Tab: Cntains dcuments describing the design f transactin ME31L ( in case template management was used, functinal specificatin r additinal dcumentatin ) Prject Dcumentatin Tab: Prject related dcumentatin fr ME31L Cnfiguratin Tab: Dcument describing the cnfiguratin needed fr transactin ME31L (Cnfiguratin bjects and descriptins, Authrizatin Rles ) Page 18 f 79
Develpment Tab: Test Case Tab: Training Materials: All develpments needed t run the transactin ME31L (Technical specificatins, develpment frms ) Test case descriptins. All types f functinal tests can be represented by different dcument types. Additinally, test data dcuments can be assigned at business prcess level. All kinds f training dcuments which will be made available t end users (simulatins, presentatins) Use f a cmmn final status value fr all dcument types (dcuments). All dcument types use the same r different status schema(s). Every status schema ends with the same cmmn final status value. Reuse f dcuments by links. In rder t decrease the number f dcuments, yu can link dcuments t the same business prcess steps used in different business prcesses (basic dcumentatin). Additinal dcuments describing the differences can be assigned t the ccurrence selectively. Dcument Type Descriptin Structure Tab ZBPD Business Prcess Descriptin Business Prcess Gen/Prject. Dcumentatin ZFSP Functinal Specificatin Business Prcess/Step Gen./Prject Dcumentatin ZCON Cnfiguratin Descriptin Business Prcess/Step Cnfiguratin ZAUT Authrizatin Business Prcess/Step Cnfiguratin ZTSP Technical Specificatin Business Prcess/Step Develpment ZTCD Test Case Descriptin Step Test Cases ZUT User Training Step Training Material ZINT Interface Descriptin Interface Step Gen./Prject Dcumentatin Abve dcument types are examples. Different dcument types can be created t suit different requirements. Shw hw this prcedure is executed in SAP Slutin Manager. Page 19 f 79
3.1.5 Template as an Infrmatin Prvider Once the business scenaris, prcesses, and steps are defined and all relevant assignments are made, yu can create the apprpriate template IDs and assign them t the business scenaris n the Structure tab. After the assignments, the templates can be released. Frm nw n, templates are visible fr all prjects in the SAP Slutin Manager system and prvide all assigned business scenaris, prcesses, and steps with all assignments. Hwever, a template can be made invisible fr maintenance purpses. During this time, it is nt pssible t assign this template t an implementatin prject. There are a few rules fr template creatin: A template can nly be assigned at business scenari level One template can be assigned t several business scenaris A template can be used in several rllut prjects N active versin management f the template is available 3.1.6 Interface Scenaris in Template SAP Slutin Manager prvides the pssibility t dcument interfaces between systems. Interfaces can be specified in a specific interface scenari structure. Fr each interface, yu can specify the sending and receiving system; the type and technlgy. On the dcumentatin tabs, the interfaces can be dcumented and described. Once the interfaces are dcumented, yu can assign them t the apprpriate business prcesses n the Graphics tab. This assignment f ne interface can be dne several times fr several business prcesses. After this, evaluating which interface is used fr which prcess becmes very easy. Once the interface is assigned t a business prcess in a template, and the template is used fr a rllut prject, the interface infrmatin is still represented n the Graphics tab. The riginal, hwever, is still in the template prject. In case yu decide t change the interface fr the rllut prject, yu can reslve the external interface, thereby cpying the riginal interface int the rllut where it can be changed. The cpy f the interface is made nly after the scpe definitin phase f the rllut prject has been cmpleted. 3.1.7 Template Testing Defined glbal business prcesses and their cnfiguratin cntent have t be tested in the system where the template was develped. Fr this purpse, the SAP Slutin Manager functinality fr testing (Test Wrkbench) can be used. Please refer t the chapter Rllut Testing t get mre infrmatin abut the test functinality in SAP Slutin Manager. Page 20 f 79
3.2 Template Rllut Prcedure The scpe fr the rllut prject is usually defined based n the predefined templates. After template selectin in the transactin SOLAR_PROJECT_ADMIN n the Scpe tab, all crrespnding scenaris will be cpied int the rllut prject. Using the predefinitins, the business prcesses can be dcumented, cnfigured, and tested. Befre starting the rllut f the predefined cntent, the system landscape has t be replaced by the rllut-specific system landscape. This can be dne by using mass change in the transactin SOLAR_PROJECT_ADMIN using buttn :. 3.2.1 Implementatin f Predefined Cntent As all relevant IMG bjects which are necessary t run business scenaris and which are cllected in the template are already assigned t the business prcesses, the prcedure fr business scenari/prcess implementatin starts by evaluating which custmizing/develpment has t be activated fr the rllut prject. Transactin SOLAR_EVAL can be started t detect and centrally prcess these bjects. The activatin status can be recrded and shwn in the Cnfiguratin tab in the rw where the custmizing bject is assigned. The same prcedure can be chsen fr dcumented transprt requests assigned t the Cnfiguratin r Develpment tab. Thus, all assigned transprts can be centrally prcessed via the task list (refer t chapter Change Request Integratin int Template and Rllut ). 3.2.2 Methdlgy fr Rllut (Radmap) T dcument the methdlgy f a rllut, the radmap functinality can be used. Using transactin RMMAIN, yu have access t standards like ASAP r upgrade radmaps which are delivered by SAP. Hwever, yu can define and create yur wn radmaps in SAP Slutin Manager using transactins RMDEF and RMAUTH. In this case, custmer-specific phases, tasks, and activities can be described and specific acceleratrs can be prvided (dcumentatin n hw t prceed with the phase, task, r activity). Page 21 f 79
Afterwards, radmaps, which are assigned t the rllut prject, can be used t stre all dcument types which help manage a prject, such as meeting minutes. 3.2.3 Dcument Management All dcuments assigned t the business prcess structures f the template prject (except fr dcuments n the Prject Dcumentatin tab) can be linked directly t all rllut prjects. When a rllut prject changes a dcument, the dcument is cpied. The new dcument nw has the name Cpy f <title f the riginal dcument>, and the status will be set t initial status by the status schema assigned t the dcument template. Alternatively, dcuments can be kept in sync between the template and all rllut prjects. In this case, when the rllut prject changes a dcument prvided by a template, the system will nt cpy it, but will nly allw changes t the riginal dcument. The authrizatin fr these activities can be restricted t just a few individuals, s that the changes can be cntrlled. When the secnd prcedure is used, the dcument cntent changes will be visible immediately in all rllut prjects. It culd make sense t use this, fr instance, with specificatins fr a glbal business prcess step. Shw hw this prcedure is executed in SAP Slutin Manager. 3.2.4 Template Maintenance during Rllut In case the template cntent has t be adjusted during an nging rllut, all changes (except fr changes t dcument cntent) can be cmpared and adjusted t all nging rllut prjects using transactin SA_PROJECT_UPGRADE. Cmpare & Adjust can be used fr all new assignments r deletins n the fllwing tabs: General Dcumentatin Structure Transactins Cnfiguratin Develpment Test Cases Learning Material End User Rles Hwever, cntent changes have t be well prepared in rder t be detected by the Cmpare & Adjust run. They als depend n the lgical cmpnents used in the template and rllut prjects. Shw hw this prcedure is executed in SAP Slutin Manager. Page 22 f 79
3.2.5 Rllut Testing The infrmatin n hw business scenaris, prcesses, and steps have t be tested was already assigned t the structures in the template. This makes the creatin f test plans fr a rllut prject easier. The prject team (r test rganizatin) has the ptin t rganize tests based n predefined r new test case descriptins. Using transactin STWB_2, all necessary test plans fr the rllut prject can be created fr scenaris r selected prcesses. T d s, the structure attributes assigned t the business prcesses can be used t create test plans which are mdule-riented r based n ther attributes. The test plan can then be rganized int test packages. These can be set up in a tpicrelated categrizatin r accrding t an end-t-end principle: that is, as a sequence. T build the sequence, yu can cmbine and rerder the test cases by assigning them t several testers wh are assigned t the particular test package. A tester can be infrmed autmatically, via wrkflw, abut the release f a test plan/package t which he/she is assigned. T reprt n the test results, yu can use the central evaluatin transactin SOLAR_EVAL. If requested, BW integratin can be activated t evaluate and cmbine the test results. Shw hw this prcedure is executed in SAP Slutin Manager. 3.2.6 Training Management After successfully testing implemented business scenaris, the end user needs t be trained. If this training infrmatin was already assigned t the business prcesses in a template prject, it can nw be distributed by using Learning Maps in SAP Slutin Manager. This functinality gives yu the pssibility t create end-user-grup-specific Learning Maps and distribute r publish them in a specific knwledge transfer area. The end user will get access t the dcuments prvided in his Learning Map withut the necessity f having a user in SAP Slutin Manager. All training materials cllated in the Learning Map will be shwn t the end user in display mde. Shw hw this prcedure is executed in SAP Slutin Manager. Page 23 f 79
3.3 G-Live and Maintenance There are nly a few tasks frm the tl pint f view during the deply phase f the rllut prject: Creatin f a Slutin: The slutin is where the business prcesses, tgether with the entire dcumentatin, will be stred after g-live. Cntent Cpy frm the Rllut Prject int the Slutin: It is recmmended t use the Wrk Center t cpy the business prcesses frm the rllut prject int the slutin. All cpied dcuments have names Cpy f and will get initial dcument status. T fix this, yu can use the BAdI interface IF_EX_SOLAR_DOCUMENTS. All ther bjects will be cpied directly frm the prject int the slutin (structure and dcument attributes will be cpied as well). If necessary, the lgical cmpnents can be replaced by thse representing the maintenance landscape. Shw hw this prcedure is executed in SAP Slutin Manager. Cntent Maintenance: T perfrm planned changes t the prductive cntent, it is recmmended t create and assign a maintenance prject t the slutin. Activating check-in/ut will allw business prcesses t be changed exclusively in a maintenance prject assigned t a slutin, but nt in the slutin itself. Optinally, the Change Request functinality can be activated fr this maintenance prject. Befre every maintenance cycle, the planned nrmal crrectins can als be reflected in the checked-ut structures in which dcumentatin and further assignments can be adjusted. Hwever, business prcess changes cannt be perfrmed in a maintenance prject, nly in the template. Prductively-used business prcesses can be redesigned in a s-called lng-term prject as a secnd rllut. Hw t use this is described in a separate dcument fcusing n the implementatin prject type. Shw hw this prcedure is executed in SAP Slutin Manager. Adjustments after Maintenance Cycles: All changes t business scenari, prcess, r prcess step cntext which were made during maintenance shuld als be rlled int the template prject. T accmplish this, use the Cmpare & Adjust functinality. Page 24 f 79
3.3.1 Rll-In int Template When ne f the rlled-ut plants has t lcalize business prcesses prvided by a template, it is pssible t change the template directly in a rllut prject. The changeability is determined by glbal attributes assigned t the business prcess structures. Alternatively, the business prcesses/scenari has t be cpied and the changes perfrmed n the cpy (riginal can be taken ut f scpe). After a lcal variant f a scenari/business prcess has been implemented, the dcumentatin and all changed business prcesses can be rlled int a template prject. This prcedure has t be perfrmed either manually, using the input help in a specific area f the template prject reserved fr lcal variants, r half-autmatedly, using the extended Cmpare & Adjust functinality. In rder t make the new variant available fr succeeding rllut prjects, it has t be included int a template which will nly rll ut scenari/prcess variants. Shw hw this prcedure is executed in SAP Slutin Manager. Page 25 f 79
4 Change Request Integratin int Template and Rllut T manage all changes made t all relevant rllut develpment systems, yu can use the Change Request functinality. This functinality can be used fr building the template landscape which is t be rlled ut t the implementatin. All transprt requests created during the template preparatin can be assigned t the business prcess structures als. This helps tracking which business prcesses need which develpment and cnfiguratin. In case f a central client cncept, Change Request Management can nly be activated fr a rllut prject. Since mst f the cntent is client-independent, it is necessary t dcument client-dependent cnfiguratin/develpment. Activating the ChaRM flag fr yur maintenance prject allws the system t cntrl all changes planned fr the maintenance system landscape in s-called maintenance cycles. 4.1.1 Methd After cnfiguring and activating the standard ChaRM functinality in yur system, yu can use the wrkflw-based functinality. This means that when a change necessity is detected (pssible integratin int SAP Slutin Manager service desk), the change can be requested using the Change Request. This transactin type is used fr apprval wrkflw tasks. During the wrkflw, the change is categrized (see 4.1.2 Change Types), and then apprved r rejected by a change manager. Once the change has been apprved, the system will create anther transactin type (based n the categrizatin) called the change dcument. This type f dcument is used t perfrm all develpment activities aligned t the apprved change request. Typical tasks are: - Creatin f a transprt request - Lgn t relevant system t develp/test/validate the requested functinality - Testing - Organizatin f transprt (depending n change type) 4.1.2 Change Types Fur main Change Types, delivered in the standard versin, can be used by default (as a cpy f the SAP rigin): - Nrmal Crrectin: Used t make regular crrectins in yur maintenance landscape and t implement planned features int yur develpment landscape. Nrmal - Test Message: Used during testing fr crrective develpment. - Administratin Changes: Used fr all system changes which cannt be included in a typical transprt request. An example f this is number range. Page 26 f 79
4.1.3 Phase Change (Task List) Maintenance cycles can be managed and switched in a task list. The task list is a cllectin f all typical activities during the maintenance cycle. Activating Change Request Management fr the lng-term prject n the ChaRM tab in the transactin SOLAR_PROJECT_ADMIN creates a task list in the backgrund. This task list recrds, cllects, and manages all changes made t the managed system(s) r clients. The task list can be used fr: Creating transprt requests and tasks Scheduled and/r n demand imprt Transprting cpies Security functinalities like Crss System Object Lck and Critical Objects Check Retrfit fr n+1 landscape Reprting capabilities Transprting nn-abap bjects thugh the integratin with CTS+ The Change Tracking functin f Change Request Management allws yu t track everything that relates t changes within the cntext f a Slutin Manager r an IMG prject. Yu can track all transprt requests frm the system where they are created t the systems/clients int which they are imprted. Within the prject cntext, all transprt requests that belng t a particular prject can be tracked acrss all the systems in the prject landscape. Yu can navigate int the transprt lgs and imprt queue as well as int the crrespnding service transactin r task list. Yu can als navigate int the Slutin Manager prject, the satellite IMG prject, r the CTS prject. 4.1.4 Business Prcess Integratin fr Dcument Management Change Request Management can be used nt nly in a maintenance prject, but especially in cnnectin t a slutin embedded in a check-ut/in prcedure. By using this variant, yu create a change request which is directly related t a business prcess r its steps. S the infrmatin abut existing change requests will be available nt nly in the business prcess structure, but als n the Cntext tab in Change Request and thus als in Change Dcument. This methd allws yu t cmbine the technical wrk with dcumentatin tasks by directly linking the Change Request Management t the business prcess dcumentatin. The Cntext tab can als be used t check ut the business prcesses directly int the maintenance prject (taking int maintenance) and t check it back after successful testing. Fllwing this prcedure ensures that the change dcumentatin is always in sync with the technical realizatin. Fr ther prject types, like template, rllut, r lng-term prjects, the Cntext tab in Change Request can als be used t dcument t which prcess the change request relates. Thrugh this dcumentatin, yu have a direct link t the business prcess dcumentatin frm Change Request/Dcument. Page 27 f 79
5 Organizatinal Aspects fr Template Rllut Using SAP Slutin Manager as an implementatin tl requires ensuring the quality f all activities perfrmed in this tl. A prven methd is t establish a quality assurance team which ensures that all basic activities in SAP Slutin Manager are perfrmed crrectly. Gvernance is needed in several areas: System Landscape: The system landscape infrmatin is the fundatin fr nearly all SAP Slutin Manager functinalities. The quality assurance team shuld have access t this area, be authrized t create and change managed systems, and als be able t create all necessary RFCs fr all apprpriate clients. The systems can then be gruped int lgical cmpnents. These lgical cmpnents are used fr all current and future prjects. Standard and Design Definitins: T ensure the cnsistency f all standards used in the prjects, like dcument types, status schemas, structures, and dcument attributes, the team shuld als attend t design questins, decisins cncerning building f the ALM in SAP Slutin Manager, and t the decisins n which nn- SAP tls have t be used fr ALM purpses. The aim f this team shuld als be t ensure the crrectness and quality f the business prcess design. Business prcesses shuld be kept granular (please refer t the chapter Business Prcess design ) and crrect assignment handling guaranteed. Pssible services fr incming prjects: Prject Cnsulting (which prcesses, prject type and s n). Befre a new prject starts, the quality assurance team culd discuss with their prject management hw t perfrm the prject and hw SAP Slutin Manager can supprt them fr this purpse. Pssible reuse f existing business prcesses r dcuments shuld be discussed. Prject Creatin. As a service t the prject team, SAP can ffer t take ver central activities in SAP Slutin Manager, like creating a prject r assigning a prject landscape. This will als ensure the quality f perfrmed tasks. Standards Review. Definitin f quality cntrl pints (Quality Gate) and regular checks f business prcesses and dcumentatin quality. Business Prcess Design Cnsulting. Assurance that all new prjects have the same design and fllw the same prcedures t allw reuse in ALM. SAP Slutin Manager Cnsulting. This central team is the main cntact pint fr all requests regarding SAP Slutin Manager functinalities. All custmizing and/r develpment activities have t be apprved and activated by this team. Knwledge Transfer. Every new prject team has t be trained n hw t use SAP Slutin Manager functinalities: especially n hw t handle dcuments, make develpments, and clarify custmizing tasks. Page 28 f 79
6 Authrizatins 6.1 Prjects Cncerning restrictins, yu have tw ptins: Restrictins between Prjects: Yu culd use the authrizatin bject S_PROJECT. Depending n the number f implementatin prjects, yu culd: 1) Assign the authrizatin fr specific prjects t the bject (PROJECT_ID Prject name) t which the user has access. 2) Wrk with a predefined name space fr the prjects (e.g., Implementatin Prjects begins with I; template prjects with T). Afterwards, yu prepare the bject S_PROJECT fr several users (ne grup has PROJECT_ID = I* and the ther PROJECT_ID =T*). Authrizatin bject S_PROJECTS and S_PROJECT can be fund, fr example, in the rle SAP_SOLAR_PM. Please cpy the rle and set it up. Restrictins within a Prject (Structure): The setting "Restrict changes t ndes in prject t assigned team members" can be activated in SOLAR_PROJECT_ADMIN n the Team Members tab and allws changes t ndes in SOLAR01/02 where the user is assigned. All ther ndes will nly be in display mde. 6.2 Dcument Management Standard Slutin: Restrictins within a Prject This slutin is based n a standard functinality f SAP Slutin Manager which restricts the ability t change ndes in a prject t assigned team members. This flag can be set in transactin SOLAR_PROJECT_ADMIN n the tab Prject Member. If yu check this bx, nly team members wh are assigned in the Administratin tab can wrk n the ndes f a prject structure. Other team members can nly pen the tab in display mde. Yu need t change the authrizatin fr the tab (authrizatin bject AI_SA_TAB) t enable assigned team members t wrk in the tab. Using additinal KW Flders Yu can use different KW flders within ne prject. One KW Flder can be assigned t exactly ne flder grup. The authrizatin fr all included dcuments is checked against this flder grup. Please fllw the descriptin belw t set these up in yur system. 1) Please start transactin SI23, fr the area SAP Slutin Architect, and g t the menu Settings Flder Grups. In this view, yu can create a flder grup fr the new flder. Page 29 f 79
2) Afterwards, start transactin SI80 and select the flder in which the flder grup will be changed. G t the menu Flder Attributes Change (the cntext where yu currently are shuld be equal t the rigin cntext in the attributes f the flder; therwise, it will nt be pssible t change the flder grup). Nw yu shuld be able t chse the flder grup (created in step 1), using F4-help. Alternatively, yu can create a new KW flder and assign the flder grup t it. 3) The flder grup can be assigned t the authrizatin bject S_IWB. The parameter IWB_FLDGRP is usually equal t the prject name f the flder created by the system during prject creatin. Afterwards, yu shuld be able t mve special "tp secret" dcuments t the newly created flder, using the Attribute ppup f the dcument and the buttn Replace Flder. Alternatively, the assignment is als pssible when saving the dcument in Methd HANDLE_EXIT_BEFORE_SAVE in Class CL_SA_IO_DOC, using KW functin mdules. Page 30 f 79
7 Setup/Cnfiguratin and prcedures 7.1 General Cnfiguratin 7.1.1 Definitin f System Landscape SMSY SAP Slutin Manager is the central access pint fr yur landscape. If a new Managed System is t be included, sme basic cnfiguratin needs t be executed in transactin SMSY either manually r autmatically. The fllwing instructins describe hw t create RFC cnnectins between SAP Slutin Manager and the Managed System. Fr details n hw t maintain a system in SAP Slutin Manager, please refer t the basic cnfiguratin guide f SMSP (Slutin Manager Starter Pack). Select system and client frm SMSY in SAP Slutin Manager Fr a new client, n RFC cnnectins are established. Select the client and click buttn Generate RFC with Assistant. Page 31 f 79
Fllw the wizard and use default values fr creating RFC cnnectins. Select Cntinue. Page 32 f 79
Create users fr RFC cnnectin, select Cntinue. Create users fr RFC cnnectin, select Cntinue. Page 33 f 79
Select Cntinue. Select Cntinue. Page 34 f 79
Select Cntinue. The system lgn screen will appear. Input the user name and passwrd t generate the RFC cnnectin. Nte: this user shuld have authrizatin fr RFC creatin as well as fr Trusted RFC. (Please refer t SMSP cnfiguratin guide fr details) Page 35 f 79
7.1.2 Prject Standards T use dcument management in SAP Slutin Manager, sme adjustments and custmizatin is needed. 7.1.3 Definitin f Dcument Types At least the fllwing dcument types are available in the custmer system (example): ZBPD: Business Prcess Descriptin ZCON: Cnfiguratin Descriptin ZFSP: Functinal Specificatin ZTSP: Technical Specificatin ZUT: User Training ZUAT: User Acceptance Test ZAUT: Authrizatin Where t cnfigure/hw t d: Dcument Types (transactin SOLAR_PROJE CT_ADMIN menu Gt Prject Template Implementatin Prject, Template Prject ) Select Dcumentatin Type Tab Page 36 f 79
Define Dcumentatin Type (here: ZBPD) Uplad the template int the Dcumentatin Type New template has t be released in rder t be available fr later use Page 37 f 79
Pssible crrectins n the Dcumentatin template Further settings fr the Dcumentatin Type like: glbal availability, several assignments pssible, relevance fr Blueprint dcument r status schema assignment. Page 38 f 79
7.1.4 Definitin f Status Schema Dcument types are assigned t custmer specific status schema(s). All status schemas cntain custmer defined status values like: Z_NEW Z_PROGRESS Z_APPROVAL Z_RELEASED Status value Z_RELEASED shall be included int the table fr Read Authrizatin. Please create ne cmmn release status value fr all status schemas. Where t cnfigure/hw t d: Status Value Definitin (transactin SPRO) Press New Entries and create Values Page 39 f 79
Save and recrd in a transprt Assign Status Values t Read Authrizatin Select frm the list f available Status Values Page 40 f 79
Definitin f Status Schema Create the Status Schema by pushing New Entry Decide which entries shall be part f Status Schema Assign Status Schema t Dcumentatin Types Page 41 f 79
Make Dcumentatin Type available fr prject type Return t tpic cntent Page 42 f 79
7.1.5 Adjustments t the Blueprint Dcument The functinality fr creating the Business Blueprint is prvided fr all prject types in SAP Slutin Manager. Using it, yu can create the blueprint dcument based n the cntent f all blueprint-relevant dcuments cllected fr the rllut prject (prcess descriptin, functinal specificatin r similar). The template f the blueprint dcument can be adjusted in custmizing, as shwn. Where t cnfigure/hw t d: Dwnlad f SOLARBLUEPRINT.DOC and crrectin (replacement f Lg). Page 43 f 79
Change the template Uplad the template frm the strage lcatin, where it was changed Frm nw n the custmer versin will be used t create a blueprint dcument. Page 44 f 79
7.1.6 Structure/Object Attributes Structure attributes are typically used fr filtering purpses in templates, rllut prjects, test plans, and als as a reprting help in a slutin. Fr this, custm-defined tables can be used with a defined range f pssible input values. Where t cnfigure/hw t d: Custmizatin in transactin SPRO Creatin f Structure/Object attribute Area Page 45 f 79
Decide which entries will be used fr the attribute (table assignment) Assign attribute Z_SAP_AREA t bjects Attribute will be available fr structure ndes Page 46 f 79
Assign attribute Z_COMPONENT t bject Prject and Slutin Nde Set the ther ptins Result: the attribute is available fr business prcess structures Return t tpic cntent Page 47 f 79
7.1.7 Custmer Attributes fr Dcuments T imprve reprting f dcuments in the design r cnfiguratin phase f yur prject, it is pssible t create custmer attributes fr dcuments. The advantage f these attributes is their ALM accmplishment: they are passed t all dcument cpies f the riginal dcuments. One pssibility fr such an attribute is the Prject ID under which the dcument was created/changed. The infrmatin n wh changed the attribute and when it was changed will be lgged in the histry f the dcument. The custmizatin described belw is made with the example f Prject ID as an attribute. Where t cnfigure/hw t d: Create an attribute thrugh transactin SPRO Create an attribute Prject ID Page 48 f 79
Assignment f a table and field t which the attribute will relate Activate the attribute Recrd changes in a package Assign the newly created custm attribute t PHIO class SOLARGENSRC_V Page 49 f 79
New attribute has t be assigned t instance attributes After saving, the new custmizatin has t be activated Result in SOLAR01/02 fr dcument After creating the attributes, it might be necessary t refresh the buffer n servers (transactin SE33 fr cntext IWB_CLASS_PROPS). The same activities can als be perfrmed fr the attribute SAP Cmpnent t detect which dcuments belng t which SAP area. Page 50 f 79
7.1.8 Creatin f a Reference Flder Where t cnfigure/hw t d: Creatin f a flder grup ZREFERENCE (transactin SI23) Creatin f a flder grup ZREFERENCE (transactin SI23) Flder Creatin KW Flder ZREFERENCE Assignment f the flder grup ZREFERENCE (transactin SI80) Page 51 f 79
Chse Area Result Run reprt SM_FOLDER_NO_ REFCOPY against the flder (SAP Nte 1236369) After assignment f sme prject dcuments t this flder in a template prject yu will be able t change them directly frm a rllut prject (if yur user is authrized fr this authrizatin check against the flder grup). Return t tpic cntent Page 52 f 79
7.2 Template Prject Creatin T use the template prject in SAP Slutin Manager, several steps need t be perfrmed in the system: Template creatin System Landscape maintenance Business prcess structure creatin Assignments - Dcument - Transactins - Cnfiguratin, Develpment, Test Cases, Training Materials - Structure Attributes - Dcument Attributes - Reference Flder Template release Template Prject Creatin Enter the T-Cde SOLAR_PROJEC T_ADMIN and then yu will g t the prject administratin screen where yu can start t create the prject. Prject Landscape Maintenance Yu can maintain the Template Prject landscape in this tab. Page 53 f 79
Business Prcess Creatin a. Navigate t the business blueprint screen as fllws b. G t the structure tab t type in the scenari names business prcesses and steps (in case f manual creatin). Business Prcess Assignments a. Uplad dcuments as fllws: b. Assign Transactins as fllws: Page 54 f 79
c. Assign Cnfiguratin and Develpments test cases and training material as fllws: d. Assign structure attributes as fllwing in the business scenari nde: e. Assign dcument attributes as fllws: Page 55 f 79
f. Define and dcument intefaces Dcumentaitn can be assigned n the General Dcumentatin Tab g. Assign Interfaces t busines sprcesses Page 56 f 79
Template Creatin and Release a. Create templates b. Assign template t scenaris Page 57 f 79
Assign Glbal attributes t business prcesses And pass n glbal attributes c. Yu may change the visibility f the prject t public t release the prject. Return t tpic cntent Page 58 f 79
7.3 Rllut Template rllut cnsists f tw parts: creating an implementatin prject based n a template prject in SAP Slutin Manager, and transprting/uplading and activating all relevant custmizing, r imprting transprt requests accrding t lcal requirements in the develpment system. Create an Implementatin Prject in the SAP Slutin thrugh transactin SOLAR_PROJECT _ADMIN Enter a title fr the Implementatin Prject. Define the prject language. English is recmmended. It is pssible t leave the field Slutin as empty. After g-live, Slutin can be maintained in Prject Administratin. Page 59 f 79
Select templates After creatin f Implementatin Prject, available templates will be listed in tab Scpe Template Selectin. Frm tab Scpe Template Selectin, all available templates are listed. Select the check bx frm each template t include them. Save yur changes. Frm tab Scpe Radmap Select, assign relevant radmap Page 60 f 79
Enhancements fr dcuments are used in Dcument Management. It is recmmended t accept the default value and then change it accrding t dcument reference requirements. 7.3.1 System Landscape If lgical cmpnents exist in the template but are nt maintained in an Implementatin Prject, the system will list them als in the Implementatin Prject. The lgical cmpnent has t be exchanged by the rllutrelevant lgical cmpnent. Page 61 f 79
This can be dne thrugh mass change in the Implementatin Prject. This replacement will change the lgical cmpnent assignment t the business prcesses. Page 62 f 79
Create IMG Prject and Transprt Requests The IMG prject and transprt requests will be created in the develpment system. Frm the SAP Slutin Manager, it is pssible t cntrl the creatin and transprt f requests centrally. Frm the Prject Administratin tab System Landscape IMG Prjects, select the target prject name and chse Create IMG Prject. System will prmpt a dialg bx fr the creatin f transprt requests. Chse Yes then jump t the target develpment system and create the Wrkbench Transprt Request and Custmizing Transprt Request immediately. Chse N, later t clse the dialg bx and create these transprt requests during cnfiguratin phase. Page 63 f 79
After creatin, the status will be green if n prblem ccurs. Page 64 f 79
7.3.2 Rllut Prcedure During the rllut phase, it is imprtant t enable business prcess related cnfiguratin, this can be dne by selecting the required IMG Objects. Review f Business Prcesses if necessary adjust and Rllut blueprint in SOLAR01 Frm tab Cnfiguratin, IMG Objects will be taken ver frm the Template Prject t the Implementatin Prject. Page 65 f 79
Selectin f relevant custmizatin can be dne via SOLAR_EVAL In rder t select relevant custmizing in a target system, select the target rw, then select the buttn Cnfigure. Cnfigure the views with relevant cntent Page 66 f 79
IMG Object List IMG Object cntains the path t the target system cnfiguratin nde. If the cnnectin between SAP Slutin Manager and the managed systems is set up crrectly, it is pssible t jump directly frm the SAP Slutin Manager t the transactin SPRO in the managed system. This reduces the time needed fr searching the right path t cnfiguratin bjects. Return t tpic cntent 7.3.3 Template Maintenance during Rllut 7.3.3.1 Cmpare & Adjust The cmpare and adjust prcedure is shwn using a general dcumentatin example: Make a change in template (assignment f a new dcument) Start Cmpare & adjust (transactin SA_PROJECT_UPGR ADE) fr the Implementatin Prject Page 67 f 79
Results will be displayed in the Implementatin Prject. Adjustment can be started. Yu can adjust all changes r select changes yu want t take ver (depending n glbal attributes). Afterwards select Cpy and Cmplete. Return t tpic cntent Page 68 f 79
7.3.4 Testing During the prject implementatin phase, tests will be executed after realizatin. SAP Slutin Manager ffers a functinality t rganize test cases accrding t business structure, generate test plans and test packages accrding t business prcesses, and t track the prgress f testing and reprting. Test case assignment in a template prject It is pssible t assign test cases, ECATT scripts, r test descriptins t a business scenari, prcess, r step, either in the template r implementatin prject. These test dcuments can be reused fr test plan creatin. Test Wrkbench The Test Wrkbench is embedded in SAP Slutin Manager fr Test Management. After assigning a test dcument, a test plan can be generated in the Test Wrkbench, and test packages can be created fr different testers. Assign test dcuments int a business prcess step, frm tab Test Case. Test plan creatin in STWB_2 Page 69 f 79
Decide which test cases is t be cnsidered Use f structure attributes t detect the testing scpe (here: an example f SAP Cmpnent, CS test) Test scpe definitin and test plan generatin Page 70 f 79
Creatin f a test package Test package cntent definitin and generatin Save Tester assignment Page 71 f 79
Tester Wrklist STWB_WORK Return t tpic cntent 7.3.5 Learning Map Prerequisites: - Assignment f training material t the business prcesses - Assignment f End User Rles (ptinal) Assignment f training material and end user rles in SOLAR02 n the Training Materials tab (this assignments can be already dne in template prject) Page 72 f 79
Create a learning map using transactin SOLAR_LEARNING_ MAP Create Chapter and Units Search fr training material using filter end user rles. Page 73 f 79
Assign training material t the units Send t End User Return t tpic cntent Page 74 f 79
7.3.6 Rll-In int Template Detectin f business prcess/scenari variants (by name r structure attributes) Rll int template Result Dcuments have t be relcated t Gen.Dcumentatin tab Page 75 f 79
Variant Scenari assignment t Variant Template (just in case new scenari has been created) Variant Template available fr new Rllut prjects SOLAR_PROJECT_ ADMIN Return t tpic cntent Page 76 f 79
7.3.7 G-Live After implementatin and g-live, the prject will be cut ver t the slutin. Slutin Cncept A slutin is the set f business prcesses, dcuments and the system landscape. Nrmally, a slutin is created clsely after the g live f the prject. Handver frm Prject t Slutin In SAP Slutin Manager, it is pssible t create a Slutin frm the transactin DSWP r SOLUTION_MANAG ER. Cpy related business prcesses, dcuments, and the landscape frm the prjects t this slutin. Frm transactin DSWP, select Slutin Landscape Slutin Landscape Maintenance. Page 77 f 79
Cpy all related infrmatin frm the prject. Adpt the system landscape Result: all selected business prcesses with all assignments are available in slutin Return t tpic cntent Page 78 f 79
7.3.8 Pst G-Live Maintenance A slutin is created after g-live. Frm nw n, all peratins and maintenance are executed n the slutin instead f n the prject. Maintenance Prject T change the business prcess structure in a slutin, it is recmmended t use a maintenance prject instead f making changes t the slutin directly Assign a maintenance prject t a slutin, then enable the Check-ut/Check-in functinality. Check-In/Out After the maintenance prject is assigned t a slutin, it is n lnger pssible t change the business structure, dcument, r landscape directly in the slutin. Any necessary changes will be checked ut int the maintenance prject and checked in after changes. Return t tpic cntent Page 79 f 79