cancel
Showing results for 
Search instead for 
Did you mean: 

RBPD results does not match the usage of transaction in the system

former_member184806
Participant
0 Kudos

Hi,

I have performed an RBPD analysis on a Solar01 project and have found many transactions which have been used in the managed system.

However there is a huge discrepancy between the number of usage we found in the RBPD analysis and the actual usage in the managed system

for example the transaction VA11 is shown to have been executed more than 80,000 times but there are less than 1000 Inquiry document in the system.

It is possible that not everytime the transaction VA11 is executed an Inquiry will be saved and also if there are multiple windows which are opened in VA11 that will also be counted. However still there is a huge difference between the numbers.

Also the EWA was not configured in the same Solution Manager in which I performed the RBPD. It was loaded from another Solution Manager. Can there be an issue while loading the data of EWA from another Solution Manager?

What can be the possible reason for such a huge discrepancy.

Regards,

Vishal

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Vishal,

you wrote "there is a huge discrepancy between the number of usage we found in the RBPD analysis and the actual usage in the managed system for example the transaction VA11 is shown to have been executed more than 80,000 times but there are less than 1000 Inquiry document in the system."

The workload statistics for transactions are taken over (e.g. via EWA) from transaction ST03N in the managed system. There you can find the same total numbers for the period and client analyzed. These usage data contain the number of dialog steps performed with regards to a certain transaction displayed and not the number of transaction executions. That might explain the discrepancy reported by you.

Best regards,

Andreas

former_member184806
Participant
0 Kudos

Hi Andreas,

We also checked in the ST03N and still there is a huge descrepancy between the two numbers. Also I would like to add that the EWA data has been loaded from another Solution Manager. The EWA report was not configured in this Solution Manager and the RBPD analysis was to be executed on this Solution Manager.

Also in every transaction there is a decreasing trend in the number of usage. Like for any transaction the usage in the month March is higer than than in Apr and similarly for Feb its much higer than Apr and it goes on that way for the previous months.

Regards,

Vishal

Former Member
0 Kudos

Hi Vishal,

in case you have detected a discrepancy between the ST03N data and the data used in RBPD Solution Documentation Assistant(SDA) analysis, I would recommend you to open a message on component SV-SMG-SDA and describe the differences detected and the activities performed with regards to the EWA data copy from another Solution Manager system.

In case that ST03N seems to be not accurate a message might be addressed to ST03N related component.

By the way, an SDA analysis can be performed in newer releases also with data retrieved directly from the managed system (e.g. if EWA is not configured) or with ST03N data collected in the BW.

Best regards,

Andreas

Former Member
0 Kudos

Hi Vishal,

UPL is based on kernal Exe hits, it is not actually based on any tables or EWA.  It actually counts number of times the methods, function modules got called .   You cant really compare the UPL value with any of these entries. more over UPL  count only objects, fm, methods usage

The object usage tab in RBPD is not exactly representing UPL. This get data from n number of sources. It brings the data from EWA ( for transactions from st03N ), e2e diagnosstics, upl ( for objects usage) and also rfc used in charm ( for badi and others).

refer here Display object usage

The link is totally different from UPL recording, refer here,  Objects recorded by UPL

this given clear statement that UPL is totally different provide more accurate data than other sources.

The case, why SAP broght UPL concept, is very simple, because regular workload stats will be counting only the direct calls, means it wont consider the calling by other programs, UPL is cross client, so its more accurate.

Hence the entries which is shown in Analysis project result is fine,

Thanks and Best regards,

Jansi

former_member184806
Participant
0 Kudos

Dear Jansi,

In my RBPD analysis there is only the EWA data available. There is no UPL or any other source of data.