Transaction steps using multiple systems
In a simple SAP ERP system, a transaction step usually consists of one action within a system. In a more complex system environment, a single transaction step can involve actions in multiple systems. Examples of these transactional steps include the following:
->Applications such as SAP NetWeaver Portal or Java Web Dynpro applications, in which the frontend communication takes place via SAP NetWeaver AS Java and the backend functionality is implemented via the AS ABAP
->Applications that involve two or more ABAP systems coupled via RFC, for example, sales transactions in the SAP ERP system that use the available-to-promise (ATP) function in SAP APO for availability checks
For all these cases, SAP NetWeaver technology enables you to carry out a cross-system workload analysis that links the performance statistics of the various components with each other.