Documentation: SOLAR01/02 or Solution Directory?

Dear all:
We are implementing SOLMAN to use change request management and a place to store the documentation, for our live system. Ive been reading a lot the last month trying to understand all the strange concepts about solman, and implement it in the best way, until 2 days ago I thought that documentation should be stored within SOLAR01/02, but yesterday I was reading a blog and it says documentation should be stored at Solution Directory, for a live system like mine.
Anyone could shed light on this?
Hope you can help me guys, I really need help on this!
Best regards,

Hi,
The documentation that you do in your SOLAR01/SOLAR02 actually gets stored in Solution Directory (We can call it a repository)
Check these links.
http://www.wilsonmar.com/sap_solution_manager.htm
http://help.sap.com/saphelp_sm32/helpdata/en/5a/c08802c3f446ed968db8cecce8ac35/content.htm
http://help.sap.com/saphelp_sm32/helpdata/en/11/1c2441ce87a22be10000000a1550b0/content.htm
Hope this helps.
Feel free to revert back.
-=-Ragu

Similar Messages

Question regarding documentation in a solution in the solution directory

My understanding of SAP Solution Manager is that after the implementation project is finished the business process structure with the documentation objects are moved to a solution.
During the operational phase a support team can use this documentation. But I do not see a way of searching for documents in a solution similar to the way of searching a project with SOLAR_EVAL.
Please clarify, thanks in advance.

Thanks for your answer.
I still do not completely understand the concept of a solution. In the SAP documentation I come across statements like:
<i>"The Solution gives you a means of ensuring that all information remains accesible and can be consolidated once the project is over."</i>
With the transfer of the project to the solutions you can copy the project documents to the solution. But what is the use of copying the documentation to the solution (besides consolidation) when a support team is not able to search for documents in the Solution. In other words does a support team have to look for documentation in the Implementation Project itself or should they use the Solution Directory.
Thanks in advance...

Copying Certain document types only from project to Solution Directory

Hello,
We are in the process of setting up Solution Directory in Solution Manager 4.0 sp12. After creating a solution we'd like to add scenarios from multiple implementation as well as template projects based on the document type.
We have several document types that we use in various tabs (config, testcase etc) and would like to get only a subset of document types from the soruce projects.
When trying to use the copy options in the pop-up window the copy filter works only on the documentation tab and does not filter the documents in other tab's based on the copy option filter.
Is there anyway we can filter the document types upon copy from project to directory. Please let me know if there is any Badi or User-exit for this functionality as well.
Any Help is much appreciated.
Thanks
Rajesh Sundar

Hi Rajesh,
I just came across this article and I reckon it will answer your question. Please read the section Documents copied when copying a project.
http://wiki.sdn.sap.com/wiki/display/SM/Documents+in+Solar01+and+Solar02
Cheers
Ganesh

How many Solutions entries in Solution Directory?

What is the best practice for setting up Solutions in the Solution Directory?
Should we have one for all business processes?
Should we have maybe something like the following?
1. Campaign to Cash Business Processes
2. Employee Business Processes
3. Solution Manager -- ITIL Business Processes
Are there any disadvantage to having multiple solution entries?
I searched service.sap.com and this forum for an answer before posting this question.
Regards,
Mel Calucin
Bentley Systems

Hi Mel,
I will try to answer your questions:
1. New and to-be-modified business processes are developed and tested using Solution Manager Projects and are never developed or tested using Solution Manager Solutions; CORRECT!
therefore, Solution Manager Solutions only contain production business processes.
CORRECT! you can transfer the business processes in a project to a Solution to used for example "Business Process Monitoring scenario"
2. When a Solution Manager Project is completed, business processes in that Project are copied to one or more Solution Manager Solutions; consequently, the business processses become production business processes.
Correct!
3. The structure of a Solution Manager Solution is the same as a Solution Manager Project; however, some tabs in a Solution Manager Solution are not modifiable and can only be populated when a business process in a Solution Manager Project is copied to the Solution Manager Solution.
You can transfer the data from a project to a Solution, and in this case you will get the same business scenario structure that you had in SOLAR01, but you can change this structure in order to delete scenarios, or add new once.
Also you can create a clean solution and add this Business Scenarios manually comming from different projects if you like.
4.
5. The business processes defined under a Solution or Project must be linked to a Logical Component
Correct!
The business scenarios that you define in your solutions are only use for "Business Process Monitoring" scenario.
Usually other customer creates Solutions and add the logical components that ate included in the solution.
6,7, 8 Logical component definition
A logical component define the different systems, with different roles involved in a
usual DEVclient->QUA_client->PRD_client landscape for a specific version and installation type.
For example, a usual logical component would be:
Z_ECC60: DEV 100 QUA 200 PRD 300
You can also enter other system roles in this logical component
This DEV 100,etc, has previously defined in SMSY and RFC connection created to these satellites.
9. Correct! because the processe take place in logical components finally, in SAP or not SAP systems.
"Given the above statements are true, the goal would be to document all business processes in Solution Manager Solutions. It is unnecessary to create Solution Manager Solutions based on system roles e.g. one for Solution Manager Solution for Production, one Solution for QA, one for Dev or combinations of system roles e.g. Dev->QA->Production. By defining one Solution Manager Solution, the system roles are also defined for the business processes contained in the Solution Manager Solution."
The goal is to have the documentation of the business processes in the SOLMAN system.
The Solution are mainly created for Administration and monitoring activities, based on system "basis" site, so usually Solution are created for these purposes usually after the Go live of the project.
I mean, Solution are used for the technical part of the project.
Although for Service Desk and Change request management scenarios more than
technical roles must be involved.
So, do you want to generate a report with the response times for all your productive systems? if yes, you will need to define a Solution that includes all
the logical components available in your landscape, but only "Put in Solution" the production systems.
Do you want to see the alerts from only want system, instead of seeing a graphic with 10 systems, you will need to create a Solution with only this system.
Usually to have a Solution with all system is not operational, unless you have few systems.
I have to insist in the idea that the Solution is not used by "Functional" team, mainly for "Technical" team.
!"My quesiton is: Is it better to have one Solution Manager Solution for all business processes or to divide the business processes into multiple Solutions. If it is better to break up the business processes into multiple Solutions, what is the best way to break them up? Does SAP offer a best practice for this?"
Usually customer even not define the Business Scenarios in their Solution for the Operational scenarios, because these Business Scenarios are not used.
Hope this clarify your questions, best regards,
Dolores

Solution Directory--Business process --Check in /Out option

Dear Friends,
I am working in Solution directory (t.code: DSWP). I have created one maintenance project. In this maintenance project i have maintained the following business process.
1. Sale Order Processing
2. Production Order Processing.
These two business processes are currently running in my R/3 production process.
In SOLAR01 , "admin" tab i have assigned project team member as "ZSRAGHU" for business process 'Sale Order Processing"
Like the same way, for business process "Production order Processing" i have assigned the project team member as "ZSRAO".
In SOLAR_PROJECT_ADMIN t.code, i have checked in the box "Restrict changes to nodes in project to assigned team members" so that only assigned team member can edit the business process.
Now i have assigned this maintenance project to my Solution. (The name of my Solution is "TEST")
As per the help.sap.com document, if the business process has been "checked Out" from Solution directory by the project lead, then only the team mmeber can edit the process in SOLR01.
Am i right?
But in my system, the team members are possible to edit the business process (In SOLAR01..."Structure" tab) before the business process are being "Checked Out" from Solution directory.
I want to restrict this option to my team members.
My requirement is:
If the Business process been "Checked out" in Solution, then only the team member can able to edit the business process in SOLAR01 otherwise i can not preserve my production business process....
Please guide me to achive this & will be very much rewarded.
Note:
In "SOLAR_PROJECT_ADMIN" under "Scope" tab, check in the box "Edit structures" will NOT help to map this requirement as all aware.
Regards
Senthil

Dear Senthil,
By Business Process 'Check Out', I hope you are talking of the 'Document' attached at Process level and not the Process itself, as in the structure.
I can understand your frustration about the indicator "Restrict changes to nodes in project to assigned team members" not working.
As mentioned in the online help, did you try to work your way through Authorisation Object "AI_SA_TAB" ?
Is it due to some other authorisation that users have, which 'supersedes' this authorisation object ? Did you check any SAP Note for this object ?
If nothing else works, can you try to introduce a 'Custom Status' and use the following IMG setting to restrict it by users:
SAP Solution Manager -> Configuration -> Scenario-Specific Settings -> Cross-scenario Settings -> Document Management -> Status for Documents -> Assign Status Values for Read Authorisation
This may be a workaround !
Regards,
Srini

Solution Directory - How to lock a business process for a implement project

We have Solution Directory assigned to a maintenance project and I understand the checkout/checkin process and how it locks the business process in the Solution. What is the best practice when you are starting a new IMPLEMENTATION project that will impact existing business processes that are in the Solution? I know that I can copy from the solution to build the new project, but it doesnu2019t lock the BP from the solution.
I have a new Implementation project, that i want to checkout/pull existing business processes for the Solution Directory.
*How can these Business Processes be "locked" in Solution Directory as they are with a Maintenance project?*

Kelly,
You would use the maintenance project to make daily modifications.
Consider the case of a O2C business scenario. You need to almost make daily configs etc, which get pushed through, such things will go into a maintenance project.
But if you plan to enhance O2C with a CRM front end or include a better planning solution or TPM or something, then you are looking at an implementation project.
Rule of thumb. Short Scale changes : Maintenance Project, Long term/major enhancements : Implementation Projects.
Also In this case to speak about the lock down. Well the Solution Directory kind of takes care of that for you.
I am assuming that you have a solution populated with business processes. So now if you want to enhance it with a new functionality, you would use an implementation project. So when you define the implementation project, and then navigate to Solar01, and try to add business scenarios , ensure that on the Structure tab you select the Solution as the source. This ensures you are copying content from your current, updated, productive solution. Once you do that, the implementation continues on its track, whilst daily support processes are managed with the check-in / check-out functionality of the Solution and the Maintenance Project.
You technically do not need to lock the business processes down, since the Compare and Adjust functionality of a solution will help you identify the deltas between the Solution and the implementation project and you can always make those adjustments post go-live and thus just update the Solution at one shot. Also remember that with SolMan 7.1 the Compare and Adjust functions can be used with Template, Implementation and Solutions in any permutation-combination.
Hope this helps.
Plz let me know if you need any additional information
Cheers!!

Compare and adjust business processes to a solution directory

Dear all,
I'm having truble with viewing changes that I have made in my maintenance project, using the compare and adjust function. Can you please tell me what I'm doing wrong?
These are the steps I took:
1. I chose a solution using transaction SOLUTION_MANAGER.
2. I have made the solution settings, including creating a maintenance project, and enabling the check out/ check in & history functions.
3. Added business scenarios to the solution directory (some I chose from a project, and some I have created manualy).
4. Checked the Scenarios out to the maintenance project.
5. Made some changes in the maintenance project, including adding documents and transactions (transaction SOLAR01).
6. Changed my user-specific settings to comparison mode - "display changes made in original".
7. Checked the edited business scenarions back into the solution directory. I have checked, and the changes I've made in the maintenance project apeared now in the solution directory.
Now starts the trouble...:
8. I checked the scenarios out again from the solution directory to the maintenance project.
9. Went to transaction SOLAR_PROJECT_ADMIN, marked the maintenance project line, and did "compare and adjust" of a "new version of original" .
10. Went back to SOLAR01 and try to view the changes I have made in the maintenance project. I CAHNGES I'VE MADE ARE NOT MARKED...
Sorry for the long description. Can you please help?
Thank you,
Adi

Adi,
Did you find a resolution to this problem? we are faced with the exact type scenario.

Global template and rollouts vs. Solution Directory

Hello,
I would like to know what is the best way to maintain the global template and the related rollouts documentation.
I know the functionality of Solution Directory, ie. it should be the primary place to maintain a solution in production, changes should be done using maintenance project, checking out scenarios etc. However, my customer is running into a couple of challenges. The current situation is as follows:
- The global template phase I has been finished (containing financial template).
- The global template phase II development is starting (containing logistics template).
- The phase I template has been rolled out to five countries which all are in production.
- The phase I template will continue with new rollouts coming.
- All the country-specific rollouts are actually in one physical SAP system so there is only one system to be maintained.
I see it somehow impossible to try to maintain the template + rollout documentation in one single solution in Solution Directory. There is only one Documentation tab in the solution and if we put all the country-specific documentation there it is a mess. Furthermore, all the rollout projects are separate, it would be difficult to manager rollout projects with one maintenance project. Not to add the fact the compare and adjust functionality applies only to template projects not solution.
I have the feeling that we would need continue maintaining the global template and rollout projects in SolMan Implementantion projects (template + rollout projects, template versions, compare and adjustment etc.). Only if I want to start process monitoring I would use solution but otherwise it cannot be very much utilized at the moment.
Any comments? Have I missed something here now? I would appreciate any practical experiences about this.
Br,
Timo

Hi Timo -
The situation you are experiencing is similar to what I have seen. And that is...ensuring Solution Directory is the "Single source of the Truth". It is almost impossible when you have two parallel activities going on between 1) SAP implementation projects and 2) SAP maintainence/sustain activities in production.
Solution Manager seems to be a great tool for companies that are in a sustain mode, resolving issues when found in production. We recently decided to change our approach from SAP's recommended and best practice of using the Solution Directory connected to a Maintainence project and implementation projects being seperate rollout initiatives managed seperately. Instead, we have changed our "Solution Manager Landscape" to encompass all activites into a 1 template project. We now don't plan on going back to the SAP best practice of Solution Manager until we are completely done implementing SAP and we have identified what our true business processes are. For example: creating the Business Process Hierarchy.

Contacts in Solution Directory

Hi everybody
I'm trying to setup BPM in Solution Manager.
When you click the button " Contacts" In the Solution Directory the sub node Contacts is missing under Contacts Maintenance.
Does anybody has an idea how i can make this appear ?
thanks for your help
Murat

Hello Murat,
Please see the following documentation regarding setting up BPM and
in particular Page 21/22 about maintaining contacts.
https://websmp102.sap-ag.de/~sapdownload/
011000358700006137532006E/BPMon_Setup_Guide.pdf
Also make sure you have applied the most recent patches for ST-SER.
Hope this helps.
Regards,
Paul

Solution Directory

Hi all
Could you please assist. I want to make sure that my Landscape is setup correctly for the "graphical" display to work in the Solution directory. i have used SMSY to create everything. I have a DEV, QAS and PRD on ECC6. When I run SOLUTION_MANAGER, I do not see the systems to be monitored.
What can I do to "fix' this?
Jaco

Hi,
Have a look into the below link
[http://help.sap.com/saphelp_smehp1/helpdata/en/b3/64c33af662c514e10000000a114084/frameset.htm|http://help.sap.com/saphelp_smehp1/helpdata/en/b3/64c33af662c514e10000000a114084/frameset.htm]

Compare and adjust functionality for Solution Directory

Hello all,
I am trying to use the Compare and Adjust function with a Solution Directory. There is a previous discussion about how to do this between a Master Template and Implementation Project. Now that the Solution Directory exists, I would like to do the same thing. I.e. take scenarios from the Solution Directory into individual projects to extend them before putting them back into production. Together with the check in/out function, I would like to use the Compare and Adjust (SA_PROJECT_UPGRADE) function to identify differences periodically. The button for this appears in the transaction SOLMAN_DIRECTORY, but I can't seem to activate it - i.e. it is faded out. For projects, you must first run SA_PROJECT_UPGRADE to activate this button. However, you cannot select a Solution when running the project upgrade transaction. Does anyone know how to do this? Is anyone using the Solution Directory in a similar way and have advice?
Regards,
Marcel

Hi Marcel,
Funnily enough I have the exact same question.
Is there a way to compare changes between a maintenance project (business scenarios checked out this project) and the solution. This way the person approving the check in can see the changes before approving.
Have you had further information on this?
Referring back to your question, ideally once you've checked out a business scenario to a maintenance project you wouldn't continue to maintain it. It is the responsibility of that project to maintain it. In the meanwhile if you have a support issue that requires that business scenario to be updated, this will have to assessed and handled by either the project or the solution administrators.
Cheers
Ganesh

Solution Directory - Configuration Tab is freezed

Hi Experts,
I can't modify or create any item in the Configuration Tab of the Solution Directory.
I am not really used to this interface, can anyone explain why this is happening and how I should resolve the issue?
Many thanks,
Aldo

Hi Bhudev,
Yes, this is transaction solman_directory. I can view the Configuartion tab but I cannot change it.
Yes, I am in Change mode.
There are some items in there already (they were not added by me). We are trying to modify these existing ones and to add new ones... but the tab (Configuration) is freezed.
I can edit documents in other tabs. For example under "Transactions" or "Development".
Any further help will be much appreciated.
Many thanks,
Aldo

Solution Directory reports

We are defining business process in Solution Directory creating associations between process steps and logical components. For future process analyses we need to know for a specific logical component where it is utilized. There are some reports in SOLMAN to cover this requirement?
Regards

Hello Sebastian,
Its not a report as such, but for any logical component there will be the where used icon (CTRLSHIFTF3) which looks like a box with 3 arrows pointing N/E, E and S/E. Anywhere there is a logocal component this icon exists, though you may need to be in changed/edit mode to acess it.
As I say it is not a report, but will tell where any single logical is used - what projects, solutions, etc.
Is this useful for your needs?
Regards,
Paul

Solution Directory----Merging two projects in Solution

Dear Team,
I am working in Sol Man 4.0 SP 13.
we have created two projects in Sol Man & we have done our entire implementation thro Sol Man. Now the two projects are gone live.
Now we want to maintain "Solution Directory" merging these two projects.
Please guide me, what are all the primary inputs i have to collect from the customer in order to start this activity?
Note: I believe, based on the "Solution Directory" only our Business Process Monitoring works. Is it correct?
any valuable input will be very much appreciated
Thanks
Senthil

Whilst my instructions are lengthy, that is to give a full explanation of all the ins and outs. In your case the work will be little more than creating a parent and setting up your two existing projects as children.
It's a lot easier than trying to have one source project.
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge

Solution Directory Graphic Displays as XML

We are runing Solution Manager 4.0.
If I perform the following actions...
- Run transaction SOLUTION_MANAGER.
- Select "Goto Solution Directory" (pencil icon) for a solution.
- Expand the solution structure by clicking on the solution name.
- Select the Systems sub-item or the Servers sub-item.
Instead of seeing any graphics in the Graphic tab, I see XML tags. The XML is formatted using Internet Explorer's default appearance.
Any idea what could be causing this? I downloaded and installed the latest version of Microsoft XML (MSXML 6.0), but this didn't change anything.

Hi Steve,
Can you help us how to change this default name mapping.... we too are in a similar problem...where the graphics display is in XML code.
The error shows : URL http://blrkecsolman.XXXXXX.com:8001/sap/bc/solman/defaultUser/graphic/solmangraphic.htm call was terminated because the corresponding service is not available.
Thanks for your help.
Br,
Sri

Documentation: SOLAR01/02 or Solution Directory?

Similar Messages

Maybe you are looking for