Program timed out in production system.

[Former Member]

I have one program . when functional consultant run the program , it was timed out at bseg selection. But when I run the same Program in production-giving out put as no data selected.

Could any body can tell me what was the reason.

THANKS.

[Former Member]

Did you and the consultant run with different selection criteria? It's hard to give an answer without seeing the code. Could you post it please?

Rob

[Former Member]

yes we ran in production - the same program with the same variant ( test data ), but functional consultant id is different and my log id is different .

Could you please tell why ???

[Former Member]

I can't tell you the exact reason without knowing the entire situation. But here's an idea:

It may have to do with authorizations. The program could be doing something like finding all cost centers that the user is authorized to look at. Then it may be looking for all CO documents for all of the cost centers and then the corresponding FI documents.

There may also be a bug in the program that causes the program to select <i>all</i> documents when the user is not authorized to look at <i>any</i> cost centers.

Rob

[Former Member]

Hi,

Also check if the program flow can be altered with user parameters.

Kind regards, Rob Dielemans

[Former Member]

Hi Sam,

As with the same variant two different id gives different result, I think the problem mt be related with user authorization. Check if there is some function module call for which one id doesn't have the proper authorization.

The best thiong is run the program in debug mode if possible and check step by step.

[Former Member]

It is difficult to pin point at the root cause unless we see the code..but from the query it seems that the difference is due to authorisation, where it is possible that you are not having requisite rights to select/update the data while your functional consultant does have the same.

As for time out, it is due to the fact that your select query from BSEG is taking lots of time thereby exceeding the runtime limit. The solution for that is to tune your ABAP so as to reduce the runtime.

Regards

Anurag

[Former Member]

As everyone said, its quite tedious to tell root cause of problem without seeing the code. The one could be....

1. Are you getting any values from BSEG based on authorization object and using the same into your <b>SELECT</b> query.

2. Check the Roles are the same for your User Id & Functional User id

3. If so, Enable the performance trace while running the program & analysis it. (Trans. <b>ST05</b>)

Regards,

Ramki.

[Former Member]

Hi,

This is not an authorisation issue.

Pls check yur code while accessing from the BSEG table.

Rgds

Mohit

[Former Member]

Hi Sam,

All the above is also the possible chances and also better check with the BSEG table by passing the same parameter that you are passing in select query and find.

[Former Member]

Sam,

It looks most probably due to Authorization please run SU53 after the execution of program it will give all failed/successfull authority objects .

Please check ur Profile and ur function guy profile .

Since it is timing out u need to check ur query using SE30 and do some analysis.

Ramvelu