SAP Note

Header Data
Symptom
This note provides information about release restrictions for SAP Solution Manag
er 7.1
Other Terms
SAP Solution Manager
Reason and Prerequisites
When SAP Solution Manager 7.1 was released, restrictions still applied to the pr
oductive use of
certain functions (SAP wishes to inform customers of these restrictions here).
Solution
Open Limitation(s)
SV-SMG-IMP
Release with restrictions
Limitations in Business Process Blueprinting
Business process blueprinting: The name of the file downloaded via project docum
entation in BPB is
garbled. Undo of Logical Component assignment to the process step not reflected.
The name change
(rename)of an entity( eg. Scenario, process ,etc)does not reflect. The process e
ditor of the removed
scenario is not getting closed automatically while performing save operation. In
description section
of overview tab process editor, indentation and ordered list/ unordered list beh
aves in an
unexpected manner. Shortcuts (Supported in SOLAR01) are not displayed and manage
d in BPB For details
see SAP Note 1588588.
Fixed with SP05
( Changed at 12.06.2012 )
Fixed Limitation(s)
SV-SMG
Release with restrictions
Limitations in the User Interface
With SAP Solution Manager 7.1 transaction codes SOLUTION_MANAGER, DSWP, and DSMO
P will be
deactivated. With SP01 not all functions, that had been available via these obso
lete transaction
codes, will already be available in an alternative place (e.g. a work center). O
nly workarounds will
be available to get access to these functions. Affected functions are: Navigatio
n to Session
Overview (Goto -> Sessions -> Overview, Navigation??to SDCCN (Goto -> Sessions -
> SDCCN Data),
Overview of failed RFC connections to SAP (Goto -> RFC Connection Error), Servic
e Reporting
(Operations -> Solution Reporting -> Services -> Service Reporting), Overview of
Service Session
Access Keys validity (Operations -> Service Plan -> Certificates), Best Practice
documents
(Operations Setup -> Best??Practices)
This restriction is no longer valid.
Fixed with SP05
( Changed at 06.06.2012 )
No release
Limitations for Dashboards
No central navigation in dashboard framework available. There is no content yet
for the dashboards,
i.e. no apps are available to display data in the dashboard.
This restriction is no longer valid.
Correction delivered with Support Package Stack 02
( Changed at 06.06.2011 )
??1480419 - Release Restrictions for SAP Solution Manager 7.1
Version ?46 ??Validity: 2014.02.03 - active ?Language ?English (Master)
Released On 2011.03.09 22:49:46
Release Status Released for Customer
Component SV-SMG SAP Solution Manager
Priority Recommendations / Additional Info
Category Consulting
SV-SMG-CM
Release with restrictions
Limitations in Change Control Management
The field "Current Processor" in the CRM transactions is not configurable to the
need the different
customers have. The migration recommendation of the CRM transactions from CRM 5.
0 to CRM??7.0 will
be available as documentation. No guided procedure is available. There is no val
ue help of system
users in a managed system available when you want to assign a respective user to
a transport request
from with a change document in Change Request Management. Popup for Critical Obj
ects Approval
Currently the popup for critical object approval is displayed in SAP GUI , becau
se the Web UI
Framework popup was not ready
This restriction is no longer valid.
Fixed with SP05
( Changed at 06.06.2012 )
SV-SMG-IMP
Release with restrictions
Limitations in projects
Compare and adjust: Comparison of top nodes (e.g. Scenarios )are not covered. Ro
ll-in of Business
Process changes from successor cannot be completed. Reverse Business Process Doc
umentation: The
upload of external analysis content is not available. Integration into IT Servic
e Management:
Integration is only available for Incicents. Changes are not covered.
This restriction is no longer valid.
Fix delivered with SP05
( Changed at 06.06.2012 )
SV-SMG-INS
Release with restrictions
Limitations in the initial set-up of SAP Solution Manager 7.1
Customizing an SMD Agent application is not supported. It is not possible to cre
ate customer
specific guided procedure in SP1, no Maintenance UI for guided procedures is pro
vided with support
for: Manual Activities, Automatic Activities, Help Texts. For certain managed sy
stem setup scenarios
(e.g. managed system setup for a system of type BOBJ) it is required to configur
e variables for SMD
agent agelets (acess credentials for the managed system). Due to amissing UI in
the setup screens
this has to be done separatelyin the UI of the SMD Application configuration set
up and the variables
have to be defined with the expected names manually by the customer. SolMan Admi
nistration Work
Center: SolMan Admin Woc doesnt support read-only mode fully, Landscape browser na
vigation not end-
user friendly enough, Notification only possible at TS level. SolMan Configurati
on Work Center: The
SLD connection information needs to be maintained multiple times in the system p
reparation phase of
SolMan_Setup. The user management in SolMan_Setup does not allow central update
of authorizations of
users in managed systems. The setup framework doesnt provide a authoring UI to cre
ate customer
specific guided procedures. The guided procedure for the configuration of Incide
nt Management is
missing.
This restriction is no longer valid.
Fixed with SP05
( Changed at 06.06.2012 )
SV-SMG-LDB
Release with restrictions
Content sync with multiple SLDs
The content sync allows synchronization and propagation of SLD data into LMDB. T
he number of SLDs
directly connected to LMDB is limited to one, acting as a central SLD in front o
f Solution Manager.
Customer can install an additional SLD for SAP Solution Manager that serves as a
proxy to enable
multiple SLD's.
This restriction is no longer valid.
Correction delivered in SP01
( Changed at 07.02.2011 )
Hostname support
Multiple network domains with conflicting/identical host names cannot be support
ed.
This restriction is no longer valid.
Fixed with SP05
( Changed at 06.06.2012 )
Technical System Editor
The Technical System Editor of LMDB allows creation, modification and display of
technical systems
and according attributes. Limitations for Creation: No system type can be create
d manually. Only
landscape data coming via SLD data suppliers can be supported with the Technical
System Editor.
Limitations for Modification: For the system types above, modification capabilit
ies are limited to
header data, custom attributes, product instances and the diagnostics relevant f
lag. E.g. the change
of a host assignment is not possible. Limitations for Display : For ABAP and Jav
a systems, all
attributes can be displayed. For system types Unspecific Cluster System, Unspeci
fic Standalone
System , SBOP System, MS .Net System, MDM, Database System, AS ABAP System, AS J
ava System, IBM
WebSphere, TREX, liveCache, WebDispatcher, Introscope EM, Introscope MoM and Dia
gnostics Agent
display is limited to header data, custom attributes, product instances and the
diagnostics relevant
flag E.g. the display of technical instances or hosts is not yet possible. Syste
m type Apache Tomcat
can neither be displayed, nor modified, nor manually created.
This restriction is no longer valid.
Correction delivered in SP01
( Changed at 07.02.2011 )
Limitations in Landscape Management Database
Migration of product assignment from SMSY Product System to LMDB Technical Syste
m not possible.
HTTPS configuration for SLD to LMDB content synchronisation not possible Limited
usability of
Landscape Browser, like direct maintenance of host data or 3rd level system attr
ibutes of system
type Unspecific. Limited synchronization from LMDB to SMSY (example: system type
for BOE 4.0).
Performance of LMDB in some areas insufficient. Supportability of LMDB limited (
example: change log
housekeeping).
This restriction is no longer valid.
Solved with SP04
( Changed at 11.11.2011 )
SV-SMG-LIC
Release with restrictions
Distribution of maintenance certificates for java based systems
For java based systems, it is not possible to distribute the maintenance certifi
cate automatically.
Instead the certificate needs to be distributed manually (same behavior as in pr
edecessor release).
This restriction is no longer valid.
Correction delivered in SP01
( Changed at 07.02.2011 )
SV-SMG-MON
Release with restrictions
Monitoring & Alerting
System Monitoring and Alerting: Deactivated metric types in configuration explor
er are still visible
in Directory Browser Deactivated propagation event types for categories in confi
guration explorer
are still visible in Directory Browser Connection Monitoring and Alerting: 3rd p
arty connector
configuration for connection monitoring is not transferred to Directory Notifica
tion configuration
for connection monitoring is not transferred to Directory Self Monitoring and Al
erting: Additional
service??wdc_alr_log_powl_loghdl needs to be setup during configuration Step Scope
definition is
not longer necessary for Self Monitoring setup
This restriction is no longer valid.
Correction delivered with SP01
( Changed at 11.02.2011 )
Job Management Work Center and Business Process Operations Work Center - Alert I
nbox
SAP delivers a redesigned Business Process Alert Inbox with Solution Manager rel
ease 7.1, however
this new Alert Inbox is not set as default inbox. In the meantime, customers may
access the
redesigned Alert Inbox by manually adding an entry to the respective work center
s related Links
menus.
This restriction is no longer valid.
Correction shipped with SP01
( Changed at 11.02.2011 )
Limitations in Alerting and Monitoring
System Monitoring and Alerting: Conflict resolution of SAP templates between dif
ferent versions is
not possible. It is not possible to define exclude criteria for metric parameter
s inside a metric
group. Reconfiguration of managed objects from System Monitoring and Alert Inbox
is not possible.
Two-step activation of monitoring templates is missing in setup ("Expert??mode")
. Metric thresholds
cannot be changed for a work mode. Mass change of template assignment for manage
d objects of the
same type is not possible. Definition of third party data providers is not possi
ble. Customer events
cannot be created in the Configuration Explorer. Filtering on rating is not poss
ible in alert
details. Handling of atomic exceptions is not possible via MAI sufficiently. Ale
rt Inbox is not
prepared for atomic exceptions. SysMon application doesnt support all necessary sy
stem types.
Connection Monitoring and Alerting: RFC destination collector not working when t
wo systems with
identical short, but different long SIDs are relevant for collection. Connection
Monitoring does not
react on current work mode. Self Monitoring and Alerting: Deactivation of a self
monitoring scenario
is not possible in the setup Self Monitoring does not react on current work mode
. End-User
Experience Monitoring: The current implementation of EEM is not connected to the
generic Work Mode
Management, therefore EEM is running in a constant work mode. The parameterizati
on of EEM Scripts
based on recorded and replayed Scenario executions is not working. Flash-based l
ong term reporting
UI is currently not covering all features of the web template-based reporting UI
. PI Monitoring:
Data collector for PI Message based Alerting doesnt work sufficiently. Alert Inbox
is not prepared
for message based alerting. No support of Central User-defined Search for archiv
ed PI messages. No
capability to exclude Channels from Alerting within PI Channel Monitor. No fallb
ack solution in case
SSO is not configured for management functions in local PI Monitors. BI Monitori
ng: Only part of
configured metrics are showing up correctly rated in the monitoring applications
. Alerting is based
on last run (BO jobs) or worst case of multiple runs (Process Chains). Single in
stances are not
distinguished. Quality / Correctness of single metrics not verified. Flexible ti
me schedule for
metric collection not verified. Enabling for Work Mode Management not available.
Technical Reporting
and Management Reporting: No adoption of Work Mode Management data in Metric Vie
wer. Dashboard FWK
has missing navigation and security capabilities and an Insufficient app develop
ment environment. No
configuration apps for Alert Management Reporting dashboard. Technical Administr
ation: Central tool
access is not based on URL Framework and needs to become enhanceable. Performanc
e of Work Mode
Management API is insufficient. API needs to be??reworked. MDM Cockpit needs to
be integrated in
central tool access. It is not possible to plan work modes directly in the SAP I
T Calendar. The
"Product System" hierarchy level needs to be removed from WMM. Task inbox is not
supporting
Techsystems / tech Instances and POWL design. Central Notification Management ap
plication
performance is bad if more than 1000 recipients are added to the Global Recipien
t Pool. CSA has to
support also non-ABAP system types. Keyboard navigation inside IT Calendar is no
t possible. Creation
of work modes for other system types than ABAP, Java, MDM is not possible. Root-
cause Analysis: Bad
performance in Application Change Reporting due to LMDB accesses. Support for
MS .Net /IIS/Sharepoint not completely incorporated. Support for Trex not comple
ted (Software
component at instance level instead of TS). Diagnostic Infrastructure: ST-PI SP0
4 is missing a lot
of permissions which impacts : Extractors, PI Mon, etc. (permissions issues have
been reported some
time before close, but not integrated correctly). Handling of business partner i
s not integrated.
Outside discovery runs multiple time per pHost. Diagnostics Agent: possible inst
ability in clustered
SolMan engine installation (with several instances).
This restriction is no longer valid.
Fixed with SP05
( Changed at 06.06.2012 )
SV-SMG-MON-EEM
Release with restrictions
Limitations in end-user-experience monitoring
The current implementation of EEM??is not connected to the generic Work Mode Man
agement, therefore
EEM is running in a constant workmode. Flash-based long term reporting UI is cur
rently not covering
all features of the webtemplate-based reporting UI. The parameterization of EEM
Scripts based on
recorded and replayed Scenario executions is not working.
This restriction is no longer valid.
Fixed with SP05
( Changed at 06.06.2012 )
SV-SMG-SER
Release with restrictions
Authorizations for Service Sessions
Authorization checks for service delivery do not perform as required. There are
security loopholes,
such as if you have no access in WC, you still can open a restricted service in
DSWP.
This restriction is no longer valid.
Correction is delivered with SP01
( Changed at 09.06.2011 )
Limitations in SAP Engagement and Service Delivery
Limitation in Guided Self Services: Popups not possible. Background: Such popups
are currently used
to (a) warn the user and (b) to provide detailed information (for example: by cl
icking on a table-
entry, we can get additional background information) . The web dynpro user inter
face for delivering
services is not integrated. Instead the SAP Gui based transaction DSA is used. U
sing the guided
procedure to deliver self guided services it is only possible to enter 40 charac
ters. However the
underlying infrastructure (DSA) supports 120 characters. Text tabs cannot be use
d as Guided
Procedure content. Only tables can be used. Currently it is not possible to perf
orm a remote logon
via SAP GUI out of the web dynpro appllication of the Guided Self Service. As a
workaround the
manual activation of the data collection is possible. Issues in Follow Up step c
an only be
maintained after the report service report is created. Works for the initial poi
nt in time, when
check tree/check tables are created the first time. Any dynamic is missing, when
visibility depends
on activity within the already created guided procedure. Background: Changing th
e visibility of
checks or a table within a check dynamically is used to react to tailor-made a c
heck layout
depending on all the information that became available. Example: if a system PRD
is chosen to??be
analyzed, it might depend on the database used whether a table with detailed infor
mation can be
displayed or not. Additional Limitation: The service session is displayed as a h
ierarchy. With this
the customer is not able to filter or sort the list. Therefore an alternative UI
has to be provided
which displays the service session as a flat list. The benefit case is currently
only editable
during top issue creation in??360 review session but it should be editable at an
y point in time.
This restriction is no longer valid.
Solved with SP03
( Changed at 17.11.2011 )
SV-SMG-SR
Release with restrictions
Limitations in Maintenance Management
System recommendations is limited to a single system view. It shows relevant not
es and patches only
for the selected system. A check whether notes and patches are relevant for more
than one system or
a full solution is not possible.
This restriction is no longer valid.
Solved with SP03
( Changed at 17.11.2011 )
SV-SMG-SUP
Release with restrictions
Incident Management - Automatic Forwarding of Priority Very High messages to SAP
(VAR
Function)
With Solution Manager release 7.1, SAP delivers several new CRM transaction type
s for use in the CRM
Web Client. These new CRM transaction types do not fully support all functions i
ntended for Service
Provider (VAR) Incident Management scenarios. The Incident Management transactio
n types which were
previously delivered by SAP prior to release 7.1 are not subject to this restric
tion and change.
They will continue to function as before.
This restriction is no longer valid.
Correction delivered in SP01
( Changed at 07.02.2011 )
Validity
Support Packages & Patches
References
This document refers to:
SAP Notes
This document is referenced by:
SAP Notes (1)
Software Component From Rel. To Rel. And Subsequent
ST
710
710
Support Package Patches
Software Component Support Package Patch Level
SAP BUSINESS ONE 2005 A SP01
SP001
000000
SAP XPD 200
SP011
000000
VIRAE 520_640
SP002
000000
VIRAE 520_700
SP002
000000
VIRCC 520_640
SP001
000000
SP002
000000
VIRCC 520_700
SP001
000000
SP002
000000
VIRFF 520_640
SP001
000000
VIRFF 520_700
SP001
000000
VIRRE 520_640
SP002
000000
VIRRE 520_700
SP002
000000
1509091 ?QGM: General note for Quality Gate Management 7.1
1509091 ?QGM: General note for Quality Gate Management 7.1