System/Ibase for DQ0 to be added in Solution Manager SM0-010

Hi,
Question: System/Ibase for DQ0 to be added in Solution Manager SM0-010
Please let me know the process how can do this. I will really appreciate.
Regards, Nabi.

Hi Nabi,
if it is an ABAP based application, check in transaction IB52, if it has been already automatically created there. If yes, you might only need to go to transaction dswp (solution_manager) and go to the menu select edit and in the drop down menu you should have 'Initial Data Transfer for IBase´.
If it is not there, you need first to check:
- RFC connections maintained for DCQ in SMSY
- Logical Component created in SMSY for DCQ
- Assignment to Logical Components in SMSY for DCQ
- DCQ added to the Solution SMSY
Then check again in IB52. IB51 is used for creating the entries manually.
If the entries are now in IB52, you need to execute the "Initial Data Transfer for IBase" again.
I hope this helps.
Regards,
Markus

Similar Messages

Centralized View for all the Project Document in Solution Manager

we assign roadmap to our Implementation project and as per roadmap we upload different documents for the project(e.g. business case, project charter) at different phases of roadmap. can we see all the documents related to a project from a single centralized view??

Hi B_J,
it is correct, each document has attributes, on the attribute tab in the button bar, there is an icon to generate an url for the selected document. This link is stored in your windows clipboard, so you can past this link in an e-mail or wordfile. The person who gets the e-mail must have access to the Solution Manager via network, he needs no personal user in the system. The link used a service of Solution Manager(check in the Solution Manager IMG at the HTTP services). This service requires a user to read the document. If you have no user, then it is necessary that in the system a default user is assigned to the service or to its alias. Now to your second use case, the approval, you can not bring any information INTO Solution Manager, you can only answer the e-mail, with the info, yes the document is OK, but you can not set a status or an other attribute at the document, that the document is approved.
Regards,
uDo

BI content for Solution Manager 4.0

Hi Experts,
I want to install BI content for Solution Manager 4.0 but i don't know what kind of BI content i need and where can i get some information about this.
if somebody knows somthing , please , let me know.
Thank you.

There isn't a lot of standard content for Solution Manager. It's mostly alerts, server, module, database and overall system information for the environments connected to that Solution Manager instance. The standard DataSources are:
0SM_DSWPBI_BPM                   BPM Data (Alert Data)
0SM_DSWPBI_DB390
0SM_DSWPBI_DB400                DB400 Data
0SM_DSWPBI_DBADA               Adabas Data
0SM_DSWPBI_DBDB2               DB2 Data
0SM_DSWPBI_DBINF                Informix Data
0SM_DSWPBI_DBMSS              SQL Server Data
0SM_DSWPBI_DBORA              Oracle Data
0SM_DSWPBI_MODUL              Module Data
0SM_DSWPBI_PERF                 Performance Data
0SM_DSWPBI_SERVER            Server Data
0SM_DSWPBI_SYSDATA          System Details Data
0SM_DSWPBI_SYSTEM            System Data
There are several InfoCubes, one for each DataSource in the standard content. These InfoCubes are then unioned in a standard content MultiProvider.

Create a Support Message in Production system showing up in Solution Manage

Has anyone setup the link between creating a support message (under help) in a production system (like ECC) and SAP's Solution Manager.
I understand that it uses BADI SBCOS001 with the interface method PREPARE_FEEDBACK_BO, but when I try to run it, it tells me that Customizing for feedback functionality missing. What functionality is missing? And how to I correct this? And how do I ensure it shows in SAP Solution Manager under a solution or project?
Thanks
Paul

Hi Paul
The only way is to use the IMG. I have just completed this via the IMG info. BUT, it is not that simple.
Make sure your RFC's are trusted and that you have SAP ALL during config.
I hope this will help:
Setup Service Desk
Steps to follow while configuring support desk.
1) Implement the note 903587 .
2) Create all the relevant RFC objects in the satellite system and add the appropriate logical components using transaction SMSY.
3) Check all the objects in the table BCOS_CUST using transaction SM30.
Appl : OSS_MSG
+ :W
DEST :BACK RFC NAME (for solution manager system keep this field as 'NONE')
+ :CUST 620
+ :1.0.
*4) Check whether the BC sets are activated or not using the transaction SCPR20.If the BC sets are not activated then implement the note 898614.The steps to activate the BC sets are described below
4.1) Activate SOLMAN40_SDESK_BASICFUNC_000 BC Set.
4.2) Activate this in expert mode with option u201COverwrite everythingu201D.
4.3) Activation of the following components has to be done by replicating the previous steps
3.1) SOLMAN40_SDESK_TPI_ACT_AST_001
3.2) SOLMAN40_SDESK_ACTIONLOG_001
3.3) SOLMAN40_SDESK_ACT_ADVCLOSE_001
3.4) SOLMAN40_SDESK_TEXTTYPES_001
*Depends upon the number of inactive BC set objects that we have after the upgrade.
4.4) if the actions mentioned in 4.3 are not listed while executing the transaction SCPR20, then implement the note 898614.In the source client 000 of the solution manager system create a transport request using transaction SE09, unpack the file 'PIECELIST_SERVICE_DESK_INIT.ZIP' from the attachment of the note. Copy the contents of the file 'PIECELIST_SERVICE_DESK_INITIAL.TXT' to the transport request. And activate the actions. Use transaction SCC1 to import the transport request to the solution manager client. If any short dump occurs during the activation, implement the note 939116.
5) Check whether the number range is set correctly. If not set the number ranges of basic notification (ABA) and the support desk message (Service transaction SLFN).To be able to use the same number ranges for both message types, the internal number range for basic notification (ABA) must correspond to the external number range for the support desk message.
Number ranges for ABA notifications
5.1) create an internal and external number range using transaction DNO_NOTIF.
5.2) assign number range intervals to groups internal and external.
5.3) SLF1 is the internal number range group
5.4) SLF2 and SLF3 is the external number range interval
5.5) Use transaction DNO_CUST01 to assign message categories to the number range.
5.51) Go to transaction DNO_CUST01
5.52) From the GOTO menu select the menu item DETAILS
5.53) Now you can assign the number range of basis notification (ABA) into the notification type.
The number range for ABA notification is 12 characters in length and to make it compatible with the CRM service transaction insert 2 ZEROES at the beginning.
Number ranges for Support Desk notification
5.54) Use transaction CRMC_NR_RA_SERVICE, and define the internal and external number ranges. Intervals must correspond to the intervals of the basic notifications (ABA notification).
5.6) Then assign both the external and internal numbering
5.61) Go to SPRO and then to SAP Solution Manager
5.62) Then select General Settings and then select Transaction types
5.63) Select the transaction type SLFN and then select the menu item DETAILS from the GOTO menu.
5.64) In the Transaction Numbering block, assign the internal and external number range. The Number Range object should be CRM_SERVIC.
5.7) To view the priorities use transaction DNO_CUST01 and select the notification type as SLF1 and then select priorities from the left pane of the screen. The priorities of the first four cannot be deleted, but new priorities can be added.
6) Check the Action profiles for ABA Notifications (Action profiles are used for synchronization of ABA notification with the CRM Service transaction).
6.1) To check the action profiles use the transaction SPPFCADM and select the application type DNO_NOTIF then select u2018DEFINE ACTION PROFILE AND ACTIONSu2019.
6.2) Select the item u2018SLFN0001_STANDARD_DNOu2019 and then from the menu GOTO, select the menu item DETAILS.
7) The Action profile u2018SLFN0001_STANDARD_DNOu2019 has to be assigned to the message category SLF1 (ABA notifications) using the transaction DNO_CUST01.
8) The action profile for the support desk message can be set to u2018SLFN0001_ADVANCEDu2019.
8.1) From SPRO select SAP Solution Manager then Scenario Specific Settings.
8.2) Select the item Service Desk and then to general settings.
8.3) Execute the category u2018Define Transaction Typesu2019.
8.4) Select the transaction type as SLFN
8.5) From the GOTO menu select the menu item u2018DETAILSu2019 and assign the action profile as SLFN0001_ADVANCED .
9) Activate the partner/ Organization
9.1) Go to CRM->MASTER DATA->BUSINESS PARTNER->INTEGRATION BUSINESS PARTNER ORGANIZATION MANAGEMENT->SET UP INTEGRATION WITH ORGANIZATIONAL MANAGEMENT.
9.2)Find the entries starting with HRALX
HRALX-HRAC WITH VALUE 'X'.
HRALX-OBPON WITH VALUE 'ON'.
HRALX-PBPON u2018ONu2019.
HRALX-MSGRE u2013 u20180u2019.
9.3) If entries are not found create it.
10) Generate Business partner screens
10.1) Go to transaction BUSP.
10.2) Execute the report with the following parameters
CLIENT - Client in which business partners should be created (solution manager client)
APPLICATION OBJECT-
SCREEN - *
Generate all/ selected screens - All screens.
delete sub screen containers -
11) implement SAP note 450640.
11.1) Go to transaction SA38 and select the report CRM_MKTBP_ZCACL_UPDATE_30.
11.2) Execute it with test mode box unchecked.
If a new relationship is to be created then steps 12 and 13 has to be followed
12) To create a relationship category
12.1) Go to transaction BUBA
12.2) Select the entry CRMH00: Undefined relationship
12.3) click on copy
12.4) Rename CRMH00 to ZCRMH00.
12.5) CREATE A RELATIONSHIP CATEGORY.
IN GENERAL DATA FILL LIKE ' FROM BP1 : HAS THE ACTIVITY GROUP '.
' FROM BP2 : IS A PART OF ATTUNE
13) Add the relationship category to the support team partner function
13.1)Use SPRO
IMG GUIDE->SAP SOLUTION MANAGER->SCENARIO SPECIFIC SETTINGS->
-> SERVICE DESK->PARTNER DETERMINATION PROCEDURE->DEFINE PARTNER FUNCTION.
13.2) FIND THE PARTNER FUNCTION SLFN0003 (SUPPORT TEAM).
13.3) In the field relation ship category, Select the newly created relationship category and save.
14) Steps 12 and 13 should be repeated for various business partner types like sold-to-party, message processors if new relationship is to be created for the respective business partner types.
15) Create a new access sequence for the support team determination
15.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
SAP Solution Manager -> Configuration ->
-> Scenario Specific Settings ->Service Desk -> Partner Determination Procedure ->
->Define Access Sequence
15.2) Click on New Entries
15.3) Define a new access sequence with sequence name as u2018Z001u2019 and description u2018NEW BP RELATIONSHIP ACTIVITY GROUPu2019
15.4) Create an new Individual Access with the following value:
u2022 Batch Seq: 10
u2022 Dialog Seq : 10
u2022 Source : Business Partner Relationship.
u2022 Detail on the source:
u2022 Partner Function : Reported By (CRM)
u2022 Mapping/restrictions
u2022 Flag Mapping/definition for partner being Searched
u2022 Partner Function in Source: Support Team (CRM).
Save it.
This Access Sequence will give us the Partner which has the relationship assigned
to the Support Team in the Reported By partner data.
16) Adapt the partner determination schema/Function
16.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
SAP Solution Manager -> Scenario Specific Settings ->Service Desk ->
-> Partner Determination Procedure -> Define Partner Determination Procedure.
16.2) The two options to adapt partner determination schema are
16.21) Adapt the standard Procedure (SLFN0001) or to create a new one by copying the standard one.
16.22) select the line starting with SLFN0001 or the newly created procedure.
16.23) Double Click on Partner Function in Procedure.
16.24) Select the Partner Function "Support Team", and click Details.
16.25) in the detail view only change the Partner Determination/access Sequence to
the one we've just created. Save your entry.
17) Create a root organizational model.
17.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration-> Scenario Specific Settings ->Service Desk -> Organizational Model ->Create a Root Unit for Your Organizational Structure.
17.2) creating an organizational unit by entering the data in the BASIC DATA tab.
17.3) enter the organizational unit, the description and save it.
18) Create the support team organization
18.1) go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Scenario Specific Settings ->Service Desk -> Create Organizational Objects in the Organizational Structure. Or use transaction (PPOMA_CRM).
19) Create the business Partners.
19. 1) Key users- End user (Business Partner General) ,Address should be specified.
19.2) go to the transaction BP.
19.3) create a new Person, Select the role: Business Partner (Gen).
For Identification of the key user
19.31) click on the identification tab
19.32) enter a line in the identification number formatted as follows
IDTYPE : CRM001.
Identification number : <SID><INSTALL NUMBERS><CLIENT><USERNAME>
eg: USER NAME : USER1.
CLIENT : 100.
SID : ER1.
INSTALL NUMBER : 123456789.
IDENTIFICATION NUMBER : ER1 123456789 100 USER1.
20) Message Processors- Support Team members .
20.1) they should be created first as the users in the corresponding client of the solution manager.
20.2) As business partners they will have the role 'EMPLOYEE'.
20.3) Go to transaction BP .
20.4) Create New Person with the role employee.
20.5) In the Identification tab you should enter the user name in the employee data/User Name.
eg: username: proc1
enter proc1 in the field User name.
21) Organizational Business Partner- Organizational BPS have the same country in there main address tab. They should be created through the organizational model. Business partner corresponding to the root organization have the role 'SOLD TO PARTY'.
22) Assign the business partners (Message Processors) to the previously created support team.
22.1) Go to transaction PPOMA_CRM.
22.2) Select the support team 1.
22.3) Click on create
22.4) select position
22.5) call it 'MPROC_T1/Message Processors for team 1
22.6) Replicate it for the other support teams.
22.7) Select the position MPROC_T1/Message Processors for team1 and click assign,
choose owner/Business Partner find and select the business partner
22.8) Validate and Save it.
22.9) If the assignment of business partner is not possible then implement the note 1008656
Or 997009
23) Create the iBase component
23.1) IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings -> Standard Configuration of Basic Settings -> Solution Manager -> iBase -> Initially Create and Assign the Component Systems as iBase Components.
23.2) or use the transaction IB51 to create the installed base.
23.3) it is also possible to create the SOLUTION_MANAGER, select the solution and go to menu Edit -> Initial Data Transfer for iBase.
24)Assign Business Partners to iBase Components
IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings
-> SAP Solution Manager System ->ServiceDesk-> iBase -> Assign Business Partners to iBase Components.
*--optional--
If you want to be able to assign the System Administrator: Go to the IMG: SAP Solution Manager Implementation Guide -> Customer Relationship Management -> Basic Function -> Partner Processing -> Define Partner Determination Procedure.
Select the entry "00000032 Installed Base/IBase" and double click on Partner Functions in Procedure.
Then copy the Entry "Contact Person (CRM)" to a new entry with the partner Function "System Administrator (CRM)" , save it.
Go back to transaction IB52, select a component, and Goto -> Partner, you should be able
now to assign the partner Function "System Administrator".
25) Assign the SAP Standard Role to the user. Message Creator should have the role : SAP_SUPPDESK_PROCESS.
26)Define the transaction variant for the message processors
Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration -> Scenario Specific Settings ->Service Desk -> General Settings -> Specify User Selection Variant.
Here we will create variants for the central message processing transaction CRM_DNO_MONITOR.so that the user will have direct access to there dedicated message.
27) Go to transaction PFCG
27.1) Enter the role name as Z_MSG_PROCESSORS and choose single role.
27.2) Give a description Message Processor role and save it.
27.3) Go to the menu tab and choose add report
27.4) select the report type : ABAP Report
27.5) And in the report enter the report name as 'CRM_DNO_SERVICE_MONITOR'.
27.6) Enter the previously created variant.
27.7) flag the skip initial screen box.
27.8) flag the SAPGUI for windows.
27.9) Create a new transaction with tcode starting with Y or Z.
27.10)Display this transaction and check the values at the bottom of the screen
in the subscreen Default Values, you should have the following parameters:
u2022 D_SREPOVARI-REPORT = CRM_DNO_SERVICE_MONITOR
u2022 D_SREPOVARI-VARIANT = MY_TEAM_MSG
u2022 D_SREPOVARI-NOSELSCRN = X
And also all the user should have the correct role.

Using central Solution Manager for monitoring multiple customers

Hello,
We are working on monitoring SAP systems of several customers. For every customer we have configured central monitoring on Solution Manager system of that customer. All satellite systems are added to RZ21 and CCMS agents are configured correctly. On the Solution Manager, in RZ20 we have created a rule based monitor specific to the needs of customer, and that monitor is used for the whole landscape of every customer.
But now I need to configure our central Solution Manager system which will collect CCMS data from all satellite systems of all customers on one place in RZ20. That central Solution Manager system should have direct connection only to customer Solution Manager systems and not to their satellite systems. Is this possible? If yes, can you please explain me how to do it or point me to documentation? I was unable to find solution.
To make this more clear I made a picture of desired configuration:
https://picasaweb.google.com/108686894540363563900/SAP#slideshow/5571983242527848482
Edited by: Dejan Terzic on Feb 10, 2011 10:04 AM

Hi Dejan,
as far as I know this is not possible.
we had similar issues, every time we migrated a new customer to or datacenter. Our solution was, to register the CCMS agents to two systems for a period of migration.
Sometime ago, I found a question for that an SDN:
Using another CEN for Solution Manager
I know, that this is not your question exactly, but it is the right direction...
Kind regards

New componant list for service desk in Solution manager.

Hello,
We wanted to customize new componants for service desk. Please let me know is it possible to define new componant list in the Solution manager.
Regards,
Bhavesh

Hello Waseem,
Actually I want to configure a list of Customise component in side solution manager for incident management.( service desk)
when we create ticket in service desk (in Solman) we have to select a component for the respective module( like BASIS, MM , Etc) those are the standard
Components that is given by SAP. I want to change that list and want to put my own list of component in the system.
is it possible to do it in Solution manager? If yes then what sort of configuration required. ?
Thanks in Advance
Regards,
Bhavesh

Problem while adding SAP Netweaver 7.3 As Java in Solution Manager 7.1

Hi All,
We are facing strange problem while configuring managed system- SAP Netweaver 7.3 As Java in Solution manager 7.1 SP3. We added this system in SLD of solution manager and synchronized it with LMDB. As a result this As Java system is present under Technical systems in SMSY. Now we are assigning Product system to it with Landscape verification tool. But the problem is when we try to save after assigning Product version as SAP Netweaver and Product as SAP Netweaver 7.3. It always gives below error:
Fatal error trying to update Technical System (UPDATE_TSYSTEMS). Update could not be executed.
Product instance 54 not found
Product instance number error keep on changing depend upon what usage i select like ADS 7.3, Application Server Java 7.3 etc.
Please suggest if someone has faced this issue.
Thanks
Sunny

Hi Sunny,
You can refer to my first blog on this topic:
#sapadmin:: How to assign Product System in SOLMAN 7.1 & How LMDB, SLD, SMSY and Landscape Verification work in SOLMAN7.1
Try to select only one product instance in LMDB and saved. After that, you can add more product instance in SMSY.
Hope it helps.
Cheers,
Nicholas Chang

RFC at customer for EWA into our Solution Manager

Hi,
I have created a BACK RFC in a customer system to get EarlyWatch reports sent into our Solution Manager.There is no direct connection between the 2 systems, so I'm connecting via their SAPRouter and our SAPRouter.
In the customer system in SM59 I've set up :-
RFC SM_<SID>CLNT100_BACK where <SID> is our SolMan
Routestring i.e. Target Host.- /H/<customer_internal_SAPRouter_IP/S/sapdp99/H/VAR_external_SAPRouter_IP/S/sapdp99/H/VAR_internal_Solman_IP/S/sapgw00
Gateway Host - VAR_internal_Solman_IP
Gateway service - sapgw00
Question 1 - Does RFC and routestring look correct?
I've also modifed saprouttab on the customer side with the entry :-
P ... VAR_external_SAPRouter_IP 3299
And on our side with the entry :-
P * * 3300
Question 2 - Do both saprouttab entries look correct?
I've also asked for our external firewall to allow traffic from the customer IP to get to our SAPRouter server.
Also for the customer firewall to allow traffic to our external SAPRouter IP
Question 3 - Have I missed anything on these 2 firewalls?
Question 4 - After the traffic reaches our SAPRouter server, are any changes to our internal firewall required for it to get to our Solution Manager system?
Any help is much appreciated - at the moment when we test the RFC on the customer system we can see traffic from the customer reaching our SAPRouter server, but then get an error in dev_rfc0 :-
Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 2803
CPIC-CALL: 'ThSAPOCMINIT' : cmRc=17 thRc=223
CPIC program connection ended (read error)
dev_rd shows :-
ERROR => NiBufIProcMsg: hdl 52 received rc=-93 (NIEROUT_INTERN) from peer [nibuf.cpp 2125]
Thanks,
Richard Shaw

Hi Anil,
Thanks a lot.
SAP provides the EWA report for all its clients production system without a Solution Manager system & not provide the sam for non productive system. That means to say that for quality & developement system SAP does not provide a EWA report without a SOLMAn. For this system you must required SOLMAN to generate the report.
Kind Regards,
Jitu

Is Solution Manager required for ECC 6.0 upgrade?

We will upgrade our system from 4.7 to ECC 6.0. Is Solution Manager a required tool in ECC 6.0? My understanding is Solution Manager has to be run on a different server, ie. we will have to buy a new server. We have a small SAP implementation with only FI & CO modules, so we are trying to cut our costs if we could. Can anybody share their experience? Thanks for any input.

In an Upgrade , Solution Manager is required for Upgrade Keys and downloading the support packs . Now a days to download the support packs you have to approve it in Solution Manager otherwise it won't show up in your download basket.
May be SAP can provide you the keys & approve the SPs ( they used to do that before ) , in that case it isn't required.
You can also manage your upgrade project in Solman . Sooner or later you need to install solution manager. it's a nice system.Many good features like central monitoring, early watch alert etc etc ...
Thanks
Prince Jose

Regarding Monitoring Service for Solution manager

We need to configure "Monitoring" services in SAP solution manager 7.0.
Could somebody suggest us what are the main tasks we need to consider for doing Monitoring settings.
How many Minimum servers required to configure Monitoring services in solution manager system.
Also if any good document reference for this?
Thanks

Hi Jai,
welcome to sdn.
COMPONENTS & TOOLS OF SAP NETWEAVER
SAP Solution Manager
The SAP Solution Manager application management solution facilitates technical support for distributed systems u2013 with functionality that covers all key aspects of solution deployment, operation, and continuous improvement. A centralized, robust application management and administration solution, SAP Solution Manager combines tools, content, and direct access to SAP to increase the reliability of solutions and lower total cost of ownership.
With SAP Solution Manager, you can be sure your entire SAP solution environment is performing at its maximum potential. The toolset addresses your entire IT environment, supporting SAP and non-SAP software and covering current and forthcoming SAP solutions. And, as a customer of SAP, you have full access to the core SAP Solution Manager for no extra charge.
SAP Solution Manager targets both technical and business aspects of your solutions, focusing strongly on core business processes. It supports the connection between business processes and the underlying IT infrastructure. As a result, it eases communication between your IT department and your lines of business. And it ensures that you derive the maximum benefits from your IT investments.
SAP Solution Manager features and functions include:
SAP Business Suite implementation and upgrades u2013 SAP Solution Manager provides content that accelerates implementation. Configuration information and a process-driven approach to implementation speed the blueprint, configuration, and final preparation phases. SAP Solution Manager enables efficient project administration and centralized control of cross-component implementations.
Change control management u2013 SAP Solution Manager controls all software and configuration changes of the IT solution. This includes the approval process for change requests, the deployment of changes, and later analysis of changes. This ensures quality of the solution and enables traceability of all changes.
Testing u2013 SAP Solution Manager speeds test preparation and execution. It provides a single point of access to the complete system landscape and enables centralized storage of testing material and test results to support cross-component tests.
IT and application support u2013 The service desk included in SAP Solution Manager helps you manage incidents more efficiently and eases the settlement of support costs. Centralized handling of support messages makes the support organization more efficient.
Root cause analysis u2013 The diagnostics functions in SAP Solution Manager allow identification, analysis, and resolution of problems, even in heterogeneous environments. This helps to isolate general performance bottlenecks, to isolate exceptional situations, to record the activity of single users or processes, and to identify changes to the productive landscape. As a result, problem resolution is accelerated and business availability increased.
Solution monitoring u2013 SAP Solution Manager performs centralized, real-time monitoring of systems, business processes, and interfaces, which reduces administration effort. It can even monitor intersystem dependencies. Proactive monitoring helps you avoid critical situations, while automatic notifications enable fast response to issues.
Service-level management and reporting u2013 SAP Solution Manager allows easy definition of service levels and provides automated reporting. Service reporting covers all systems in the solution landscape and provides a consolidated report containing the information you need to make strategic IT decisions.
Service processing u2013 SAP Solution Manager makes appropriate service recommendations and delivers SAP support services. These include SAP Safeguarding, which helps you manage technical risk; SAP Solution Management Optimization, which helps you get the most from your SAP solutions; and SAP Empowering, which helps you manage your solutions.
Administration u2013 Administration tasks are mainly executed locally on the involved systems, but can be accessed and triggered from a central administration console. The administration work center in SAP Solution Manager offers a central entry point and unified access to all SAP technology.
SAP Solution Manager as the name suggests is for managing the whole gamut of SAP and Non-SAP solutions in the IT Landscape of an organisation. It provides you the tool, content and gateway to create, operate, manage and monitor your solutions over time.
It provides a range of scenarios to support this. Extending from project management to Solution Monitoring to Service Desk to E-learning Management, it provides an efficient way to carry out a plethora of business tasks.
SAP Solution Manager is the successor to ASAP ValueSAP. SAP Solution Manager helps in implementing and managing complex system landscapes. Globally systems are getting distributed across geographies and business processes cover more than one system. In such complex scenarios, integrating technical and business requirements is important for the success of IT. SAP Solution Manager provides SAP customers with an efficient means of handling both the technical and business process side of solution implementation .
As part of SAP Solution Management Solutions, the customers receive best practices relating to:
- Global Strategy and Service Level Management
- Business Process Management
- Management of MySAP Technology
- Software Change Management
- Support Desk Management
SAP delivers this using support programs during implementation of the system solution. Some of the benefits of using SAP's Solution Manager are that it helps:
- Manages the technical risk associated with the implementation of the solution ensuring technical robustness
- Helps leverage users core competencies in implementing solutions
- Ensures solution works as intended with best practices built in.
see these links...
http://www.ne-sap-solution-manager.com/
http://www.saptechies.com/category/sap-solution-manager/
thanks
karthik
reward me if usefull

Process for applying for Solution Manager Key?

I have to install a NW2004s system in a AIX Machine.
I understand that i need a solution manager key for installation. We dont have solution Manager installed in our Landscape. But i came to know that i can request for a solution manager key from SAP
Please let me know the website, process for applying for Solution Manager key

Balaji,
This is interesting, SAP is pushing customers to have solution Manager installed with features like Solution Manager Key, Maintainance Optimizer etc. It will get difficult for customers who do not have solution Manager running on their site.
You will have to create support message under the component XX-SER-SMKEY and request for solution manager key, provide them all the details of your system.
Cheers,
Nisch

Solution Manager Key for Java AS

I'm new to SAP Netweaver so maybe this question has been answered before.
I need to install SAP Netweaver AS Java for development/QA purposes. I understand that I need also Solution manager key for installation so I installed another Solution Manager System.
When I enter to Solution Manager http://<server>:50000 I get "System Landscape Directory is not accessible. Only local system can be administered". What does it mean? I remember I chose to create local SLD.
I saw also in couple of threads the following:
Just go to transaction SMSY transaction of solman and locate the system for which you need to generate Solman Key and just right clilck on that system...You will find the option of Generating Solution Manager Key....
I don't have such an option when I enter to Solution Manager.
Any suggestions?
Thanks,
Haim Beyhan

Hi,
For Solman key generation refer the link below, which has the screen shots.
http://www.saptechies.com/step-by-step-procedure-to-generate-solution-manager-key-smsy-solution-manager-40/
Regards,
Ravi

Solution manager 7.0 and Non-SAP Sys. for managing whole IT infrastructure

Hello Gurus,
ive tried to search the allmighty google and SDN network for an answer how can we use the SolMan 7.0 for external applications (non-SAP).
What is our concern is that basically the Sol Man is described for using with whole SAP product environment. project management, chagne management, support, updating and etc.
My idea is:
Can we use SolMan for describing our whole IT projects and processes?
What i mean is if for example we have a payroll system which is running in non-SAP environment, can we describe the project for it? track the changes to it? document everything and etc. Its like to use the SolMan for whole IT infrastructure no matter if the application is SAP or non-SAP environment.
Best regards
Laurynas Prikockis
Edited by: Laurynas Prikockis on Aug 18, 2010 6:50 AM

Hello there,
SAP Solution Manager contains some functionality to work with non SAP products. For example, in transaction SMSY (system landscape) you can define non SAP products and therefore non SAP systems, although the functionatlity that you get thus is somewhat limited (no automatic refresh, no logon from RFC destination, etc).
The same applies for the project (SOLAR_PROJECT_ADMIN) part of Solution Manager. It is possible to assign a logical component for a non SAP product to a project, then in the project it is possible to describe the process and document it but it will not be possible to use the more SAP oriented functionality like links to IMG projects, etc.
Best regards,
Miguel Ariñ

Is it possible to connect a DEV System to more than one SAP Solution Manage

Hello,
My system DEV is already connected to a first SAP Solution Manager, I would also like to reconnect the same system so that it communicates and will be monitored by a second SolMan.
Is it possible to do so and the do the operation involve any risks ?
Thanks for your help
Regards
Ben

Hello,
This is possible in many scenarios. Often this is done to distribute load, for example on Solution Manager will do the Service Desk Function, one may do ChaRM, one may be doing Monitoring & Reporting, one may be doing Diagnostics.
In these cases a managed ssytem can be connected to many Solution Manager systems.
However as Mateus has pointed out, you cannot connect one managed to two Solution Managers and do SMD on both Solution
Manager systems, but you can have more than one Solution Manager doing Diagnostics.
Even in the case of EWA, while you can connect a Managed system to multiple Solution Manager systems and have then generate a report, one of the Solution Manager systems must be defined as the Master.
So the specific scenario may place some restrictions on connecting a managed system to more than one Solution Manager,
but for most instances it can be done.
Regards,
Paul

Solution Manager for Implementation project

Hello,
I want to know how we should use solution manager for an implementation project. I am aware about the ASAP methods and the transactions in solman system for each phase. I have starting trouble like how to and where to start with? My ECC systems are not yet installed. Still we can go ahead with Blueprint creation and definition of roadmaps etc. Currently, it is done on paper. If anybody has done an implementation project through solution manager, could you please give me some hints how to start ? I repeat I am aware of the transactions but dont know what to add there in solar01/02 when the process are not defined/system not installed. Please guide me.
Rajeev

Hi Rajeev,
You're correct; you can start building the Business Blueprint without SMSY having all the systems that are 'to-be'. As long as you enter logical components in the project landscape with the correct product versions, you can replace those with the actual components once they have been installed. The BPR needs those product versions in the blueprint when you load the relevant scenario's. Once loaded, you can start documenting the scenario's, place the processes and process steps not used out of scope or delete them entirely and define custom scenario's, processes and process steps.
When the Blueprint has been completed with relevant design documentation, the Configuration transaction can be used to document how you actually configure the systems and, of course, to configure them from Solution Manager. The system landscape officially has to be definitive at the end of the Blueprint phase, unless you won't be configuring the systems centrally from Solution Manager.
The Solution is actually not necessary for a clean implementation; the Project will eventually lead to the solution. Once the systems are all configured and documented in SSM, you create the Solution and upload the project documentation into it in the Solution Directory.
Let us know how you get on!
Kind regards,
Patrick

System/Ibase for DQ0 to be added in Solution Manager SM0-010

Similar Messages

Maybe you are looking for