SAP Library - Find your answers

Use

You can customize the availability monitoring with CCMSPING for ABAP and Java systems in a number of ways. The following functions are available:

· You can activate and deactivate availability monitoring for particular systems

· You can define the type of availability monitoring for application servers and logon groups of an SAP system. When doing so, you can both create and change monitoring rules, in accordance with which the servers and groups of the system are monitored, and change the monitoring settings of servers and groups individually.

Logon groups exist only for ABAP application servers.

· You can activate and deactivate availability monitoring for systems groups. You can also decide whether these settings should also automatically apply for systems that are later added to the relevant system group (see Monitoring System Groups with CCMSPING).

· If you have installed multiple CCMSPING agents, you can decide which CCMSPING is responsible for the monitoring of a system. This is, for example, useful for the monitoring of distributed system landscapes (see Using Multiple CCMSPING Agents).

· You can select time periods in which the availability of selected systems is not checked (see Creating and Changing a Monitoring Pause)

· You can add new systems to the list of systems that can be checked using availability monitoring.

Prerequisites

You have performed the Installation of the Availability Agent CCMSPING.

Process Flow

...

1. Choose CCMS ® Configuration ® Alert Monitor, or call transaction RZ21.

2. The Monitoring: Properties and Methods screen appears. Choose Technical Infrastructure ® Availability Monitoring ® Configure CCMSPING Monitoring.

3. The Configure Availability and Performance Overview screen appears. The screen shows monitored and unmonitored systems in two lists, where you can display for the monitoring of the monitoring systems by expanding the subtree for the corresponding system:

The configuration of the availability and performance overview is also set as the analysis method for the nodes of the Availability and Performance Overview Monitor. This means that you can display this screen by double-clicking a node in this monitor.

Displaying the Monitoring and System Data

There are various views available on the Configure Availability and Performance Overview screen, with which you can display information about the monitored systems and their application servers and logon groups. To activate a view, choose the Views button, and then one of the following buttons:

Activities

Changing the Monitoring of Systems

To change the monitoring of systems, select the desired systems on the Configure Availability and Performance Overview screen by selecting the folder icon of the relevant systems. The following functions are then available to you:

You can also activate and deactivate system monitoring by moving selected systems to the desired list by Drag&Drop.

Monitoring System Groups

You can combine systems into system groups (see System Groups in the Alert Monitor), where one system can belong to multiple system groups. In this way, you can, for example, organize systems into system groups by their function (development, quality assurance, production), their release status, or their geographic location.

In large IT environments, it can greatly simplify the configuration of availability monitoring, if you can, for example, monitor all systems in a system group with one command. You can also set up the monitoring so that changes to the systems that belong to a system group automatically cause a change in the availability monitoring of the relevant systems.

For more information about monitoring system groups, see Monitoring System Groups with CCMSPING.

Changing the Monitoring of Application Servers and Logon Groups

You can change the monitoring settings for servers and groups on the Configure Availability and Performance Overview by selecting the relevant indicator in the ALV Tree Control.

Add New Systems to the List of ABAP Systems that Can Be Monitored

On the Configure Availability and Performance Overview screen, choose Load System List (). If the desired ABAP system does not appear on the list, add the system to it manually (see Add Systems to the Availability Monitoring Manually).

The SAPMSG.INI file, which is also used for functions of SAPLOGON, is uploaded from the front end for the system list. It does not contain any standalone Java systems.

Changing Technical Settings of the Availability Agent CCMSPING

You can also change technical settings of the registered CCMSPING availability agents, such as the frequency of the monitoring, or the timeouts that define how long CCMSPING waits for a response from the message servers and the application servers (see Changing the Monitoring Frequency and Timeouts of CCMSPING).

Result

You have customized the availability monitoring to your requirements. Use the Availability and Performance Overview Monitor from the SAP CCMS Monitor Templates monitor set to perform availability monitoring.

Availability Monitoring with CCMSPING start page

With this monitor, you can perform availability monitoring for selected ABAP and Java systems and their instances. For ABAP systems, you can also monitor the availability of logon groups, and the most important performance attributes for the status of the dialog system are also displayed for the monitored ABAP instances.

For more information about selecting systems and application servers for monitoring, see Configuring Availability Monitoring.

Description of the Tree Structure of the Monitor

Prerequisites

Availability monitoring uses the standalone agent CCMSPING, you must therefore have performed the installation of the availability agent CCMSPING.

Features

Availability of Systems

For availability monitoring, CCMSPING checks the availability of the message server of the corresponding system. A system is regarded as available if the responsible message server responds to the availability agent’s query and at least one application server is registered as active with the message server. The system availability is monitored by one or more CCMSPING agents, depending on the configuration of your availability monitoring.

In the case of ABAP+Java systems, if you have specified both message servers in the configuration of the availability monitoring, both availability values are displayed here.

Availability of ABAP Instances

The monitor displays the following MTEs for the monitored ABAP instances:

For more information about the performance values for the dialog system, see Dialog Overview Monitor.

Availability of Java Instances

Java instances are displayed under different names, depending on which message server (ABAP or Java) is used for the availability monitoring of the system:

· In the case of monitoring purely using the ABAP message server, Java instances are displayed under the name of the assigned ABAP instance with the suffix :Java (such as: Host1_C11_00:Java). This is only possible if the relevant system is a double-stack system).

· In the case of monitoring using the Java message server, Java instances of the relevant system are displayed under their server ID with the prefix J2EE (such as J2EE7305550). This is also the case, if the monitoring is performed using both message servers.

The monitor displays the following MTEs for the monitored Java instances:

Availability of Logon Groups

In the case of ABAP systems, you can monitor logon groups for their availability. A logon group is regarded as available, if it is possible to log on to the application server with the best dialog system quality in this group. In addition to the availability of the logon groups in the last 15 minutes, the system also displays the application server of the group with the best dialog system quality in the monitor.

Analysis Method

If you double-click a node in this monitor, you start the analysis method Configure Availability and Performance Overview. (see Configuring Availability Monitoring).

Activities

To start the monitor, follow the procedure below:

...

1. Start the Alert Monitor using transaction RZ20 or choose CCMS ® Control/Monitoring ® Alert Monitor.

2. On the CCMS Monitor Sets screen, expand the SAP CCMS Monitor Templates set.

3. Start the Availability and Performance Overview monitor from the list by double-clicking it.

For SD material Determination you can create a Substitution reason and on the Strategy field, the following info. is available:

Product selection in the background is performed on the basis of the availability check.

We want to have the material determination only in case on material shortage. We expect the Substitution reason to give us this functionallity. It does not hovever take the availabilty into account before substitution.

We thought the worse case is to create a ABAP which is linked to the "requirement" field in the Procedure (OV13).

Has anyone had the same requirement? Is this a bug or just incorrectly documented?

I also encountered this abnormally recently using material determination. In order to combat the problem, the first product substitution should be for the original material. I've illustrated this below:

Original Product: ABC
Substitutes: DEF, XYZ

In order to perform product substitution ONLY in the case of ATP failure for product ABC, structure the Material Determination record as follows:

Material Entered: ABC Substitutes: ABC
DEF
XYZ

There seems to be a devaition at availability check and or on a conceptual note still.

Availability check can be configured both at requiremnt class and at the schedule line categories level.

Whilst the availabilty check at the requirement class level via global and mandatory configuration the schedule line catgry availability check deals with the order.

It is mandatory that the reqmnt class is flagged off for avlblty check and the schdelu line cat need not be.

The following are the mandatory for Availability check to happen--

1. Must be swithced on at the requirment class level and at the schedule line level.

2. Reqmnt type must exist by which a requiremnt class can be found

3. There must exist a plant and is defined

4.Checking group must be defined in Material Master records(it controls whthr the system is to create individual or collective reqmnt)

A combination of checking gropup and checking rule will determine the scope of availbaility check.

SAP standard does not do an availability check on the quotation, as it is not a definite order, usually just a pricing quote.

When it is converted to an order, the first availability check is carried out, as well as credit checks. The system will check stock in the plant, plus what is contained in the availability checking rule (scope of check) eg: can add POs for replenishment, purchase reqs, different planned orders, and subtract sales orders, deliveries etc already created against that material in that plant (and possibly Storage location).

If there is enough stock in the plant/SLoc, the system will give you a confirmed date, or give you a date based on the production time or purchasing time from the material master. The date the system proposes is based on the customer's requested delivery date.

SAP first backward schedules looking at the required delivery date, less transportation time, less transportation lead time, less pick and pack time, less production/purchase time if applicable. If the date it calculates is equal or later than today’s date, then it will confirm the customer’s required date. If it falls in the past, SAP will then forward schedule for today’s date, plus the times listed above to get the date when the customer can actually have it.

ATP is the single most complex part of the SD module, depending upon how PP and MRP is set up.

MRP works semi-separately, depending on how it is set up. Basically, MRP looks at the demand on the plant, and if it the stock does not meet expected sales orders and deliveries, it will create a purchase requisition (outside purchase) or requirement or planned order (for production) to cover the shortfall. When MRP is started, it will turn the PR into a PO or the requirement into a production order.

SAP Product Availability Matrix

Here we can find information on the availability of SAP component releases, maintenance end dates, and platform version availability.

Please go through the following link for more information:-

https://websmp210.sap-ag.de/pam

Keyword: BASIS
Title : SAP NetWeaver Application Server High Availability

Keyword: BASIS
Title : SAP NetWeaver Application Server High Availability

Keyword: BASIS
Title : SAP NetWeaver Application Server High Availability

Keyword: BASIS
Title : SAP NetWeaver Application Server High Availability