topic Re: Warning message in Application Development and Automation Discussions

Warning message

former_member189354 — Thu, 12 May 2005 09:54:59 GMT

Hi,

Iam executing one of the userdefined report it many selection fields defined with select-options statments.

When Iam executing using F8 key it gives warnig message saying that selection was not restricted. Can any body help in this regard. Thanks in advance.

bye,

MSN.

Re: Warning message

Former Member — Thu, 12 May 2005 09:59:29 GMT

May be you have too many fields for selection and you are not entering KEY values, which means you are tryign to acess lot of data.

Rgds,

Manohar

Re: Warning message

Former Member — Thu, 12 May 2005 10:09:13 GMT

I guess it is just to warn you that the report can take a long time to run, because you do not restrict in the selection screen.

Re: Warning message

Former Member — Thu, 12 May 2005 10:41:21 GMT

Hi MSN,

This warning is to inform you that, as you have not restricted the selection of the data, the following consequences may apply:

1. The report will contain a large amount of data (potentially too much to be useful)

2. The report will be very slow to run (as it will most likely have to do table scans to access data rather than selecting using primary key indexes)

3. As a consequence of 2, it may timeout due to running too long and short dump giving you no result

4. Due to the large number of data to be selected, the execution of the report may affect the overall system performance as CPU time is dedicted to the database to perform the selection.

Thus, it is recommending that you fill in some of the selection criteria in order to minimise the risk of encountering problems 1 through 4.

Cheers,

Brad

Re: Warning message

former_member189354 — Thu, 12 May 2005 11:16:18 GMT

Hi,

This warning message comes after upgrading to the serice patch to server.

bye,

MSN.

Re: Warning message

Former Member — Thu, 12 May 2005 11:25:49 GMT

Thanks MSN,

So, with the latest service pack, SAP has introduced the warning message into the report code as this report must have been causing problems in some environments.

That makes sense.

If you are happy then please close the thread.

Cheers,

Brad