Solution Manager - Overview

Building a Monitoring Infrastructure with NagiosSAP Solution Manager is a tool, which assists in application management as per ITIL (IT Infrastructure Library) environment. The tool supports the entire lifecycle of solution mainly having six phases – Requirements, Design, Build, Deploy, Operate & Optimize as per ITIL standard.
It runs in a separate central system to which all the other SAP systems are connected. These other systems are called as Satellite Systems.

Download -


Features of SAP Solution Manager:

· Solution Manager helps in all types of project management like Implementation, Upgrade, Maintenance, Rollout etc. by providing the project specific template.
· It is in line with SAP’s AcceleratedSAP. And provide Roadmaps for the different types of projects.
· It has Business Process Repository, which talks about SAP’s best practice of running the business.
· It has eLearning feature, which offers the training along with feedback over web.
· It has test management feature, which offers the central storage repository for storing the automated eCATT scripts along with manual scripts. The results of testing are centrally stored and always available.
· It has its own standard Helpdesk feature, which is both SAPGUI based and web based.
· The Helpdesk feature is totally linked with Change Request Management, which helps in transport for changes required in production issues.
· It has Solution Monitoring as well as Diagnostic feature, which helps in Operation Phase of project.
· Solution Manager has lots of inbuilt reports, which server the different areas of it.
· It is linked with SAP Service Market Place.
· It can generate Installation/Upgrade key.
· It has its own Knowledge Warehouse for central documentation storage.
· It can integrate with ARIS, a detailed graphical business process modeling tool
· It can also integrate with Mercury tools like QTP for testing in web based environment.

AcceleratedSAP (ASAP) Roadmaps:
AcceleratedSAP Roadmaps are the proven procedures for Project Management. Roadmaps provide a methodology for the executing successful SAP projects of any kind like Implementation, Upgrade & Global Rollout. The methodology has a defined framework for different kinds of projects and has lots of tools, services etc. Special Accelerators are available in Roadmap structure, which help in following the best offered practices of project management and hence accelerates the speed of project. Accelerators are in terms of templates, examples, documentation, links etc.

Transaction Codes involved in Roadmaps:
· For launching Roadmap: RMMAIN
· For creating Custom Roadmaps(without structure change): RMDEF
Using this option, one can use copy of SAP’s roadmaps with custom contents. No changes can be made to the structure of the roadmap. Only header data like name & attributes (flavors, roles & subject areas) can be defined.
· For creating Custom Roadmaps(with structure change &; entry screen): RMAUTH
Using this option, one can define his own structure of roadmap or make changes to copied structure of standard roadmap. The documentation created or changed in terms of accelerators or so is stored in SAP NetWeaver Knowledge Warehouse.
Though the feature is given to create a new or modify copied standard roadmaps, one should be careful in using the custom functionality here. As SAP releases new roadmap, it may become difficult to adjust those parameters in custom roadmaps. So it is recommended to strictly keep track of all changes in standard roadmap and then change the custom roadmap accordingly.

Scenario: Document being distributed – Changes are not possible (Document cannot be edited/changed)

Temporary solution

Go to smq2 -> choose (double click) on required queue -> choose (double click) again -> execute the required entry

 

 Permanent solution

Go to transaction SMQR -> select registration -> add queue name as CSA_ORDER_*

Implement Solman MSG : Send To SAP

Issue is to send message to SAP through Solman - service desk. When you change the stsatus to SEND TO  SAP the message should go to SAP service market place.
Well, to do this I assuming that, the system set is already done and customer is already registered in service market place.



I have tried to list down all possible steps required to achieve this

Deactivate Standard badi implementation AI_SDK_SP_RFC

                                                                                                           Create your Z implementation and Implement Method Change Destination

BASIS Activities

1. Create RFC SM_SP_ and maintain below mentioned details in RFC.


a. Technical settings
    Target s1ystem : OSS
    Msg. Server : /H//S/sapdp99/H/194.39.131.34/S/sapdp99/H/oss001
    Group : 1_PUBLIC
b. Logon & Security
    Username :
    Password : *****

2. Maintain Customer no. in transaction AISUSER

3. Apply note 0001165980-Connection to SAP/RFC using key user's customer no/S-user

Double click on the preceding document.

Enter the message, save and exit and go back to service message menu.

Change the status to ‘send to SAP’

Click on action button

Observe the message

Message created in Service market place.

Automatic Sold-to-Party determination

Steps and procedure to determine sold-to-party automatically in CRM / Solution Manager.
Create BP role as Sold-to-Party.

Use T-code - BP

Generate I base

Use T code - solution_manager

Assign SP to the client

Use Tcode - IB52

Automatic creation of BP (business partner) at PPOMA_CRM

Automatic creation of BP (business partner) at PPOMA_CRM can happen only when Partner / Organization integration is activated in CRM or Solution manager but constrain is activation has to be done before organization structure is created. So, any organization structure created before caring out activity below will not be affected.
Go to the following IMG path: Customer Relationship Management -> Master Data -> Business Partner -> Integration Business Partner-Organization Management -> Set Up Integration with Organizational Management.


Find the entries starting with HRALX. You should have those entries:
• HRLAX - HRAC with the value ‘X', if you don't create this entry in the table and Save.
               Group              Sem.abbr.           Value abbr.              Discription
               HRALX           HRAC                   X                         Activate HR Integration


• HRLAX-OBPON with the value ‘ON', if you don't create this entry in the table and Save.

Deleting old Support Desk messages in SAP-CRM.

Unfortunately it is not that easy to delete old Support Desk messages.As you know every message consists of two messages in reality. The CRM message has to be archived using transaction SARA. The archiving object
is CRM_SERORD. The basis messages cannot be archived because there is no archiving object existing for them. What you can do is to set the deletion flag (status I0076) for every message you do not need any more.
Afterwards you can use report Z_DELETE_BASIC_NOTIFICATIONS provided in the attached note: #566225 Report to delete the basis notifications with deletion flag for CRM test messages alternatively the report CRM_ORDER_DELETE can be used with the following restriction.
Deleting of CRM message with report "crm_order_delete" works only if the item of the CRM message (with exists in the background without being displayed) is not released. But if you are using transactiontype SLF1
for the CRM message the status 'Released' is set for the item as soon as you set the status 'In process' for the message. As 'Completed' is a follow-up status of status 'In process' you cannot delete the CRM messages  anymore using the report.
To set the deletion flag for the basic notification you have to use transaction DNOTIFWL. Here you have to set the status 'complete notificattion' so that it is set to completed. Afterwards you can set the status 'Mark for
deletion' at the same place.