What monitoring capabilities are available for SAP applications?
SAP applications have different supported versions, platforms, and functionality. Therefore, there are different supported protocols used for communication between SAP systems and external applications, as well as different supported user interface technologies. Depending on your application and platform, you will have Analytics, Business Transactions, or both.
The visibility currently available differs from what you are familiar with. Every SAP application server is tightly coupled to a database and all code uses that database. The node that displays in the flow map includes the application server and database.
In ABAP, there is no specific protocol to access the database since it's tightly coupled. You can monitor the databases with database monitoring and view information but that information isn’t tied in with the flow map.
Also, you can’t do the instrumentation and inject your own code at runtime in ABAP like you can in Java; it can only be done at compile time. There are specific static implicit enhancement points where you can inject, typically at the beginning or end of a method.
Additionally, you can’t inject code at SQL execution since this is happening inside the SAP kernel rather than in ABAP.
Can I baseline specific RFCs?
Baselining is done on the complete Business Transaction, not the individual RFCs. However, if you configure a Business Transaction for a specific RFC, you will get a baseline of that RFC.
Where can I see which RFC was called?
This information is listed in the snapshot properties under the URL section.
Where does the SQL Statement data in Data Collectors come from?
This data comes directly from SQL traces on the SAP System or the Expensive Statement Trace on HANA (tcode DB02).