PHD tab

The PHD tab stores the settings used by the selected RFC Destination to retrieve performance history data, and contains a summary of the last set of data that was collected. Performance history data is downloaded from SAP tables used by the ST03 transaction, and for BW systems, from a selection of BW tables.

Performance history data may be retrieved using a LiveCompare remote function call, a native SAP remote function call, or from an External Data Source. These last two options may be used on SAP systems that do not have LiveCompare’s transports installed on them.

You can retrieve performance history data for an RFC Destination by using a schedule set in the PHD tab, or by using the Collect Performance History Data action. You can access retrieved performance history data in a workflow using the Read Performance History Data action.

The PHD tab has the following sections:

Cache

This 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.

Collection

This section allows you to specify how the LiveCompare retrieves performance history, and to set a schedule to specify when LiveCompare retrieves performance history data. It has the following fields:

Source

Use this list box to specify the source for the RFC Destination’s performance history data.

Select LiveCompare RFC to retrieve performance history data using a function provided by LiveCompare’s SAP components.
Select SAP Native RFC to retrieve performance history data using a native SAP function. The function called is specific to the RFC Destination’s SAP kernel release.
Select External Data Source to retrieve performance history data from the specified Performance History Data External Data Source.

If you select either LiveCompare RFC or SAP Native RFC, LiveCompare retrieves usage data for BSP Applications (including Fiori/UI5 BSP Applications) if you have configured this for the RFC Destination.

External Data Source

The PHD tab displays this list box if you select External Data Source in the Source section. Select the Performance History Data External Data Source to use as a source for the RFC Destination’s performance history data.

Schedule collection

Select this check box to schedule the retrieval of performance history data for this RFC Destination. If you don’t set a schedule, you can use the Collect Performance History Data action to retrieve performance history data for the RFC Destination. Note the check box is unavailable if you select External Data Source in the Source list box.

To set a schedule for the retrieval of Performance History Data, select the Schedule collection check box and complete the screen fields 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.

The Collection section displays the current date and time on the LiveCompare server.

If you set the OnlyAdminEditsRFCDest option in the Configuration - Security screen or during the installation of LiveCompare, only LiveCompare Administrators may update the fields in the PHD tab.

Save

Click Save to save the details in the Collection section.

Delete Cache

Click Delete Cache to delete the performance history data retrieved for this RFC Destination. LiveCompare displays a confirmation message box.

Performance history data classes

Internal class names stored in SAP’s performance history data are stored as classes (CLAS) in an RFC Destination’s PHD tab, using the external name of the class. If you have upgraded from an earlier release of LiveCompare, class-like programs (PROG) in any existing performance history databases populated using the ‘LiveCompare RFC’ option are automatically converted to classes (CLAS). These names are 32 characters long, with 0 or more equals signs followed by the characters CP.