SAP SOLUTION MANAGER AT A GLANCE. •Solution Manager is mandatory, SAP contractually requires usage of this toolset. •Business Case: ROI 1½. Free download SAP Solution Manager PDF Books and training material, online training materials, complete beginners guide, ebooks, study material. 1 Concept of SAP Solution Manager .. SAP Solution Manager at the HARTMANN GROUP . . Reporting in SAP Solution Manager and the.
|Language:||English, Portuguese, Japanese|
|ePub File Size:||23.59 MB|
|PDF File Size:||8.50 MB|
|Distribution:||Free* [*Registration needed]|
With this hands-on guide to SAP Solution Manager, you'll find everything you need to PDF ( MB), EPUB (72 MB), and MOBI file ( MB) for download. SAP Solution Manager supports heterogeneous system environments. Its functions cover all aspects of implementation, deployment, operation. Best Practice Guide CUSTOM ER SAP So lutio n Manager Do c ument Versio n: – 20 Solution Documentation Content Activation Act ivat ing.
Example of business scenario within BPR Implementation Roles within Solution Manager The SAP Solution Manager platform includes some predefined user roles, which can be modified, copied, or adapted according to customer needs and which provides a user menu for each role, including the typical project implementation tasks that are associated with each role.
When logging on the Solution Manager using these roles, the members of the project team will be able to access implementation projects with the authorizations assigned to them within the roles and work their specific project activities. Remember that authorizations determine the degree of access to functions and transactions within the project.
Project managers are responsible for the supervision, control, and realization of the SAP implementation projects and to perform the daily project management tasks. Application consultant. The main task is to should ensure that the Business Blueprint and configuration defines correctly the target business processes, and all other requirements for a successful implementation, such as the analysis documentation, interfaces, reporting, and so on.
Application consultants must have both business knowledge and SAP knowledge to configure and implement the customers' requirements. This role has more limited authorizations than project managers, and is intended for project members working in the Solution Manager with Business Blueprint, Configuration, Testing, Message Handling, and a few others.
This role is meant for working on the authorization concept and development activities, for instance when there is a need for customer development not found in the standard SAP Solutions. Technical consultant. Technical consultants are in charge of performing all the technical tasks in the systems, including all tasks typical to system administration and technical support, and access to Solution Manager functions such as Defining System Landscapes, Synchronizing Customizing, Message Handling, and so on.
Users assigned this role will only be able to display the functions in the system, without authorizations to do any modifications.
They contain standard SAP implementation methodology and include the most important aspects and phases of a SAP implementation project. An example of Roadmap is shown in Figure. A fundamental component of Roadmaps is links to accelerators and tools to perform project tasks. Accelerators are mainly documents, information, and document templates that are attached to structure items within the Roadmaps.
With roadmaps, you can do the following: Open and browse the road map structure to display all indications relevant to the project steps, whether the phases, work packages, activities, and tasks. Display accelerators, or documents linked to structure items within the Roadmap.
You have also the option of assigning your own documents. Search for specific items within the Roadmap structure. Register and track the status for each structure item.
You can assign your personal notes to these status settings.
Create issues or messages within the system, to keep track of problems or open issues to be resolved. You can print any of the documents, or the information displayed in the structure items of the Roadmap.
Filter structure items by role or subject area. This is the roadmap directing functional SAP implementations. It is meant mainly for Project Managers and Application Consultants. This functional roadmap synchronized with the technical one through the milestone concept. Solution Management Roadmap. The roadmap for the technical Implementation and Operations of SAP Solutions and aimed to the technical team and system managers.
SAP BASIS Related Interview Questions
The Solution Management Roadmap synchronizes with the Implementation Roadmap using the milestone concept. Global Template Roadmap meant for multisite and multinational projects, providing a methodology for the implementation of a global customer solution. However, when a local implementation is to take place, you have to proceed with regular Implementation and Solution Management roadmaps. Upgrade Roadmap, which is used to SAP solutions upgrade projects.
In their own specific project targets, each roadmap type contains the standard SAP implementation methodology and cover the most important aspects and phases of a SAP implementation. Solution Manager Roadmap Structure View You get the structure view when double-clicking the graphical view. The structure on the left of the screen is the project area and contains the structure of the Roadmap with some of the attributes.
The text displayed in the right part of the screen is the viewing area, which contains the description according to the structure item selected in the project area. The tabs and objects you find in the lower right hand of the screen is known as the attachment area.
There you can find several tabstrips: The Accelerators tabstrips contains links to accelerators, when there are any available for the structure item. The Notes tabstrip is used to display or create notes about the particular structure elements. The Messages tab is used to create, send, display, and edit problem messages for the selected structure element.
If needed, you have the option to attach documents to the message. Set Status. The status of a structure step is displayed as an icon in the structure and you can see it graphically in the Roadmap initial screen. SAP So lution Manager 7. In release 7. Release cyc les suppo rt release management. We reco mmend to c lo se all request fo r c hange and all c hange do c uments in SAP So lution Manager 7.
Fro m bo th a tec hnical and business perspec tive, there is not muc h difference between the o ld and new fo rmats. As part of the c o ntent activatio n pro cess, data from yo ur QGM pro jec ts are automatically mapped to the new QGM sc enario s. If yo u did so and these pro jec ts are o ngo ing and yo u want to use them in the future, yo u have to activate them fo r the use in the So lutio n Do c umentatio n c o ntext. The pro jec ts are preselected in the preparato ry guided procedure and you can ac tivate them in the activity Ac tivate ITPPM Co nte nt in 7.
Yo u do not need to make any manual adjustments. The c o ntent ac tivatio n c hanges the projec t management related assignments automatically. If yo u do no t ac tivate the pro jec ts, you c an still use them but the integratio n with So lutio n Do c umentation and Change Request Management c an only be displayed. Befo re yo u start wo rking with projec t management co ntent in 7. During the ac tivatio n pro cess including the suppo rting guided procedures the o ld name is used.
In partic ular, one SDC is assigned and permanently dedicated to exac tly o ne so lutio n. Bringing 7. All SDCs are transfo rmed into the new fo rmat, by replac ing the reference o f SDCs to logical compo nents by a reference to a lo gical c ompo nent gro up also fo r pro ject-independent SDCs.
Test management entities such as test cases, test scripts and test data c o ntainers, whic h make use o f SDCs in 7. Altho ugh this pro c ess is tec hnically complex, it is largely auto mated and requires little manual effo rt.
As the arc hitec ture of so lutio ns and asso c iated pro c ess do c umentatio n has changed in SAP So lution Manager 7. Ac tivatio n of BPMon fo r 7. Ac tivating BPMon co ntent is o nly an 'add-o n' proc ess. The presence o f BPMo n do es not influence ho w yo u plan and exec ute ac tivatio n, it happens in additio n to the o ther, leading the parts o f the ac tivation proc ess.
Instead yo u have to go thro ugh the two guided pro cedures mentioned abo ve and take dec isions regarding the shape o f 7. Using the guided pro c edures, yo u will determine ho w many so lutio ns usually o nly o ne, see belo w 7. To get yo u started, here is an initial minimal set of useful rules: Dos 1. Apart from service pro viders, o ne so lution is usually eno ugh fo r o ne c ompany.
Use pro duc tion, maintenance and develo pment branches in o ne so lution to gro up So lutio n Do c umentatio n c o ntent which belo ngs to yo ur produc tio n, maintenanc e and develo pment landscapes.
Additional branches are po ssible fo r additio nal purpo ses. Use o ne lo gical co mpo nent group per produc tive system and system type. Co nsider whether to mo ve the c o ntents o f a 7. No te that the initial so lutio n design propo sed by the co ntent activatio n too l, cf. Don't s 1.
Introduction to SAP Solution Manager: About This Module
Do no t try to ac tivate o ld lo gic al c ompo nents one-to-one into new lo gical c ompo nent gro ups. If you run, e. Use o ne lo gical c omponent gro up with different sites see terminology table abo ve: Impo rtant 7. The c ombinatio n of so lutions and pro jec ts that have been typical for 7. Use Case 1: You have worked with only one Solution or Project in 7. This is, and will remain, the mo st prominent and simple use c ase. Yo u will find both the 7. Use Case 2: You have worked with one central Project plus additional projects in 7.
Put extensio n pro jects into the co re pro jec t, to end up with the simplest po ssible scenario ideally one c entral pro jec t, as in use case 1. Delete outdated or sandbo x pro jects o r so lutions in 7.
If you cannot co nso lidate everything in one pro jec t, the likely o utc ome of the transitio n into 7. Use Case 3: You have worked with only one Solut ion and associated Projects in 7. Maintenanc e has been handled in a separate maintenance pro ject, and inno vatio ns have been do c umented in o ne o r mo re additio nal pro jec ts of type implementatio n o r similar.
Befo re co ntent activatio n, yo u have to at least c o nso lidate the maintenanc e pro jec t bac k into the so lutio n. Fo r the o ther pro jec ts, you can proceed as in use c ase 2 — the mo re pro jects you c o nso lidate into the central so lutio n in 7. Use Case 4: You have worked with several Solutions and associat ed Projects in 7.
Yo u canno t link c ontent ac ro ss so lutio ns in 7. The o nly realistic exceptio n from the o ne so lutio n rule is fo r the service pro viders use case, i. The 7. In prac tic e, yo u have to re-distribute system info rmatio n from 7. Altho ugh this may so und c omplic ated, many 7. Fo r tho se, the co ntent activatio n rules and proc ess are co rrespo ndingly so simple that SAP has been able to largely auto mate activation fo r yo u.
Even ac tivating mo re co mplex landsc apes has been partially auto mated, but requires some dec isio ns to be made by yo u. Semi-automated infrastructure remodeling assigns systems to system ro les, logical co mponent gro ups, branc hes etc. In sec tio n 2. The aim is that yo u have a chance to understand why in step 2 systems are propo sed to be assigned to a c ertain branch in a certain system ro le. In the remainder of this c hapter, we present a number of typical landscape sc enario s from simple to c omplex and we explain ho w they can be implemented in the c ontext of 7.
Lo gical c ompo nents exist bo th in 7. System ro le is the o nly entity that remains unchanged in 7. Ho wever, the business and administrative pro cesses yo u are suppo rting with SAP So lutio n Manager will probably not c hange between versio ns 7.
In prac tice, existing 7. In the fo llo wing, we explain how the c o ntent ac tivatio n algo rithm turns this info rmation into a proposal fo r yo ur 7. These rules will be referred to again in later parts o f this chapter, when we go thro ugh examples of landscape transitio ns from 7.
Base Assumption: There is only one 7. This will in fac t ho ld true fo r the vast majo rity of c usto mers simply o n the grounds of how 7. See Designing a 7. In the unlikely c ase that yo u require multiple so lutio ns in 7. Rule 1: Which syst em roles are included in t he landscape proposal? All system roles from the to p ro le do wn to and including the SAP delivered productive system ro le are c o nsidered by the propo sal generato r and therefore appear in the new system landsc ape propo sed fo r 7.
Rule 2: Which systems are included in the landscape proposal? The fo llo wing systems are co nsidered fo r 7. The relevant set o f systems can be extended by inc luding additional systems that are part of transpo rt trac ks o f TMS, as explained in the next rule. How default logical component groups are creat ed Firstly, fo r every 7. Seco ndly, all 7. If further systems are fo und there, they are added to the same 7. Our task is then again to assign eac h of tho se systems to a system ro le and a branch.
It is impo rtant to understand that the assignment of systems to logical co mponent gro ups has the fo llowing two implic atio ns in 7.
A user wo rking in a branch c an o nly jump fro m the so lution do c umentation in this branch into a managed system, if the system is - by virtue o f its system ro le - ac tually inc luded in this branc h.
Assignment o f tec hnical systems to branches and system ro les happens in step 2 o f the first guided pro cedure see Step 2: After c o ntent activatio n is c omplete yo u c an make further changes in the 7.
All elements assigned to a 7. The way 7. Caution Mapping of 7. Adapting these assignments can be c umbersome o nce c o ntent ac tivatio n has been completed. Therefo re, invest suffic ient tho ught into ho w c o ntents are mapped during c o ntent ac tivatio n.
Rule 4: How syst ems are given syst em roles and are assembled in branches If you have run a very simple landscape with SAP So lutio n Manager 7. You can skip the remainder of Rule 4, have a quic k look at Rule 5 and pro c eed straight to Ac tivating Simple Single and Dual Transport Trac k Landscapes to get an explanatio n of ho w your landsc ape will lo o k befo re and after.
If you have run anything mo re co mplex than a simple single o r dual trac k landscape in 7. There are two broad logical flows used to engineer an initial draft landsc ape. If TMS is present, it is used as the so urce of wisdo m, otherwise the co mpo sitio n of lo gical c ompo nents in 7.
The reaso n fo r this prioritizatio n is that TMS is usually c lo ser to reality than the mo re abstrac t lo gic al c ompo nent design.
Building Branches from t he Product ion Syst em Downwards The basic rule is that the produc tio n system sits in its o wn pro duc tion branc h and develo pment and quality systems form a number o f maintenance and development branc hes. Remember, a maintenance branch is used to o rganize mino r o r standard c hanges to a pro duc tion system suc h as implementing suppo rt packages.
A development branc h suppo rts majo r, no n-standard c ode c hanges whic h eventually end up in the produc tio n system. So do no t be c onfused that bo th maintenanc e and develo pment branc hes usually c ontain development and maintenance systems. Ho w branc hes turn out exactly, depends o n the fo o d c hain underneath the produc tio n system.
The co ntent ac tivatio n too l goes thro ugh an algorithm as desc ribed in the fo llo wing. From t he Product ion Syst em t o t he first Development Syst em: All systems between the pro duc tio n system and the first development system form the maintenanc e branc h, exc luding the pro ductio n system itself whic h remains in its o wn produc tio n branc h.
All systems stay in their o riginal system ro le. From t he first Development Syst em to t he next Development Syst em: If there is a quality systems between the first and sec o nd development system, a development branch is propo sed. The roles of all systems invo lved remain unchanged. If there is no quality system between the first and sec o nd development system, then the sec o nd development system is lumped into the abo ve maintenance branch and rec eives another development system role whic h is no t identical to the development system ro le of the first development system.
Keep It erat ing Keep repeating Step 2 until you run o ut o f development systems. The quality systems between the development system and the produc tio n system in o ur example: Q1 and Q2 will be assigned to the available quality ro les defined between the develo pment ro le and the pro ductio n ro le. The development system D1 will be assigned to the development system ro le. And bo th the development system D1 and the quality systems Q1, Q2 will be assigned to the maintenanc e branch.
The produc tio n system P will bec ome part o f the productio n branc h. In this case systems D2 and Q3 are assigned to the development branc h, with D2 assigned to the development system ro le and Q3 to the quality system ro le. What Happens when t here are more t han one Product ion Syst ems? If there a mo re than one productio n system, then sites are needed and introduced see belo w to understand the number o f sites being propo sed. Fo r each pro ductio n system a site is created, and eac h productio n system is assigned to its c o rrespo nding site of the pro duc tio n branc h in system ro le Productio n.
It is generally a muc h less po werful way of setting up the first draft of a landsc ape. Det ermining t he Syst em Role of a Syst em Instead o f analyzing TMS data, system roles are here adopted from the system ro les rec o rded in 7.
Systems which canno t be uniquely assigned to o ne system role, are not automatic ally assigned to a role at all. Yo u have to pic k a system ro le manually in the co ntent ac tivation too l. Building Branches Only two , simple c onstruc tio n rules applies here. If all 7. All o ther no n-pro duc tion systems are assigned to the maintenanc e branc h ac co rding to the system roles in the 7.
Fo r eac h branc h, a lo gical c ompo nent with the same name will automatic ally be c reated, ac tually co ntaining the systems in system ro les. If there are mo re productive systems then sites are c reated, and additio nally the global site, too see belo w to understand ho w many sites are propo sed.
Sites are also created if there are more than o ne produc tive c lient in the same productive system. SITES Sites are needed and automatic ally propo sed by the system fo r bo th TMS and lo gic al c ompo nent based modelling to separate systems in pro duction ro les in lo gical c ompo nent groups. One lo gical c ompo nent group must not c o ntain mo re than o ne produc tio n system. The default number of sites c reated is taken to be equal to the highest number o f productio n systems c ontained in o ne logical c omponent gro up.
The default names o f the sites fo llow a simple numbering sequence i. All sites are available and visible in the c o ntent ac tivatio n too l fo r eac h lo gical co mpo nent gro up with mo re than o ne produc tio n system. Rule 5: How logical component groups are named A lo gical c ompo nent group whic h is pro po sed by the system will be automatic ally named ac c o rding to the fo llo wing princ iples. If the new lo gical c ompo nent group c ontains 7.
If a produc tive system c an be fo und then the name of the product version whic h is assigned to the pro ductive system is used to pro po se the lo gic al compo nent gro up name. The names of the logical co mponent gro ups must be unique. If the same product versio n is used fo r multiple logical compo nent groups the names fo r these lo gical groups are made unique by adding a c ontinuo us number to the produc t versio n name.
Yo u can change the propo sed name in step 2 of the preparatio n guided pro c edure. Assume the fo llo wing simple transport track: From there, the developments are transported first into a quality system Q4S, c lient 10 0 and finally into the productio n system P4S, c lient 10 0. A landscape like this lends itself to a standard maintenance situatio n: In this minimal example it is eno ugh to understand the Rules of Engagement to be able to guess how the 7.
Hence when mo ving from So lutio n Manager 7. Pro ductive system P4S: The two o ther systems bec ome part o f logical co mpo nent "Maintenance".
Fo r eac h logical co mponent, a branch see Impo rtant 7. With this, o ur final, neatly cut 7. Yo u can also understand ho w we have arrived at this landscape pro po sal by go ing through the 5 rules set o ut in the preceding sec tion System Landsc ape Propo sal: Assuming all three systems exist in LMDB, all three systems appear in the landscape propo sal.
SAP Solution Solution Manager main functions - SAP BASIS
The lo gical c o mponent to gether with its three lo gical systems is grouped fo rms a single new lo gical c ompo nent group. Produc tio n system P4S: Development system M4S: Quality system Q4S: Prac tically speaking, in the new 7. All So lutio n Do c umentatio n changes related to maintenanc e activities are made in the Maintenanc e branch.
Produc tio n, Maintenance and Develo pment We extend o ur example ac co rdingly by development system D5S: Maintenanc e ac tivities fo r the c urrent release will be do c umented in the maintenanc e branch. Lo ng-term developments, o r developments fo r the next release, will be do c umented in the development branc h. Tho se development-related do c umentatio n c hanges are then released fro m the develo pment branch into the produc tio n branc h, and will then be automatic ally also available in the maintenance branc h.
Fo r example, in 7. In the sample landsc ape depicted belo w, this is system D4S: The o ther hybrid system in o ur sample is M4S: So urce systems, like the development systems mentioned abo ve, are automatically c onsidered as target, pro duction and retro fit systems by task list generatio n in Change Request Management.
This simplifies the setup of lo gical c ompo nent groups. Fo llowing our example landscape thro ugh the ac tivatio n proc ess from 7.
The systems are distributed into three new logical c omponents in 7. Assume that a delivery relation between systems T4S: The final result is o ne so lution with two logical component gro ups and one productio n and maintenance branc h eac h.
Ho w did the co ntent activatio n to o l come up with this design in detail? The planning guided pro cedure propo ses - as always, see rule 3 in System Landscape Propo sal - o ne logical component gro up fo r eac h productio n system. Pro duction systems ERP: The other systems are assigned to their c orrespo nding system roles in bo th logical co mpo nents "Maintenance". The two c lients are using the same c oding, c o ming from development system GHD.
A plausible use case would be fo r GHD: Building the 7. As in the simpler example in Activating Simple Single and Dual Transpo rt Trac k Landsc apes, abo ve, we split into a "productio n" and a "maintenance" logical c ompo nent. Having two productio n systems, GHP: This appro ac h is no t feasible fo r system landsc apes co ntaining many productio n systems in parallel.
Mult iple sit es support ed by mult iple product ion syst ems If your multiple pro ductive systems in 7. In the example below, both 7. Like in the previous example with two similarly used productio n systems, bo th productio n systems GHP: Additio nal system ro les are no t needed this time, ho wever. Differently used pro duc tion systems and the maintenance track systems that feed them are separated using "sites" see Impo rtant 7.
Here, fo r each branch the planning guided procedure c reates two sites called "site1" and "site2" by default for yo u and distributes all systems appropriately, as sho wn in the fo llo wing figure: With this landscape design, users wo rking with so lution do cumentatio n after the 7. The site and ro le selecto rs in So lution Do c umentatio n determine who can navigate inside whic h site and branc h eco system witho ut further autho rizatio n ado.
Users c ho o sing to wo rk o n so lutio n do cumentatio n in the maintenance branc h c an e. Users wo rking with pro ductive so lution do c umentation in display mo de c an just as easily navigate to their site's pro duc tio n system.
In additio n, standard "Global" sites are auto matic ally inserted into bo th branc hes. It is the expressio n of the global significance of the c ommo n development source system DVT: As the site c o nc ept c o vers both the global and site-spec ific aspec ts of SAP so lutio n landsc apes, a "Global" site is always inc luded.
Yo u c anno t delete it. As a final step, we cho se mo re meaningful names fo r o ur infrastruc ture entities. The final landsc ape propo sal for 7. If you have to c reate new system ro les to be able to mo ve some of yo ur systems into tho se ro les, pro c eed as fo llo ws, depending o n the SAP So lutio n Manager release you are wo rking in. On the start screen, selec t the tab Lo gic al Co mpo nents.
Enter the name o f o ne o f your lo gical c ompo nents and display it. On the display screen for the selec ted lo gical compo nent, selec t the butto n Maintain Ro les.
Maintain system ro les as required. On the start screen, selec t the tab Lo gic al Co mpo nents Groups. Enter the name o f o ne o f your lo gical c ompo nent groups and display it. In the display mode of the logical c omponent gro up edito r selec t a logical compo nent in the navigation tree and then c hoo se the button Maintain Ro les. Maintain the system ro les as required. If you need system roles beyo nd the standard, you can use up to ten pre-cast c usto m system roles with a key value between 0 and 9.
Co nfirm the warning that the table is c ro ss-c lient. In the fo llo wing o verview screen selec t func tio n Ne w Entrie s — here yo u can c reate additio nal system roles. Permissable keys are upperc ase c harac ters whic h are no t used yet for o ther system ro les. The desc riptio n of the new system roles must be maintained in this view, to o.
Data and Applic ation Affec ted co ntains info rmation to help you to dec ide whether to proceed with or opt o ut of c o ntent ac tivatio n. If you are uncertain, c o ntinue with this guide and the co ntent ac tivatio n pro c ess. Use cont ent act ivat ion for housekeeping At the beginning o f the preparatio n guided pro cedure, yo u selec t whic h pro jec ts, so lutio ns and asso c iated c o ntent to mo ve from 7.
Think c arefully abo ut which pro jec ts and so lutio ns you really need to inc lude in the c o ntent ac tivatio n scope. Yo u may have c reated test data or toy so lutions and pro jec ts o ver time, whic h you can get rid of by not taking them into c o ntent ac tivatio n sc ope.
If you are unsure abo ut what needs to be mo ved into 7. What happens during t he preparat ion guided procedure? To prepare co ntent ac tivatio n, yo u go thro ugh the fo llo wing steps: Ste p 1: Sco pe o f Conte nt Ac tivatio n - Identify so urc es o f co nte nt in 7.
This sc ope determines also the systems whic h will be c o nsidered in the fo llowing steps where yo u define your system landscape fo r 7.
Ste p 2: Syste m Landscape for 7. Ste p 3: Target Branche s and Remote Sourc e s - Link 7.
SAP BASIS Related Tutorials
Ste p 4: Summary - Have a last lo ok at and c lo se your sc ope definitio n o Chec k the final o verview tables regarding sourc e c ontents and target landscape.
Learn mo re in SAP No te This guided pro c edure helps yo u to plan and prepare existing 7. Dec isio ns yo u make here do not ac tually c hange or o therwise affect co ntent in yo ur SAP So lution Manager 7. Therefo re, yo u c an in princ iple repeat these preparatio n steps and adjust settings as often as necessary, until yo u enter the sec o nd guided pro c edure in SAP So lutio n Manager 7. To navigate between steps, c hoo se Ne xt o r Previous at the to p of the sc reen.
Rest art ing the Guided Procedure If you interrupt wo rk o n the guided pro cedure and yo u re-enter it later, the guided procedure will o pen up in the last step you had previo usly been wo rking o n.
What to do when the Guided Procedure brings up Errors or Warnings Great c are has been taken to standardize the handling and appearance of warning and error messages ac ro ss the guided pro cedure. At the end o f eac h step you sho uld - and in some cases yo u have to - trigger a c heck ro utine that analyses the c urrent state o f affairs in terms of c o nsistency o f underlying data sets by c lic king [Save and] Che ck Consiste ncy. The status of the background job that pro c esses the c hec k routine can be refreshed using the butto n of same name, Re fre sh.
Underneath the Pre vious and Ne xt buttons in the top left-hand c o rner of the sc reen, you can watch how the c onsistenc y check pro gresses and view its o utc omes, either a co nfirmatio n that all is go od o r a statement summarizing the number of warnings and erro rs whic h leads to a log whic h details the problems.
If the inline instruc tions linked to the errors o r warnings are no t suffic ient, refer fo r further details to the do c ument at the fo llo wing lo catio n: Fo r the pro jects and so lutio ns you dec ide to keep, you c an restrict the fo c us o f c ontent ac tivation by selec ting whic h application co ntent will remain relevant to them in 7.
Ho wever, if you are o verwhelmed bec ause the list presented in this step o f the guided pro cedure is just to o bulky and c omplex you can also use the embedded Rule Base d Sco ping to o l to get a pre-selected list based o n rules yo u c an define. Of c ourse, you can keep freely editing your scope selec tio n after invo king Rule Base d Sco ping , too. Detailed Selection of Application Content related to Projects and Solutions Yo u can select the fo llowing c o ntent fo r eac h pro jec t and solutio n to be mo ved to 7.
Yo u sho uld usually select this optio n. Reso lve means here, fo r example, that when a po inter exists from o ne 7. This option reso lves all external sho rtc uts.
Graphics assigned to a pro cess are only brought into 7. The graphic s in shortc uts to o ther pro jec ts or so lutions will not appear in 7. By default, o nly pro jec ts with an open change cycle and open task list are available fo r selec tio n. The task lists do not have to be activated, they are reused. Inc lude all pro jec ts with an open task list in the sc ope. If a SOLAR pro jec t c anno t be put into the co ntent activatio n sco pe, check whether there is an open c hange c yc le and task list.
If the c hange c yc le and task list of the SOLAR pro jec t were c lo sed while there were still o pen c hange doc uments assigned to the pro ject, c reate a new change c yc le and a new task list to put the pro jec t into sco pe fo r co ntent activatio n. This ensures that the Analytic s and Mo nito ring co nfiguratio n and its relatio nship to pro c ess struc tures is being preserved.
Procedure 1. Read the o nline do c umentatio n ac companying this step. If yo u feel the info rmatio n pro vided there is suffic ient, fo llow it, process the step and go to step 2 bo th in the applicatio n and in this do cument. Otherwise keep reading. To dec ide whether a 7. Co nsidering when a 7. This number tells yo u whether and how many do c uments are assigned to the pro cess structure o f the 7.
If a test plan has been c reated for a 7. If you are c o nfro nted with a bewildering co llectio n of 7. This opens a screen that func tio ns like a global filter based on a number o f simple rules which are c onnected by an OR: Insert a date, if yo u want to exc lude pro jec ts and so lutio ns who se so lutio n do c umentatio n has no t been updated after the cut-off date.
Insert a date, if you want to exc lude pro jects and so lutio ns who se test plans have no t been updated after the c ut-o ff date. Insert a date, if you only want to exc lude projec ts and so lutio ns that c ontain a Tec hnical Bill of Materials TBOM who se last update has been prio r to the cut-o ff date. Tic k the bo x, if yo u want all 7. Tick the bo x, if you want all 7. Tick the bo x, if yo u want to co unt in all 7. In the Sco ping mo de bo x underneath the selection fields, you c an determine what to do with the pro jects and so lutions that meet your selectio n c riteria in relatio n to what you may have manually selec ted in the list befo re.
Yo u have the c hoice o f adding them to whatever is already in sc ope o r to o verwrite earlier sco ping selec tio ns. Note With the Initialize List butto n, you c an restore the list to its initial state, i.
There is no c onfirmatio n prompt, so be careful. Initialize means that the system re-reads pro jec t and so lutio n data fro m the database like during the first start of this guided proc edure.
C_SM100_7205 Free PDF Demo 2018.pdf - SAP C_SM100_7205 SAP...
It is useful if yo u had to c hange pro jec t o r so lutio n data while wo rking on this step. After sorting o ut whic h 7. Save the scope yo u defined and ensure that the data behind the scenes is c onsistent by selec ting butto n Save and Chec k Co nsiste nc y. A background job will c hec k the data c onsistenc y fo r you.
A pro gress desc ripto r underneath butto ns Pre vious and Ne xt indicates the c urrent state of the job. Yo u must use the Re fre sh butto n to mo nito r the state of the job. When the job is finished, its summary results will be displayed. By c lic king o n the link pro vided with the summary results yo u can open a new windo w with details regarding po ssible warnings and erro rs. If errors do appear, you must fix them and re-run the co nsistenc y c hec k until no error is left befo re you c an pro c eed with step 2.
Refer to "What to do when the Guided Procedure brings up Errors o r Warnings", abo ve fo r mo re details. Yo u can interrupt the c hec k run at any time using Canc e l Consistency Che ck. Cho o se Ne xt to pro ceed to the next step. System Landscape for 7. In step 2 you define how the 7. In step 3 you will co nnec t o ld with new infrastructure elements so that the 7. Therefo re, befo re getting into this step you must understand what logical co mpo nents, lo gical c ompo nent groups, branc hes, and sites are.
See Impo rtant 7. Lo gical c ompo nents still exist in 7. Lo gical Compo nents Gro ups and Branc hes are new 7. Sites are mo re exo tic and c hanc es are go od that you will not need them, unless yo u run a c ompany fo r whic h the site co ncept is relevant.
See the definitio n fo r Site in Impo rtant 7. From a First Guess to your New 7. Tho se rules are explained in suffic ient detail in the o nline do cumentatio n ac c ompanying step 2 and in Activating Commo n Landscape Scenarios, abo ve.
Assuming that the c ontent ac tivation to o l's initial, automated infrastruc ture mo delling is no t too far off the mark, the rest o f step 2 is dedicated to c orrectio ns and enhanc ements.
ABAP, Java , so the too l pre-gro ups lo gical c ompo nents with identic al productio n system. Pre-gro uping means that the to o l generates default names fo r lo gical c ompo nent gro ups as explained below. Rename them suitably. Some entities suc h as Produc tio n and Maintenance branc hes are part of SAP standard nomenc lature and c annot be renamed. Caution This step offers the o nly oppo rtunity in the guided pro cedure to rename an object lo gical c ompo nent group, so lutio n, branch, site - the latter two with the exceptio n of standard production and maintenanc e branches and global site to something mo re descriptive.
Renaming later is only po ssible by returning to this step. Regarding logical co mpo nent gro ups, o nce yo u have c ompleted the first step of the activation guided proc edure Step 1: Chec k Prerequisites , their names c annot be edited at all within the co ntext o f c ontent ac tivatio n. After you have c rossed that line, yo u are only left with the cumbersome renaming pro cess in the So lution Do c umentatio n applicatio n of SAP So lutio n Manager 7.
It is therefo re best yo u set aside the time fo r renaming your logical compo nent groups at this stage of the ac tivatio n pro cess and no t leave it for later. The guided proc edure tries to distribute all systems fro m the o ld 7. When there is mo re than o ne plausible o ptio n, the to o l makes no dec ision and the system remains in limbo.
In LCG Overview yo u c an see whic h systems have already been assigned to a new 7. LCG Overview is a simplified versio n o f the main table in step 2 leaving away site, branc h and system ro le info rmation thus allowing you to fo c us o n assigning systems to lo gic al c ompo nent gro ups. Sho w So urc es adds two c o lumns with info rmatio n o n the 7. Edit allo ws yo u to mo ve systems between lo gic al c ompo nent gro ups. Do Not Forget to Rename your Logical Component Groups To reiterate the explanatio ns given abo ve, this step in the co ntent ac tivation proc ess is the best one to replac e ugly system-generated default names for lo gical c ompo nent gro ups by names that suit your business purpo ses.
No te that as several pro ducts c an be installed o n o ne produc tive system this naming c onventio n is no t unambiguo us. How Logical Com ponent Groups are Creat ed, if 7. Bo th dummy entities show up in LCD Ove rvie w.
While it is po ssible to leave the dummy entities unc hanged, we rec ommend that you at least rename the dummy logical compo nent group o r — preferably - re-assign the dummy lo gical c ompo nent to another logical co mponent gro up in the LCG Overvie w.
Yo u do so by selec ting the dummy logical c ompo nent and assigning it to another logical compo nent group. The dummy logical co mponent gro up then disappears. More than One 7. Ho wever, if you do require additional 7. Cho o sing this optio n will trigger recalc ulatio n of the system landscape propo sal, no w c omprising multiple so lutio ns. Target Branches and Remote Sources Some data asso c iated with 7. SAP transac tio ns, c o nfiguratio n and develo pment o bjects and t est case descript ions see sec tio ns Bac kgro und on Why and Ho w Re mote Data are Brought fro m 7.
Step 3 makes sure that data related to tho se remote objects is c orrectly ac cessed during the c ontent ac tivation pro c edure. How Managed Systems Are Ident ified as Sources for Remote Object s Lo o king at the list which co mes up when entering step 3, it is no t immediately c lear how all the data in the various c o lumns determines a managed system as a so urce of no n-loc al data. It wo rks as fo llows. If you no w add a logical c omponent gro up LCG to tho se fo ur elements, a managed system has in general been uniquely determined.
Again, these fo ur elements and an LCG will in general suffice to find the pro per so urce system for test c ase data and the LCG is the o ne into whic h the 7. If things are still unc lear, go through the simple example at the end o f this chapter.
The Mechanics of St ep 3 Step 3 presents yo u with a list of the 7. Yo u have to co rrec tly c o nnect those infrastructure elements to the managed systems whic h co ntain remote o bjects o f types tec hnic al objects and test cases. The struc ture of the list mirro rs yo ur task: Rearrange tho se, if nec essary, by applying the fo llo wing rules. Where Remot e Objects Are Usually Found Object s t ypically found in product ion syst ems Produc tive Technical Objects reside in productio n systems, so setting Branch fo r Te chnical Obje cts to 'pro duc tion branc h' wo uld be the plausible cho ice - unless you have fo r so me reaso n no t assigned yo ur produc tio n system to a productio n branc h.
Object s t ypically found in non-product ion syst ems All o ther remo te objects are mo re likely to reside in development, quality o r other no n-produc tive systems. Test Cases are, fo r example, usually relevant in quality o r even development enviro nments. Procedure Read the abo ve, then fo llo w the instruc tio ns in the inline do c umentatio n of the guided pro cedure.Insert a date, if yo u want to exc lude pro jec ts and so lutio ns who se so lutio n do c umentatio n has no t been updated after the cut-off date.
First, SAP Solution Manager enables the customer to have a faster implementation of SAP solutions and helps optimize operations once implementation is complete. Let's take a closer look at these features and how they relate. Yo u can fill the exec utable and the develo pment libraries auto matically in so lutio n administratio n o n so lutio n level.
Remo te objec ts o f type "manual test c ase" are handled differently. Table of contents, in-text references, and index fully linked. Reduce yo ur c o ntent management effo rt by wo rking o n reusable do c umentatio n elements o nly o nce fo r multiple use in different end-to-end business pro c esses.
- MECANICA DE LA MOTOCICLETA WILLIAM H.CROUSE PDF
- THE LAST APPRENTICE NIGHT OF THE SOUL STEALER PDF
- QURANIC LANGUAGE MADE EASY PDF
- SERVICE BOOK DAUDEN
- FRONTIERS OF ELECTRONIC COMMERCE BOOK
- FIRST BLOOD DAVID MORRELL EBOOK
- DFA AUTHENTICATION FORM PDF
- MECHANICAL ENGINEERING BASICS BOOK
- ASSEMBLY LANGUAGE STEP BY STEP PDF
- HIMACHAL GK BOOK