UPL Raw and Summary Data
This topic describes how raw and summary data is collected by LiveCompare’s UPL function. The function retrieves a single file of UPL data from the specified SAP system, indicating the date when an executable was run, and its usage count for that day. For example:
| Date (YYYYMMDD) | Object | Count |
|---|---|---|
| 20140101 | FUNC1 | 5 |
| 20140101 | FUNC2 | 6 |
| 20140102 | FUNC1 | 2 |
| 20140102 | FUNC2 | 9 |
This means that FUNC1 ran 5 times on 20140101 and twice on 20140102. FUNC2 ran 6 times on 20140101 and 9 times on 20140102.
When LiveCompare reads this data, it is stored in the raw dataset as follows. The ‘months of data to keep’ setting in the RFC Destination’s UPL tab is converted to a date at the beginning of the month at the start of the period. For example, if the current date is 20140515 and the number of months of data to keep is 3, then the oldest date of the data to keep is 20140201.
When updating its UPL data, LiveCompare firstly deletes any old data from the raw dataset. Old data has a retrieval date that is older than what needs to be kept. It then adds any new data that it needs to. If the raw dataset already contains UPL data for a particular date, any SAP UPL data for that date is ignored.
After the raw dataset has been updated, LiveCompare deletes and then recreates the summary dataset. The summary dataset has a single entry for each object that the raw dataset has data for, including a sum of the SAP object’s ‘Count’ values. For the example above, the summary dataset would look like this:
| Object | Count |
|---|---|
| FUNC1 | 7 |
| FUNC2 | 15 |
The summary dataset will never contain more rows than the raw dataset.