best practice-system monitoring

System Monitoring for

SAP APO (3.x) / mySAP SCM (4.x, 5.0) Best Practice for Solution Management

Version Date: December 2005. Valid for SAP APO 3.0A, 3.1 and mySAP SCM 4.0, 4.1, 5.0

The most up-to-date version of this Best Practice document can always be obtained through the SAP Solution Manager

Contents

Applicability, Goals, and Requirements ....................................................................................2 Best Practice Procedure and Verification .................................................................................3

Alert Monitor .................................................................................................................3 Function of the CCMS Agent ........................................................................................4

Procedure ...........................................................................................................................4 Monitoring SAP liveCache, the SAP Optimizer, and qRFC Inbound and Outbound Queues .........................................................................................................................4 Set Up System Monitoring in Solution Manager 3.1 and 3.2......................................10 Central Auto Reactions...............................................................................................28 SCM Basis System.....................................................................................................36 Solution Architecture and Core Business Processes for mySAP SCM ......................38

Further Information.................................................................................................................39

Best Practice: System Monitoring for SAP APO(3.x) / mySAP SCM (4.x, 5.0)

© 2005 SAP AG

2

Applicability, Goals, and Requirements Read the following information to ensure that this Best Practice document is the right one for you.

Goal Use this document as a foundation for setting up monitoring procedures for mySAP SCM systems. The recommended technique is to define an explicit monitoring concept for central system monitoring using the Computer Center Management System (CCMS) in conjunction with the SAP Solution Manager.

This form of business-process-oriented system monitoring, starting with individual business processes and monitoring all operations-relevant system components, is known an inside-out approach.

This document is intended to assist you in setting up monitors that focus on the availability of various components you may have within your mySAP SCM solution. There are several components whose monitoring processes will be concentrated on within this documentation. Each component is described separately.

Skills Your Team Needs You need:

1. A monitoring team who all possess basic mySAP Technology skills

2. An SAP-certified technical consultant with a basic understanding of performance analysis

3. CCMS agents running on all computers with software which does not use SAP Basis

4. A monitoring concept should be available should a big solution infrastructure exist.

System Requirements You need:

1. An SAP Solution Manager installation of version 2.2 or higher. SAP Solution Manager Version 3.1 is recommended. For details on the Release Strategy for the SAP Solution Manager see SAP Notes 453034 and 402806.

2. An SAP APO Version of >=3.0 with SAP liveCache 7.2 and higher.

3. The latest ST-PI should be installed on all satellite systems. CCMS agents should run on all computers with software which do not use SAP basis.

4. SAP Note 455356 must be implemented.

Duration and Timing Apply the methods described in this Best Practice document before the start of production; i.e., before going live with the mySAP.com solution concerned.

You will need around one week to set up your monitoring concept and implement it for the first software component. You will need an additional two or three days for each subsequent component, depending on the size of the respective component.

Before reading this Best Practice document, you should already have read and applied the methods described within the Central System Monitoring for mySAP.com Best Practice document that provides information on how to enable and set up system monitoring for mySAP SCM Monitoring with the SAP Solution Manager.


© 2005 SAP AG

3

Best Practice Procedure and Verification This Best Practice document informs you about how to use the Alert Monitor in transaction RZ20 to map and monitor one or more mySAP systems in the SAP Solution Manager. This document focuses on monitoring mySAP APO systems (referred to as APO systems from now on). APO systems are distinguished from classic mySAP R/3 systems (referred to as R/3 systems from now on) by the presence of SAP liveCache, the SAP optimizer, and the qRFC interface. The individual sections of this document concentrate on setting up the Alert Monitor for liveCache, the optimizer, and the qRFC interface. For general information on setting up system monitoring using transaction DSWP in the Solution Manager, see the Central System Monitoring for mySAP.com Best Practice document as this document provides only brief details on this.

Glossary Component/Satellite system: A component system is the SAP system that is to be monitored; in this document, the component system is an SAP APO system.

SAP Solution Manager system: The SAP Solution Manager is a small SAP R/3 system. We recommend that you run it on a separate, dedicated server in order to:

• Ensure service delivery and monitoring functionality • Prevent possible upgrade conflicts

• Prevent the SAP Solution Manager system load from affecting production

• Simplify routine maintenance of the SAP server infrastructure

• Control access to the SAP Solution Manager

Alert Monitor Background The Alert Monitor is a tool for globally monitoring the most important components, processes, and performance within the system infrastructure of one or more mySAP systems. You can also connect and monitor external non-SAP systems. The Alert Monitor uses a variety of methods to inform the administrator about any problems that have occurred. The source of the problem is always highlighted in a different color. The advantage of the Alert Monitor is that it transfers information to the system administrator without the administrator needing to request this information explicitly from the system concerned and without even needing to log on to this system. SAP has developed an Alert Monitor that can use selected parameters and limit values to analyze the different areas of the system infrastructure by itself and trigger any warnings. Alert Monitors are supplied with every mySAP software product. These Alert Monitors cover all areas of system, database, and operating system administration significant for software component operation.


© 2005 SAP AG

4

Function of the CCMS Agent Non-SAP R/3-based components can be monitored using CCMS agent technology. This technology enables you to monitor components remotely from any SAP R/3-based system (in this Best Practice document, this is the SAP Solution Manager system). The SAPCCMSR agent uses RFC to communicate with the SAP Solution Manager system. As an RFC client, the agent automatically sends the collected data to the SAP Solution Manager system. The agent monitors components on which there is no active SAP instance, such as SAP liveCache, the SAP optimizer server, and OS components. It also monitors other component’s log files. Data collected by SAPOSCOL can be viewed using the agent technology. For more information about how to configure the CCMS agent SAPCCMSR, see SAP Note 209834.

Configuring SAPOSCOL Install SAPOSCOL on the dedicated liveCache and optimizer server as described in SAP Note 19227. After it has been installed successfully, SAPOSCOL is able to supply the following operating system data: − File systems − CPU − Paging − Commit charge (NT) − OS Collector − LAN

Data is written to a shared memory and read by the agent. The agent transfers this data to the CCMS of the SAP Solution Manager system.

Procedure

Monitoring SAP liveCache, the SAP Optimizer, and qRFC Inbound and Outbound Queues Setting up System Monitoring You have the following two options for monitoring a mySAP system based on RZ20:

1. You can perform monitoring activities centrally from your SAP Solution Manager system. 2. You can monitor alerts directly from within the component system in RZ20.

A revised version of the RZ20 alert monitor was delivered for SAP DB and liveCache with the following Basis Support Packages.

Basis 4.6C: SP40

Basis 4.6D: SP29

Basis 6.10: SP28

Basis 6.20: SP16


© 2005 SAP AG

5

The updated version provides many new alert nodes and extra information that you can display for specific versions and instance types. The data collection concept has also been completely changed for this version. In addition to having a concentration of fewer data collectors, the operability of collectors is now monitored internally and the collectors are activated or deactivated automatically as necessary.

Additionally the liveCache application node is available with the following Basis Support Packages: • Basis 4.6C: SP 45

• Basis 4.6D: SP 34

• Basis 6.10: SP 38

• Basis 6.20: SP 29

• Basis > 6.20: as standard

This application node appears when the APO system which belongs to the liveCache has the following APO Basis Support Packages implemented: • APO 3.0: APO Support Package ≥ 26

• APO 3.1: APO Support Package ≥ 17

• SCM 4.0: SCM Support Package ≥ 05

• SCM 4.1 and higher: as standard

Example: The central monitoring system without APO has Basis 6.10 with SP 38. The APO system belonging to the monitored liveCache has APO 3.0 with APO SP 26 and Basis 4.6C with SP40. The application node appears in the central monitor system but is not available in the APO 3.0 system. This application node is independent of the liveCache version.

After you have completed this setting up process, you have to either restart the SAP system or call report RSLVCALMON. This creates the new monitor for liveCache in RZ20.

For more information, see SAP Note 545030.

Recommendation:

It is more efficient to configure and run the Basis Support Package in the SAP Solution Manager system. If you do this, you do not then need to keep implementing the most up-to-date Basis Support Packages in your component systems. This also helps avoid the risk of software errors being installed in your production systems through the implementation of new Support Packages.

Setting Up the liveCache Alert Monitor in the SAP Solution Manager System or in the Component System Activate liveCache Alert Monitor You need the following basic knowledge when integrating a liveCache into the monitoring system:

I) Authorization for liveCache Monitoring/Administration

You have authorization as a DBM user. The monitoring system must be informed of this during integration. You have to use the central authorization option. Central authorization means that DBM user information is stored centrally in table DBCONUSR (which is similar to DBCON). This means that


© 2005 SAP AG

6

user data (XUSER concept) does not have to be stored on every single application server. In APO 3.0, many customers criticized the XUSER concept, noting (with good reason) that it was prone to errors. You configure DBM users and authorization in LC10, "Integration."

II) Communication between monitoring system and APO/liveCache

The following significant change/addition has been made regarding the communication between monitoring system and liveCache server: In addition to program DBMCLI with which you should already be familiar, program DBMRFC is implemented for communication with the DBM server. The liveCache architecture views DBMRFC as another client for liveCache administration; the SAP system, on the other hand, sees it as an RFC server for liveCache integration. It is integrated with the monitoring system the first time transaction LC10 is called. The two TCP/IP connections: SAPDB_DBM (default) and SAPDB_DBM_DAEMON are generated automatically at this point. To perform a simple unit test for the SAPDB_DBM TCP/IP connection, choose ‘Test connection’ in transaction SM59. If this unit testing is successful, DBMRFC can be correctly called from the monitoring system.

The first step for setting up the liveCache Alert Monitor is to activate the Alert Monitor in transaction LC10:

• Start transaction LC10 and enter a name for the logical connection. • Choose Integration. • A dialog box appears. Choose enter to create a new connection to liveCache. • Maintain the liveCache ID and the liveCache server name in the appropriate fields. • Do not maintain the preparation reports. • Choose Alert Monitoring tab page, set the Activate Alert Monitor indicator and save. • After saving the liveCache monitor is active. Press button liveCache: Alert Monitor to start

with monitoring.


© 2005 SAP AG

7

CCMS Monitoring in transaction RZ20 As in the standard system, the SAP SCM system itself has CCMS available for monitoring the SAP SCM system. The revised liveCache monitor is located in transaction RZ20 under SAP CCMS Technical Experts -> System/All Monitoring Segments/All Monitoring Contexts -> SAP DB Monitoring: <SID> • Log on to the SAP SCM system and call transaction RZ20. Choose Extras | Activate

maintenance function

• Select the My favorites field and choose Monitor (set) | Create to create a new Monitor set In the following dialog box, maintain a name for the Monitor set (example: SCM Monitor)

• In the Attributes field, choose Only for administrators and me and set the Public indicator • Choose Enter. The new monitor ‘SCM Monitor’ is now available.


© 2005 SAP AG

8

• Mark the new monitor. (example: SCM Monitor) • Choose Monitor (set) | Create to create a new Monitor set.

• Expand the SAP SCM system tree and select the monitor elements of interest. We suggest

creating three monitors with the following selections: o Database Monitor

Database Monitor o Interface Monitor

Transactional RFC and Queued RFC o liveCache Monitor

SAP DB Monitoring: <liveCache connection> or MaxDB Monitoring: <liveCache connection>

• Configure the Monitor by choosing Monitor definition | Generate Monitor or choose the matchstick icon

• In the next dialog box, enter the name of the monitor (liveCache Monitor, for example).


© 2005 SAP AG

9

• Next, choose Save • Repeat the steps for Database Monitor and Interface Monitor.


© 2005 SAP AG

10

Set Up System Monitoring in Solution Manager 3.1 and 3.2 This section looks briefly at setting up system monitoring in the Solution Manager 3.1 and 3.2. For more information about the Solution Manger, go to the SAP Service Marketplace and choose alias: SolutionManager Functions in Detail or see the Central System Monitoring for mySAP.com Best Practice document.

Definition of Solution Landscape An overview of active solutions is displayed with transaction DSWP or Solution_Manager

To create a new solution press the ‘New’-button. Enter all the necessary information in the new screen. For Solution Manager 3.1 go to Global Strategy Solution Landscape and Business Processes Edit Landscape in Operations Setup mode:


© 2005 SAP AG

11

Now flag all systems which have to be monitored in this solution.

To create Logical Components for your relevant servers in Solution Manager 3.2 choose Solution Landscape System Landscape Maintenance in Operations Setup mode:

To define which logical components are relevant for the specific solution and to maintain business processes choose the point Solution Landscape Maintenance.


© 2005 SAP AG

12

Activate Monitoring The next section shows the activation of system monitoring for the SCM system. For Solution Manager 3.1 go to SAP Technology Monitoring Setup System Monitoring -> in Operations Setup mode.

To activate the Monitoring in Solution Manager 3.2 follow the path Solution Monitoring System Monitoring Setup System Monitoring in Operation Setup mode:


© 2005 SAP AG

13

You have now entered the Setup System Monitoring Session. By marking the corresponding systems in column ‘Active?’ within check ‘Activate Monitoring’ and saving this check the monitoring for the chosen system will be activated.

To be able to monitor an SAP system it is necessary to create appropriate RFC connections to this system. It is possible to examine whether all necessary connections are maintained correctly within the next check ‘Check CCMS Connection’.


© 2005 SAP AG

14

For remote monitoring two RFC connections are required: RFC Destination for Data Collection or CCMS Read Destination This destination is used for the CCMS to get the monitoring data from the remote systems. For this connection a user 'CSMREG' is required. The password for this user has to be entered into the appropriate field ('password' in table 'RFC Connections'). The name of this RFC destination is displayed in table column 'RFC Destination for Data Collection' or ‘CCMS Read Destination’. RFC Destination for Monitoring or CCMS Login Destination This destination will be used for dialog users to logon to the remote system. To logon via this connection the current user is used. The name of this RFC destination is displayed in table column 'RFC Destination for Monitoring' or ‘CCMS Login Destination’. For more detailed information about CSMREG user and prerequisites for the System Monitoring see SAP Note 455356. As of Solution Manager Release 320 it is possible to connect a remote system via another Central Monitoring System (CEN) that has at least SAP Basis release 6.40. This measure allows you to monitor systems on basis of SAP NetWeaver. To enable this functionality you must connect the Central Monitoring System via the RFC connections described above When you activate monitoring there are several alerts for the APO system i.e. performance alerts which are displayed automatically from CCMS monitoring.


© 2005 SAP AG

15

When you activate monitoring there are liveCache alerts which are displayed automatically from CCMS monitoring.

You can also define your own alerts in addition to the R/3 Basis default alerts that are already reconfigured in the SAP Solution Manager. You use the CCMS (RZ20) in the component system to do this. You need MTE names to be able to map user-defined alerts in the SAP Solution Manager

1. Go to RZ20 in the component system.

2. Open the monitor from where you wish to take the alerts

3. Select the nodes and choose F1 to see the MTE name of the node. 4. Copy the MTE name and enter it in the ‘Alert Long Name’ column in the Solution Manager. 5. Set the indicator under the ‘Active’ column in the Solution Manager.

6. Enter a name for the alert in the ‘Alert Description’ column.

After you have saved these entries, the set threshold value of RZ20 is automatically inserted into the table.


© 2005 SAP AG

16

Interface Monitoring in SAP Solution Manager 3.1 and 3.2 Interface monitoring (Core Interface) can only be partially mapped using system monitoring. You can set individual nodes that are relevant to the interface from RZ20 (under a system monitoring instance in the Solution Manager), but this interface is hidden from the graphical overview. Only an alert (traffic light) would be visible.

We therefore recommend that you use business process monitoring to configure interface monitoring. A ‘certification key’ is required for releasing business process monitoring for use in the SAP Solution Manager. You can request this certification key by creating a SAPNet R/3 front-end message for component 'SV-SMG-OP' with short text: "Certification key for BPM. “ You should enter the following information in the message: Service Business Process Management (CP_BPM) System ID <of the Solution Manager> Installation number <of the Solution Manager> Customers who set up, configure, and use business process monitoring in the SAP Solution Manager without the dedicated SMO service "Business Process Management” accept full responsibility for this and are not entitled to support. You can purchase this service through the SAP Solution Manager or directly in the service marketplace. For more information about this, see SAP Note 52182.


© 2005 SAP AG

17

Important liveCache Alerts, Maintaining Alert Thresholds and how the System Administrator should respond to Red or Yellow Alerts You have to define alert thresholds and activate the automatic reaction method (such as sending an e-mail) for the following most important liveCache alerts. To find the liveCache alerts, go to either transaction LC10 | liveCache Alert Monitor or transaction RZ20 of your Monitor set. We recommend that you maintain the alert thresholds only in transaction RZ20.

To maintain the alert thresholds, start transaction RZ20 and choose the liveCache node in your monitor set. Activate the maintenance function by following this menu path: Extras | Activate Maintenance function.

Status of the liveCache Kernel Process Background The liveCache kernel process has three types of status: Offline, admin, and online. To find the liveCache status node, follow this path: Properties | State | Current State.

Thresholds

1. Select the Current State node and choose Properties

2. Choose the Status attribute tab page

3. In the When should a message cause an alert? section, set Always (at every message)

The alert node color changes as soon the liveCache kernel status changes from online to admin to offline, or from online to offline.

Action to Take in the Event of Red or Yellow Alerts: RED The alert will be rated red due to an abnormal liveCache shutdown. The status could be ABORT, SHUTKILL, KILL or SHUTDOWNKI. If the liveCache crashed, open an OSS message under component BC-DB-LVC and save the files knldump, knldiag, knldiag.err


© 2005 SAP AG

18

YELLOW

Yellow alerts indicate that liveCache has an offline status, that the status cannot be determined, or any other instances excluding online and the four red alert instances mentioned above.

The OMS Data Cache Hit Rate Background For a balanced liveCache, the OMS data cache hit rate should always be over 99.8%. A liveCache is balanced if the number of accesses to OMS data is more than 100 x OMS_SIZE. OMS_SIZE is the number of objects in 8kB-pages. You can determine this value with the following DBMCLI-command:

sql_execute select sum(pagecount) from classcontainers

An OMS data hit rate of less than 99.8 % causes a drop in performance. The reason for a poor OMS data cache hit rate could be that the CACHE_SIZE setting is too small or that there is a large amount of history pages in the data cache. To find the OMS data cache hit rate alert, follow this path: Performance | Caches | Data Cache Hitrate – OMS Data.

Thresholds

1. Select the Data Cache Hitrate – OMS Data node and choose Properties

2. Choose the PerformanceAttribute tab page and maintain the following threshold values

Change from GREEN to YELLOW 9980 1/100% 99.8% Change from YELLOW to RED 9950 1/100% 99.5% Reset from RED to YELLOW 9960 1/100% 99.6% Reset from YELLOW to GREEN 9980 1/100% 99.8%

3. Indicator for Alert is triggered if the comparative value: ‘falls below threshold value’

Action to Take in the Event of Red or Yellow Alerts: RED

Check whether liveCache is balanced. Shortly after restarting liveCache, the OMS hit rate of the data cache is usually below 100%.


© 2005 SAP AG

19

Example

OMS_SIZE = 100000. The liveCache is balanced when the number of OMS data accesses is 10000000.

If the alert for the OMS data cache hit rate is red even when liveCache is balanced, check the following:

1. Total data cache fill level

2. History fill level in data cache

A data cache usage of almost 100 percent could be due to a high proportion of history data or OMS data. If the history proportion is too large, check whether there are any long-running OMS versions (transactional simulations).

You should also make sure that job /SAPAPO/OM_REORG_DAILY is scheduled daily and that /SAPAPO/OM_DELETE_OLD_SIMSESS is scheduled every 30 minutes.

Report /SAPAPO/OM_REORG_DAILY deletes long-running OMS versions that were not properly completed by the application. Long-running OMS versions which cannot be removed by a daily reorganization can be closed by restarting liveCache.

If the proportion of OMS data is too large, you have to increase the CACHE_SIZE parameter to enable it to hold all the OMS data in the data cache. If you have any questions about setting this parameter, create a customer message for component XX-SER-TCC-APO.

YELLOW

Pay attention to this alert. No further action is required.

SAP liveCache Volume Fill Level Background Monitoring the liveCache fill level is mandatory to avoid a full database. A full liveCache could stall an APO system. It is also not possible to shut down a full liveCache. This situation can only be corrected by adding more data volume. The free data volume alert is visible in the path: Space Management | Data Area | Used Data Space.


© 2005 SAP AG

20

Thresholds

1. Select the Used Data Space node and choose Properties

2. Choose the PerformanceAttribute tab page and maintain the following threshold values Change from GREEN to YELLOW 70 % Change from YELLOW to RED 94 % Reset from RED to YELLOW 94 % Reset from YELLOW to GREEN 69 %

3. Indicator for Alert is triggered if the comparative value: ‘exceeds the threshold value’


The liveCache is over 90% full. If the liveCache fill level increases, liveCache is in danger of becoming full. It is not possible to correctly shut down a full liveCache. Add at least 4GB more data volume. After you have added additional data volume, liveCache distributes the data equally over all data volumes or the entire fill level falls. Continue to investigate the causes of the high data dataset in liveCache. Have enough data volumes been configured? Are there any long-running OMS versions and therefore a higher history proportion in liveCache?

YELLOW


The liveCache Heap Consumption Background Running COM routines and copying objects from the data cache into the liveCache heap consumes heap memory. The liveCache heap memory consumption can internally increase and decrease dynamically. Externally the heap, once allocated, will not be released to the operating system, although it is not needed anymore. Therefore the external allocated heap represents a high water mark of the liveCache heap consumption. This external heap usage is relevant for the monitoring.

You should also - if possible - set the OMS_HEAP_LIMIT liveCache parameter to limit the heap allocation of COM routines. For more information about whether you are allowed to set OMS_HEAP_LIMIT or not, see SAP Note 496318 for liveCache version 7.4. Otherwise, it is possible that the liveCache memory allocation exceeds the virtual memory. This results in a liveCache crash. To find the alert, go to RZ20: Space Management | Memory | Maximal Heap Usage in kB.


© 2005 SAP AG

21

Thresholds For a 64-bit liveCache, the sum of CACHE_SIZE plus OMS_HEAP_LIMIT should be less than the virtual memory, which is physical memory plus swap space. After setting the OMS_HEAP_LIMIT, you should define the thresholds for the alert heap usage.

1. Select the Heap Usage in KB node and choose Properties

2. Choose the tab page PerformanceAttribute tab page and maintain the following threshold values Change from GREEN to YELLOW 70 % of OMS_HEAP_LIMIT Change from YELLOW to RED 80 % of OMS_HEAP_LIMIT Reset from RED to YELLOW 75 % of OMS_HEAP_LIMIT Reset from YELLOW to GREEN 70 % of OMS_HEAP_LIMIT

Remark

The units of the threshold values in %

3. Indicator for Alert is triggered if the comparative value: ‘exceeds the threshold value’


© 2005 SAP AG

22

Example:

The setting for OMS_HEAP_LIMIT is 1000000. That is 1 GB.

Set the thresholds as followed in KByte:

Change from GREEN to YELLOW 700000 Change from YELLOW to RED 800000 Reset from RED to YELLOW 750000 Reset from YELLOW to GREEN 700000

If parameter OMS_HEAP_LIMIT is not set, the Heap Usage node can be ignored since it uses this parameter as a measuring point.

You should define the threshold value for Heap Usage in KB for this. Note that the value is given in KB.


The total consumption of the liveCache heap threatens to reach the limit of liveCache parameter OMS_HEAP_LIMIT. If this occurs, any COM routines that are running are canceled and the application experiences an ABAP short dump. Check whether the OMS_HEAP_LIMIT parameter is set correctly. Create a customer message for OSS component XX-SER-TCC-APO

YELLOW


Last Complete Data Backup Return Code

Since SAP liveCache 7.4 is able to log all transactions and all changes for both the OMS (Object Management System) and RDBMS data to log devspaces. It is also always able to recover the most up-to-date point in time.

The liveCache 7.4 has an alert in RZ20 called ‘Last Complete Data Backup Return Code.’ The return code indicated here comes from the dbahist.prt file. This file is a database manager log file about DBA actions. To find the alert, go to RZ20: Backup/Recovery | Last Backup | Last Complete Data Backup Return Code.


© 2005 SAP AG

23

If the return code is not equal to 0000 (SUCCESS), the backup failed and cannot be used for recovering the database. The only exception from this rule is status 9999, which means that the backup is in progress. The following list shows the most common return codes: Red 0002 - ERROR: This return code informs you that an error has occurred. You have to check the log files for a more detailed analysis or the exact error code. To do this, start the analysis method in RZ20. 9998 - UNKNOWN: This return code is given when the action was at 9999 for several days. It shows that something is not quite right. Further analysis is required. Red will also appear if no saves have been made over the past three months. Yellow 9999 - RUNNING: ‘Running’ means that data is currently being saved. Even if the last save could not be determined, a yellow alert is shown with a message. Green 0000 - SUCCESS: This means that everything is fine. There are no problems.

For more information about the APO backup, see the APO backup and Availability Best Practice document or the information in the SAP DB Library under http://www.sapdb.org/7.4/htmhelp/79/822f26b3e011d5993800508b6b8b11/frameset.htm.

For detailed information about APO monitoring and administration, see the Monitoring and Administration for SCM/APO Best Practice document.

Autosave Log Log backups are performed regularly to prevent liveCache standstills due to log overflow. Log backups can be made in parallel to online liveCache backups either - Manually by an administrator - Automatically in liveCache mode Autolog If the autosave log mode is enabled, log backups of completed log segments are started automatically. To find the alert, go to RZ20 SCM\SAP DB Monitoring: <SID> | SAP DB | Space Management | Log Area | Autosave Log


© 2005 SAP AG

24

Red: Automatic log backup is activated, but more than 1.5 times the log segment size has not been saved to the log or

Automatic log backup is not activated, although the last DBA action in this context was the activation of the automatic log backup.

Yellow: Automatic log backup is not activated, or cannot determine status of the automatic log backup.


© 2005 SAP AG

25

Enable e-mails to be Sent An important decision when configuring a monitor is the type of automatic reaction method required. In principle, any remote function module or report could be used as an automatic reaction method. The most important type of automatic reaction method is the sending of e-mails.

Use SAP Connect to configure an SAP system as a system that sends e-mails. SAP Connect is the interface between the SAP office environment and external communication partners. SAP Connect customizing is client dependent. For sending notifications out of CCMS monitoring infrastructure SAP Connect has to be configured in client 000. When e-mails are transferred via SMTP, the SAP Web Application Server communicates directly with a mail server. No gateway or connector is necessary. Any SMTP-conforming product can be used as a mail server. SMTP is available as SAP Release 6.10. You can find further information about SAP Connect and SMTP in SAP Note 455140.

There now follows a brief overview of how to configure the ‘sending e-mails with SMTP’ automatic reaction method:

1. Start transaction SCOT. Choose View | Node.

There are different types of node in SAP Connect:

SMTP node (for the SMTP function of the SAP application server)

HTTP node (for paging/SMS providers using Web services, as of 6.20)

RFC node (for old RFC-compatible e-mail/fax/paging gateways)

There is always a single SMTP node in each client. It is created automatically by the system and cannot be deleted. It is configured as follows:

2. Double-click on the node name.

3. Select "Node in use".


© 2005 SAP AG

26

4. Under "Mail Host" and "Mail Port", specify the mail server to which outbound mails are to be transferred.

5. Choose "Set" adjacent to "Internet".

6. Specify address areas of recipient addresses that are to be reached via this node (usually "*" if all e-mails are to be sent via SMTP).

7. For "Output Formats for SAP Documents" the following is recommended:

a. SAPscript / Smart Forms PDF

b. ABAP List HTM

c. Business Object / Link HTM

d. RAW Text TXT

Your SAP system is now ready for sending e-mails. You have to define and assign an automatic reaction method for sending e-mails when an alert turns red. We now have to define which alerts should trigger an automatic reaction method.

Enable the Automatic Reaction Method for Sending e-mails

The procedure for enabling notification by e-mail when an alert turns red is the same for all alerts. You should enable notification by e-mail in the following instances: For the status of the liveCache kernel process, the OMS data cache hit rate, the liveCache data devspace fill level, and the liveCache heap consumption.

The following example shows you how to enable e-mail notification for the Actual State alert, which you find by following this path: Properties | State | Actual State

Start transaction RZ20 and choose the liveCache node in your monitor set. Activate the maintenance function by following this menu path: Extras | Activate Maintenance function.

1. Select the required node and choose Properties

2. Choose the third tab page (Methods) and choose the Method assignment button


© 2005 SAP AG

27

3. In the following screen choose the Auto-reaction tab page, set the Method name indicator in the Method assignment section and choose change. Maintain CCMS_OnAlert_Email in the Method name section and save.

4. After saving, the string CCMS_OnAlert_Email appears in section Effectively assigned method | Method name. Choose this string: CCMS_OnAlert_Email.

5. In the following screen, choose the Parameters tab page and maintain the e-mail address for line RECIPIENT and U for RECIPIENT-TYPEID and save.


© 2005 SAP AG

28

In the screenshot, we maintained an e-mail address for user ALERT_BLA (using transaction SU01)

E-mail notification for red alerts is now enabled. The Alert Monitor checks the status of an alert node every five minutes and activates the automatic reaction method if necessary. Unfortunately, it is not currently possible to change this check frequency to anything other than five minutes.

For information about sending alert e-mails to several users or for information about other automatic reaction methods, see SAP Note 176492 and follow the instructions contained within it.

Central Auto Reactions As of Basis Release 6.10, you can define central auto-reaction methods as part of the central monitoring of mySAP.com components in the CCMS monitoring architecture. The auto-reaction methods are not started in the system in which the alert occurs, but in the central monitoring system. As a result, events which occur in monitored components can be reacted to automatically on central positions without any delay.

Prerequisites • The central monitoring system (CEN) must have Basis Release 6.10 as a minimum. • The monitored mySAP.com components with SAP Basis have the following kernel versions as a

minimum:

o 4.0B patchno 937

o 4.5B patch no 815

o Release 4.6B/C/D: as of 46D DCK 4.6D patchno 1192

o 6.10 patchno 582

o 6.20 patchno 193

• The monitored mySAP.com components with SAP Basis are linked with the CEN via the SAPCCM4X agents.The agent has at least the following patch versions (see note 202591)

o 4.6D patchno 1192 (patch 10 in ccmagent.info)

o 6.10 patchno 582 (patch 6 in ccmagent.info)

o 6.20 patchno 193 (patch 4 in ccmagent.info)


© 2005 SAP AG

29

• Monitored mySAP.com components with Basis Release 3.1 and systems, which are included centrally via the SAPCCMSR agents, are formally related to CEN. You can therefore already start the auto-reaction methods centrally.

Procedure 1. An alert occurs in the monitored system on an MTE, to which a central auto-reaction method is

assigned.

2. The agent recognizes the alert within a minute and informs the CEN of the MTE and the alert data via RFC.

3. The SAP_CSM_TRIGGER_CENSYS_DISPATCH background event is triggered in the CEN. As a result, the central method dispatcher, RSAL_CENSYS_TOOL_DISPATCHING, is started as a background job in the CEN. The job calls the corresponding method in the CEN and transfers its information to the MTE and the alert. In addition, it adjusts the method runtime status in the monitored system through the agents.

Execute all configuration steps in the CEN only. • Start transaction RZ21 there and select -> Technical infrastructure -> Assign Central

Autoreactions.

In this screen, you can execute all the steps for defining, assigning and processing central auto-reaction methods. Detailed information about the setup is described in SAP Note 429265.


© 2005 SAP AG

30

Online Alerting A new feature in Solution Manager 3.1 allows critical liveCache condition information to be sent to system administrators and to SAP.

With Online Alerting your liveCache is monitored. For critical situations, an automatic alert is triggered and sent to the system administrator and SAP.

Online Alerting can be switched on for SCM Customers. The setup of Online Alerting will be carried out during onsite service (APO SMO/ System Administration) by SAP consultants.

System requirements for Online Alerting: SAP Solution Manager 3.1

Basis 6.20 SP2 ST-PI 003C

ST-SER 311 SP01

Minimal configuration of Support Desk and Issue Tracking APO System

Basis Support Package -> See SAP Note 545030

We recommend using the latest ST-PI.

Detailed information is available in SAP marketplace under alias /safeguardingscm -> Media Library -> Online Alerting in SAP Solution Manager 3.1.

Optimizer Server Alerts The optimizer server is usually a standalone server and is only available on the Windows NT or 2000 operating systems. There are no explicit alerts to monitor for the optimizer apart from hardware data such as CPU and main memory usage.

RFC Alerts The RFC interface layer is used for several mySAP.com components such as SAP SCM and SAP CRM.

Enabling and setting up qRFC alerts in transaction RZ20 is very similar to that described in the mySAP CRM Mobile Sales Monitoring best practice document. For more information, see the following SAP Notes.

With the following SAP_BASIS support packages functionality for monitoring transactional and queued RFC is available:

- Release 4.5B SAPKH45B47 SP 47 - Release 4.6B SAPKB46B35 SP 35 - Release 4.6C SAPKB46C26 SP 26 - Release 4.6D SAPKB46D15 SP 15 - Release 6.10 SAPKB61008 SP 08 (also for Release 5.0)

Once installed, the new monitoring functionality is automatically active as soon as the central instance starts. SAP Note 441269 - Setting up tRFC/qRFC monitoring in the Alert Monitor SAP Note 418285 -

Installation of the ITS Plug-in for the CCMS Agent SAP Note 486308 - Setting up the OS monitoring of the BC for SAP The new tRFC/qRFC Monitor can either be found under SAP CCMS Monitor Templates in monitor Communications or under SAP CCMS Technical Expert Monitors monitor ‘All Monitoring Contexts’.


© 2005 SAP AG

31

ARFCSSTATE: Outbound tRFC Calls The number of outbound transactional RFC calls that cannot be processed because of errors. These errors include communication errors (the server that was to process the calls could not be reached); execution errors (there was an error in the function module that was to be executed in a tRFC call); or resource errors (the RFC server group did not have enough servers (see transaction SM59, RFC -> RFC groups)). Alerts are generated if the number of calls with errors exceeds thresholds.

ARFCSSTATE: Inbound tRFC/qRFC Calls

The number of inbound transactional RFC and queued RFC calls waiting to be processed. An alert is triggered if the number of calls waiting exceeds a threshold.

Outbound and Inbound Queues

Error messages for inbound and outbound qRFC queues. An error message means that the affected queue cannot be processed and that any additional calls added to the queue must wait until the error is corrected.

QIN and QOUT Scheduler

Communication errors or execution errors for inbound and outbound queued RFC schedulers. The monitoring tree for inbound schedulers also reports on queues that have not been registered for processing. Calls in these inbound queues are not executed until the queues are registered.

Action to Take in the Event of Red Alerts Problems occur when transferring data between R/3 and the Core Interface (CIF). These can be technical or application-specific problems. Note therefore that APO administrators and departments need to work closely together.


© 2005 SAP AG

32

Technical Details Make sure that the gateway parameters have been optimally configured. Implement Note 384971 for all connected R/3 systems and the APO system itself to ensure secure communication and prevent terminations when sending data. At the sender, you can use parameter rdisp/rfc_min_wait_dia_wp to configure how many dialog work processes are not to be used to send qRFCs. These work processes are available for administrative tasks and online users. You can use parameter rdisp/rfc_max_own_used_wp to restrict the percentage of dialog work processes that can be occupied by a user (the interface user, for instance). See Note 74141 if you wish to configure these parameters. To prevent qRFC activities having an adverse effect on online users, you should check the sender and receiver to see whether you can configure an instance exclusively for qRFC communication. To restrict the dialog work processes used by qRFC at the receiver, you should convert CIF communication at the receiver to inbound queues. See notes 416475 and 430725 for information on how to do this. As soon as inbound queues are used, you can use the aforementioned parameters (rdisp/rfc_min_wait_dia_wp and rdisp/rfc_max_own_used_wp) to restrict the number of processes being processed in the inbound queue. You can also restrict the load at the receiver by using the QOut scheduler at the sender. For information on how to configure the QOut scheduler, see Note 400330. For optimum performance, make sure that the most up-to-date qRFC version is being used in both R/3 and APO. For information about the most up-to-date qRFC version, see Note 438015. Check whether you can improve performance by deleting the cost-based optimizer statistics of the qRFC tables (see note 371068 for more information). On a regular basis, check if there are a large number of entries in the RFC tables. For information about what to do if there are, see Note 375566.

For more information about what action to take in the event of a red alert, see the Manage APO Core Interface in SCM Best Practice document.

Application-Specific Details

Alongside the technical view provided by the qRFC monitors, you can also gain a more application-technical insight into the active data channels within the dedicated R/3 systems. For this, use transaction CFP2.

A red traffic light indicates that data transfer problems occurred in a channel. If the problem is not technical, you can use the monitor to find the affected application module.

Further SCM System Alerts As well as monitoring of liveCache, additional alerts in the SCM system need to be monitored. The definition of particular alerts depends on customer specifications. For this reason, the following section serves merely to highlight a cornerstone of SCM System monitoring.

Operating System Alerts • Start transaction RZ20. • Select System / All Monitoring Segments / All Monitoring Contexts • Select the monitored application server <hostname_SID_Instancenumber> • Select Monitoring Tree Element Operating System


© 2005 SAP AG

33

File Systems This monitoring tree element in the alert monitor offers information on the file systems in a host server.

Data on file systems includes the following:

• The amount of unused disk space in the file system

• The percentage of space used in the file system.

CPU This monitoring tree element reports on the state of the central processing unit in one of the host servers in your APO System. You will find a CPU MTE hierarchy for each server in the system.

Paging This monitoring tree element reports on paging in a particular host system. Paging is the exchange of pages (blocks) of data between a host system's main memory and overflow storage in a paging file on a hard drive.

Paging occurs when main memory is not large enough to hold the contexts of all processes that are running in the host system. Data that is required by a running process is paged in as required from the paging file; data that is not currently needed is paged out to the paging file to make room.

Swap Space This monitoring tree element reports on the amount of swap space available in a particular host system.

Swap space is the amount of disk storage available for swapping or paging out data from main memory. Because of its high-performance memory management design, the SCM System makes intensive use of swap space.


© 2005 SAP AG

34

OS Collector The SAP program SAPOSCOL should be running on every host system on which either an SAP application server or a database system is running. The program collects system data for the host system, which it reports to the monitoring architecture, and which is displayed in the alert monitor.

LAN This monitoring tree element monitoring consists of different monitoring attributes which characterize the local network from the point-of-view of a server.

Monitored Processes The operating system collector SAPOSCOL offers the chance to permanently monitor specific processes. The name (or name pattern) of processes of this type are stored in a configuration file of SAPOSCOL. A subtree is then automatically created for each process name in transaction RZ20.

Database In Release 4.5B (CAUTION: for MSSQL server as of Release 4.6!) the database alerts from RZ03 were integrated into RZ20. The values for 'Freespace' under 'Space Management' cannot yet be changed directly in RZ20, but the information as to whether an alert is triggered is retrieved by the collective method from report RS<DBNAME>T8M. As of Release 4.6X, the individual areas of the database (for example, tablespaces on Oracle) are displayed in the 'Freespace' sub-tree and alert threshold values can be adjusted in RZ20 -> Properties.

New sub-trees as of Release 4.6:

- Performance: database specific values, for example, cache hit ratio, redo log buffers, checkpoints, disk statistics

- Backup/restore

- R/3 consistency: Health

Oracle SAP note 483856 provides you with an overview of the alerts reported within the Oracle database monitoring (\Database\Oracle tree) in transaction RZ20. In particular, this note refers to the new alerts that were delivered in the Support Packages specified in note 426781.

For more information on existing alerts, see the SAP online documentation:

"Computing Center Management System (BC-CCM)"

-> "Database Administration in CCMS"

->-> SAP/Oracle DBA in CCMS

->->-> Monitoring the Oracle Database

SQL Server As of release 4.6B, alert monitor functionality has been incorporated into the SQL Server port.

Transaction rz20 takes you to the alert monitor. The database folder exists within the SAP CCMS Monitor Templates folder. Inside the database folder is a folder called "Microsoft SQL Server". There are seven nodes within this folder that are common to all database ports:

Space management, Performance, Backup/restore, R/3 consistency, Users, Running jobs, and Health. Some ports delete some of these various nodes and for release 4.6B, SQL Server deletes node Running jobs.


© 2005 SAP AG

35

Another folder for alert monitor data specifically for SQL Server is found under the path: database -> R/3 DB Clients (Application servers) -> <app server name> -> Database Client -> Slow SQL Statements. SAP note 171120 provides an overview of the alert monitor and the items monitored for SQL Server.

Monitoring background jobs You can monitor special background jobs in the monitor architecture (transaction RZ20) with the following Support Packages:

Software Component Release Package name

SAP Basis component

46B SAPKB46B49

46C SAPKB46C40

46D SAPKB46D29

610 SAPKB61027

620 SAPKB62014

The purpose of this new function is to offer an overview of the status and runtime of jobs, which are regularly run in the system. In addition to the general monitoring of the background run-time environment previously provided, alerts can now be created for particular job names or name patterns in the event of an error. More detailed documentation is available in SAP Note 553953.


© 2005 SAP AG

36

SCM Basis System • Start transaction RZ20. • Select System / All Monitoring Segments / All Monitoring Contexts • Select the monitored application server <hostname_SID_Instancenumber> • Select Monitoring Tree Element R3BasisSystem

Memory Management An application runs in a work process. The work process requires memory for this application. The Memory Management System assigns the memory to the process. Which type of memory is assigned in which order depends on the work process type (Dialog or non-dialog) and the underlying operating system.

You can find detailed information about the Memory Management System in the SAP Library under:

SAP Library -> Basis Components -> Client/Server Technology (BC-CST) -> Memory-Management (BC-CST-MM)

Buffers This MTE offers information on the quality and efficiency of critical buffers that the SCM System uses to speed performance.

For each buffer, the alert monitor tracks the following data:

• The percentage of directory entries in use. Directory entries hold the management data for data in a buffer. Directory entry usage must never reach 100 percent, while free space for data is still available. If all directory entries are used, then remaining free space goes to waste, as no new entries can be added.

• Space used: The amount of space used in the area of a buffer that is reserved for buffered data.


© 2005 SAP AG

37

• Hit ratio: The efficiency of the buffer (the percentage of the time that the buffer can satisfy the information requirements of the R/3 System). After a warm-up phase while a buffer is being loaded, the hit ratio should always be at 95% or above. Otherwise the buffer is probably too small.

Syslog • Start transaction RZ20. • Select System / All Monitoring Segments / All Monitoring Contexts • Select the monitored application server <hostname_SID_Instancenumber> • Select Monitoring Tree Element R3Syslog

To monitor the system log (syslog), the syslog messages are grouped into thematically linked subtrees. The subtree in which an alert is reported depends on the category of message. You set these categories depending on the message ID in transaction SE92. In this transaction, you also set the syslog message text and the criticality and the severity of the alert.

You can additionally correct the criticality and severity of the alerts for individual intervals in transaction RZ20 by choosing the desired category, Attributes and Filter.

For more information, see:

• SAP Note 214247 (RZ20: Questions on configuration/interpretation)

• SAP Library -> Basis Components -> Client/Server Technology (BC-CST) -> BC System Services -> Tools for Monitoring the System -> System Log.


© 2005 SAP AG

38

Solution Architecture and Core Business Processes for mySAP SCM The set up process for the System Monitoring session in SAP Solution Manager for SAP APO is the same as for other SAP components and should be carried out in accordance with the Central System Monitoring for mySAP.com Best Practice document.

Procedure To monitor the SAP APO infrastructure, we assume that you have an extra SAP R/3-based system available with the Solution Manager installed, in order to:

* Ensure service delivery and monitor functionality * Prevent possible upgrade conflicts

* Prevent the SAP Solution Manager system load from affecting production

* Simplify routine maintenance of the SAP server infrastructure

* Control access to the SAP Solution Manager

All individual components send their monitoring data to the CCMS of the monitoring SAP R/3-system, i.e. monitor data for each component can be displayed in transaction RZ20 of the APO –system that is being used for monitoring. It is then possible to map this data to the Solution Manager, where monitoring can be configured using a graphical representation with simple step-for-step navigation. For a complete description of the business processes that can be monitored in mySAP SCM and the respective business process management procedures, see the following Best Practice documents:

Manage the Global ATP Service

Manage Production Planning in SCM / APO

Manage the Transportation Management Solution in SCM/APO

Manage Supply Network Planning in SCM/APO

Manage Demand Planning in SCM/APO


© 2005 SAP AG

39

Further Information Troubleshooting If after following this Best Practice document, you have not achieved the desired results, you may have tried to implement System Monitoring too quickly, in insufficient detail, or without the full cooperation of all the company employees involved. If you encounter problems with the SAP Solution Manager, send feedback to SAP.

Background Information and References For more information, follow this link. SAP Solution Manager: http://www.service.sap.com/SolutionManager

Background Information and References • Best Practice Document: “Central System Monitoring for mySAP.com”

• Best Practice Document: ‘Monitoring and Administration for SCM/APO”

• Best Practice Document: “Manage APO Core Interface in SCM”

• Best Practice Document: “Backup and Recovery for SCM/APO”

• Best Practice Document: “Manage the Global ATP Service”

• Best Practice Document: “Manage Production Planning in SCM/APO”

• Best Practice Document: “Manage the Transportation Management Solution in SCM/APO”

• Best Practice Document: “Manage Supply Network Planning in SCM/APO”

• Best Practice Document: “Manage Demand Planning in SCM/APO”

• Best Practice Document: “Data Consistency for SCM/APO”

Feedback and Questions If you would like to provide feedback, create an SAP customer message for component SV-SMG-SER. You do this at http://service.sap.com/message.

SAP Notes Useful SAP Notes

SAP Note Brief Description 572003 SCM operating concept

424886 Parameter values as of liveCache Version 7.2.5

496318 Parameter values as of liveCache Version 7.4.02

817884 Parameter values as of liveCache version 7.5.00

545030 Revised alert monitor SAP DB/liveCache

453034 You want to order the SAP Solution Manager

394616 Release strategy for Solution Manager (ST)

402806 Release strategy for Add-On ST (Solution Manager)

455356 Requirements for System Monitoring in Solution Manager

418285 Installation of the ITS-PlugIn for the CCMS Agent

176492 Automatic e-mail in case of alert (RZ20)


© 2005 SAP AG

40

209834 CCMS agent technology (composite SAP note)

209834 Installing CCMS agents

441269 Setting up tRFC/qRFC monitoring in the alert monitor

436186 Installing saposcol as a service

19227 Get the latest saposcol

451166 SAPOSCOL: monitoring processes

52182 Availability of Business Process Monitoring

455140 Configuration E-mail, fax, paging/SMS via SMTP

486308 Setting up the OS monitoring of the BC for SAP

450741 Setting up OS monitoring of remote servers for SAP

101573 Internet Mail Gateway: Versions

99965 Internet Mail Gateway: Configuration (Ver.4.x)

371023 OS07/ST06: Monitoring of operating system data

522453 RZ20: Monitoring operating system data

483856 Description of the alerts for Oracle database monitor

171120 Alert Monitor for SQL Server

553953 RZ20: Monitoring background jobs

203924 Performance 4.6 - collective note

146289 Parameter Recommendations for 64-Bit SAP Kernel

103747 Performance in 4.0/4.5/4.6: Parameter recommendations

97497 Memory Management Parameter (3.0/3.1)

Important transactions

Transaction Code Brief Description DSWP or SOLUTION_MANAGER SAP Solution Manager

RZ20 CCMS Monitoring

RZ21 CCMS Monitoring: Properties and Methods

SCOT SAPconnect – Administration

SMSY Solution Manager System Landscape

LC10 liveCache Assistant

SM59 RFC Destinations (Display/Maintain)

SU01 User Maintenance

SE92 New SysLog Msg Maintenance as of 46A


© 2005 SAP AG

41

© Copyright 2005 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.