December 10, 2014

Concept of the Monitoring Architecture

The alerts are displayed in a tree structure in the alert monitor, and assigned a severity and a color (yellow for a warning, red for a problem). You can see the current status of your system and process alerts here. The alert monitor is based on the monitoring architecture, which was introduced in SAP R/3 4.0:
This graphic is explained in the accompanying text
The CCMS monitoring architecture is not a monolithic monitoring and administration program. Rather, it offers a flexible framework into which extensive monitoring and administration functions can easily be added.
The elements of the monitoring architecture function largely independently of each other and can, particularly, be further developed and adjusted independently of each other.
·  Data Supplier
A data supplier is a program that delivers data to the monitoring architecture. It belongs to one of the individual system components and creates monitoring objects that report values to the monitoring architecture. The monitoring architecture is delivered with the data suppliers for the most important components of your SAP system and its environment and can therefore be immediately used.
Data suppliers pass their information to the monitoring architecture. The monitoring architecture provides an infrastructure for gathering and managing system information. The monitoring architecture therefore constantly compares the values reported by the data suppliers for the monitored objects with threshold values and displays an alert if a value exceeds or falls below a threshold value.
·  Data Consumers
A data consumer is a program that reads data from the monitoring architecture; it displays the information transferred to the monitoring architecture by the data suppliers. SAP delivers both the standard data consumer and other special monitors that all use the data delivered by the monitoring architecture.
·  Monitoring Objects and Attributes
A monitoring object describes an object that is to be monitored. A monitoring attribute represents a type of information that is to be reported for a monitoring object. Monitoring objects include, for example, the CPU in your host system, the database, and SAP services, such as background processing. Monitoring attributes for a CPU object could be CPU utilization and the average CPU workload for the last five minutes.
The alert monitor also provides the administration methods that you need to monitor the system. In this way, you can set threshold values for alerts and add or adjust auto-reaction and analysis methods: if an alert is triggered, auto-reaction methods react automatically, and you can use an analysis method to investigate the cause of an alert without leaving the alert monitor. The monitoring architecture also contains tools for administering and archiving the alerts.

SAP CIN Interview Questions & Answers

1.     How does CIN determine the tax rates?
CIN determines taxes based on the chapter-id of the material. There are 2 levels for rate determination. First the system will check if there is an exceptional rate available. If this is available then that rate is picked up. This rate could be for a material or material and customer combination. If there are no exceptions then the system looks for chapter-id of that material.  The customer will have an excise tax status, which along with the plant status will give a final excise status. Based on the excise status and the chapter-id the rates are maintained.
2.      Can I change the tax rates retrospectively?
You can change the excise rates with any given validity period. After making the changes you will have to update the sales orders if the new tax rates have to be considered for future deliveries.

How SAP BW and HANA will merge over time -- and why it matters

Though SAP swears HANA won't replace Business Warehouse (BW), there are good reasons to believe the in-memory analytics platform will eventually absorb BW. But I think it is more accurate to say thatSAP BW and HANA will begin to merge. If this scenario plays out as I believe it will, the murkiness surrounding skill and technology decisions between BW and HANA starts to clear.
This article describes the likely paths of BW and HANA and outlines three possible scenarios for their convergence, or lack thereof. While this discussion of roadmaps is speculative, it's informed by carefully watching SAP's moves and a good understanding of the products and technologies involved. I've linked to public statements from SAP. Anything not referencing such public statements is speculative.

Does SAP HANA Replace BW?

Well – I can’t say I am surprised by all the debate on Twitter about SAP HANA potentially replacing BW. I wrote this blog in response to about 50 tweets I saw on Friday about the topic. I plan on covering four scenarios in this blog that will hopefully help guide people. Those scenarios are:


1. I have SAP ECC and BW, what do I do?
2. I have SAP ECC and may want BW, what do I do?
3. I have SAP ECC, but someone told me SAP BusinessObjects Rapid Marts are better, what do I do?
4. I have SAP ECC and someone told me they will design a data warehouse for me from scratch, what do I do?

Top BusinessObjects interview questions (BO) with Answers

Welcome to the finest collection of SAP BusinessObjects (BO a.k.a BOBJ) Interview Questions with standard Answers. Based on our years of experience in BusinessObjects reporting tool, we have hand-picked these questions and provided to-the-point answers to each one of them so as to help you prepare better for BusinessObjects job interviews.

1. What are the differences between Personal, Shared and Secured connections?

  1. A Personal connection is created by one user and cannot be used by other users. The connection details are stored in PDAC.LSI file.
  2. A shared connection can be used by other users through a shared server. The connection details are stored in SDAC.LSI file in the Business Objects installation folder. However one cannot set rights and securities on objects in a shared connection. Neither can a Universe to exported to repository using a shared connection
  3. A secured connection overcomes these limitations. Through it rights can be set on objects and documents. Universes can be exported to the central repository only through a secured connection. The connection parameters in this case are saved in the CMS