Retrieve performance history data

If you have LiveCompare Administrator privileges, an RFC Destination’s PHD tab may be configured to retrieve performance history data from the associated SAP system. LiveCompare Editors may also configure RFC Destinations to retrieve performance history data if this has been permitted by your installation.

Retrieved performance history data includes used Programs (PROG), Transactions (TCOD), Remote Function Calls (FUNC), Web DYNPROs (WDYN) and SPROXREG Services (SPRX). Usage data for BSP Applications (WAPA) is retrieved if this has been configured for an RFC Destination. For BW systems, retrieved performance history data includes the following object types.

  • Composite Providers (HPCR)

  • Data Stores (Advanced) (ADSO)

  • Functions (FUNC)

  • InfoCubes (CUBE)

  • InfoObjects (IOBJ)

  • MultiProvider (MPRO)

  • ODS Objects (ODSO)

  • Queries (ELEM)

Performance history data retrieved for an RFC Destination may be accessed using the Read Performance History Data action in one or more workflows.

Performance history data retrieval methods

An RFC Destination’s PHD tab provides three ways of collecting performance history data.

LiveCompare RFC

This method uses a remote function provided with LiveCompare transports to read performance history data into a set of internal tables. It should be used for SAP systems where the LiveCompare’s SAP components have been installed.

SAP Native RFC

This method uses an SAP function call to retrieve performance history data. It does not require any LiveCompare RFCs, and may be used on SAP systems that do not have LiveCompare transports installed. For example, there may be a restriction on installing transports on a production system. Also, the use of the SAP HANA Migration Assessment app does not require LiveCompare’s SAP components to be installed.

External Data Source

This method obtains performance history data from an External Data Source of type ‘Performance History Data’. When creating the External Data source, one or more files downloaded from the SAP ST03N transaction may be specified. These are merged together, and the usage counts for transactions and programs are aggregated. An RFC Destination is also specified, which is used to classify object names as either programs or transactions.

This method does not require LiveCompare’s SAP components to be installed, and may be used in cases where performance history data has been obtained in one or more files downloaded from the SAP ST03N transaction.

Retrieve performance history data immediately

Use the Collect Performance History Data workflow to retrieve performance history data immediately.

Retrieve performance history data using a schedule

To retrieve performance history data for an RFC Destination using a schedule, carry out the following steps:

  1. Select an RFC Destination from the Administration/RFC Destinations folder in the LiveCompare hierarchy and click the PHD tab.
  2. Select a data retrieval method in the tab’s Source field. Note that the ‘External Data Source’ method does not allow you to set a schedule.
  3. Select the ‘Schedule collection’ check box.
  4. Complete the fields in the Scheduling section as follows:
Field What to do
Keep N months of data Enter a value (N) between 0 and 99 to specify how many months of data to retain. When the schedule runs, LiveCompare retrieves the most recent <N> months of performance history data, overwriting any previous performance history data stored for the RFC Destination.
Run at time on the first of every month Specify run time for the schedule. To ensure that performance history data for the previous month is available, set this field to a value other than 00:00.
  1. Click ‘Save’ to save the schedule. At the scheduled time, the performance history data is retrieved, any previous performance history data stored for the RFC Destination is overwritten.

Delete performance history data

To delete the performance history data retrieved for an RFC Destination, click ‘Delete Cache’ data in the RFC Destination’s PHD tab. A confirmation dialog is displayed.

Cache section

The PHD tab’s Cache section shows the number of rows of application and users statistics available for the RFC Destination, and the time and date when LiveCompare last retrieved performance history data.

The scheduling details and the performance history data retrieved in the PHD tab are associated with the RFC Destination, and not with a particular LiveCompare user. If a user updates or deletes the retrieved data or modifies the schedule, the changes will be reflected for all users who have access to the RFC Destination.

Edit RFC Destinations