Troubleshooting in Solman

Tags

,

Connection to SAP

An SAP Support Portal connection is required, to be able to send data to SAP. Usually this connection is created by the SAP Solution Manager Setup, with transaction SOLMAN_SETUP.

  • In transaction SM59, check if connection SAPOSS works; if not, adjust it as required. For more information, see SAP Note 33135: Guidelines for OSS1.
  • Check whether the distribution group is set to EWA; if not, adjust it as required. For more information, see SAP Note 766505: OSS1: Changes to RFC Connection SAPOSS.

For more information, see the following SAP Notes: SAP Note

Short Text

33135

Guidelines for OSS1

766505

OSS1: Changes to RFC Connection SAPOSS

182308

Incorrect Logon Data in R/3 Destination SAPOSS

Advertisements

Support Packages and Patch Implementation in Solman

Tags

, ,

The SAP Solution Manager has several software components which have their own release strategy. For further information, see the notes below

SAP Notes

Description

394616

Release strategy for SAP Solution Manager (ST)

539977

Release strategy for add-on ST-PI

569116

Release strategy for Solution Manager Service Tools (ST-SER)

608277

Installing and updating content for SAP Solution Manager

631042

Release strategy for Implementation Content (ST-ICO)

939897

SAP Solution Manager usage data

1109650

SAP Solution Manager 4.0 Extension Add-Ons

1169247

Upgrading SAP Solution Manager 7.0 to 7.0 EHP 1

1244225

SAP Solution Manager: SAP Notes for support packages

1260646

Changes to SAP Solution Manager customizing (IMG) as of EHP 1

1276022

SAP Solution Manager 7.0 EHP 1 installation

1276263

Roles: SAP Solution Manager 7.0 as of EHP 1

1276895

Additional information on upgrading to SAP Solution Manager 7.0 EHP 1

Software Change Management in Solman Part 2

Tags

,

SAP Reference IMG – Manual Update Configuration

You can update basic settings configuration and scenario-specific configuration using the SAP Reference IMG (transaction: SPRO).

Recommendation We recommend that you update your basic settings using the automated guided procedure, see section Guided Procedure (transaction SOLMAN_SETUP) – Automated Update Configuration.

Activate Release Notes Display release notes by choosing Release Notes. The system flags the release information with a blue information icon in front of the IMG activity.

Caution

See SAP Note 903274 for details of new IMG activities, changed IMG activities, and deleted IMG activities up to SP17. For later support packages, see the release notes and SAP Note 1260646. Using IMG – Manual Update Configuration Short Text

SAP Note

Changes to SAP Solution Manager 7.0 IMG after SP01

903274

Changes to SAP Solution Manager 7.0 IMG as of Enhancement Package 1

1260646

Ensure Basic Functions via SAP Note

In order to ensure that the basic functions of SAP Solution Manager are running properly, it is recommended to regularly check SAP note 1172948. This central note includes other required notes that are extended and renewed regularly. As soon as a new version of the note exists, you should implement it with the Notes Assistant (transaction SNOTE), in which you can automatically implement all notes included. If these notes contain manual actions, these are only described in the note. The note is valid for Solution Manager 7.0 EHP 1 (ST-400 Support Package 18 and 19). SAP Note 1334252 applies to ST-400 Support Package 20.

Ensure Basic Functions Component

Transaction

Detailed Description

Basic Functions

SNOTE

Check SAP Note regularly

1172948 (SP 18 and 19), 1334252 (SP 20)

Software Change Management in Solman Part 1

Tags

Software change management standardizes and automates software distribution, maintenance, and testing procedures for complex software landscapes and multiple software development platforms. These functions support your project teams, development teams, and application support teams. The goal of software change management is consistent, solution-wide change management, with specified maintenance procedures, global rollouts (including localizations), and open integration with third-party products.

Configuration after Support Package Update

After you have implemented a new support package or support package stack (SAP Enhancement Package), you need to check your configuration settings for new and updated configuration tasks. This is especially important for the basic settings. For instance, with every newly-shipped Web Dynpro application, its ICF service needs to be activated. You can update your basic settings configuration by either:

  • Re-running the Guided Procedure for Automatic Basic Configuration (transaction SOLMAN_SETUP, recommended) or
  • Checking for new or changed IMG activities in the SAP Reference IMG.

Guided Procedure – Automatic Update Configuration

You can use the guided procedure for the basic settings configuration to update your basic settings (transaction: SOLMAN_SETUP). To do this, check all activities in the Overview area in transaction SOLMAN_SETUP, and use your initially-created project to track update changes (see section Automatic Basic Settings Configuration). In the following, we give an overview of both procedures.

Prerequisites

  • Initially configure all basic settings using the guided procedure for the automatic basic settings configuration.
  • Update your authorizations, see SAP Note 1236420.

Using the Overview for Update Activities

  1. Call transaction SOLMAN_SETUP.
  2. In the Overview, the system displays a configuration table with all activities you need to perform after updating your system. If you select an entry in this table, the Open Activities column shows the steps you need to execute. In Basic Configuration, this may be the activity Activate BC Sets. The system updates this list automatically.
  3. In case of an update, you can specify here whether you have to re-execute activities that have already been executed. You can use the existing implementation project to track all information about the setup progress of your basic settings. Call transaction SOLAR02 and choose your project.

List of SAP Notes on Archiving and Deletion in Solman

Tags

SAP Notes for Additional/Background Information SAP Note

Short Text

544295

Basis message: Deletion flag status

546685

Archiving in Solution Manager (Operation)

566225

Report to delete the basis notifications with deletion flag

638785

SAP Solution Manager – reduce data volumes

845433

Deleting a service process with support message

976695

New features for RDSMOPDELETESOLUTIONS in SP08

1006094

cProjects problems with archiving/resources/deletion

1077447

Solution Manager: TEST_DSMOPSERSESSN_DELETE

1091497

Deleting in archive: RDARCH_ARCHIVE_DELETE_SOLMAN

1092503

Archiving reporting documents in SAP Solution Manager

Alternative Storage & Deletion Strategies in Solman

Tags

Although generic archiving is not supported by most scenarios in SAP Solution Manager, there are several functions to reduce the amount of data in the database. A customer can save the objects using other methods (put objects in transport requests using migration functions, store reports on separate file server, use SAP content server for knowledge warehouse documents, keep backup of whole system before data deletion).

Solutions. Solutions can be deleted from SAP Solution Manager using the functionality in transaction DSWP, or by directly executing report RDSMOPDELETESOLUTIONS. When deleting a solution, all objects produced within that solution (service sessions, reports etc.) will be deleted – if this is possible. If CRM transactions such as service tickets, which carry an attribute for the solution, have been created, deletion of the solution might not be possible (as it is not possible to delete the related CRM transactions).

Service reports in solutions. SAP EarlyWatch Alert and service level reports could be stored on a separate file server. They can be deleted from SAP Solution Manager using report RDSMOPREDUCEDATA.

Projects SAP Solution Manager projects can be stored in a transport using transaction SOLAR_PROJECT_ADMIN. However, this function will only store the business process structure and all related documents; it will not save referenced data, such as CRM transactions or test workbench items. Solution Manager projects can also be deleted using transaction SOLAR_PROJECT_ADMIN.

Archiving Projects Topic

Link

SAP Solution Manager Help

http://help.sap.com → SAP Solution Manager

cProjects Archiving

http://help.sap.com → SAP CProjects Suite → Editing Project Structures → Collaboration Projects → Basic Functions → Archiving

Archiving Test Management Topic

Link

Archiving Logs (SAP Library – eCATT: Extended Computer Aided Test Tool, BC-TWB-TST-ECA)

http://help.sap.com → SAP NetWeaver → SAP NetWeaver 7.0 including Enhancement Package 1 → <language> → SAP Library → SAP NetWeaver Library → SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability → Test → eCATT: Extended Computer Aided Test Tool (BC-TWB-TST-ECA) → Logs → Archiving Logs

Business partners Obsolete business partners can be deleted using transaction BUPA_DEL, but only if they have not been used in a service transaction.

Data extracted to BI If data from SAP Solution Manager has been extracted for Business Intelligence (reporting on EWA raw data, CPH monitoring data, SMSY data, root cause analysis data, and Business Process Monitoring data), the BI aggregation and deletion mechanisms can be used to reduce the amount of data in the BI database.

Archiving & Data Deletion in SAP Solution Manager

Tags

,

Achiving functionality in core SAP Solution Manager

There is only limited archiving functionality in SAP Solution Manager 7.0. In particular, the following objects cannot be archived using default SAP archiving mechanisms:

  • Solution Manager projects
  • Solution landscapes
  • CRM transactions, such as service tickets, change requests, change documents and issues.
  • Monitoring data in central performance history database
  • Test packages/test cases These objects do not usually contain a lot of data.

Documents in Solution Manager projects

The only function which might need a lot of database space is document management in the implementation scenario. Depending on the number, type and frequency of documents checked in, several hundred MBs per week and project might be needed – because usually every version of a document is kept. Those documents (or old versions) in Solution Manager projects can be archived using the report SOLMAN_DOCU_VERSION_ARCHIVE. This report moves the document contents (files) from the built-in knowledge warehouse (KW) layer, to another repository, e.g. an archive. However, the document attributes needed to administer the documents will be kept in SAP Solution Manager. The report SOLMAN_DOCU_VERSION_DEL deletes interim versions of any documents. It deletes all versions in all accessible repositories – particularly those documents which have already been archived using the report SOLMAN_DOCU_VERSION_ARCHIVE, if they can still be deleted.

Service reports in solutions

Service sessions such as EarlyWatch Alert reports, Service Level reports, and the documents attached to them, can be archived using the ArchiveLink interface. SAP Note 546685 “Archiving in Solution Manager (Operation)” explains the functionality and setup in detail. SAP Note 1092503 describes how to automate the archiving by a job. The following “Solution Reporting” documents can be archived:

  • Service Reporting
  • System Availability Reporting
  • System Administration Reporting
  • Change Management Reporting
  • Service Desk Reporting
  • Issue und Top Issue Reporting
  • Expert-on-Demand Reporting
  • BI Extraction

CRM-based transactions (incidents, change requests, etc.)

There is a generic way to archive CRM-based transactions (e.g. service ticket, change document), but it is not supported in SAP Solution Manager, because many functions, such as test workbench and implementation projects, have links to service tickets or change documents. Archiving these CRM-based transactions would break the links to them, and might cause inconsistencies. For details, see SAP Note 845433. Documents on the generic CRM tabs (transaction CRMD_ORDER) cannot be archived.

Notes for Archiving SAP Note

Short Text

546685

Archiving in Solution Manager (Operation)

845433

Deleting a service process with support message

High Availability in Solman

Tags

There are no general High Availability (HA) requirements for the SAP Solution Manager. High-availability applications allow you to maximize downtime security and minimize downtimes. You can achieve this by controlling the growth of redundant data and implementing redundant systems control logic. At SAP, high availability is always focused on business applications and their related components. SAP relies on the high availability applications of partner products for components which are mandatory for implementing the infrastructure, such as the operating system, database, and hardware. Collaborative business can give you a competitive advantage. This means integrating existing heterogeneous system landscapes to include business partners, customers, and suppliers. You may also have requirements of your own, depending on the availability requirements of the implemented IT management processes.

Further Documentation Tool

Link

Service Marketplace – High Availability

http://service.sap.com/ha

Help Portal

http://help.sap.com/ → SAP NetWeaver → SAP NetWeaver 7.0 including Enhancement Package 1 → <language> → SAP Library → SAP NetWeaver Library → Administrator’s Guide → Technical Operations for SAP NetWeaver → General Administration Tasks → High Availability → SAP High Availability documentation

SolMan – Agent Administration

Tags

, ,

Agent Administration

Agent Administration manages diagnostics agents, which are installed on all managed systems, centrally. With this administration interface you can do the following:

  • Display and change the connection status of all agents
  • Change the connection type of agents
  • Assign a dedicated user and password to all agents
  • Display or download log files of all agents

Prerequisites

The administrator has configured diagnostics agents in the monitored systems, and registered them with the monitoring system. For more information, see the diagnostics agent setup guide on SAP Service Marketplace at http://service.sap.com/instguides Installation & Upgrade Guides SAP Components SAP Solution Manager <current release> .

You have started the Agent Administration.

Features

On the Agents tab page, you can do the following:

  • Display all connected agents and their respective statuses when you set up a new managed system and want to verify that an agent is correctly assigned to the managed system
  • Restart agents that are offline
  • Switch the maintenance mode on and off, when new managed systems are being set up and the agents have to be temporarily stopped
  • Start the Agent Candidate Management to connect diagnostics agents to SAP Solution Manager.

On the Agent Connectivity tab page, you can change the connection type of agents, for example in the following cases:

  • When agents do not connect correctly to the SAP Solution Manager system
  • When you want to switch from insecure to secure communication

On the Application Viewer tab page, you can check if all agelets available on the server are deployed on the selected diagnostics agent. You can check if the version deployed on the diagnostics agent matches the server version.

On the Application Management tab page, you can upload agelets to diagnostics agents and remove them from diagnostics agents.

On the Applications Configuration tab page, you can change the configuration of each agelet and send the modifications to the diagnostics agents.

On the Agent Credentials tab page, you can do the following:

  • Assign a single dedicated user to all agents and thus minimize the administration effort
  • Assign a new password to all agents simultaneously when the SAP Solution Manager password changes

On the Agent Log Viewer tab page, you can do the following:

  • Display all log files to identify connection problems
  • Download all log files when you are required to submit a log file to SAP support

SM50 Long process

Tags

, ,

Question :

If a tcode is taking too long time to finish and I wand to end the work process in sm50 how to find which work process is currently executing that tcode?

Answer :

In SM50, mostly you can only see the ABAP program name and the respective table which is being accessed,insert,update,select,etc. To find which tcode, you may use tcode SM04 to make comparison for running transaction on specific user showing in SM50. There might be a case that one user run more than one transaction, in this case you need to find the related tcode with the running program using for example SE38 and select where used list of transaction.